A Case Study of Two Configurable Software Product Families

Author(s):  
Mikko Raatikainen ◽  
Timo Soininen ◽  
Tomi Männistö ◽  
Antti Mattila
2005 ◽  
Vol 10 (1) ◽  
pp. 41-60 ◽  
Author(s):  
Mikko Raatikainen ◽  
Timo Soininen ◽  
Tomi Männistö ◽  
Antti Mattila

2005 ◽  
Vol 74 (2) ◽  
pp. 173-194 ◽  
Author(s):  
Sybren Deelstra ◽  
Marco Sinnema ◽  
Jan Bosch

Author(s):  
MICHEL JARING ◽  
JAN BOSCH

In a software product family context, software architects design architectures that support product diversification in both space (multiple contexts) and time (changing contexts). Product diversification is based on the concept of variability: a single architecture and a set of components support a family of products. Software product families have to support increasing amounts of variability, thereby making variability engineering a primary concern in software product family development. The first part of this paper (1) suggests a two-dimensional, orthogonal categorization of variability realization techniques and classifies these variability categories into system maturity levels. The second part (2) discusses a case study of an industrial software product family of mobile communication infrastructure for professional markets such as the military. The study categorizes and classifies the variability in this product family according to criteria common to virtually all software development projects.


Author(s):  
YOUNG-GAB KIM ◽  
SEOK KEE LEE ◽  
SUNG-BONG JANG

Software Product-Line Engineering (SPLE) is composed of two areas, namely domain engineering and application engineering. Domain engineering is associated with product-line architecture, which is a core asset of the product-line. One of the key issues of the software product-line, especially in domain engineering, is handling the variability among product families. That is, variation management for the software product-line architecture determines the success of software development. Therefore, this paper proposes processes and artifacts to build the software product-line architecture and to manage uniform variability over the life cycle of software product-lines. Furthermore, a case study, namely, the Electronic Medical Record (EMR) system, is presented.


2021 ◽  
pp. 204388691987054
Author(s):  
Karthikeyan Chandran ◽  
Madhuchhanda Das Aundhe

This case study documents the challenges faced by Iota Consultancy Services, an IT Service organization, as it simultaneously developed and deployed an IT Services Management software product for one of its premier clients, The Clementon Company. A leading market research firm, The Clementon Company had its footprints across the globe. Its recent acquisition of several smaller research agencies had created a complex IT landscape, in terms of the technologies adopted and the processes followed. In Iota Consultancy Services’ 10-year-old history, this engagement with The Clementon Company was a significant milestone, consisting of two parts—(1) Streamlining and standardizing The Clementon Company’s IT processes and (2) maintaining The Clementon Company’s organization-wide IT infrastructure. Iota Consultancy Services began this crucial assignment with an initial study to identify a product for the The Clementon Company’s IT department. Iota Consultancy Services, a rapidly growing player in the sector, had indigenously developed a few IT products, as well. It had an IT Services Management product called Helpdesk Management. Being the sole service provider for maintaining The Clementon Company’s entire IT infrastructure, Iota Consultancy Services felt that Helpdesk Management could be deployed as a single tool across the organization. However, until now, Helpdesk Management had never been deployed as a comprehensive IT Services Management product for any organization. This meant that Iota Consultancy Services needed to simultaneously enhance its Helpdesk Management tool by developing new features, and also deploy it for The Clementon Company. This was Iota Consultancy Services’ chance to earn a reputation as a successful product company, which would result in increased revenue. However, if things did not go well, Iota Consultancy Services could lose face forever. Iota Consultancy Services’ dilemma was whether it should propose Helpdesk Management as a tool for The Clementon Company, or not. At this juncture, everything depended on whether Iota Consultancy Services could successfully customize the Helpdesk Management tool to suit The Clementon Company’s requirements.


Sign in / Sign up

Export Citation Format

Share Document