![]() Personnel attributes Analyst capability Software engineering capability Applications experience Virtual machine experience Programming language experience Hardware attributes Run-time performance constraints Memory constraints Volatility of the virtual machine environment Required turnabout time Required software reliability Size of application database Complexity of the product ![]() This extensionconsiders a set of four "cost drivers",each with a number of subsidiary attributes:- Product attributes Intermediate COCOMOsIntermediate COCOMO computes software development effort as function of program size and a set of "costdrivers" that include subjective assessment of product, hardware, personnel and project attributes. However it does not account for differences inhardware constraints, personnel quality and experience, use of modern tools and techniques, and so on. People required = Effort Applied / Development Time The coefficients ab, bb, cb and db are given in the following table.īasic COCOMO is good for quick estimate of software costs. )The basic COCOMO equations take the formĮffort Applied = ab(KLOC)bb ĭevelopment Time = cb(Effort Applied)db Requirements Embedded projects - developed within a set of "tight" constraints (hardware, software, operational. Program size isexpressed in estimated thousands of lines of code (KLOC)COCOMO applies to three classes of software projects: Organic projects - "small" teams with "good" experience working with "less than rigid" requirements Semi-detached projects - "medium" teams with mixed experience working with a mix of rigid and less than rigid Intermediate COCOMO takes these CostDrivers into account and Detailed COCOMO additionally accounts for the influence of individual project phases.īasic COCOMOBasic COCOMO computes software development effort (and cost) as a function of program size. ![]() The first level, Basic COCOMOis good for quick, early, rough order of magnitude estimates of software costs, but its accuracy is limited due to itslack of factors to account for difference in project attributes (Cost Drivers). This article refers to COCOMO 81.COCOMO consists of a hierarchy of three increasingly detailed and accurate forms. The need for the new model came as software developmenttechnology moved from mainframe and overnight batch processing to desktop development, code reusability and theuse of off-the-shelf software components. It provides more support for modern softwaredevelopment processes and an updated project database. COCOMO II is the successor of COCOMO 81 andis better suited for estimating modern software development projects. In 1997 COCOMO II was developed and finally published in2000 in the book Software Cost Estimation with COCOMO II. The study examined projectsranging in size from 2,000 to 100,000 lines of code, and programming languages ranging from assembly to PL/I.These projects were based on the waterfall model of software development which was the prevalent softwaredevelopment process in 1981.References to this model typically call it COCOMO 81. It drew on a study of 63 projects at TRW Aerospacewhere Barry Boehm was Director of Software Research and Technology in 1981. Boehm's Book Software engineering economics as a model forestimating effort, cost, and schedule for software projects. The model uses a basic regression formula, with parameters that are derived from historical project data andcurrent project characteristics.COCOMO was first published in 1981 Barry W. COCOMOThe Constructive Cost Model (COCOMO) is an algorithmic software cost estimation model developed by BarryBoehm.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |