The Community for Technology Leaders
RSS Icon
Issue No.03 - May/June (2010 vol.27)
pp: 42-47
Isabel John , Fraunhofer IESE, Kaiserslautern
Product line scoping is the process of determining which of an organization's products, features, and domains would find systematic reuse economically useful. Scoping is generally the first phase in product line engineering. For a decade, it has been recognized as its own discipline in product line engineering. Scoping, also called product line planning, is based on expert knowledge and information; in meetings and workshops, individuals must interactively elicit information on the features, products, and further plans in the expert's product line domain. But often, these domain experts don't have the time to really reproduce and formulate all the knowledge needed for scoping. They should be heavily integrated into the scoping knowledge elicitation process, but they're only minimally available. The CAVE (Commonality and Variability Extraction) approach and its industrial applications offer a solution to the problem of domain experts' availability. CAVE supports scoping and product line engineering in a development organization by systematically eliciting the needed information from user documentation of existing systems. This article describes the approach and its embedding in scoping, as well as results and lessons learned from three industrial applications of the approach.
product line engineering, product line scoping, user documentation, product line analysis, elicitation, elicitation methods, requirements/specifications, software engineering, domain engineering, reusable software
Isabel John, "Using Documentation for Product Line Scoping", IEEE Software, vol.27, no. 3, pp. 42-47, May/June 2010, doi:10.1109/MS.2010.34
1. I. John and M. Eisenbarth, "A Decade of Scoping: A Survey," Proc. Software Product Line Conf. (SPLC 09), ACM Press, 2010, pp. 31–40.
2. I. John, Pattern-Based Documentation Analysis for Software Product Lines, doctoral dissertation, Fraunhofer IRB Verlag and Technical Univ. of Kaiserslautern, 2010.
3. V. Alves et al., "An Exploratory Study of Information Retrieval Techniques in Domain Analysis," Proc. 2008 12th Int'l Software Product Line Conference (SPLC 08), IEEE CS Press, 2008, pp. 67–76.
4. J. Nattoch Dag et al., "A Linguistic-Engineering Approach to Large-Scale Requirements Management," IEEE Software, vol. 22, no. 1, 2005, pp 32–39.
5. N. Niu and S. Easterbrook, "On-Demand Cluster Analysis for Product Line Functional Requirements," Proc. 2008 12th Int'l Software Product Line Conf. (SPLC 08), IEEE CS Press, 2008, pp. 87–96.
6. I. John, J. Knodel, and T. Schulz, "Efficient Scoping with CAVE: A Case Study," Applied Software Product Line Engineering, K.C. Kang, V. Sugumaran, and S. Park eds., Auerbach Publications, 2009, pp. 421–445.
7. A. Helferich, G. Herzwurm, and S. Schockert, "QFD-PPP: Product Line Portfolio Planning Using Quality Function Deployment," Proc. 9th Int'l Conf. Software Product Lines (SPLC 05), LNCS 3154, Springer, 2005, pp. 162–173.
8. K. Schmid, "A Comprehensive Product Line Scoping Approach and Its Validation," Proc. 24th Int'l Conf. Software Eng. (ICSE 02), ACM Press, 2002, pp. 593–603.
14 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool