cocomo model in software engineering tutorial point

In this step, you will need to break your software into smaller components and functions and you can categorize them to a different set of elements, this is similar to work breakdown structure but only for the software components not all the working activities for the software. You can always list your assumptions to justify the outcome of the estimation process and its results. You can read this article to understand what is the scope and how it is different from the requirements specifications. While in most cases you will have a defined scope to start with. You need first to scope the project even if you do not have the full detailed requirements but you can assume some of them or add margins later. The Estimation ProcessĪs mentioned the estimation is a process and this process contains the following steps to reach the estimate, this process is cycling until you reach the final estimate for the project. Moreover, not all software project is time and material contracts, some of them are fixed cost projects and this estimate will be used as a foundation to negotiate the project cost. The estimation is important because it gives the project team some confidence about the required effort and time to plan ahead for the project.

The estimation is a process to find the most accurate sizing figure for the software project effort, for example, how many months you will need to develop the software, how many resources you will need to finish the project in the required time. What is Estimation and why it is important? In this article, I will illustrate how to easily estimate the software effort using known estimation techniques which are Function Points Analysis (FPA) and Constructive Cost Model (COCOMO).

The software development effort estimation is an essential activity before any software project initiation.

Cocomo model in software engineering tutorial point