1. Evolution in Software Product Line
Team 16:
Panth Shah (A20345606)
Mengyuan Wen (A20354337)
Ran Ao (A20363029)
Jiao Qu (A20386614)
Mingru Gu (A20352480)
Presented By:
Panth Shah
2. OUTLINE:
Introduction to Software Product Line(SPL)
Concepts
Components
Software Product Line (SPL) Architecture
Mapping Problem space with Solution space
Schematic Design
Software Product Line (SPL) Evolution
Case Study: Phillips Medical System
Introduction to Evolution Model
Product Line Evolution: A History
Platform Architecture
Magnetic Resonance: A Product
Conclusion
Reference
3. INTRODUCTION TO SPL :: CONCEPTS
Concepts of Software Product Line(SPL): A Definition
Bringing a systematic approach for by defining the type of outcome that is targeted by
combined common key elements to satisfy mass customization by intra-organizational
software reuse
Describing the features of deliverable, defining the development process, attaching the
development process to the architecture and then attaching the assets to the development
process.
Assets which are treated as a group and not just as a random sequence of unrelated efforts.
Software Product Line Engineering: Focusing on development and evolution of entire
product line and not just a single product.
Software Evolution: Cycle of activities/processes involved in the development, application
and maintenance of any software system.
4. • Components of Software Product Line: A Top-Down Approach
INTRODUCTION TO SPL :: COMPONENTS
Individual
Product
Product Base
Variability
Software
Platform
Software
Product Line
Standardized
Infrastructure
Product Scope
Expansion
Feature Extension
of Product Line
Development for reuse:
Product Management
Domain requirements engineering
Domain design
Domain realization
Domain testing
Development with reuse:
Application requirements
engineering
Application design
Application realization
Application testing
5. SOFTWARE PRODUCT LINE ARCHITECTURE
• Product Line Architecture: Mapping Problem-space with Solution- space
Requirements
Domain
Analysis
Architecture Design Implementation
Problem Space Solution Space
Domain Engineering
SPL Features and Relations Solution Assets
Problem Space Solution Space
Product Features and
Properties
Single Problem
Independent Product
Single Solution
Application Engineering
7. SOFTWARE PRODUCT LINE EVOLUTION
In figure shown, overview of the evolution process is
presented with the inclusion of various activities included
in each step of evolution
Business/Business Unit is responsible for single or set of
related products and involved in supporting requirements.
Requirements on particular product are implemented in a
product-specific code but common requirements are
supported by the software product line component
configuration and simulation
Variability introduced in any domain artifacts for
individual product is handled by variability modeling
mechanism through product line evolution.
Core Assets are mainly a part of legacy systems in software
product line which are reused to support product
population in product line
Problem-space features are mapped into solution-space
features by providing set of configuration rules
8. CASE STUDY :: PHILLIPS MEDICAL SYSTEM
• Phillips: A Software Product Line (SPL) for Medical Imaging System
Introduction:
Phillips Medical System is one of the
world’s largest contributor in the
development of infrastructure platform for
medical imaging products and related
healthcare services
Phillips Medical System is functional in four
major business groups: Cardiac and
Monitoring system, digital imaging system,
medical IT and ultrasound
The Medical Imaging Platform (MIP)
developed by Phillips is used to produce
camera functionality is shared various same
divisional products, such as printing,
storage and rendering capabilities
Reusable Core Assets
Architecture Components
Imaging Platform
Platform A Platform B
X
Hierarchical Product Line
9. CASE STUDY :: PHILLIPS MEDICAL SYSTEM
• Phillips Product Line Evolution: A Time Line Approach
1997
• First raised the
imaging platform
notion
1998
• Started to design
the imaging
platform
2001
• Introduced
Product groups on
imaging platform
2014
• Building digital
platform to
provide cloud-
based healthcare
10. CASE STUDY ::
PHILLIPS MEDICAL
SYSTEM
Architecture adopted by
Phillips to build their imaging
platform is possessing
following characteristics:
Open by nature
Extensible
Flexible
System components:
Third party commodity
software
Middleware components:
Medical middleware
products used in product
line
• Phillips Medical System: Platform Architecture
Independent automated
products
Business specified
components
Middleware
components
System components Base
Services
Application
Products
11. CASE STUDY :: PHILLIPS MEDICAL SYSTEM
• Phillips Medical System > All Products > Magnetic Resonance
1.Why Magnetic Resonance?
• There are three major companies (Philips, LG and Siemens) in the
production of magnetic resonance equipment. The Philips’ product is
the best.
2. Image Processing System
• This product adopts Image Processing System which is mainly used in
10 product groups now. PHILPS is the first company to apply this
technology to the medical field in 1914. And the Magnetic resonance
devices represent the highest level of this technology and the
evolution of the software product line of Imaging Systems.
12. CASE STUDY :: PHILLIPS MEDICAL SYSTEM
• Phillips Medical System : Product Line of Magnetic Resonance
Multiva 1.5T
(2013)
• Get fast, right first time
imaging for a wide range
of routine and advanced
applications with Multiva
1.5T magnetic resonance
imaging (MRI) system.
Clinicians need less time
to make a confident,
accurate diagnosis,
improving throughput
and referral status.
Ingenia
1.5T(2014)
• Put quality first with
Philips Ingenia 1.5T MRI
system. Digital clarity
and speed help clinicians
diagnose with
confidence, explore new
applications, and work
productively. Great
patient reviews build
your image in the
community. All
supported by our
commitment to helping
you grow.
Ingenia
3.0T(2015)
• The Ingenia 3.0T is
designed to take you to
the forefront of clinical
excellence. Leverage its
consistent, high quality
imaging and clinical
versatility to expand your
practice into highly
advanced neuro, msk,
body and cardiac.
Provide exceptional
patient comfort. Enhance
productivity with
automation where it
makes sense.
13. CONCLUSION & FUTURE WORK
• Work presented here aims to represent a wide variation in software product line approach
adopted by organizations to support their product population needs
• Evolution in Software Product Line benefits organizations in terms of cost reduction, product
quality improvement, inter-organizational platform support and product base expansion
• Product Line Evolution approach supports the growth of organizational business with asset
reuse, requirement change absorption by addressing the problems of traditional software reuse
approach
• Practical industrial architecture for software product line evolution is represented with relation
between intermediate component
• Finally, a case analysis is done on Phillips Medical System for having the historical Imaging
Platform and holding a Product Line of Medical Imaging Software product with multiple
generation products
• As a future work, multiple domain platforms can be merged on a single domain platform to
support cross technology product development under same product line
14. REFERENCES
1. RAFAEL CAPILLA, JAN BOSCH, PABLO TRINIDAD, ANTONIO RUIZ-CORTES and MIKE HINCHEY, “An
overview of Dynamic Software Product Line architectures and techniques: Observations from
research and industry”, 2014 Elsevier Inc., The Journal of Systems and Software
2. R.R. MACALA, L.D. STUCKEY, D.C. GROSS, ‘Managing Domain-Specific Product-Line
Development,’ IEEE Software, pp. 57-67, 1996.S
3. JAN BOSCH, PO BENGTSSON, “Component Evolution in Product-Line Architectures”, Department
of Software Engineering and Computer Science
4. KATHRIN BERG, JUDITH BISHOP, “Tracing Software Product Line Variability – From Problem to
Solution Space”, SAICSIT 2005
5. MIKAEL SVAHNBERG, “Variability in Evolving Software Product Line”, Karlskrona 2000, ISBN 91-
631-0265-X
6. FRANK VAN DER LINDEN, KLAUS SCHMID, EELCO ROMMES, “Software Product Lines in Action –
The Best Industrial Practice in Product Line Engineering”, ISBN 978-3-540-71436-1 Springer
Berlin Heidelberg New York
