A discipline for software engineering

By W. Humphrey. Series in software engineering, 2012

1,342 citations recorded by the source corpus.

Subfields: Computer Networks and Communications, Information Systems

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

How researchers see this paper

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

In Computer Networks and Communications

In Information Systems

Citations in the corpus

The costs and benefits of pair programming (2001, background): “Based on representative statistics reported in [7], programmers inject 100 defects per thousand lines of code.”
Reverse engineering: a roadmap (2000, positive): “Thus, the insights of the SEI Capability Maturity Model R © (CMM R ©) framework [34, 35] ought to apply to reverse engineering as well as forward engineering.”
Experimentation in Software Engineering (2012, methodology): “This type of table is presented by Humphrey [82].”
Effort, co‐operation and co‐ordination in an open source software project: GNOME (2002, background): “The deﬁnition of this often-disputed metric LOC (Park, 1992; Humphrey, 1995) is taken from the CVS repository and therefore includes all types of LOC, e.g. also commentaries (Fogel, 1999).”
Agile Software Development Methods: Review and Analysis (2017, background): “not been clearly established. However, it has been shown that certain methods are not necessarily suitable for all individuals (Naur 1993) or settings (Baskerville et al. 1992). For this reason, e.g. Humphrey (1995) calls for the development of a personal process for each software developer. Despite”
Empirical Findings in Agile Methods (2002, background): “various waterfall and iterative approaches, such as the Personal Software Process (PSP) [1].”
On the value of static analysis for fault detection in software (2006, neutral): “Fault-detection yield refers to the percentage of defects present in the code at the time of the fault-detecting practice that were found by that practice [15], as shown in (4).”
Distributed Scrum: Agile Project Management with Outsourced Development Teams (2007, methodology): “…new software system the requirements will not be completely known until after the users have used it -Humphrey's Requirements Uncertainty Principle [4] x It is not possible to completely specify an interactive system – Wegner's Lemma [5] x Ambiguous and changing requirements, combined with…”
Effects of Process Maturity on Quality, Cycle Time, and Effort in Software Product Development (2000, methodology): “However, this can result in major delays in product development resulting from the additional time required to fix errors detected during customer acceptance testing (Humphrey 1995).”
A Control Theory Perspective on Agile Methodology Use and Changing User Requirements (2009, background): “Project leaders often set performance standards related to project quality, meeting project deadlines, and managing project budgets (Humphrey 1995, Kirsch 1996), and frequently, clients have a hand in determining performance standards (Kirsch et al. 2002).”