Ads
related to: cocomo model solved problems worksheet
Search results
Results From The WOW.Com Content Network
The Constructive Cost Model (COCOMO) is a procedural software cost estimation model developed by Barry W. Boehm. The model parameters are derived from fitting a regression formula using data from historical projects (63 projects for COCOMO 81 and 163 projects for COCOMO II).
AFCAA REVIC is a set of programs for use in estimating the cost of software development projects. [1] The Revised Enhanced Version of Intermediate COCOMO (REVIC) model is a copyrighted program available for public distribution under agreement with the REVIC developer, Ray Kile, and the U.S. Air Force Cost Analysis Agency (AFCAA).
The perhaps most common estimation methods today are the parametric estimation models COCOMO, SEER-SEM and SLIM. They have their basis in estimation research conducted in the 1970s and 1980s and are since then updated with new calibration data, with the last major release being COCOMO II in the year 2000.
The Constructive Systems Engineering Cost Model (COSYSMO) was created by Ricardo Valerdi while at the University of Southern California Center for Software Engineering. It gives an estimate of the number of person-months it will take to staff systems engineering resources on hardware and software projects.
Object points are an approach used in software development effort estimation under some models such as COCOMO II. [1] [2]Object points are a way of estimating effort size, similar to Source Lines Of Code (SLOC) or Function Points.
The function point is a "unit of measurement" to express the amount of business functionality an information system (as a product) provides to a user. Function points are used to compute a functional size measurement (FSM) of software.
Jones family worksheet for Maintenance Costs. Plus signs indicate good maintenance history; the more plus signs, the lower the maintenance costs. Even though every column on the worksheet contains a different type of information, the Joneses can use it to make reasonable, rational judgments about Maintenance Costs.
The Putnam model is an empirical software effort estimation model [1] created by Lawrence H. Putnam in 1978. Measurements of a software project is collected (e.g., effort in man-years, elapsed time, and lines of code) and an equation fitted to the data using regression analysis .