The detailed model also provides a three-level product hierarchy and has some other capabilities such as a procedure for adjusting the phase distribution of the development schedule. Example: Banking software or Traffic light control software. This project having a high level of complexity with a large team size by considering all sets of parameters (software, hardware and operational).
These phase dependent effort multipliers yield better estimates because the cost driver ratings may be different during each phase. Example: Database design or OS development. The Detailed COCOMO Model differs from the Intermediate COCOMO model in that it uses effort multipliers for each phase of the project.
DSI values and cost drivers can be chosen for individual components instead of for the system as a whole. The Intermediate model also allows the system to be divided and estimated in components. The software development effort estimation is an essential activity before any software project initiation.
It produces better results than the Basic model because the user supplies settings for cost drivers that determine the effort and duration of the software projects. The Intermediate model uses an Effort Adjustment Factor (EAF) and slightly different coefficients for the effort equation than the Basic model. Suppose it is estimated that a project will take 51 nominal staff-months at 5,000 / staff-month. The Intermediate COCOMO Model an extension of the Basic COCOMO model. 2 So, the nominal amount of staff-months will be increased by 17 for organic, semi-detached, or embedded projects. The Basic model is good for quick, early, and rough order of magnitude estimates. COCOMO Model (Boehm, 1981) According to Boehm, software cost estimation should be done through three stages: 1. There are a number of different types: The Basic COCOMO Model estimates the effort required to develop software in three modes of development ( Organic Mode, Semidetached Mode, or Embedded Mode) using only DSIs as an input. 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.