Managing Variation in Services in a Software Product Line Context

Abstract : Software product line (SPL) and service-oriented architecture (SOA) approaches both enable an organization to reuse existing assets and capabilities rather than repeatedly redeveloping them for new systems. Organizations can capitalize on such reuse in software-reliant systems to achieve business goals such as productivity gains, decreased development costs, improved time to market, increased reliability, increased agility, and competitive advantage. Both approaches accommodate variation in the software that is being reused or the way in which it is employed. Meeting business goals through a product line or a set of service-oriented systems requires managing the variation of assets, including services. This report examines combining existing SOA and software product line approaches for variation management. This examination has two objectives: (1) for service-oriented systems development, to present an approach for managing variation by identifying and designing services explicitly targeted to multiple service-oriented systems, and (2) for SPL systems, to present an approach for managing variation where services are a mechanism for variation within a product line or for expanding the product line scope.

[1]  Linda M. Northrop,et al.  A Framework for Software Product Line Practice , 1999, ECOOP Workshops.

[2]  Rick Kazman,et al.  Evaluating Software Architectures: Methods and Case Studies , 2001 .

[3]  Paul Clements,et al.  Variability in Software Product Lines , 2005 .

[4]  Paul Clements,et al.  Software product lines - practices and patterns , 2001, SEI series in software engineering.

[5]  Paul Clements,et al.  Software architecture in practice , 1999, SEI series in software engineering.

[6]  Michael Stal,et al.  Combining Product Line Engineering and Service Oriented Architecture in Health Care Infrastructure Systems: Experience Report , 2008, SPLC.

[7]  Kamal Bhattacharya,et al.  A Layered Service Process Model for Managing Variation and Change in Service Provider Operations , 2007, WISE.

[8]  Paul Clements,et al.  A framework for software product line practice - version 2 , 1999 .

[9]  Patrick Donohoe,et al.  Product Line Analysis: A Practical Introduction , 2001 .

[10]  Kyo Chul Kang,et al.  Feature-Oriented Domain Analysis (FODA) Feasibility Study , 1990 .

[11]  Paul Jensen Experiences with Product Line Development of Multi-Discipline Analysis Software at Overwatch Textron Systems , 2007, 11th International Software Product Line Conference (SPLC 2007).

[12]  G.A. Lewis,et al.  Service-Oriented Architecture and its implications for software maintenance and evolution , 2008, 2008 Frontiers of Software Maintenance.

[13]  Phil Bianco Evaluating a Service-Oriented Architecture , 2007 .

[14]  Soumya Simanta,et al.  SMART: Analyzing the Reuse Potential of Legacy Components in a Service-Oriented Architecture Environment , 2007 .

[15]  Stefan Biffl,et al.  Systematic management of software product lines , 2005, Softw. Process. Improv. Pract..