On the Design and Development of Program Families

By D. Parnas. IEEE Trans. Software Eng., 2001

989 citations recorded by the source corpus.

Subfields: Artificial Intelligence, Information Systems, Software

View Paper: https://www.semanticscholar.org/paper/2a63e23954ac820d95f1d222e6e3152fd9953e51

How researchers see this paper

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

In Artificial Intelligence

In Information Systems

In Software

Citations in the corpus

Software Factories: Assembling Applications with Patterns, Models, Frameworks, and Tools (2004, methodology): “Before we can talk about Software Factories, we must introduce software factory schemas and software factory templates.”
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].”
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].”
Staged configuration through specialization and multilevel configuration of feature models (2005, background): “1 Introduction Software product-line engineering (also known as system-family engineering) seeks to exploit the commonalities among systems from a given problem domain while managing the variabilities among them in a systematic way (Clements and Northrop, 2001; Weiss and Lai, 1999; Parnas, 1976).”
Modal I/O Automata for Interface and Product Line Theories (2007, methodology): “In order to further demonstrate the usefulness of our modal I/O automata, we construct a product line [11,12,13] theory.”
A taxonomy of variability realization techniques (2005, methodology): “a moderately sized class in a modern object oriented system), and Reference [54] discusses a space allocation algorithm consisting of (roughly) 25-30 lines of code.”