Classification of Cost Drivers and their attributes: i Product attributes — Required software reliability extent Size of the application database The complexity of the product ii Hardware attributes — Run-time performance constraints Memory constraints The volatility of the virtual machine environment Required turnabout time iii Personnel attributes — Analyst capability Software engineering capability Applications experience Virtual machine experience Programming language experience iv Project attributes — Use of software tools Application of software engineering methods Required development schedule ; Cost Drivers Very Low Low Nominal High Very High Product Attributes Required Software Reliability 0.
The detailed model uses different effort multipliers for each cost driver attribute. In detailed cocomo, the whole software is divided into different modules and then we apply COCOMO in different modules to estimate effort and then sum the effort. The Six phases of detailed COCOMO are: Planning and requirements System design Detailed design Module code and test Integration and test Cost Constructive model The effort is calculated as a function of program size and a set of cost drivers are given according to each phase of the software lifecycle.
Prev Next. More topics on Software Engineering. Email We respect our user's data, your email will remain confidential with us. Subscribe to Our Newsletter. Software Engineeri Software Engineering Couplin Software Engineering Project Software Engineering System Software Engineering Require Software Engineering Classic This model depends on the number of lines of code for software product development. It was developed by a software engineer Barry Boehm in The COCOMO estimates the cost for software product development in terms of effort resources required to complete the project work and schedule time required to complete the project work based on the size of the software product.
It estimates the required number of Man-Months MM for the full development of software products. Such as:. This project having a high level of complexity with a large team size by considering all sets of parameters software, hardware and operational. It is the one type of static model to estimates software development effort quickly and roughly. The estimated effort and scheduled time for the project are given by the relation:.
Calculate the Effort, Scheduled time for development. Also, calculate the Average resource size and Productivity of the software for Organic project type. Effort is the total effort required to develop the software product, expressed in person months PMs. For the three classes of software products, the formulas for estimating the effort based on the code size are shown below:.
For the three classes of software products, the formulas for estimating the development time based on the effort are given below:. Some insight into the basic COCOMO model can be obtained by plotting the estimated characteristics for different software sizes. Fig shows a plot of estimated effort versus product size. From fig, we can observe that the effort is somewhat superliner in the size of the software product.
Thus, the effort required to develop a product increases very rapidly with project size. The development time versus the product size in KLOC is plotted in fig. From fig it can be observed that the development time is a sub linear function of the size of the product, i.
This can be explained by the fact that for larger products, a larger number of activities which can be carried out concurrently can be identified. The parallel activities can be carried out simultaneously by the engineers. This reduces the time to complete the project. Further, from fig, it can be observed that the development time is roughly the same for all three categories of products.
For example, a 60 KLOC program can be developed in approximately 18 months, regardless of whether it is of organic, semidetached, or embedded type.
From the effort estimation, the project cost can be obtained by multiplying the required effort by the manpower cost per month. But, implicit in this project cost computation is the assumption that the entire project cost is incurred on account of the manpower cost alone. In addition to manpower cost, a project would incur costs due to hardware and software required for the project and the company overheads for administration, office space, etc.
It is important to note that the effort and the duration estimations obtained using the COCOMO model are called a nominal effort estimate and nominal duration estimate.
The term nominal implies that if anyone tries to complete the project in a time shorter than the estimated duration, then the cost will increase drastically. But, if anyone completes the project over a longer period of time than the estimated, then there is almost no decrease in the estimated cost value. Calculate the effort and development time for each of the three model i. Software development team has average experience on similar type of projects.
The project schedule is not very tight. Calculate the Effort, development time, average staff size, and productivity of the project.
0コメント