Nicolas Garcia Romero

ACTIVITY 3 TASK SOFTWARE

 COCOMO

COCOMO are the initials of Constructive Cost Model, that basically is a model for estimating
effort, cost and schedule for software projects. The first version of this model was developed
by Barry W. Boehm in the late 1970s, and finally published in 1981 (due to this,the first
version of this model is also known as COCOMO 81)
 Levels

Is composed by three levels:

 Basic: Used for quick estimations. Little precise
 Intermediate: Similar to the basic model but adding attributes that can be used for an
estimation more detailed.
 Detailed: Similar to the intermediate model, but adding some improvements to be an
estimation more detailed
 COCOMO 2

This model basically is an updated version of the initial COCOMO. This updated version is
published and used mainly from the 1990, and is adapted to the current life cycle of software
development models, because this updated model is applicable to quick development of
applications, re-engineering, object oriented programming, nonsequential applications, etc.
 Characteristics

 It is a tool based on lines of code which makes it very powerful for estimating costs and
not like others that only measure effort based on size.
 It’s the most extensive empirical model for software estimation.
 Cocomo counts with automatic tools for estimate costs based like Costar and Cocomo81.
 Models

COCOMO 2 is composed by 3 different models, which are:

 Composition of the application model: Generally used for projects developed with
modern GUI tools.
 Pre-architecture model: Used to obtain strong estimations about costs and time, before
determine the architecture of the project.
 Post-architecture model: It is the more detailed model, and generally is used after the
architecture of the project has been developed.
 Accommodating Progression

 Three-level model that allows increasingly detailed estimates to be prepared as development progresses.

Early prototyping level

 Based on “object points”
 Simple formula
Early design level
 Based on “function points” that are then
 translated to lines of source code (LOC)
Post-architecture level
 Estimates based on LOC
 Early Prototyping Level

 Supports prototyping projects and projects where there is extensive reuse.

 Estimates effort in object points/staff month

 PM = ( NOP × (1 - %reuse/100 ) ) / PROD, where:

 PM is the effort in person-months
 NOP is the number of object points
 PROD is the productivity
 Early Design Level

 Estimates made after requirements confirmed

Where:
 A = 2.5 in initial calibration
 Size in KLOC
 B varies from 1.1 to 1.24 depending on novelty of
 project, development flexibility, risk management
 approaches, and process maturity
 EM = (ASLOC × (AT / 100) ) / ATPROD
 M = PERS × RCPX × RUSE × PDIF × PREX × FCIL ×
 SCED
 Multipliers

Multipliers reflect capability of developers, nonfunctional requirements, familiarity with

development platform, etc.
 RCPX - product reliability and complexity
 RUSE - the reuse required
 PDIF - platform difficulty
 PREX - personnel experience
 PERS - personnel capability
 SCED - required schedule
 FCIL - the team support facilities
 Post-Architecture Level

 Uses same formula as early design estimates

 Estimate of size adjusted to account for:
 Requirement's volatility
 Rework required to support change
 Extent of possible reuse
ESLOC = ASLOC x (AA + SU +0.4DM + 0.3CM + 0.3IM) / 100
 ESLOC is equivalent number of lines of new code
 ASLOC is the adjusted number of lines of reusable code which must be modified
 DM is the % of design modified
 CM is the % of the code that is modified
 IM is the % of the original integration effort required for integrating the reused software
 SU is a factor based on the cost of software understanding
 AA is a factor which reflects the initial assessment costs of deciding if software may be
reused
 Factors

COCOMO 2 model includes a new concept, which is the scale factors, which are:
 PREC: Related to previous similar developments
 FLEX: Related to the flexibility of the development
 RESL: Related to the management of risks and the architecture
 EAM: Related to the cohesion of the development team
 EPML: Related to a maturity level
 Bibliography

 Bohner, S. (n.d.). Csse 372 Software Project Management: Software Estimation With
Cocomo-II.