The costs for these three components can be estimated separately, and summed up to give the overall cost of the system. The database part could be semi-detached software, and the GUI part organic software.
Detailed cocomo model example driver#
The system should have a life-cycle architecture package, which provides detailed information on cost driver inputs. The Post-Architecture is a detailed model that is used once the project is ready to develop and sustain a fielded system.
![detailed cocomo model example detailed cocomo model example](https://www.researchgate.net/profile/Brad-Clark-4/publication/243482239/figure/tbl6/AS:668354062872588@1536359434749/Scale-Factor-Values-SF-j-for-COCOMO-II-Models.png)
Of these, the communication part can be considered as embedded software. The COCOMO II model is part of a suite of Constructive Cost Models. A distributed Management Information System (MIS) product for an organization having offices at several places across the country can have the following sub-components: The following development project can be considered as an example application of the complete COCOMO model. This approach reduces the margin of error in the final estimate. The cost of each subsystem is estimated separately. The complete COCOMO model considers these differences in characteristics of the subsystems and estimates the effort and development time as the sum of the estimates for the individual subsystems. Not only that the inherent development complexity of the subsystems may be different, but also for some subsystems the reliability requirements may be high, for some the development team might have no previous experience of similar development, and so on. These subsystems may have widely different characteristics.įor example, some subsystems may be considered as organic type, some semi-detached, and some embedded. However, most large systems are made up of several smaller sub-systems.
Detailed cocomo model example software#
Team members may have limited experience on related systems but may be unfamiliar with some aspects of the system being developed.Įmbedded: A development project is considered to be of embedded type, if the software being developed is strongly coupled to complex hardware, or if the stringent regulations on the operational procedures exist.Ī major shortcoming of both the basic and intermediate COCOMO models is that they consider a software product as a single homogeneous entity. Semi-detached: A development project can be considered of semidetached type, if the development consists of a mixture of experienced and inexperienced staff. According to Boehm, software cost estimation should be done through three stages: Basic Model Intermediate Model Detailed Model. COCOMO was developed by Barry Boehm in his 1981 book, Software Engineering Economics. Organic: A development project can be considered of 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 types of projects. Detailed COCOMO: an extension of the Intermediate model that adds effort multipliers for each phase of the project to determine the cost driver s impact on each step. Organic, Semidetached and Embedded Software ProjectsĪccording to Boehm (1981), any software development project can be classified into one of the following three categories based on the development complexity: organic, semidetached, and embedded.