COCOMO

COCOMO IIConstructive Cost Modelconstructive-cost model
The Constructive Cost Model (COCOMO) is a procedural software cost estimation model developed by Barry W. Boehm.wikipedia
38 Related Articles

Source lines of code

lines of codeLOCSLOC
The study examined projects ranging in size from 2,000 to 100,000 lines of code, and programming languages ranging from assembly to PL/I.
There are several cost, schedule, and effort estimation models which use SLOC as an input parameter, including the widely used Constructive Cost Model (COCOMO) series of models by Barry Boehm et al., PRICE Systems True S and Galorath's SEER-SEM.

Barry Boehm

Barry W. BoehmDr. Barry BoehmBoehm
The Constructive Cost Model (COCOMO) is a procedural software cost estimation model developed by Barry W. Boehm.
His contributions to the field, according to Boehm (1997) himself, include "the Constructive Cost Model (COCOMO), the spiral model of the software process, the Theory W (win-win) approach to software management and requirements determination and two advanced software engineering environments: the TRW Software Productivity System and Quantum Leap Environment".

Object point

Object points are an approach used in software development effort estimation under some models such as COCOMO II.

SEER-SEM

The Jensen-inspired System-3, and other modeling systems like Barry Boehm's COCOMO and early works by the Doty Associates can be seen as direct and indirect contributors to the software suite that would be developed by Galorath in the late 1980s.

Function point

function pointsFunction point analysisAutomated Function Point

Software development effort estimation

Comparison of development estimation softwareestimationsoftware effort estimation
The perhaps most common estimation methods today are the parametric estimation models COCOMO, SEER-SEM and SLIM.

COSYSMO

Similar to its predecessor COCOMO, COSYSMO computes effort (and cost) as a function of system functional size and adjusts it based on a number of environmental factors related to systems engineering.

Cost estimation in software engineering

software estimationEstimation in software engineeringestimate
The Constructive Cost Model (COCOMO) is a procedural software cost estimation model developed by Barry W. Boehm.

Regression analysis

regressionmultiple regressionregression model
The model parameters are derived from fitting a regression formula using data from historical projects (63 projects for COCOMO 81 and 163 projects for COCOMO II).

TRW Inc.

TRWRamo-WooldridgeRamo-Wooldridge Corporation
It drew on a study of 63 projects at TRW Aerospace where Boehm was Director of Software Research and Technology.

Assembly language

assemblerassemblyassembly code
The study examined projects ranging in size from 2,000 to 100,000 lines of code, and programming languages ranging from assembly to PL/I.

PL/I

PL/1PL1Early PL/I
The study examined projects ranging in size from 2,000 to 100,000 lines of code, and programming languages ranging from assembly to PL/I.

Waterfall model

waterfallwaterfall methodadvanced programming methods
These projects were based on the waterfall model of software development which was the prevalent software development process in 1981.

Software development process

software development methodologydevelopment cyclesoftware development life cycle
COCOMO II is the successor of COCOMO 81 and is claimed to be better suited for estimating modern software development projects; providing support for more recent software development processes and was tuned using a larger database of 161 projects.

List of University of California, Los Angeles people

UCLA Department of PhilosophyDepartment of PhilosophyPhilosophy Department

Unified Code Count (UCC)

UCC
It implements a code counting framework published by the Software Engineering Institute (SEI) and adapted by COCOMO.

Weighted Micro Function Points

Weighted Micro Function Points (WMFP) is a modern software sizing algorithm which is a successor to solid ancestor scientific methods as COCOMO, COSYSMO, maintainability index, cyclomatic complexity, function points, and Halstead complexity.

Pareto principle

80/20 rule80-20 rule80:20 Rule
This factor is usually a part of COCOMO estimating for software coding.

Apache PDFBox

PDFBox
Using the COCOMO model, it took an estimated 46 person-years of effort.