Software Product Lines: Practices and Patterns

By Linda M. Northrop, P. Clements. 2001

3,841 citations recorded by the source corpus.

View Paper: https://www.semanticscholar.org/paper/8f25aa2eca9966610bbdb8ed89867b121a155ba5

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

Software Architecture (2008, unknown): “) Moreover, organizations such as the CMU Software Engineering Institute are well on their way towards providing concrete guidelines and processes for the use of a product line approach [37].”
S.P.L.O.T.: software product lines online tools (2009, background): “Software Product Lines (SPLs) [6, 7] is a contemporary approach to software development that promotes “reuse” to a first-class citizen aiming at reducing overall development time and cost while improving product quality.”
Reverse engineering feature models (2011, background): “The SPL paradigm is centered around a number of practices leading to systematic code reuse [9].”
Feature-Oriented Software Product Lines (2013, methodology): “Of course, product-line tools are covered by the standard books on software product lines (Clements and Northrop 2001; Pohl et al. 2005).”
An Overview of Feature-Oriented Software Development (2009, methodology): “of software systems instead of on a single system and emphasize the similarities between the systems instead of their differences [47,45,101].”
Staged configuration through specialization and multilevel configuration of feature models (2005, background): “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).”
An orchestrated survey of methodologies for automated software test case generation (2013, background): “Software product lines are sysems of program families that have a well managed asset base and eature model; from which one can derive a CIT model (Cohen t al., 2006; Clements and Northrop, 2001).”
Automated analysis of feature models 20 years later: A literature review (2010, methodology): “In the software engineering literature, the mass customization of software products is known as software product lines[24] or software product families[62].”
Model-driven engineering: A survey supported by the unified conceptual model (2015, methodology): “…Factories [Greenfield et al., 2004] is the approach proposed by Microsoft strongly inspired by the "assembly line" metaphor, found in industrial automation areas, which has also been adopted by software engineering through initiatives such as Software Product Lines [Clements and Northrop, 2001].”
Software traceability: trends and future directions (2014, background): “One special case of link evolution occurs in product lines which provide a scalable framework for the structured reuse of a wide range of software artifacts, including requirements, architecture, design, code, and test cases [13].”
Evolving software product lines with aspects (2008, background): “Software product lines (SPLs) [9] [23] represent an increasingly popular technology to support the derivation of a wide range of applications.”
Automated Reasoning on Feature Models (2005, methodology): “Most of the existing methods [3, 6] for SPL engineering agree that a way for modelling SPL is needed.”
Software Engineering for Automotive Systems: A Roadmap (2007, unknown): “Nevertheless, today the process of software reuse is not systematically planned between OEMs and suppliers, as required, say, for software product lines ([ CN01 ]; see the comment below).”
A taxonomy of variability realization techniques (2005, background): “and its product family is further described in Reference [3].”
Model checking lots of systems: efficient verification of temporal properties in software product lines (2010, background): “particular market segment or mission and that are developed from a common set of core assets in a prescribed way” [10].”
Generic semantics of feature diagrams (2007, methodology): “Work supported by Walloon Region and FSE under FIRST Europe Objective 3 Project PLENTY EPH3310300R0462 / 215315 Preprint submitted to Elsevier Science 4 May 2006”