- #COCOMO MODEL E IS PRODUCTIVITY DRIVERS#
- #COCOMO MODEL E IS PRODUCTIVITY DRIVER#
- #COCOMO MODEL E IS PRODUCTIVITY SOFTWARE#
Function Point Analysis These function-point counts are then weighed (multiplied) by their degree of complexity: Simple Average Complex Inputs 2 4 6 Outputs 3 5 7 Files 5 10 15 Inquires 2 4 6 Interfaces 4 7 10 16. Function Point Analysis How is Function Point Analysis done? Working from the project design specifications, the following system functions are measured (counted): Inputs Outputs Files Inquires Interfaces 15.
#COCOMO MODEL E IS PRODUCTIVITY SOFTWARE#
The main other approach used for measuring the size, and therefore the time required, of software project is lines of code (LOC) which has a number of inherent problems.
Albrecht of the IBM Corporation in the early 1980s. It is also useful in comparing and highlighting opportunities for productivity improvements in software development. Function Point Analysis What is Function Point Analysis (FPA)? It is designed to estimate and measure the time, and thereby the cost, of developing new software applications and maintaining existing software applications. Basic COCOMO Model: Example We have determined our project fits the characteristics of Semi-Detached mode We estimate our project will have 32,000 Delivered Source Instructions. Basic COCOMO Model: Limitation Its accuracy is necessarily limited because of its lack of factors which have a significant influence on software costs The Basic COCOMO estimates are within a factor of 1.3 only 29% of the time, and within a factor of 2 only 60% of the time 12. The coefficients ab, bb, cb and db are given in next slide. Basic COCOMO Model: Formula E=ab (KLOC or KDSI) b b D=cb(E) d b P=E/D where E is the effort applied in person-months, D is the development time in chronological months, KLOC / KDSI is the estimated number of delivered lines of code for the project (expressed in thousands), and P is the number of people required. Basic COCOMO Basic COCOMO is good for quick, early, rough order of magnitude estimates of software costs It does not account for differences in hardware constraints, personnel quality and experience, use of modern tools and techniques, and other project attributes known to have a significant influence on software costs, which limits its accuracy 8.
#COCOMO MODEL E IS PRODUCTIVITY DRIVER#
COCOMO: Some Assumptions Primary cost driver is the number of Delivered Source Instructions (DSI) / Delivered Line Of Code developed by the project COCOMO estimates assume that the project will enjoy good management by both the developer and the customer Assumes the requirements specification is not substantially changed after the plans and requirements phase 7. Contd Embedded Mode Software projects that must be developed within a set of tight hardware, software, and operational constraints. The Development Modes: Project Characteristics Organic Mode Relatively small, simple software projects Small teams with good application experience work to a set of less than rigid requirements Similar to the previously developed projects relatively small and requires little innovation Semidetached Mode Intermediate (in size and complexity) software projects in which teams with mixed experience levels must meet a mix of rigid and less than rigid requirements. COCOMO Models COCOMO has three different models that reflect the complexity: the Basic Model the Intermediate Model and the Detailed Model 4.
#COCOMO MODEL E IS PRODUCTIVITY DRIVERS#
Introduction COCOMO is one of the most widely used software estimation models in the world It was developed by Barry Boehm in 1981 COCOMO predicts the effort and schedule for a software product development based on inputs relating to the size of the software and a number of cost drivers that affect productivity 3.