Embedded: A development project is treated to be of an embedded type, if the software being developed is strongly coupled to complex hardware, or if the stringent regulations on the operational method exist. Example of Semidetached system includes developing a new operating system (OS), a Database Management System (DBMS), and complex inventory management system.ģ. Team members may have finite experience in related systems but may be unfamiliar with some aspects of the order being developed. Semidetached: A development project can be treated with semidetached type if the development consists of a mixture of experienced and inexperienced staff. Examples of this type of projects are simple business systems, simple inventory management systems, and data processing systems.Ģ. In COCOMO, projects are categorized into three types:ġ.Organic: A development project can be treated of the organic type, if the project deals with developing a well-understood application program, the size of the development team is reasonably small, and the team members are experienced in developing similar methods of projects. The value of the constant a and b are depends on the project type. To determine the initial effort E i in person-months the equation used is of the type is shown below The initial estimate (also called nominal estimate) is determined by an equation of the form used in the static single variable models, using KDLOC as the measure of the size.
#The cocomo model code#
Get an initial estimate of the development effort from evaluation of thousands of delivered lines of source code (KDLOC).COCOMO predicts the efforts and schedule of a software product based on the size of the software. Setting mixed investment strategies to improve organization's software capability, via reuse, tools, process maturity, outsourcing, etc.Boehm proposed COCOMO (Constructive Cost Estimation Model) in 1981.COCOMO is one of the most generally used software estimation models in the world.
Making legacy software inventory decisions: what parts to modify, phase out, outsource, etc Making software cost and schedule risk management decisionsĭeciding which parts of a software system to develop, reuse, lease, or purchase Setting project budgets and schedules as a basis for planning and controlĭeciding on or negotiating tradeoffs among software cost, schedule, functionality, performance or quality factors Making investment or other financial decisions involving a software development effort It has new cost drivers, new line counting rules, and new equations.ĬOCOMO II can be used for the following major decision situations You'll use it after you've developed your project's overall architecture. This is the most detailed COCOMO II model. Based on Unadjusted Function Points or KSLOC. It uses a small set of new Cost Drivers, and new estimating equations. You can use this model to get rough estimates of a project's cost and duration before you've determined it's entire architecture. Suitable for projects built with modern GUI-builder tools. COCOMO II targets modern software projects, and will continue to evolve over the next few years. The original COCOMO model has been very successful, but it doesn't apply to newer software development practices as well as it does to traditional practices. It provides more support for modern software development processes and an updated project database.ĬOCOMO II is tuned to modern software life cycles. COCOMO II is the successor of COCOMO 81 and is better suited for estimating modern software development projects. In 1997 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. COCOMO was first published in 1981 Barry W. The model uses a basic regression formula, with parameters that are derived from historical project data and current project characteristics. The Constructive Cost Model (COCOMO) is an algorithmic software cost estimation model developed by Barry Boehm.
0 kommentar(er)
