3 replies
by dc_guy
Well, since no gurus have popped up to help you, I'll share what I know after several years of teaching software project management. (I assume that project estimation is what you're talking about.)
Arguably the three most-used project estimating techniques are top-down, bottom-up, and parametric.
Top-down is simply the project manager using his own experience (and perhaps his notes and records) on prior projects to estimate the project labor and schedule (and other costs if there's more involved than simply creating software, which is highly labor-intensive) for this project. Where would security and privacy figure in his point of view? If security and privacy are requirements issues, e.g. the application to be built must guarantee a given level of security and privacy), they just affect his ideas of how much work will be needed.
Bottom-up is the same thing, but done by the engineers rather than a manager. Security and privacy have the same impact on them: more requirements to fulfil mean more work. Typically the engineers won't think of some things the manager will, and vice versa. They complement each other well.
A parametric estimate is based on an estimate of the size of the software in Function Points, using labor-per-Function-Point statistics from previous, similar projects. In a shop with a reasonable level of discipline and repeatability, parametric is often more accurate than top-down and bottom-up. Again, security and privacy affect tje estimate only insofar as they result in more requirements, or in more difficult requirements.
Hope this has helped.
by sridharpandu
by vipinkailas
This discussion is closed to new replies.
Trending IT Employment posts
Sort by Trending