COCOMO COST

MODELLING
 Introduction
 Projects Categorization
 Types Of COCOMO Model And Their Examples
 Introduction To Quality Management And Configuration Management
Introduction

− Stands for Constructive Cost Model.

− Used to estimate the cost of the projects.

− The Constructive Cost Model (COCOMO) is an algorithmic software cost

estimation model developed by Barry Boehm in the year 1981.

− Using this model we can estimate the time and no of people needed to
develop a project.
Projects Categorization

− Projects are categorized into three types:

1. Organic (Small Team + Good experience)

2. Semidetached (Medium Team + Mixed Experience )

3. Embedded (Combination of organic and semidetached)

Types Of COCOMO Model And Their Examples

− According to Boehm, software cost estimation should be done through three

stages

 Basic COCOMO Model

 Intermediate COCOMO Model

 Detailed COCOMO Model

Basic COCOMO Model

− It gives an approximate estimate of the project parameters, it means it predict the

effort and cost of the project.

− The following formula is used to estimate the cost in this model.

Effort (E) = a * (KLOC)b  PM

Development Time (D) = c * (efforts)d  Months
People Required = E / D

 KLOC = Kilo Lines of Code

 a1,a2,b1,b2 are constants for each group of software products
 PM =  person months
Example

S/W Projects A b c d

Organic
2.4 1.05 2.5 0.38

Semi Detached
3.0 1.12 2.5 0.35

Embedded
3.6 1.20 2.5 0.32
Estimation of development effort

Organic: Effort = 2.4 * (KLOC)1.05 PM

Semi-detached: Effort = 3.0 * (KLOC)1.12 PM

Embedded: Effort = 3.6 * (KLOC)1.20 PM

Estimation of development time

Organic: Effort = 2.5 * (Effort)0.38 Months

Semi-detached: Effort = 2.5 * (Effort)0.35 Months

Embedded: Effort = 2.5 * (Effort)0.32 Months

Intermediate COCOMO Model

− Extension of Basic COCOMO Model.

− Some constants calculated according to the various software systems.

− It uses 15 cost drivers.

Intermediate COCOMO equation:

                
E = ( ai (KLOC)bi ) * EAF
 EAF (Effort Adjustment Factor)
 Value calculated from 15 cost drivers.
Example

Software projects a b

Organic 3.2 1.05

Semi Detached 3.0 1.12

Embeddedc 2.8 1.20

Detailed COCOMO Model

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
Introduction To Quality Management And
Configuration Management Of Software
Software Quality Management
− It ensures that the required level of quality is achieved by submitting
improvements to the product development process.

− SQA aims to develop a culture within the team and it is seen as everyone's
responsibility.

− Software Quality management should be independent of project management

to ensure independence of cost and schedule adherences.

− It directly affects the process quality and indirectly affects the product quality.
Activities of Software Quality Management:
•Quality Assurance - QA aims at developing Organizational procedures and standards for
quality at Organizational level.

•Quality Planning - Select applicable procedures and standards for a particular project and
modify as required to develop a quality plan.

•Quality Control - Ensure that best practices and standards are followed by the software
development team to produce quality products.
 Software Configuration Management(SCM)

− SCM is a process to systematically manage, organize, and control the changes in

the documents, codes, and other entities during the Software Development Life
Cycle. 

−  Goal is to increase productivity with minimal mistakes.

Tasks in SCM process

− Configuration Identification
− Baselines
− Change Control
− Configuration Status Accounting
− Configuration Audits and Reviews