A review of studies on expert estimation of software development effort

By Magne Jørgensen. Journal of Systems and Software, 2004

604 citations recorded by the source corpus.

Subfields: Information Systems, Software

View Paper: https://www.semanticscholar.org/paper/1ba2b2a382e2593d4ec3dab39e61d47123afc37b

How researchers see this paper

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

In Information Systems

In Software

Citations in the corpus

Evaluating prediction systems in software project estimation (2012, background): “Three such examples of inconsistent systematic review findings are: • Jørgensen [13] reviewed 15 studies comparing model-based to expert-based estimation.”
Systematic literature review of machine learning based software development effort estimation models (2012, methodology): “Although the research on ML model is increasing in academia, recent surveys [1,19,20] have revealed that expert judgment (a kind of non-ML method) is still the dominant method for SDEE in industry.”
Evidence-Based Software Engineering for Practitioners (2005, background): “(1) identifying a problem; (2) proposing a technology or procedure to address that problem; (3) evaluating the proposed technology in a pilot project; (4) if the technology is appropriate, adopting and implementing the technology; (5) monitoring the organization after implementation of the new techn”
The Future of Empirical Methods in Software Engineering Research (2007, background): “Systematic reviews are one of the key building blocks of evidence-based SE [41, 70, 76], and the interest in conducting such reviews within SE is clearly growing [40, 56, 65, 66, 123], although the coverage of SE topics by systematic reviews is still in its infancy and very limited.”
Findings from Evidence-Based Forecasting: Methods for Reducing Forecast Error (2006, background): “Jørgensen (2004b) examined 12 guidelines for structuring experts’ judgmental predictions of time needed to complete software projects.”
Systematic literature reviews in software engineering - A systematic literature review (2009, methodology): “We did this because Professor Travassos had reported to one of us that his research group was attempting to adopt the SLR process and because Professor Jørgensen was known to be the author of a substantial number of SLRs.”
Systematic literature reviews in software engineering - A tertiary study (2010, neutral): “Software quality 5 28 [57] 1 – 1 1 Software management 5 32 [58–60,62–64] 1 [32,33] 1 [17,18,48] 2 11 2 Computing essentials 4 41 [67] 1 1 1 Mathematical and engineering fundamentals 3 22 [22,48] 2 2 2”
Using mapping studies as the basis for further research - A participant-observer case study (2011, neutral): “[12].”
The New C Standard (Excerpted material) An Economic and Cultural Commentary (2008, neutral): “• knowledge of the computer language used, and • ability to estimate the effort needed to implement the specified functionality.[206]”
A survey of controlled experiments in software engineering (2005, methodology): “We used Inspec and various search engines to check the completeness of our inclusion and cross-checked for inclusion with other surveys [51], [22], [25].”