Software Cost Estimation with COCOMO II

By Barry W. Boehm, Chris Abts, A. W. Brown, Sunita Chulani, B. Clark, E. Horowitz, R. Madachy, D. Reifer, Bert Steece. 2000

1,954 citations recorded by the source corpus.

View Paper: https://www.semanticscholar.org/paper/fb6a8e7e28c07a0b607bdb6301a0baee6e4f71ba

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Citations in the corpus

End-user software engineering (2004, background): “End-user programming has become the most common form of programming in use today [2], but there has been little investigation into the dependability of the programs end users create.”
End-User Development: An Emerging Paradigm (2006, background): “(Boehm et al. 2000) predicts exponential growth of the number of end-user developers compared to the number of software professionals, underscoring the importance of research in EUD.”
Usability measurement and metrics: A consolidated model (2006, methodology): “Some software cost estimation methods, such as COCOMO II (Boehm et al., 2000), take account of the impact of the software development environment on the areas just mentioned.”
Software economics: a roadmap (2000, methodology): “The recent COCOMO II model [ 14 ] has an emerging extension called CORADMO to support reasoning about rapid schedules for smaller projects.”
Estimating the numbers of end users and end user programmers (2005, background): “Page 1 of 8 In 1995, Boehm predicted that by 2005, there would be “55 million performers” of “end user programming” in the United States.”
Information needs for software development analytics (2012, background): “Furthermore, numerous studies have found an order of magnitude productivity gap between developers [ 11 ], [56].”
Value-based software engineering: reinventing (2003, methodology): “These milestones are also used in the COCOMO II cost estimation model [7] to estimate the budget, effort, schedule, and staffing level required to meet these milestones.”
What we have learned about fighting defects (2002, background): “• Barry Boehm mentioned a model called COQUALMO, currently in its first draft, which tries to do this [3].”
The situational factors that affect the software development process: Towards a comprehensive reference framework (2012, methodology): “Of the empirical factor models, the Constructive Cost Model (COCOMO) [51] and its later revision COCOMO II [53] are the most widely accepted and used [54].”