The COCOMO model estimates software development effort and schedule based on project size and complexity. It consists of basic, intermediate, and detailed forms. The basic model uses lines of code to estimate effort and schedule. The intermediate model refines estimates using 15 cost drivers rated on a scale. The detailed model divides a project into modules and applies cost drivers to different development phases.
The COCOMO model estimates software development effort and schedule based on project size and complexity. It consists of basic, intermediate, and detailed forms. The basic model uses lines of code to estimate effort and schedule. The intermediate model refines estimates using 15 cost drivers rated on a scale. The detailed model divides a project into modules and applies cost drivers to different development phases.
The COCOMO model estimates software development effort and schedule based on project size and complexity. It consists of basic, intermediate, and detailed forms. The basic model uses lines of code to estimate effort and schedule. The intermediate model refines estimates using 15 cost drivers rated on a scale. The detailed model divides a project into modules and applies cost drivers to different development phases.
The COCOMO model estimates software development effort and schedule based on project size and complexity. It consists of basic, intermediate, and detailed forms. The basic model uses lines of code to estimate effort and schedule. The intermediate model refines estimates using 15 cost drivers rated on a scale. The detailed model divides a project into modules and applies cost drivers to different development phases.
Download as PPTX, PDF, TXT or read online from Scribd
Download as pptx, pdf, or txt
You are on page 1of 19
COCOMO MODEL
• COCOMO stands for “CONSTRUCTIVE COST MODEL”.
COCOMO is one of the most widely used software estimation
models in the world. COCOMO Model was proposed by BARRY BOEHM in the year 1981. COCOMO predicts the effort and schedule for a software product development based on inputs relating to the size of the software and a number of cost drivers that affect productivity • COCOMO Model is applied on 3 classes of Software Project.
1- Organic 2- Semi – Detached 3- Embedded • COCOMO Model is applied on 3 classes of Software Project.
1- Organic 2- Semi – Detached 3- Embedded
Boehm’s definition of organic, semidetached, and embedded systems:
: • Organic – A software project is said to be an organic type if the team size required is adequately small, the problem is well understood and has been solved in the past and also the team members have a nominal experience regarding the problem. • Semi-detached – A software project is said to be a Semi-detached type if the vital characteristics such as team size, experience, knowledge of the various programming environment lie in between that of organic and Embedded. The projects classified as Semi- Detached are comparatively less familiar and difficult to develop compared to the organic ones and require more experience and better guidance and creativity. Eg: Compilers or different Embedded Systems can be considered of Semi-Detached type. • Embedded – A software project requiring the highest level of complexity, creativity, and experience requirement fall under this category. Such software requires a larger team size than the other two models and also the developers need to be sufficiently experienced and creative to develop such complex models. • Types of Models: COCOMO consists of a hierarchy of three increasingly detailed and accurate forms. Any of the three forms can be adopted according to our requirements. These are types of COCOMO model:
1.Basic COCOMO Model
2.Intermediate COCOMO Model 3.Detailed COCOMO Model Basic COCOMO can be used for quick and slightly rough calculations of Software Costs. Its accuracy is somewhat restricted due to the absence of sufficient factor considerations. Software development effort is estimated using LOC(Lines of Code).
- Efforts Applied (E) =
- Development Time(D) = - Person Required (P) = Efforts Applied(E) / Development Time(D) The above formula is used for the cost estimation of for the basic COCOMO model where E (efforts applied) in person month( P M ). D(development time) in month( M ). • The constant values a, b, c and d for the Basic Model for the different categories of system: INTERMEDIATE MODEL • It is extension of Basic COCOMO Model. • It refines estimate Obtained by Basic COCOMO. • Efforts Applied (E) = • It refines estimate by using a set of 15 cost drivers. The values of a and b in case of the intermediate model are as follows: 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 The project manager is to rate these 15 different parameters for a particular project on a scale of one to three. Then, depending on these ratings, appropriate cost driver values are taken from the above table. These 15 values are then multiplied to calculate the EAF (Effort Adjustment Factor). The Intermediate COCOMO formula now takes the form: Detailed Model – Detailed COCOMO incorporates all characteristics of the intermediate version with an assessment of the cost driver’s impact on each step of the software engineering process. 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: 1. Planning and requirements 2. System design 3. Detailed design 4. Module code and test 5. Integration and test 6. 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.