Review of David L. Parnas' "Designing Software for Ease of Extension and Contraction"

By A. Sverdlov. 2004

713 citations recorded by the source corpus.

View Paper: https://www.semanticscholar.org/paper/08d16c28d15fdab9455685d222eee67a79b7931c

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

Using dependency models to manage complex software architecture (2005, unknown): “General Terms Design, Algorithms, Management.”
A taxonomy of variability realization techniques (2005, background): “For example, Reference [56] discusses an “address processing subsystem” that consists of 25 function calls (i.”
Feature-Oriented Software Product Lines (2013, background): “The field of software product lines started its success story in the 1990s, though the field has its roots in the much earlier works on program families (McIlroy 1969; Parnas 1979).”
An Overview of Feature-Oriented Software Development (2009, background): “The problem of separating the code of different features follows the seminal principle of separation of concerns , credited to Dijkstra [54] and Parnas [98,99].”
Value-based software engineering: reinventing (2003, unknown): “Architecture-based techniques focus on identifying the product’s most likely sources of change, or evolution requirements, and using information-hiding modularity techniques to hide the sources of change within architectural modules [26].”
A view of 20th and 21st century software engineering (2006, background): “Principles of modularity were strengthened by Constantine’s concepts of coupling (to be minimized between modules) and cohesion (to be maximized within modules) [48], by Parnas’s increasingly strong techniques of information hiding [116][117][118], and by abstract data types [92][75][151].”
The Role of Interdependence in the Micro-Foundations of Organization Design: Task, Goal, and Knowledge Interdependence (2020, background): “A similar emphasis exists on directionality in the modularity literature—for example, the Parnas (1979) definition of dependence as an A uses B—and social interdependence theory (e.g., Victor & Blackburn, 1987).”
DDDAS-based multi-fidelity simulation framework for supply chain systems (2010, methodology): “Generalizing software to anticipate all the possible ways in which it could change is difﬁ-cult, and attempting to do so usually comes at the expense of performance, as well as making the code unmanage-ably complex (Parnas, 1979).”