Evaluation of a Method for Proactively Managing the Evolving Scope of a Software Product Line
[Context and motivation]PLEvo-Scoping is a method intended to help Product Line (PL) scoping teams anticipate emergent features and distinguish unstable from stable features, with the aim of preparing their PL for likely future adaptation needs. [Question/problem]This paper describes a quasi-experiment performed to characterize PLEvo-Scoping in terms of adequacy and feasibility. [Principal ideas/results] This quasi-experiment was performed by two scoping teams in charge of scoping the same PL, where one scoping team applied first an existing PL scoping approach and then PLEvo-Scoping, while the other scoping team interweaved activities from both. The two approaches achieved similar results: The method could be applied in just one day, and it was considered adequate and feasible. [Contribution] Ideas on how to improve the method and its tool support have been obtained, and similar results are expected from other professionals facing the problem of evolution-centered PL scoping. However, further empirical studies should be performed.
KeywordsQuasi-experiment Empirical Study Product Line Scoping Requirements Volatility Analysis Product Line Evolution Planning
Unable to display preview. Download preview PDF.
- 1.Clements, P., Northrop, L.: Software Product Lines: Practices and Patterns. Addison-Wesley, Reading (2001)Google Scholar
- 4.Savolainen, J., Kuusela, J.: Volatility Analysis Framework for Product Lines. In: Proc. SSR 2001, Toronto, pp. 133–141 (2001)Google Scholar
- 5.Bayer, J., Flege, O., Knauber, P., et al.: PuLSE: A Methodology to Develop Software Product Lines. In: Proc. SSR 1999, Los Angeles, pp. 122–131 (1999)Google Scholar
- 6.Bengtsson, P., Lassing, N., Bosch, J., van Vliet, H.: Analyzing Software Architectures for Modifiability. TR HK-R-RES00/11-SE, University of Karlskrona/Ronneby. Ronneby (2000)Google Scholar
- 7.Schmid, K.: Planning Software Reuse – A Disciplined Scoping Approach for Software Product Lines. PhD Theses in Experimental Software Engineering. Fraunhofer IRB (2003)Google Scholar
- 8.John, I., Knodel, J., Lehner, T., et al.: A Practical Guide to Product Line Scoping. In: Proc. SPLC 2006, Baltimore, pp. 3–12 (2006)Google Scholar
- 9.Villela, K., Dörr, J., Gross, A.: Proactively Managing the Evolution of Embedded System Requirements. In: Proc. RE 2008, Barcelona, pp. 13–22 (2008)Google Scholar
- 10.John, I., Villela, K., Gross, A.: AAL Platform Product Line – Scoping Results and Recommendations. TR 074.09/E, Fraunhofer IESE, Kaiserslautern (2009) (available upon request)Google Scholar
- 11.Zelkowitz, M., Wallace, D.: Experimental Models for Validating Technology. IEEE Computer 31(5), 23–31 (1998)Google Scholar
- 12.Basili, V., Caldiera, G., Rombach, H.: Goal Question Metrics Paradigm. Encyclopedia of Software Engineeering 1, 528–532 (1994)Google Scholar
- 13.Villela, K., John, I.: Usage of PLEvo-Scoping in the Ambient Assisted Living Domain: A Quasi-Experiment Package. TR 093.09/E, Fraunhofer IESE, Kaiserslautern (2010)Google Scholar
- 15.Yin, R.: Case Study Research: Design and Methods, 3rd edn. Sage Publications, Thousand Oaks (2003)Google Scholar