Open In App

Early Design Model : COCOMO-II

Last Updated : 28 Sep, 2020
Improve
Improve
Like Article
Like
Save
Share
Report

It is used at the Stage – II in COCOMO -II models and supports estimation in early design stage of project. Base equation used in COCOMO – II models is as follows –

PMnominal = A * (size)B 
where PMnominal = Effort for the project in person months
A = constant representing the nominal productivity where A = 2.5
B = Scale Factor
Size = size of the Software

The early design model uses Unadjusted Function Points (UFP) as measure of size. This model is used at the early stages of software project when there is not enough information available about size of product which has t be developed, nature of target platform and nature of employees to be involved in development of projector detailed specifications of process to be used. This model can be used in either Application Generator, System Integration, or Infrastructure Development Sector.

If B = 1.0, there is linear relationship between effort and size of product. If the value of B is not equal to 1, there will be non-linear relationship between size of product and effort. If B < 1.0, rate of increase of effort decreases as the size of product increases. If B > 1.0, rate of increase of effort increase as the size of product is increased.

This is due to growth of interpersonal communications and overheads due to growth of large system integration. Application composition model assumes value of B equal to 1. But Early Design Model assumes value of B to be greater than 1.

Thus here the basic assumption stands as effort on project usually increases faster than size of product. However, value of ‘B’ is computed on basis of scaling factors that may cause loss of productivity corresponding to an increase in the size as follows –

  1. Precedentness :
    It reflects the experience on similar projects previously. This is applicable to individuals as well as organizations both in terms of expertise and experience. High value would imply that organization is quite familiar with application formula and very low value means no previous experience or expertise. The value for scale factor is 6.20(Very Low), 4.96(Low), 3.72(Average), 2.48(High), 1.25(Very High) and 0.00(Extra High).

  2. Development Flexibility :
    It reflects degree of flexibility in development process. Low value would imply well defined process being used. Very high value would imply that the client offers very general idea of the product or project. Value for the scale factor is 5.07(Very Low), 4.05(Low), 3.04(Average), 2.03(High), 1.02(Very High) and 0.00(Extra High).

  3. Architecture Risk and Resolution :
    It represents degree of risk analysis being carried out during course of project. Low value would indicate little analysis and very high value would represent complete and thorough risk analysis. Value for the scale factor is 7.07(Very Low), 5.65(Low), 4.24(Average), 2.83(High), 1.41(Very High) and 0.00(Extra High).

  4. Team Cohesion :
    Reflects the team management skills of the employees developing the project. Very low value would imply very low interaction and hardly any relationship among the members however high value would imply great relationship and good team work. The value for scale factor is 5.48(Very Low), 4.38(Low), 3.29(Average), 2.19(High), 1.10(Very High) and 0.00(Extra High).

  5. Process maturity :
    Reflects process maturity of organization. Very low value would imply organization has no level at all and high value would imply that organization is rated as highest level of the SEI-CMM. The value for scale factor is 7.80(Very Low), 6.24(Low), 4.68(Average), 3.12(High), 1.56(Very High) and 0.00(Extra High).
The value of B can be calculated as -
B = 0.91 + 0.01 * (Sum of rating scaling factors for project)

When all scaling factors of project are rated as extra high, best value of B is obtained which is equal to 0.91.

When all scaling factors are very low worst case values of B is obtained as 1.23.

Hence value of B varies from 0.91 to 1.23.


Similar Reads

Difference between COCOMO 1 and COCOMO 2
COCOMO 1 Model: The Constructive Cost Model was first developed by Barry W. Boehm. The model is for estimating effort, cost, and schedule for software projects. It is also called as Basic COCOMO. This model is used to give an approximate estimate of the various parameters of the project. Example of projects based on this model is business system, p
2 min read
Advantages &amp; Disadvantages of COCOMO Model
Overview :Cocomo stands for Constructive Cost Model is a regression model based on LOC, i.e number of Lines of Code. COCOMO model is proposed by Boehm in 1981 It is a procedural cost estimate model for software projects and often used as a process of reliably predicting the various parameters related to making a project such as size, effort, cost,
3 min read
Difference Between Organic, Semi-Detached and Embedded Modes in COCOMO Model
Pre-requisites: COCOMO Model Software is a program or set of programs containing instructions that provide desired functionality. And Engineering is the process of designing and building something that serves a particular purpose and finds a cost-effective solution to problems. Cocomo (Constructive Cost Model) is a regression model based on LOC, i.
2 min read
Differences Between the Basic, Intermediate, and Detailed COCOMO Model
In the realm of software engineering, the Construction Cost Model (COCOMO) is a significant technique for estimating software costs that has been used for many years. To estimate the time, effort, and resources needed for software development to be successful, COCOMO offers an organized method. For better decision-making, enhanced project planning,
4 min read
COCOMO Model-Software Engineering
COCOMO-II is the revised version of the original Cocomo (Constructive Cost Model) and was developed at the University of Southern California. It is the model that allows one to estimate the cost, effort, and schedule when planning a new software development activity. Sub-Models of COCOMO Model[caption width="800"]COCOMO Sub-models[/caption]1. End U
2 min read
Application Composition Estimation Model (COCOMO II | Stage 1) - Software Engineering
Application Composition Estimation Model allows one to estimate the cost, and effort at stage 1 of the COCOMO II Model. In this model, size is first estimated using Object Points. Object Points are easy to identify and count. Object Points define screen, reports, and third-generation (3GL) modules as objects. Object Point estimation is a new size e
4 min read
COCOMO Model - Software Engineering
Cocomo (Constructive Cost Model) is a regression model based on LOC, i.e., the number of Lines of Code. This article focuses on discussing the Cocomo Model in detail. Table of Content What is the Cocomo Model?Detailed Structure of COCOMO ModelImportance of the COCOMO ModelTypes of COCOMO ModelCASE Studies and ExamplesAdvantages of the COCOMO ModelD
12 min read
Difference between Waterfall model and Incremental model
Waterfall Model is also known as Classical/Traditional Model. Sometimes It is referred as linear-sequential life cycle model because all phases involve in this model completed one by one in linear fashion. In this model, we get software after completion of all coding phase. This model is basically used for small projects. There exist only one cycle
3 min read
Difference between Agile Model and V-Model
Agile Model: Agile Model is the software development model in which the development and testing process carries on simultaneously. In this model, both development-related processes and testing-related processes are parallel. This model provides the facility for more interaction between the development team, testing team, and end-users. V-Model: V-M
2 min read
Difference between Prototype Model and Spiral Model
A risk-driven model of the software development process is the spiral model. The spiral model directs a team to adopt components of one or more process models, such as incremental, waterfall, or evolutionary prototyping, based on the specific risk patterns of a given project. The client reviews the progress at the conclusion of each phase in the sp
5 min read
Article Tags :