It offers a medium to process all the project characteristics for calculating the software estimation. The detailed model provides a set of phase-sensitive effort multipliers for each cost driver. This helps in determining the workforce allocation for each phase of the project. Three-level product hierarchy: In the three-level product hierarchy, there are a module, subsystem, and system levels.
|Genre:||Health and Food|
|Published (Last):||28 October 2009|
|PDF File Size:||20.84 Mb|
|ePub File Size:||20.69 Mb|
|Price:||Free* [*Free Regsitration Required]|
It is the model that allows one to estimate the cost, effort and schedule when planning a new software development activity. It consists of three sub-models: 1. End User Programming: Application generators are used in this sub-model. End user write the code by using these application generators.
Example — Spreadsheets, report generator, etc. Intermediate Sector: a. Application Generators and Composition Aids — This category will create largely prepackaged capabilities for user programming. Their product will have many reusable components.
Application Composition Sector — This category is too diversified and to be handled by prepackaged solutions. It includes GUI, Databases, domain specific components such as financial, medical or industrial process control packages.
System Integration — This category deals with large scale and highly embedded systems. For this it uses Application Composition Estimation Model. This model is used for the prototyping stage of application generator and system integration.
Stage-II: It supports estimation in the early design stage of the project, when we less know about it. For this it uses Early Design Estimation Model. This model is used in early design stage of application generators, infrastructure, system integration. Stage-III: It supports estimation in the post architecture stage of a project. For this it uses Post Architecture Estimation Model.
This model is used after the completion of the detailed architecture of application generator, infrastructure, system integration.
Software Engineering | COCOMO Model
It is a procedural cost estimate model for software projects and often used as a process of reliably predicting the various parameters associated with making a project such as size, effort, cost, time and quality. It was proposed by Barry Boehm in and is based on the study of 63 projects, which make it one of the best-documented models. It is measured 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 effort put. 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 in subsequent calculations.
Constructive Cost Model (COCOMO)
Software Engineering | COCOMO II Model