litetopia.blogg.se - Where do the constants of cocomo model come from

#Where do the constants of cocomo model come from drivers#
#Where do the constants of cocomo model come from software#
#Where do the constants of cocomo model come from code#

#Where do the constants of cocomo model come from code#

Where E is the effort applied in person-months, KLoC is the estimated number of thousands of delivered lines of code for the project, and EAF is the factor calculated above. The Intermediate Cocomo formula now takes the form: Volatility of the virtual machine environmentĪpplication of software engineering methods

Typical values for EAF range from 0.9 to 1.4. The product of all effort multipliers results in an effort adjustment factor (EAF). An effort multiplier from the table below applies to the rating.

#Where do the constants of cocomo model come from software#

Application of software engineering methodsĮach of the 15 attributes receives a rating on a six-point scale that ranges from "very low" to "extra high" (in importance or value).

Volatility of the virtual machine environment.

This extension considers a set of four "cost drivers", each with a number of subsidiary attributes:. Intermediate COCOMO computes software development effort as function of program size and a set of "cost drivers" that include subjective assessment of product, hardware, personnel and project attributes. Last one is Complete COCOMO model which is short coming of both basic & intermediate.

#Where do the constants of cocomo model come from drivers#

Intermediate COCOMO takes these Cost Drivers into account and Detailed COCOMO additionally accounts for the influence of individual project phases. The first level, Basic COCOMO is good for quick, early, rough order of magnitude estimates of software costs, but its accuracy is limited due to its lack of factors to account for difference in project attributes ( Cost Drivers). The need for the new model came as software development technology moved from mainframe and overnight batch processing to desktop development, code reusability, and the use of off-the-shelf software components.ĬOCOMO consists of a hierarchy of three increasingly detailed and accurate forms. 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. In 1995 COCOMO II was developed and finally published in 2000 in the book Software Cost Estimation with COCOMO II. References to this model typically call it COCOMO 81. These projects were based on the waterfall model of software development which was the prevalent software development process in 1981. 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. It drew on a study of 63 projects at TRW Aerospace where Boehm was Director of Software Research and Technology. Boehm in the late 1970s and published in Boehm's 1981 book Software Engineering Economics as a model for estimating effort, cost, and schedule for software projects. The constructive cost model was developed by Barry W.