MAHARASHTRA STATE BOARD OF
TECHNICAL EDUCATION.
NAVJEEVAN EDUCATION SOCIETY’S
POLYTECHNIC BHANDUP(W)
MICROPROJECT:
COCOMO MODEL
Academic year: 2023-2024
Subject:- Software
Engineering (22413)
MAHARASHTRA STATE BOARD OF TECHNICAL
EDUCATION CERTIFICE
This is to certify that Mr. Samyak, Divyam, Himansu
Roll no:- 434,435,436 of forth semester of diploma in Information
Technology of institute , NAVJEEVAN polytechnic (code:0144) has
completed the micro project satisfactorily in subject Software
Engineering (SEN)For the academic year 2022 to 2023 as prescribed in
the curriculum.
Place: Bhandup Enrollment no: 2101440211
2101440212
2101440213
Date: Exam seat:
Subject Teacher Head of department Principal
Navjeevan Education Society’s
Polytechnic
TITLE:
COCOMO MODEL
PROGRAM COURSE: -
SECOND YEAR INFORMATION
TECHNOLOGY
ACADEMIC YEAR: 2023–2024
HELPED AND GUIDED BY:
Mrs.
GROUP ROLL NO ENROLLMENT
MEMBERS NO
Samyak 434 2101440211
Gaikwad
Divyam 435 2101440212
Singh
Himansu 436 2101440213
Pedini
3.0 ACTION PLAN
Sr. Details of activity Planned Planned Name of
No start date finish responsible
date term member
1. Discussion for the selection All members
of micro project
2. Finalization of topic for All
micro project members
3. Discussion on project topic All members
4. Collection of information All
members
5. Discussion on important All members
points for part A
Prepare part A format All
6. members
7. Discussion on important All members
points for part B
8. Prepare part B format All
members
9. Final submission All
members
4.0 RESOURCES USED
Sr. Name of Specification Quantity Remark
no resources
[Link]
1 Website [Link] - -
2 Book Software - -
Engineering
Software
PART-A
COCOMO MODEL
INTRODUCTION
Cocomo (Constructive Cost Model) is a regression model based on
LOC,
i.e number of Lines of Code. It is a procedural cost estimate
model for software projects and is often used as a process of
reliably predicting thevarious parameters associated with
making a project such as size, effort,cost, time, and quality. It
was proposed by Barry Boehm in 1981 and is based on the
study of 63 projects, which makes it one of the best-
documented models.
The key parameters which define the quality of any software
products, whichare also an outcome of the Cocomo are primarily
Effort & Schedule:
Effort: Amount of labor that will be required to complete
a task. It ismeasured in person-months units.
Schedule: Simply means the amount of time required
for the completion of the job, which is, of course,
proportional to the effortput in. It is measured in the
units of time such as weeks, months.
Different models of Cocomo have been proposed to predict the
cost estimation at different levels, based on the amount of
accuracy and correctness required. All of these models can be
applied to a variety of projects, whose characteristics determine
the value of constant to be used insubsequent calculations.
These characteristics pertaining to different systemtypes are
mentioned below.
Boehm’s definition of organic, semidetached, and embedded systems:
1. Organic – A software project is said to be an organic
type if theteam 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.
2. Semi-detached – A software project is said to be a
Semi-detachedtype 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.
3. 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 othertwo models
and also the developers need to be sufficiently
experienced and creative to develop such complex
models.
All the above system types utilize different values of the
constantsused in Effort Calculations.
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 Mode
3. Detailed COCOMO Model
The first level, Basic COCOMO can be used for quick and slightly
rough calculations of Software Costs. Its accuracy is somewhat
restricted due tothe absence of sufficient factor considerations.
Intermediate COCOMO takes these Cost Drivers into account
and DetailedCOCOMO additionally accounts for the influence of
individual project phases, i.e in case of Detailed it accounts for
both these cost drivers and also calculations are performed
phase-wise henceforth producing a more accurate result. These
two models are further discussed below
.
Estimation of Effort: Calculations –
1. Basic Model –
The above formula is used for the cost estimation of for
the basic COCOMO model, and also is used in the
subsequent models. Theconstant values a,b,c and d for
the Basic Model for the different categories of system:
The effort is measured in Person-Months and as evident
from theformula is dependent on Kilo-Lines of code.
The development time is measured in months.
These formulas are used as such in the Basic Model
calculations,as not much consideration of different
factors such as reliability, expertise is taken into
account, henceforth the estimate is rough.
Below is the C++ program for Basic COCOMO
// C++ program to implement basic COCOMO
#include<bits/stdc++.h>
using namespace std;
// Function for rounding off float to int
int fround(float x)
{
int a; x=x+0.5;
a=x;
return(a);
}
// Function to calculate parameters of Basic COCOMO
void calculate(float table[][4], int n,char mode[][15], int size)
{
float effort,time,staff;
int model;
// Check the mode according to size
if(size>=2 && size<=50) model=0; //organic
else if(size>50 && size<=300) model=1; //semi-detached
else if(size>300)
model=2; //embedded cout<<"The mode is
"<<mode[model];
// Calculate Effort
effort = table[model][0]*pow(size,table[model][1]);
// Calculate Time
time = table[model][2]*pow(effort,table[model][3]);
//Calculate Persons Required staff = effort/time;
// Output the values calculated cout<<"\nEffort = "<<effort<<"
Person-Month";
cout<<"\nDevelopment Time = "<<time<<" Months";
cout<<"\nAverage Staff Required = "<<fround(staff)<<"
Persons";
int main()
{
float
table[3][4]={2.4,1.05,2.5,0.38,3.0,1.12,2.5,0.35,3.6,1.20,2.5,0.32}
;
char mode[][15]={"Organic","Semi-Detached","Embedded"};
int size = 4; calculate(table,3,mode,size);
return 0;
}
Output:
The mode is Organic
Effort = 10.289 Person-Month Development Time = 6.06237
Months Average Staff Required = 2 Persons
2. Intermediate Model –
The basic Cocomo model assumes that the effort is only a
function of the number of lines of code and some constants
evaluated according to the different software systems. However,
in reality, no system’s effort and schedule can be solely
calculated on the basis of Lines of Code. For that, various other
factors such as reliability, experience, Capability. These factors
are known as Cost Drivers and the Intermediate Model utilizes
15 such drivers for cost estimation.
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 particularproject 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).
Difference between COCOMO 1 and COCOMO 2:
COCOMO I COCOMO II
COCOMO II is useful in non-sequential,
COCOMO I is useful in the waterfall rapid development and reuse models of
models of the software development software.
cycle.
It provides estimates of effort and It provides estimates that represent one
schedule. standard deviation around the most likely
estimate.
This model is based upon the linear This model is based upon the non linear
reuse formula. reuse formula
This model is also based upon the This model is also based upon reuse model
assumption of reasonably stable which looks at effort needed to understand and
requirements. estimate.
Effort equation’s exponent is
determined by 3 development Effort equation’s exponent is determined by
modes. 5 scale factors.
Development begins with the
requirements assigned to the
software. It follows a spiral type of development.
Number of submodels in COCOMO Iis In COCOMO II, Number of submodel are 4
3 and 15 cost drivers are assigned and 17 cost drivers are assigned
Size of software stated in terms of Size of software stated in terms of Objectpoints,
Lines of code function points and lines of code
Advantages and Disadvantage of cocomo model:
Advantages :
It works on historical data and provides more accurate details.
Easy to implement with various factors. One can easily
understandhow it works.
Easy to estimate the total cost of the project.
The drivers are very helpful to understand the impact
of thedifferent factors that affect project crises.
Disadvantages :
It ignores the hardware issues as well as the personal
turnoverlevel.
It ignores all the documentation and requirements.
It mostly depends on time factors.
It limits the accuracy of software costs.
It oversimplifies the impact of safety or security aspects.
It also ignores customer skills, cooperation, and knowledge.
CONCLUSION:
Software cost estimation is an important part of the
software development process. The COCOMO suite
(COCOMO II model and its extensions) offers a powerful
instrument to predict software costs. Unfortunately not all
of the extensions are already calibrated and therefore still
experimental. Only the Post-Architecure model is
implemented in a calibrated software tool. Despite this
disadvantage the COCOMO II suite helps managing
software projects. It supports process improvement
analyses, tool purchases, architecture changes, component
make/buy tradeoffs and decision making process with
credible results. Many endeavours were done to measure
up to the changes in software life cycles, technologies,
components, tools, notations and organizational cultures
since the first version of COCOMO (COCOMOI, COCOMO
81).
Micro Project Evaluation Sheet
Name of Student: Samyak
Enrollment No: 2101440211
Name of Program: Information Technology
Semester: IV.
Course Title: Software Engineering
Course Code: (22413)
Title of Micro Project: COCOMO MODEL
Course Outcomes Achieved:
Sr. Characteristic to Poor Average Good Excellent Sub
No. be assessed (Marks 1-3) (Marks 4 -5) (Marks 6-8) (Marks 9-10) Total
( A)Process and Product Assessment(Convert above total marks out of 6 marks. )
1. Relevance to the
Course
2. Literature
Review/information
collection
3. Completion of the
target as per
project proposal
4. Analysis ofdata and
representation
5. Quality of
Prototype/Model
6. Report
Preparation.
( B) Individual Presentation/Viva (Convert above marks Total Marks out of 4)
7. Presentation
8. Viva
(A) (B) Total Marks 10
Process and Product Individual
Assessment (6 marks) Presentation/Viva(4 marks)
Comments/Suggestions about team work, leadership/inter-personal communication
………………………………………………………………………………………
……………………………………… ……………………………………………….
Name and designation of the Teacher: Mrs.
Dated Signature ……………………………………………
VIII
Micro Project Evaluation Sheet
Name of Student: Divyam
Enrollment No: 2101440212
Name of Program: Information Technology
Semester: [Link] Title: Software Engineering
Course Code: (22413)
Title of Micro Project: COCOMO MODEL
Course Outcomes Achieved:
Sr. Characteristic to Poor Average Good Excellent Sub
No. be assessed (Marks 1-3) (Marks 4 -5) (Marks 6-8) (Marks 9-10) Total
( A)Process and Product Assessment(Convert above total marks out of 6 marks. )
1. Relevance to the
Course
2. Literature
Review/information
collection
3. Completion of the
target as per
project proposal
4. Analysis ofdata and
representation
5. Quality of
Prototype/Model
6. Report
Preparation.
( B) Individual Presentation/Viva (Convert above marks Total Marks out of 4)
7. Presentation
8. Viva
(A) (B) Total Marks 10
Process and Product Individual
Assessment (6 marks) Presentation/Viva(4 marks)
Comments/Suggestions about team work, leadership/inter-personal communication
………………………………………………………………………………………
……………………………………… ……………………………………………….
Name and designation of the Teacher: Mrs.
Dated Signature ……………………………………………
IX
Micro Project Evaluation Sheet
Name of Student: Himansu
Enrollment No: 2101440213
Name of Program: Information Technology
Semester: IV. Course Title: Software Engineering
Course Code: (22413)
Title of Micro Project:. COCOMO MODEL
Course Outcomes Achieved:
Sr. Characteristic to Poor Average Good Excellent Sub
No. be assessed (Marks 1-3) (Marks 4 -5) (Marks 6-8) (Marks 9-10) Total
( A)Process and Product Assessment(Convert above total marks out of 6 marks. )
1. Relevance to the
Course
2. Literature
Review/information
collection
3. Completion of the
target as per
project proposal
4. Analysis ofdata and
representation
5. Quality of
Prototype/Model
6. Report
Preparation.
( B) Individual Presentation/Viva (Convert above marks Total Marks out of 4)
7. Presentation
8. Viva
(A) (B) Total Marks 10
Process and Product Individual
Assessment (6 marks) Presentation/Viva(4 marks)
Comments/Suggestions about team work, leadership/inter-personal communication
………………………………………………………………………………………
……………………………………… ……………………………………………….
Name and designation of the Teacher: Mrs.
Dated Signature. ……………………………………………….