[1] 1980 Don Reifer and Dan Galorath paper which prompted the building of the JPL Softcost model.
This model, an early example of software estimation, allows for automated and performed risk analysis.
[3] The Jensen-inspired System-3, and other modeling systems like Barry Boehm's COCOMO and early works by the Doty Associates can be seen as direct and indirect contributors to the software suite that would be developed by Galorath in the late 1980s.
In 1988, Galorath Incorporated began work on the initial version of SEER-SEM.
[4] SEER for Software (SEER-SEM) is composed of a group of models working together to provide estimates of effort, duration, staffing, and defects.
is a form of common currency within the model and enables new, reused, and even commercial off-the-shelf code to be mixed for an integrated analysis of the software development process.
The extent of this increase is governed by the amount of rework (redesign, re-implementation, and retest) required to reuse the code.
While SLOC is an accepted way of measuring the absolute size of code from the developer's perspective, metrics such as function points capture software size functionally from the user's perspective.
as: where, A project's effort and duration are interrelated, as is reflected in their calculation within the model.
This size-duration relationship is also used in component-level scheduling algorithms with task overlaps computed to fall within total estimated project duration.