Managing variability with traceability in product and service families

Service family architectures are based on a set of basic building blocks that can be configured appropriately to build different services based on the same set of assets. These building blocks should be designed to provide variability so as to facilitate configuration and assembly in order to produce a family of products/services. Such an architectural design for a family of services is recognized as a highly knowledge intensive process. Documenting design decisions associated with these various configurations leading to variability and the capability to trace the life of a variation in both forward and backward directions are key to a flexible development of a service family. In this paper; we discuss the key role played by a traceability-based knowledge management system in documenting such design decisions and in tracing variability. Using a case study, we illustrate the importance of using such a knowledge management system in the design and development of service families.

[1]  M. Mcgrath.  Product Strategy for High Technology Companies , 2000 .

[2]  D. Mowery,et al.  Technological overlap and interfirm cooperation: implications for the resource-based view of the firm , 1998 .

[3]  T. Simpson.  A concept exploration method for product family design , 1998 .

[4]  Klaus Pohl,et al.  Adapting traceability environments to project-specific needs , 1998, CACM.

[5]  K. Ulrich,et al.  Planning for Product Platforms , 1998 .

[6]  Fj Freek Erens.  The synthesis of variety : developing product families , 1996 .

[7]  Kenneth L. Kraemer,et al.  The Information Industries: Introduction to the Special Issue , 1998, Information systems research.

[8]  Klaus Pohl,et al.  PRO-ART * : Enabling Requirements Pre-Traceability 1 , 1996 .

[9]  Jeff Conklin.  Design rationale and maintainability , 1989, [1989] Proceedings of the Twenty-Second Annual Hawaii International Conference on System Sciences. Volume II: Software Track.

[10]  Tomoji Kishi,et al.  Aspect-oriented analysis for product line architecture , 2000, SPLC.

[11]  Henk Sol,et al.  Proceedings of the 54th Hawaii International Conference on System Sciences , 1997, HICSS 2015.

[12]  Amrit Tiwana,et al.  Supporting Collaborative Process Knowledge Management in New Product Development Teams , 1999, Decis. Support Syst..

[13]  Daniel Hoffman,et al.  Commonality and Variability in Software Engineering , 1998, IEEE Softw..

[14]  M. Lynn.  Hawaii International Conference on System Sciences , 1996 .

[15]  Matthias Jarke,et al.  Toward Reference Models of Requirements Traceability , 2001, IEEE Trans. Software Eng..

[16]  B. Kahn.  Variety: From the Consumer’s Perspective , 1998 .

[17]  Renato Vinga-Martins.  Requirements Traceability for Product-Lines , 1999, ECOOP Workshops.

[18]  Olly Gotel,et al.  An analysis of the requirements traceability problem , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[19]  James L. Heskett,et al.  The Service Profit Chain: How Leading Companies Link Profit and Growth to Loyalty, Satisfaction, and Value (Цепочка создания прибыли в сфере услуг: как ведущие компании связывают прибыль и рост с лояльностью, удовлетворением и ценностью) , 2014 .

[20]  Hau L. Lee,et al.  Value of Postponement , 1998 .

[21]  August-Wilhelm Scheer,et al.  ARIS - Business Process Frameworks , 1998 .

[22]  Kosuke Ishii,et al.  Design for Variety , 1998 .

[23]  B. Morris.  The Service Profit Chain: : How Leading Companies Link Profit and Growth to Loyalty, Satisfaction, and Value , 1998 .

[24]  Amrit Tiwana,et al.  E-services: problems, opportunities, and digital platforms , 2001, Proceedings of the 34th Annual Hawaii International Conference on System Sciences.

[25]  Klaus Pohl,et al.  PRO-ART: enabling requirements pre-traceability , 1996, Proceedings of the Second International Conference on Requirements Engineering.

[26]  Jan Bosch,et al.  Product-line architectures in industry: a case study , 1999, Proceedings of the 1999 International Conference on Software Engineering (IEEE Cat. No.99CB37002).

[27]  Carlo Ghezzi,et al.  Program families: some requirements issues for the process languages , 1996, Proceedings 10th International Software Process Workshop.