Klaus Schmid
ABSTRACT
Product Line Engineering is a recent approach to software development that specifically aims at exploiting commonalities and systematic variabilities among functionally overlapping systems in terms of large scale reuse. Taking full advantage of this potential requires adequate planning and management of the reuse approach as otherwise huge economic benefits will be missed due to an inappropriate alignment of the reuse infrastructure.Key in product line planning is the scoping activity, which aims at focussing the reuse investment where it pays. Scoping actually happens on several levels in the process: during the domain analysis step (analysis of product line requirements) a focusing needs to happen just like during the decision of what to implement for reuse. The latter decision has also important ramifications for the development of an appropriate reference architecture as it provides the reusability requirements for this step.In this paper, we describe an integrated approach that has been developed, improved, and validated over the last few years. The approach fully covers the scoping activities of domain scoping and reuse infrastructure scoping and was validated in several industrial case studies.
- Sergio Bandinelli and Goiuria Sagarduy. A unifying framework for reuse economic models. Technical Report ESI-1996-Reuse03, European Software Institute, 1996.Google Scholar
- Joachim Bayer, Oliver Flege, Peter Knauber, Roland Laqua, Dirk Muthig, Klaus Schmid, Tanya Widen, and Jean-Marc DeBaud. PuLSE: A methodology to develop software product lines. In Proceedings of the ACM SIGSOFT Symposium on Software Reusability, pages 122-131, 1999. Google ScholarDigital Library
- Andrew Beitz and Janne Jarvinnen. FAME --- An approach for software process assessment. Technical Report 001.00/E, Fraunhofer IESE, 2000.Google Scholar
- Jan Bosch. Software product lines: Organizational alternatives. In Proceedings of the 23rd International Conference on Software Engineering, pages 91-100. 2001. Google ScholarDigital Library
- Jan Bosch, Michel Jaring, Susanne Johnsson, Klaus Schmid, Steffen Thiel, Bernhard Thomé, and Siegfried Trosch; Klaus Schmid (Ed.). Task 1.2: Domain analysis: Consortiumwide deliverable on scoping. Deliverable of the ESAPS Project, Eureka Σ! 2023 Programme, ITEA Project 99005, 2001.Google Scholar
- Lionel C. Briand, Khaled El Emam, and Frank Bomarius. COBRA: A hybrid method for software cost estimation, benchmarking, and risk assessment. In Proceedings of the Twentieth International Conference on Software Engineering, pages 390-399, April 1998. Google ScholarDigital Library
- Paul Clements, Cristina Gacek, Peter Knauber, and Klaus Schmid. Successful software product line development in a small organization. In Paul Clements and Linda Northrop, editors, Software Product Lines: Practices and Patterns, chapter 11. Addison Wesley Longman, 2001.Google Scholar
- Patricia Collins Cornwell. HP domain analysis: Producing useful models for reusable software. Hewlett-Packard Journal, 47(4), August 1996.Google Scholar
- James C. Dager. Cummin's experience in developing a software product line architecture for real-time embedded diesel engine controls. In Patrick Donohoe, editor, Software Product Lines: Experience and Research Directions; Proceedings of the First Software Product Line Conference (SPLC1), pages 23-46.2000. Google ScholarDigital Library
- Margaret J. Davis. Reuse strategy model: Planning aid for reuse-based projects. Technical Report CDRL 5159, Software Technology for Adaptable, Reliable Systems (STARS), 1993.Google Scholar
- Jean-Marc DeBaud and Klaus Schmid. A systematic approach to derive the scope of software product lines. In Proceedings of the 21st International Conference on Software Engineering, pages 34-43, 1999. Google ScholarDigital Library
- Ken Dymond. A Guide to the CMM --- Understanding the Capability Maturity Model for Software. Process Inc. US, fourth edition, 1996.Google Scholar
- Khaled El Emam and Lionel C. Briand. Costs and benefits of software process improvement. Technical Report 047.97/E, Fraunhofer IESE, 1997.Google Scholar
- Khaled El Emam, Jean-Normand Drouin, and Walcélio Melo. SPICE --- The Theory and Practice of Software Process Improvement and Capability Determination. IEEE Computer Society, 1998.Google Scholar
- Manuel Eduardo Jaime Esqueda. Product line streamlining: A methodology to guide product costing and decision-making. Master's thesis, Sloan School of Management, June 1998.Google Scholar
- International Organisation for Standardisation (Ed.). ISO/IEC TR 15504-2 "Information Technology --- Software Process Assessment --- Part 2: A Reference Model for Processes and Process Capability". 1998.Google Scholar
- Georg Gawol. Produktsimulationen mit Java im Internet. Master's thesis, Fachhochschule Frankfurt am Main, Fachbereich MND, Allgemeine Informatik, 1999.Google Scholar
- Paul E. Green and Abba M. Krieger. Models and heuristics for product line selection. Marketing Science, 4(1):1-19, 1985.Google ScholarDigital Library
- James Herbsleb, Anita Carleton, James Rozum, Jane Siegel, and David Zubrow. Benefits of CMM-based software process improvement: Initial results. Technical Report CMU/SEI-94-TR-013, Software Engineering Institute, 1994.Google ScholarCross Ref
- Project Management Institute. A Guide to the Project Management Body of Knowledge (PMBOK Guide), 2000 Edition, chapter Chapter 5: Project Scope Management. Project Management Institute, Four Campus Boulevard, Newtown Square, PA 19073-3299, USA, 2000.Google Scholar
- K. Kang, S. Cohen, J. Hess, W. Novak, and S. Peterson. Feature-oriented domain analysis (FODA) feasibility study. Technical Report CMU/SEI-90-TR-21, Software Engineering Institute, Carnegie Mellon University, November 1990.Google ScholarCross Ref
- Peter Knauber and Klaus Schmid. Using a quantitative approach for defining generic components: A case study. In Proceedings of the Fourth International Software Architecture Workshop (ISAW'4), pages 131-135, 2000.Google Scholar
- Pasi Kuvaja, Jouni Similä, Lech Krzanki, Adriana Bicego, Samuli Saukkonen, and Günter Koch. Software Process Assessment and Improvement --- The Bootstrap Approach. Blackwell Business, 1994.Google Scholar
- Charlotte H. Mason and George R. Milne. An approach for identifying cannibalization within product line extensions and multi-brand strategies. Journal of Business Research, 31:163-170, 1994.Google ScholarCross Ref
- Richard D. McBride and Fred S. Zufryden. Integer programming approach to the optimal product line selection problem. Marketing Science, 7(2):126-140, 1988.Google ScholarDigital Library
- A. Mili, S. Fowler Chmiel, R. Gottumukkala, and L. Zhang. An integrated cost model for software reuse. In Proceedings of the 22nd International Conference on Software Engineering, 2000. Google ScholarDigital Library
- Jeffrey S. Poulin. Measuring Software Reuse. Addison-Wesley, 1997.Google Scholar
- David C. Rine and Robert M. Sonnemann. Investments in reusable software. a study of software reuse investment success factors. Journal of Systems and Software, 41(1):17-32, 1998. Google ScholarDigital Library
- David Robertson and Karl Ulrich. Planning for product platforms. Sloan Management Review, 39(4):19-31, 1998.Google Scholar
- Klaus Schmid. An economic perspective on product line software development. In First Workshop on Economics-Driven Software Engineering Research, Los Angeles (EDSER-1), 1999. Google ScholarDigital Library
- Klaus Schmid. A framework for product line quality model development. IESE Report, No. 047.00/E, 2000.Google Scholar
- Klaus Schmid. Product line mapping method. Technical Report 028.00/E, Fraunhofer IESE, 2000.Google Scholar
- Klaus Schmid. Scoping software product lines --- an analysis of an emerging technology. In Patrick Donohoe, editor, Software Product Lines: Experience and Research Directions; Proceedings of the First Software Product Line Conference (SPLC1), pages 513-532. Kluwer Academic Publishers, 2000. Google ScholarDigital Library
- Klaus Schmid. An initial model of product line economics. In Proceedings of the International Workshop on Product Family Engineering (PFE-4), 2001, 2001. Google ScholarDigital Library
- Klaus Schmid and Isabel John. Case study of a product line benefit and risk analysis. In Peter Knauber and Klaus Pohl, editors, 1. Deutscher Software-Produktlinien Workshop (DSPL-1), Kaiserslautern, November 2000, pages 15-22.Google Scholar
- Klaus Schmid and Isabel John. Product line development as a rational, strategic decision. In Klaus Schmid and Birgit Geppert, editors, Proceedings of the International Workshop on Product Line Engineering in Early Steps: Planning, Modeling, and Managing (PLEES'01), 2001.Google Scholar
- Klaus Schmid and Michael Schank. PuLSE-BEAT --- a decision support tool for scoping product lines. In Third International Workshop on Software Architectures for Product Families, IWSAPF-3, Las Palmas de Gran Canaria, Spain, March 15-17, 2000, Also as LNCS 1951, pages 64-74, 2000. Google ScholarDigital Library
- Software Productivity Consortium Services Corporation. Reuse Adoption Guidebook, Version 02.00.05, November 1993.Google Scholar
- Software Productivity Consortium Services Corporation, Technical Report SPC-92019-CMC. Reuse-Driven Software Processes Guidebook, Version 02.00.03, November 1993.Google ScholarCross Ref
- Software Technology for Adaptable, Reliable Systems (STARS), Technical Report STARS-VC-A025/001/00. Organization Domain Modeling (ODM) Guidebook, Version 2.0, 1996.Google Scholar
- Steffen Thiel, Stefan Ferber, and Martin Mergel. An overview of methods supporting product line development. Deliverable BOSCH-WP1-T1.2-01, ITEA-ESAPS Project, June 2000.Google Scholar
- Peter Toft, Derek Coleman, and Joni Ohta. A cooperative model for cross-divisional product development for a software product line. In Patrick Donohoe, editor, Software Product Lines: Experience and Research Directions; Proceedings of the First Software Product Line Conference (SPLC1), pages 111-132. Kluwer Academic Publishers, 2000. Google ScholarDigital Library
- David M. Weiss and Chi Tau Robert Lai. Software Product-Line Engineering. Addison-Wesley, 1999. Google ScholarDigital Library
Index Terms
- A comprehensive product line scoping approach and its validation
Recommendations
Using Documentation for Product Line Scoping
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 ...
A Lightweight Approach for Product Line Scoping
SEAA '12: Proceedings of the 2012 38th Euromicro Conference on Software Engineering and Advanced ApplicationsMany organizations providing products with com-mon features wish to take advantage of that similarity in order to reduce development and maintenance efforts. Their goal is to move from a single-system development paradigm towards a product line ...
A Systematic Method for Scoping Core Assets in Product Line Engineering
APSEC '05: Proceedings of the 12th Asia-Pacific Software Engineering ConferenceProduct Line Engineering (PLE) is an effective reuse methodology where common features among members are captured into core assets and applications are produced by reusing the core assets, reducing development cost while increasing productivity. To ...
Comments