Software Product Line Engineering
By K. Pohl, Günter Böckle, F. V. Linden. 2005
2,899 citations recorded by the source corpus.
Subfields: Artificial Intelligence, Information Systems
View Paper: https://www.semanticscholar.org/paper/188e778ae2b5c1dee1dd76ce9c786f566f7e7079
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
- Christian Kästner
- Sven Apel
- Gunter Saake
- Don S. Batory
- Thomas Thüm
- Krzysztof Czarnecki
- Ina Schaefer
- Lionel Claude Briand
In Information Systems
- Christian Kästner
- Sven Apel
- Gunter Saake
- Emelie Engström
- Don S. Batory
- Per Runeson
- Thomas Thüm
- Krzysztof Czarnecki
Citations in the corpus
- An Overview of Feature-Oriented Software Development (2009, methodology): “This is in stark contrast to non-FOSD approaches, in which developers have to design a product line architecture first in order to define the granularity of components or extension points in a common framework [101].”
- 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).”
- Software product line testing - A systematic mapping study (2011, background): “The process of developing the platform is named domain engineering , and the process of deriving specific products from the platform is named application engineering [59].”