Software phases effort

Calculating the size of project is the foremost logical step to be taken in order to estimate the effort. If we do not know the distance to be travelled we can not estimate the cost and duration per mileage. Therefore we also first measure the size of the entire project.

Offer does not apply to e-Collections and exclusions of select titles may apply. Offer expires June 30, Browse Titles. Add to Cart. Instant access upon order completion. Free Content. More Information. Safavi, S.

Al-Bastaki Ed. IGI Global. Latif Al-Bastaki, Available In. DOI: Current Special Offers. No Current Special Offers. This risk can affect four out of a total five phases of the software development life cycle i. Analysis, Design, Coding and Testing.

Hence targeting this risk alone may reduce the overall risk impact of the project by fifty percent.

Architectural designing of the system is a great activity which consumes most of the time in SDLC. More specifically, our goal is twofold. At any given point in the software development lifecycle, we estimate the effort needed for the next phase. Also, we estimate the effort for the remaining part of the software development process.

The results show a set of statistically significant correlations between: 1 the effort spent in one phase and the effort spent in the following one, 2 the effort spent in a phase and the remaining effort, 3 the cumulative effort up to the current phase and the remaining effort. However, the results also show that these estimation models come with different degrees of goodness of fit. Finally, including further information, such as the functional size, does not significantly improve estimation quality.

Article :.