Catalogue
of Methods and Processes for
System-Family Engineering
Günter
Böckle
1. Introduction
This document presents the results (methods, processes) of the ESAPS, CAFÉ and Families projects on two different abstraction levels. A set of attributes is used to describe each method on an abstract level so that it can be viewed on a single screen. More detailed descriptions are available by following the corresponding links. Extensive navigation methods are provided - via key words, search tress, and search tables.
The system family engineering process from the CAFÉ reference framework has been used as one of the major entry points to the descriptions in this document. Each box, characterizing a sub process, is active: when the reader clicks to a box (1 to 12) or into boxes in the centre (for traceability or change management), s/he navigates to a table listing methods that are relevant for the selected sub process. From this table, links lead to the general method descriptions. Methods used in several sub processes will occur in the tables for each of those sub processes. In search trees, blue boxes are linked to sub trees while green boxes are linked to tables describing the corresponding method.
This document does not contain descriptions of the ESAPS, CAFÉ and Families validation results since those are not considered methods or processes for system family engineering.
2. The Process
Are you interested in methods
particular to a specific sub process of the basic product-family-engineering
process core above? Then click into the corresponding rectangle, representing
that sub process.
Assessing the SFE Process: CMMI-SFE
|
CMMI-SFE
|
SAL3 |
| CMMI-SFE | |
| CMMI-SFE (V&V) for Nokia | |
| PLA and CMMI: Relationships and Adoption Scenarios | |
| FEF | Family Evaluation Framework |
|
Transition process
|
Transition Process Siemens | Transition Process for Switching to Product-Family Engineering |
| Action Plan ESI | Product-Line Action Plan Specification | |
| Transition Ivorium | Lightweight, incremental transition process for PF adoption | |
| Transition Telvent | Transition from Products to Product Lines (Case Study) | |
| Transition MARKET MAKER |
Guidelines for the process of SW development conforming PLs |
|
| Transition DNV |
DNV Software’s Experiences with Adoption of Product-Family Engineering (Case Study) |
|
Innovation Management
|
Innovation Management and Technology Strategy |
| Measuring Product Lines in Place |
Organisation Structures
| Organisation Structures |
Organisation Structures for Product-Family Engineering |
3.
Methods for Phase 1 "System Family Scoping"
The methods listed below are mostly for the early phases of domain engineering: system family scoping and system family economic analysis. Many methods listed below cover several process phases. Therefore, there are links from several phases to such methods.
|
Method |
Topic |
|
Requirements for tools for requirements engineering, design, and product derivation |
|
|
How to use trace information for change integration |
|
|
Introduction to change management - process and categories |
|
|
Information models as basis for method development |
|
|
Analysis, classification, description and administration of assets and their dependencies |
|
|
|
|
|
An introduction to requirements traceability |
|
|
A methodology for modelling requirements and other artefacts in product family engineering to support traceability |
|
|
Organisation Structures for Product-Family Engineering |
|
|
Planning process for product families |
|
|
Transition from Products to Product Lines (Case Study) |
|
|
DNV Software’s Experiences with Adoption of Product-Family Engineering (Case Study) |
|
|
Specification for an integrated product family economic model |
|
|
|
|
|
|
|
|
Feature Logic-based Configuration Management Models |
|
|
Configuration Management Process: Support & Tools for Process Support |
|
|
Tool to assess CMMI practices in any organisation |
|
|
Scenario-based Requirements Derivation for Customer-specific Applications based on a Central Variability Model |
|
|
A Unified Conceptual Model for Product Family Variability Modelling |
|
Reuse Strategy
|
Reuse Action Plan impact in the BAPO-A dimension |
| Mapping of Reuse-invest Model on BAPO model | |
| ESI: R-SPICE |
Some part of this sub process is also covered by the scoping methods.
|
Method |
Topic |
| Methods for scoping | |
|
SPLIT: Software Product-Line Integrated Technology from Thales |
|
|
Identification, processing and description of features |
|
|
Information models as basis for method development |
|
|
How to use trace information for change integration |
|
|
An introduction to requirements traceability |
|
|
|
|
|
Integrated cost and investment model for product family development |
|
|
Specification for an integrated product family economic model |
|
|
|
|
|
Estimating (Future) Product Viability: A platform Development reasoning Model |
|
|
The Stage Growth Framework for a Software Product Business |
|
|
|
|
|
Organisation Structures for Product-Family Engineering |
|
|
Planning process for product families |
|
|
Product Management Assessment w.r.t. Product-Family Engineering |
|
|
|
|
|
Feature Logic-based Configuration Management Models |
|
|
Configuration Management Process: Support & Tools for Process Support |
|
|
Tool to assess CMMI practices in any organisation in the context of SFE |
|
| A Model for Product Family Economics in the Automotive Context |
| Cost / Economic Model | |
| Integrated Cost and Investment Model for Product Family Development | |
| A Cost Model for Software System Families | |
| A Model for Product Family Economics in the Automotive Context |
|
Method |
Topic |
|||
|
Conceptual domain analysis, introduction to domain analysis |
||||
|
Domain engineering methods description, analysis, comparison |
||||
|
Architecture
|
||||
|
Requirements description and categorisation + configuration and deployment onto an execution platform + examples for switch maintenance and air supervision systems + Prototype |
||||
|
The product line software engineering method from Fraunhofer IESE |
||||
|
How to identify, process and describe features |
||||
|
Model-based Value Engineering from Siemens |
||||
|
AspectAnalysis |
See Aspect-oriented Design | |||
|
Rapid Architecting: functional decomposition and architecture synthesis |
||||
|
Use-case-based method guidance process (and use-case templates) |
||||
| Logistics issues in change management | Managing changes of product family assets between parallel (component) projects in a product population | Change Management and System Family Engineering: a XML Technology Based Solution |
|
|
|
|
||||
|
Handling commonalities and variability
|
Architecture aspects | |||
| A Unified Conceptual Model for Product Family Variability Modelling | CoVAR - Comonent selection considering variability, architectural concerns and requirements | |||
|
Requirements for tools for requirements engineering,design, and product derivation |
||||
|
Information models as basis for method development |
||||
|
Applying the COTS acquisition process CAP to requirements engineering methodologies |
||||
|
SPLIT:Software Product-Line Integrated Technology from Thales |
||||
|
Identification, processing and description of features |
||||
|
Analysis, classification, description and administration of assets and their dependencies |
||||
|
Applying the COTS acquisition process CAP to requirements engineering methodologies and to MoRE/SLATE |
||||
|
|
||||
|
Building domain models based on legacy system descriptions |
||||
|
|
||||
|
UML Profile for Quality of Service |
||||
|
Decision Model Modelling and Automatic Derivation Process Using XML Technology |
||||
|
COTS Selection Process for Product Families; Requirements-driven COTS-selection Method for Product Families |
||||
|
System Performance Modelling in UML with Properties and Metrics for Asset Selection |
||||
|
Extension plans of CMMI for system family engineering (Nokia) |
||||
|
|
||||
|
Annotated catalogue of patterns for reliability and safety |
||||
|
Feature Logic-based Configuration Management Models |
||||
|
Configuration Management Process: Support & Tools for Process Support |
||||
|
|
||||
|
Domain-oriented software asset management |
||||
|
Derivation of Applications from Web Services |
||||
| Family architecture evaluation | ||||
| Integrability and Extensibility Evaluation | ||||
| RAP | Reliability and Availability Prediction | |||
| Product Line Behavioural Synthesis (PliBS) | ||||
| Toward the model-driven engineering of large scale systems in THALES - A MDFE case study in the Air-Traffic Management field | ||||
| Improve quality of domain requirements | ||||
| Tool to assess CMMI practices in any organisation in the context of SFE | ||||
| Domain architecture tool support for evolution management and variability traceability | ||||
| CoVAR - Component selection considering Variability, Architectural concerns and Requirements | ||||
| Scenario-based Requirements Derivation for Customer-specific Applications based on a Central Variability Model | ||||
| Validation of the Extended ScenTED; Method for Scenario-based Derivation of Performance Test Cases | ||||
| Architect Assistant | ||||
Search tree for the topic "Requirements engineering and traceability":
Architecture Methods for Phase 3:
|
Aspect-oriented Design
|
Aspects weaver | |
| Aspect-driven development | ||
|
Aspect Analysis
|
Thales: Air supervision
systems |
|
|
Alcatel: Switch
maintenance systems |
||
|
Method |
Topic |
|||
|
Conceptual domain analysis, introduction to domain analysis |
||||
|
Domain engineering methods description, analysis, comparison |
||||
|
Requirements description and categorisation + configuration and deployment onto an execution platform + examples for switch maintenance and air supervision systems + prototype |
||||
|
The product line software engineering method from Fraunhofer IESE |
||||
|
Model-based value engineering from Siemens |
||||
|
Aspect Analysis |
Thales: Air supervision systems |
Alcatel: Switch maintenance systems |
||
|
Rapid architecting: functional decomposition and architecture synthesis |
||||
|
Use-case-based method guidance process (and use-case templates) |
||||
|
Analysis, classification, description and administration of assets and their dependencies |
||||
|
Architecture
|
||||
|
Change Management
|
||||
|
|
|
|||
|
|
||||
|
Handling commonalities and variability |
||||
|
Requirements for tools for requirements engineering, design, and product derivation |
||||
|
Information models as basis for method development |
||||
|
Applying the COTS acquisition process CAP to requirements engineering methodologies |
||||
| Feature analysis |
Identification, processing and description of features |
|||
|
|
||||
|
Handling complexity by structuring a system along a secondary decomposition according to aspects (cross-cutting features like qualities, initialisation, error handling) |
||||
|
Portability - an example for variability in the hardware platform |
||||
|
Component and interface annotations |
||||
|
|
||||
|
A Derivation Tool Chain based on Mapping Techniques & Variability Mechanisms |
||||
|
Automated Retrieval of Design Assets in a System Family Design Approach |
||||
|
|
||||
|
|
||||
|
Feature Logic-based Configuration Management Models |
||||
|
Configuration Management Process: Support & Tools for Process Support |
||||
|
|
||||
| Change Management: Managing changes of product family assets between parallel (component) projects in a product population | ||||
|
Change Management and System Family Engineering: a XML Technology Based Solution |
||||
|
Decision Model Modelling and Automatic Derivation Process Using XML Technology |
||||
|
COTS Selection Process for Product Families; Requirements-driven COTS-selection Method for Product Families |
||||
|
System Performance Modelling in UML with Properties and Metrics for Asset Selection |
||||
|
Extension plans of CMMI for system family engineering (Nokia) |
||||
|
UML Profile for Quality of Service |
||||
|
Domain-oriented software asset management |
||||
|
Derivation of Applications from Web Services |
||||
|
Evolution of System Families Interfaces |
||||
|
Design Patterns for Configuring a Product as a Specialisation of a Product Line |
||||
| Architectural Support for Dealing with Variations in a Product Family | ||||
| Recovery of Open Source Third Party Assets |
|
|||
| Tool to assess CMMI practices in any organisation in the context of SFE | ||||
| Domain architecture tool support for evolution management and variability traceability | ||||
| Architectural Modelling | Architectural Modelling in System Family Context | |||
| Requirements Management and Modelling | Requirements Management and Modelling in System Family Context | |||
| QoS Verification in Accord|UML | ||||
| CoVAR - Component selection considering Variability, Architectural concerns and Requirements | ||||
| Scenario-based Requirements Derivation for Customer-specific Applications based on a Central Variability Model | ||||
| Validation of the Extended ScenTED; Method for Scenario-based Derivation of Performance Test Cases | ||||
Requirements and Traceability in Phase 4:
| General topics
|
Natural language requirements | Natural-language techniques for Product Families Software Requirements |
| Pulse-Cave | Building domain models based on legacy system descriptions | |
| Model driven requirements engineering | ||
| Feature trees | Use case driven feature analysis and modelling | |
| Production of Domain Requirements (PIM) and Derivation of Product Requirements (PSM) | ||
| Considering Product Family Variability when Defining Product Family Applications | ||
| Objecteering/Requirements - a tool for Requirement Engineering | ||
| Requirements tool from Softeam | Requirements Management and Expression of Variability in Requirements | |
| Concept and process
|
Traceability Introduction |
An introduction to requirements traceability |
| Modelling concept for product families |
A methodology for modelling requirements and other artefacts in product family engineering to support traceability |
|
| Requirements engineering for System Families |
Analysis of commonality, variability and volatility in the requirements specifications |
|
| Requirements Management Improvements | ||
| Adapting RE Processes to Systems Families - Development by Means of Scenarios | ||
| Requirements Engineering for Dynamic Markets | ||
| Document automation and document access | ||
| Traceability
|
Requirements traceability and SPLIT |
Introduction to requirements management and traceability and the approach in SPLIT |
| Trace capture |
Scenario-centred trace structuring |
|
| Trace usage guide |
How to use trace information for change integration |
|
| Document consistency and traceability | ||
| Meta model traceability |
Traceability from domain characteristics to architecture components |
|
| Traceability Softeam | Traceability core metamodel as UML extension in Objecteering/UML modelling tool | |
| Feature change management |
System feature (change) management in a MultiX environment |
|
| Managing System-Level Asset Bases | ||
| Case studies
|
Reference requirements for product lines: medical domain |
A class model for the requirements of the medical domain, with all variations for all products |
| Reference requirements of switch maintenance |
Application of the SPLIT method on operations, administration and maintenance for standards like UMTS, GSM, GPRS, Edge |
|
| Reference requirements of air supervision systems |
Application of the SPLIT method on air supervision systems |
Architecture Aspects for Phase 4:
|
Product Derivation
|
Product Line Behavioural Synthesis (PliBS) |
| Quality Variability Techniques for Dynamic Derivation | |
| Model Transformation Tool for System Families (UMT for System Families) |
|
Method |
Topic |
|||
|
Domain engineering methods description, analysis, comparison |
||||
|
Conceptual domain analysis, introduction to domain analysis |
||||
|
The product line software engineering method from Fraunhofer IESE |
||||
|
Model-based value engineering from Siemens |
||||
|
Description of SW architecture assessment techniques + EPOC assessment report + architecture metrics |
||||
|
Assessment guidelines for detecting architectural mismatches during systems composition |
||||
|
Extraction of software architecture models from the system implementation |
||||
|
A Method for Module Architecture verification and its application on a large component-based system |
||||
|
Requirements description and categorisation + configuration and deployment onto an execution platform + examples for switch maintenance and air supervision systems + prototype |
||||
|
Aspect Analysis |
Thales: Air supervision
systems |
Alcatel: Switch
maintenance systems |
||
|
Handling commonalities and variability |
||||
|
A meta model for architectural design, based on a requirements model from HUT |
||||
|
Case studies + lessons learned
|
Alcatel: The case study on OAM, applied on architecture design (SPLIT/DAISY) |
|||
|
Combitech: experiences with reference architecture design for 2 product families |
||||
|
Philips case study on medical imaging, see also RE case study |
||||
|
Sainco case study for supervisory control and data acquisition systems |
||||
|
A Laboratory Experiment to Study Component Functionality in a MetaCase Environment (Jyväskylä) |
||||
|
Using aspects-based secondary decompositions for system development. Example from the medical domain. |
||||
|
Rapid architecting: functional decomposition and architecture synthesis |
||||
|
Using coloured Petri nets to evaluate aspects (reliability, performance) by simulation and formal analysis |
||||
|
Use-case-based method guidance process (and use-case templates) |
||||
|
Change Management
|
Architecture evolution | |||
| Change management from a logistic viewpoint | ||||
|
|
||||
|
Portability - an example for variability in the hardware platform |
||||
|
|
||||
|
Information models as basis for method development |
||||
|
Analysing the evolution of large OO-systems using metrics |
||||
|
F eature-driven software logistics |
||||
|
Formal Method to Evaluate Aspects (Reliability, Performance) by Simulation and Formal Analysis |
||||
|
Requirements for tools for requirements engineering, design, and product derivation |
||||
|
Architecture
|
||||
| PSM Layer | Platform Independent and Platform Specific Modelling: Approaches for the PSM layer | |||
| PIM to PSM | Platform Independent and Platform Specific Modelling: PIM to PSM Transformation | |||
| Platform Independent and Platform Specific Modelling: Tools for model transformation | ||||
| Concurrency design in PF Reference and Specific Product Architecture | ||||
| Reverse Engineering of Specific Product Architecture and Abstraction of PF Reference Architecture | ||||
| Architectural Support for Dealing with Variations in a Product Family | ||||
| V-Architect | Domain architecture tool support for evolution management and variability traceability | |||
| Integration of Third Party Assets | ||||
| Quality Variability Techniques for Dynamic Derivation | ||||
| Architectural Modelling | Architectural Modelling in System Family Context | |||
| Security SF LC Model and Traceability | ||||
| A Reference Architecture for Security in System Families | ||||
| ART | UML architecture model validation and model operation tool | |||
|
Migration of existing system assets to families |
||||
| Testing and validation |
|
|||
|
UML model simulation based on the UMLAUT framework |
||||
|
Domain-oriented software asset management |
||||
|
Evolution of System Families Interfaces |
||||
|
|
||||
|
|
||||
|
Feature Logic-based Configuration Management Models |
||||
|
Configuration Management Process: Support & Tools for Process Support |
||||
|
Building domain models based on legacy system descriptions |
||||
|
|
||||
|
Decision Model Modelling and Automatic Derivation Process Using XML Technology |
||||
|
COTS Selection Process for Product Families; Requirements-driven COTS-selection Method for Product Families |
||||
|
System Performance Modelling in UML with Properties and Metrics for Asset Selection |
||||
|
Extension plans of CMMI for system family engineering (Nokia) |
||||
|
UML Profile for Quality of Service |
||||
|
|
||||
|
Change Management: Managing changes of product family assets between parallel (component) projects in a product population |
||||
|
|
||||
|
A Derivation Tool Chain based on Mapping Techniques & Variability Mechanisms |
||||
|
Automated Retrieval of Design Assets in a System Family Design Approach |
||||
|
Design Patterns for Configuring a Product as a Specialisation of a Product Line |
||||
|
Modeling of PF Reference Behaviour and Derivation of Specific Product Behaviour Models |
||||
|
|
||||
| PLiBS | Product Line Behavioural Synthesis (PliBS) | |||
| Aspects Weaver | ||||
| From requirements to test cases | ||||
| MDE Components Specification | ||||
| SAL3 | Tool to assess CMMI practices in any organisation in the context of SFE | |||
| QoS Verification in Accord|UML | ||||
| CoVAR | CoVAR - Component selection considering Variability, Architectural concerns and Requirements | |||
| Scenario-based Derivation of Performance Test Cases | ||||
| ScenTED | Validation of the Extended ScenTED; Method for Scenario-based Derivation of Performance Test Cases | |||
| Dealing with Architectural Variation in Product Populations | ||||
| Using MDA for Automotive Product Line Engineering | ||||
Requirements and Traceability in Phase 5:
| General topics | Requirements tool from Softeam | Requirements Management and Expression of Variability in Requirements |
| Concept and process
|
Traceability Introduction |
An introduction to requirements traceability |
| Modelling concept for product families |
A methodology for modelling requirements and other artefacts in product family engineering to support traceability |
|
| Requirements engineering for System Families |
Analysis of commonality, variability and volatility in the requirements specifications |
|
| Document automation and document access | ||
| Requirements Management and Modelling | Requirements Management and Modelling in System Family Context | |
| Traceability
|
Traceability between system variants and reused components |
The traceability mechanisms applied at Philips Medical for legal and business purposes |
| Trace capture |
Scenario-centred trace structuring |
|
| Trace usage guide |
How to use trace information for change integration |
|
| Traceability-based decision support |
Proposal for a commitment traceability network for identifying the persons/roles who have a responsibility in a system development program |
|
| Document consistency and traceability | ||
| Traceability Softeam | Traceability core metamodel as UML extension in Objecteering/UML modelling tool | |
| Feature change management |
System feature (change) management in a MultiX environment |
|
| Case studies
|
Reference requirements for product lines: medical domain |
A class model for the requirements of the medical domain, with all variations for all products |
| Reference requirements of switch maintenance |
Application of the SPLIT method on operations, administration and maintenance for standards like UMTS, GSM, GPRS, Edge |
|
| Reference requirements of air supervision systems |
Application of the SPLIT method on air supervision systems |
8. Methods for Phase 6: Domain Implementation
|
Method |
Topic |
|
|
Analysing the evolution of large OO-systems using metrics |
||
|
Extraction of software architecture models from the system implementation |
||
|
Introduction to traceability methods |
||
|
Requirements description and categorisation + configuration and deployment onto an execution platform + examples for switch maintenance and air supervision systems + prototype |
||
|
Analysis, classification, description and administration of assets and their dependencies |
||
|
Components
|
Analysis, classification, description and administration of assets and their dependencies |
|
|
Asset-based meta model of software components for product derivation |
||
|
Using semantic interface annotations to find the right components and use them adequately |
||
| Semantic Interface Annotations |
Semantic Component Interface Annotations for Realisation Support |
|
|
How to describe components, interfaces and information models as main parts of a platform |
||
|
Platform-neutral specification of real-time behaviour and logical specification of functionality of components |
||
|
Automatic component configuration by program specialisation |
||
|
Variability and commonality in component platforms |
||
|
How to describe components and their attributes in a platform |
||
|
Solving problems with the composition of OO-Frameworks for product families |
||
| Version Management |
Configuration and Version Management for Component Based Product Families |
|
| Components | See Component Tree | |
|
|
||
|
Handling commonalities and variability |
||
|
Requirements for tools for requirements engineering, design, and product derivation |
||
|
Traceability
|
Trace usage guide | |
|
Information models as basis for method development |
||
|
Change management from a logistic viewpoint |
||
|
F eature-driven software logistics |
||
|
The notion of variability in software product lines |
||
|
Generation of Specific Product code |
||
|
Modeling of PF Reference Behaviour and Derivation of Specific Product Behaviour Models |
||
|
Configuration Management Process: Support & Tools for Process Support |
||
|
Feature Logic-based Configuration Management Models |
||
|
Evolution of System Families Interfaces |
||
|
Automated Retrieval of Design Assets in a System Family Design Approach |
||
|
|
||
|
Migration of existing system assets to families |
||
|
A Laboratory Experiment to Study Component Functionality in a MetaCase Environment |
||
| Architecture Aspects |
|
|
| Test and validation |
|
|
| PLiBS | Product Line Behavioural Synthesis (PliBS) | |
| MDE Components Specification | ||
| SAL3 | Tool to assess CMMI practices in any organisation in the context of SFE | |
| V-Architect | Domain architecture tool support for evolution management and variability traceability | |
| Scenario-based Derivation of Performance Test Cases | ||
| ScenTED | Validation of the Extended ScenTED Method for Scenario-based Derivation of Performance Test Cases | |
Test and Validation Aspects for Phase 6:
Architecture Aspects for Phase 6:
9. Methods for Phase 7: System Definition
|
Method |
Topic |
|
|
Extraction of software architecture models from the system implementation |
||
|
Using aspects - based secondary decompositions for system development. Example from the medical domain. |
||
|
Requirements and Traceability
|
||
| Modelling concept | ||
| From requirements to test cases | ||
|
Requirements description and categorisation + configuration and deployment onto an execution platform + examples for switch maintenance and air supervision systems + prototype |
||
|
Analysis, classification, description and administration of assets and their dependencies |
||
|
Scoping
|
||
|
Scoping: General description of scoping, references to methods and tools |
||
|
Scoping in the presence of multiple domains and product populations |
||
|
Specification for a Product Family Scoping Approach and its Integration in a Tool Workbench |
||
|
Scoping Software Product Lines for the Business Context - Agility |
||
|
Variability representation and resolution in SPLIT/Cloud and SPLIT/Ladder |
||
|
Handling commonalities and variability |
Architecture aspects | |
|
Product derivation |
Selection, derivation, and parameterisation of variants with MoVE |
Product derivation with SPLIT |
|
Information models as basis for method development |
||
Introduction to change management - process and categories |
||
| Feature analysis |
Identification, processing and description of features |
|
| Variability resolution |
Variability representation and resolution in SPLIT/Cloud and SPLIT/Ladder |
|
|
Model-based value engineering from Siemens |
||
|
Organisation Structures for Product-Family Engineering |
||
|
Planning process for product families |
||
|
Product Management Assessment w.r.t. Product-Family Engineering |
||
|
Specification for an integrated product family economic model |
||
|
|
||
|
Feature Logic-based Configuration Management Models |
||
|
Configuration Management Process Support & Tools for Process Support |
||
|
|
||
| Tool to assess CMMI practices in any organisation in the context of SFE | ||
| Scenario-based Requirements Derivation for Customer-specific Applications based on a Central Variability Model | ||
| Model Transformation Tool for System Families (UMT for System Families) | ||
10. Methods for Phase 8: System Economical Analysis
|
Method |
Topic |
|
|
Extraction of software architecture models from the system implementation |
||
|
Using aspect-based secondary decompositions for system development. Example from the medical domain. |
||
|
Introduction to traceability methods |
||
|
Requirements description and categorisation + configuration and deployment onto an execution platform + examples for switch maintenance and air supervision systems + prototype |
||
|
Analysis, classification, description and administration of assets and their dependencies |
||
|
Scoping
|
||
| Variability representation techniques |
The notion of variability in software product lines |
|
| Variant configuration and derivation support | Variability representation and resolution in SPLIT/Cloud and SPLIT/Ladder | |
|
Handling commonalities and variability |
||
|
Information models as basis for method development |
||
| Feature analysis |
Identification, processing and description of features |
|
|
Use-case-based method guidance process (and use-case
templates) |
||
|
Organisation Structures for Product-Family Engineering |
||
|
Planning process for product families |
||
|
Product Management Assessment w.r.t. Product-Family Engineering |
||
|
Specification for an integrated product family economic model |
||
|
|
||
|
Feature Logic-based Configuration Management Models |
||
|
Configuration Management Process Support & Tools for Process Support |
||
|
The Stage Growth Framework for a Software Product Business |
||
|
Integrated cost and investment model for product family development |
||
|
|
||
|
Estimating (Future) Product Viability: A platform Development reasoning Model |
||
|
Requirements and traceability |
Trace usage guide | |
| Tool to assess CMMI practices in any organisation in the context of SFE | ||
11. Methods for Phase 9: System Analysis / Design
| Method | Topic | |||||
| Traceability | Introduction to traceability methods | |||||
| SPLIT - Software Product-Line Integrated Technology | Requirements description and categorisation + configuration and deployment onto an execution platform + examples for switch maintenance and air supervision systems + prototype | |||||
| Asset management | Analysis, classification, description and administration of assets and their dependencies | |||||
| Processes for system-family engineering | ||||||
| QuESt | Rapid architecting: functional decomposition and architecture synthesis | |||||
| Intelligent retrieval of domain assets | How to find the best-suited assets to derive a product (design management) | |||||
| Variability representation techniques |
The notion of variability in software product lines |
|||||
| Variant configuration and derivation support | Variability representation and resolution in SPLIT/Cloud and SPLIT/Ladder | |||||
|
Handling commonalities and variability |
A Unified Conceptual Model for Product Family Variability Modelling |
|||||
| Product derivation | Selection, derivation, and parameterisation of variants with MoVE | Derivation process | ||||
| Product derivation with SPLIT | Product instantiation case study | |||||
| Information models | Information models as basis for method development | |||||
| Feature analysis | Identification, processing and description of features | |||||
| COTS assessment | Applying the COTS acquisition process CAP to requirements engineering methodologies and to MoRE/SLATE | |||||
| Design Management | Intelligent Retrieval of Domain Assets | |||||
| Tool requirements | Requirements for tools for requirements engineering, design, and product derivation | |||||
| Web Services | Derivation of Applications from Web Services | |||||
| Method guidance | Use-case-based method guidance process (and use-case templates) | |||||
| Configuration management process | Configuration Management Process Support & Tools for Process Support | |||||
| Agile product line engineering | ||||||
| Feature Logic | Feature Logic-based Configuration Management Models | |||||
| Decision Model | Decision Model Modelling and Automatic Derivation Process Using XML Technology | |||||
| RE-driven COTS selection | COTS Selection Process for Product Families; Requirements-driven COTS-selection Method for Product Families | |||||
| Performance Modelling | System Performance Modelling in UML with Properties and Metrics for Asset Selection | |||||
| CMMI-SFE Nokia | Extension plans of CMMI for system family engineering (Nokia) | |||||
| Change-Management-ESI | Change Management and System Family Engineering: a XML Technology Based Solution | |||||
| Performance analysis models | ||||||
| Architecture Aspects for Phase 9 | ||||||
| Change Management
|
Introduction | Change management for requirements and reuse objects | ||||
| Cost of change requests in a system product program | Change management for parallel projects | |||||
| Requirements and Traceability in Phase 9 | ||||||
| Testing and validation | ||||||
| Transition process | ||||||
| Requirements PFE tools | ||||||
| PLiBS | Product Line Behavioural Synthesis (PliBS) | |||||
| Aspects Weaver | ||||||
| PIM and PSM Modelling | ||||||
| MDE Components Specification | ||||||
| MOF 2.0 Query/View/Transformation | ||||||
| MDFE Case Study | Toward the model-driven engineering of large scale systems in THALES - A MDFE case study in the Air-Traffic Management field | |||||
| SAL3 | Tool to assess CMMI practices in any organisation in the context of SFE | |||||
| Variability Management in Accord|UML | ||||||
| CoVAR | CoVAR - Component selection considering Variability, Architectural concerns and Requirements | |||||
| Scenario-based Requirements Derivation | Scenario-based Requirements Derivation for Customer-specific Applications based on a Central Variability Model | |||||
| Scenario-based Derivation of Performance Test Cases | ||||||
| ScenTED | Validation of the Extended ScenTED Method for Scenario-based Derivation of Performance Test Cases | |||||
| Quality-Aware Model Transformation | ||||||
| DSL for model to code generation | ||||||
Requirements and Traceability in Phase 9:
| General topics
|
Natural language requirements | Natural-language techniques for Product Families Software Requirements |
| Requirements tool from Softeam | Requirements Management and Expression of Variability in Requirements | |
| Model driven requirements engineering | ||
| Feature trees | Use case driven feature analysis and modelling | |
| Considering Product Family Variability when Defining Product Family Applications | ||
| Objecteering/Requirements - a tool for Requirement Engineering | ||
| From requirements to test cases | ||
| Improve quality of domain requirements | ||
| Concept and process
|
Traceability Introduction |
An introduction to requirements traceability |
| Modelling concept for product families |
A methodology for modelling requirements and other artefacts in product family engineering to support traceability |
|
| Requirements Management Improvements | ||
| Adapting RE Processes to Systems Families - Development by Means of Scenarios | ||
| Requirements Engineering for Dynamic Markets | ||
| Document automation and document access | ||
| Traceability
|
Traceability between system variants and reused components |
The traceability mechanisms applied at Philips Medical for legal and business purposes |
| Requirements traceability support and SPLIT |
Introduction to requirements management and traceability and the approach in SPLIT |
|
| Trace capture |
Scenario-centred trace structuring |
|
| Trace usage guide |
How to use trace information for change integration |
|
| Traceability-based decision support |
Proposal for a commitment traceability network for identifying the persons/roles who have a responsibility in a system development program |
|
| Document consistency and traceability | ||
| Traceability Softeam | Traceability core metamodel as UML extension in Objecteering/UML modelling tool | |
| Feature change management |
System feature (change) management in a MultiX environment |
|
| Managing System-Level Asset Bases | ||
| Change Management Philips | Change Management: Managing changes of product family assets between parallel (component) projects in a product population | |
| Case studies | Reference requirements for product lines: medical domain |
A class model for the requirements of the medical domain, with all variations for all products |
Architecture Aspects for Phase 9:
12. Methods for Phase 10: Application Analysis
| Method | Topic | |||||
| Evolution of OO-systems | Analysing the evolution of large OO-systems using metrics | |||||
| Traceability | Introduction to traceability methods | |||||
| SPLIT - Software Product-Line Integrated Technology | Requirements description and categorisation + configuration and deployment onto an execution platform + examples for switch maintenance and air supervision systems + prototype | |||||
| Asset management | Analysis, classification, description and administration of assets and their dependencies | |||||
|
Components
|
Asset management | Analysis, classification, description and administration of assets and their dependencies | ||||
| Component and interface annotations | Using semantic interface annotations to find the right components and use them adequately | |||||
| Real Time | Specification of Functional and Real-Time Behaviour of Components | |||||
| Processes for system-family engineering | ||||||
| Intelligent retrieval of domain assets | How to find the best-suited assets to derive a product (design management) | |||||
| Variability representation techniques |
The notion of variability in software product lines |
|||||
| Variant configuration and derivation support | Variability representation and resolution in SPLIT/Cloud and SPLIT/Ladder | |||||
|
Handling commonalities and variability |
||||||
| Software logistics | Feature-driven software logistics | |||||
| Architecture
|
Architecture Assessment | |||||
| Architecture Mismatch Analysis | ||||||
| Configuration and Derivation of Product Architectures | ||||||
| Reliability and safety: Annotated catalogue of patterns for reliability and safety | ||||||
| Architectural Support for Dealing with Variations in a Product Family | ||||||
| Security Issues in Dynamically Deployable System Families | ||||||
| Quality Variability Techniques for Dynamic Derivation | ||||||
| Recovery of Open Source Third Party Assets | ||||||
| Architectural Modelling | ||||||
| Asset recovery in System Family | ||||||
| Security SF LC Model and Traceability | ||||||
| Product derivation
|
Selection, derivation, and parameterisation of variants with MoVE | Product derivation with SPLIT | ||||
| Derivation process | Product instantiation case study | |||||
| Feature analysis | Identification, processing and description of features | |||||
| COTS assessment | Applying the COTS acquisition process CAP to requirements engineering methodologies and to MoRE/SLATE | |||||
| Information models | Information models as basis for method development | |||||
| Coloured petri nets | Formal Method to Evaluate Aspects (Reliability, Performance) by Simulation and Formal Analysis | |||||
| Design Management | Intelligent Retrieval of Domain Assets | |||||
| Method guidance | Use-case-based method guidance process (and use-case templates) | |||||
| Requirements and traceability | ||||||
|
Change management
|
Introduction | Change management for requirements and reuse objects | Change management for parallel projects | |||
| Cost of change requests in a system product program | Change management from a logistic viewpoint | Change Management and System Family Engineering: a XML Technology Based Solution | ||||
| Test and Validation in Phase | ||||||
| Tool requirements | Requirements for tools for requirements engineering, design, and product derivation | |||||
| Variability model | Design Patterns for Configuring a Product as a Specialisation of a Product Line | |||||
| Performance analysis models | ||||||
| Interface Evolution | Evolution of System Families Interfaces | |||||
| Asset Retrieval | Automated Retrieval of Design Assets in a System Family Design Approach | |||||
| Mapping Techniques | A Derivation Tool Chain based on Mapping Techniques & Variability Mechanisms | |||||
| Web services | Derivation of Applications from Web Services | |||||
| PIM and PSM Modelling | ||||||
| MDE Components Specification | ||||||
| MOF 2.0 Query/View/Transformation | ||||||
| SAL3 | Tool to assess CMMI practices in any organisation in the context of SFE | |||||
| QoS Verification in Accord|UML | ||||||
| CoVAR | CoVAR - Component selection considering Variability, Architectural concerns and Requirements | |||||
| Scenario-based Requirements Derivation | Scenario-based Requirements Derivation for Customer-specific Applications based on a Central Variability Model | |||||
| Scenario-based Derivation of Performance Test Cases | ||||||
| ScenTED | Validation of the Extended ScenTED Method for Scenario-based Derivation of Performance Test Cases | |||||
| Quality-Aware Model Transformation | ||||||
| DSL for model to code generation | ||||||
Requirements and Traceability in Phase 10:
| General topics
|
Natural language requirements | Natural-language techniques for Product Families Software Requirements |
| Model driven requirements engineering | ||
| Feature trees | Use case driven feature analysis and modelling | |
| Considering Product Family Variability when Defining Product Family Applications | ||
| Objecteering/Requirements - a tool for Requirement Engineering | ||
| Concept and process
|
Traceability Introduction |
An introduction to requirements traceability |
| Modelling concept for product families |
A methodology for modelling requirements and other artefacts in product family engineering to support traceability |
|
| Requirements Management Improvements | ||
| Adapting RE Processes to Systems Families - Development by Means of Scenarios | ||
| Requirements Engineering for Dynamic Markets | ||
| Requirements Management and Modelling | Requirements Management and Modelling in System Family Context | |
| Traceability
|
Traceability between system variants and reused components |
The traceability mechanisms applied at Philips Medical for legal and business purposes |
| Requirements traceability support and SPLIT |
Introduction to requirements management and traceability and the approach in SPLIT |
|
| Trace capture |
Scenario-centred trace structuring |
|
| Trace usage guide |
How to use trace information for change integration |
|
| Traceability-based decision support |
Proposal for a commitment traceability network for identifying the persons/roles who have a responsibility in a system development program |
|
| Case studies | Reference requirements for product lines: medical domain |
A class model for the requirements of the medical domain, with all variations for all products |
Test and Validation in Phase 10:
13. Methods for Phase 11: Application Design
| Method | Topic | |||||
| Evolution of OO-systems |
Analysing the evolution of large OO-systems using metrics |
|||||
| Traceability | Introduction to traceability methods | |||||
| SPLIT - Software Product-Line Integrated Technology | Requirements description and categorisation + configuration and deployment onto an execution platform + examples for switch maintenance and air supervision systems + prototype | |||||
| Asset management | Analysis, classification, description and administration of assets and their dependencies | |||||
| Components | ||||||
| Intelligent retrieval of domain assets | How to find the best-suited assets to derive a product (design management) | |||||
| Variability representation techniques |
The notion of variability in software product lines |
|||||
| Variant configuration and derivation support | Variability representation and resolution in SPLIT/Cloud and SPLIT/Ladder | |||||
| Handling commonalities and variabilities (including variability resolution) | Scoping aspects | Architecture aspects | ||||
| Software logistics | Feature-driven software logistics | |||||
| Product derivation | Selection, derivation, and parameterisation of variants with MoVE | Product derivation with SPLIT | ||||
| Derivation process | Product instantiation case study | |||||
| Decision Model | Decision Model Modelling and Automatic Derivation Process Using XML Technology | |||||
| RE-driven COTS selection | COTS Selection Process for Product Families; Requirements-driven COTS-selection Method for Product Families | |||||
| CMMI-SFE Nokia | Extension plans of CMMI for system family engineering (Nokia) | |||||
| Design Management | Intelligent Retrieval of Domain Assets | |||||
| Tool requirements | Requirements for tools for requirements engineering, design, and product derivation | |||||
| Modelling concept for product families | A methodology for modelling requirements and other artefacts in product family engineering to support traceability | |||||
| Information models | Information models as basis for method development | |||||
| Coloured petri nets | Formal Method to Evaluate Aspects (Reliability, Performance) by Simulation and Formal Analysis | |||||
| Testing and validation | ||||||
|
Change management
|
Introduction | Change management for requirements and reuse objects | Change management for parallel projects | |||
| Cost of change requests in a system product program | Change management from a logistic viewpoint | |||||
| Scoping
|
QuESt | Rapid Architecting: functional decomposition and architecture synthesis | ||||
| Method guidance | Use-case-based method guidance process (and use-case templates) | |||||
| Handling commonalities and variabilities | ||||||
| Process and process frameworks | ||||||
| Architecture Aspects | ||||||
| Requirements and Traceability Aspects | ||||||
| Performance Modelling | System Performance Modelling in UML with Properties and Metrics for Asset Selection | |||||
| Performance analysis models | ||||||
| Interface Evolution | Evolution of System Families Interfaces | |||||
| Asset Retrieval | Automated Retrieval of Design Assets in a System Family Design Approach | |||||
| Mapping Techniques | A Derivation Tool Chain based on Mapping Techniques & Variability Mechanisms | |||||
| Web services | Derivation of Applications from Web Services | |||||
| Behaviour Models | Modeling of PF Reference Behaviour and Derivation of Specific Product Behaviour Models | |||||
| Jyväskylä Case Study | A Laboratory Experiment to Study Component Functionality in a MetaCase Environment | |||||
| PLiBS | Product Line Behavioural Synthesis (PliBS) | |||||
| Aspects Weaver | ||||||
| PIM and PSM Modelling | ||||||
| MDE Components Specification | ||||||
| MOF 2.0 Query/View/Transformation | ||||||
| Architectural Support for Dealing with Variations in a Product Family | ||||||
| SAL3 | Tool to assess CMMI practices in any organisation in the context of SFE | |||||
| QoS Verification in Accord|UML | ||||||
| CoVAR | CoVAR - Component selection considering Variability, Architectural concerns and Requirements | |||||
| Scenario-based Derivation of Performance Test Cases | ||||||
| ScenTED | Validation of the Extended ScenTED Method for Scenario-based Derivation of Performance Test Cases | |||||
| Quality-Aware Model Transformation | ||||||
| DSL for model to code generation | ||||||
| Using MDA for Automotive Product Line Engineering | ||||||
Architecture Aspects for Phase 11:
Requirements and Traceability in Phase 11:
| Concept and process
|
Traceability Introduction |
An introduction to requirements traceability |
| Requirements Management and Modelling | Requirements Management and Modelling in System Family Context | |
| Traceability
|
Traceability between system variants and reused components |
The traceability mechanisms applied at Philips Medical for legal and business purposes |
| Trace capture |
Scenario-centred trace structuring |
|
| Trace usage guide |
How to use trace information for change integration |
|
| Traceability-based decision support |
Proposal for a commitment traceability network for identifying the persons/roles who have a responsibility in a system development program |
|
| Traceability Softeam | Traceability core metamodel as UML extension in Objecteering/UML modelling tool | |
| Feature change management |
System feature (change) management in a MultiX environment |
|
| Managing System-Level Asset Bases | ||
| Change Management Philips | Change Management: Managing changes of product family assets between parallel (component) projects in a product population | |
| Case studies | Reference requirements for product lines: medical domain |
A class model for the requirements of the medical domain, with all variations for all products |
14. Methods for Phase 12: Application Implementation
| Method | Topic | |
| Evolution of OO-systems |
Analysing the evolution of large OO-systems using metrics |
|
| SPLIT - Software Product-Line Integrated Technology |
Requirements description and categorisation + configuration and deployment onto an execution platform + examples for switch maintenance and air supervision systems + prototype |
|
| Asset management |
Analysis, classification, description and administration of assets and their dependencies |
|
| Components | ||
|
Scoping
|
Process Frameworks for System Familiy Engineering | |
| Method guidance | ||
| Intelligent retrieval of domain assets |
How to find the best-suited assets to derive a product (design management) |
|
| Variability resolution | Variability representation and resolution in SPLIT/Cloud and SPLIT/Ladder | |
| Variant configuration and derivation support | Variability representation and resolution in SPLIT/Cloud and SPLIT/Ladder | |
| Handling commonalities and variabilities (including variability resolution) | Scoping aspects | Architecture aspects |
| Software logistics | Feature-driven software logistics | |
| Selection, derivation, and parameterisation of variants with MoVE | Using model-based value engineering (MoVE) for product derivation | |
| Configuration management process | Configuration Management Process Support & Tools for Process Support | |
| Design Management | Intelligent Retrieval of Domain Assets | |
| Change management from a logistic viewpoint | Logistic Issues in change management | |
| Information models | Information models as basis for method development | |
| Asset Retrieval | Automated Retrieval of Design Assets in a System Family Design Approach | |
| Interface Evolution | Evolution of System Families Interfaces | |
| Agile product line engineering | ||
| Feature Logic | Feature Logic-based Configuration Management Models | |
| Behaviour Models | Modeling of PF Reference Behaviour and Derivation of Specific Product Behaviour Models | |
| Jyväskylä Case Study | A Laboratory Experiment to Study Component Functionality in a MetaCase Environment | |
| Code generation | Generation of Specific Product code | |
| Transition process | ||
| Requirements and
traceability
|
Traceability Introduction | |
| Trace usage guide | ||
| Traceability-based decision support | ||
| Architecture
|
Component Generalization: Generalization of a Framework | Component Generalization in Product Families: Generalization of a Framework to a wider scope |
| Component Generalization: Operating System Abstraction | Component Generalization in Product Families: Introduction of an Operating System Abstraction | |
| Concurrency design | Concurrency design in PF Reference and Specific Product Architecture | |
| Architecture Recovery | Reverse Engineering of Specific Product Architecture and Abstraction of PF Reference Architecture | |
| UMLAUT simulation | UML model simulation based on the UMLAUT framework | |
| Security SF LC Model and Traceability | ||
| Test and validation | ||
| PLiBS | Product Line Behavioural Synthesis (PliBS) | |
| PIM and PSM Modelling | ||
| MDE Components Specification | ||
| MOF 2.0 Query/View/Transformation | ||
| IESE PuLSE-MDD | ||
| SAL3 | Tool to assess CMMI practices in any organisation in the context of SFE | |
| Scenario-based Derivation of Performance Test Cases | ||
| ScenTED | Validation of the Extended ScenTED Method for Scenario-based Derivation of Performance Test Cases | |
| Quality-Aware Model Transformation | ||
| DSL for model to code generation | ||
Test and Validation in Phase 12:
|
This section lists the documents that have been considered for the contents of this report, together with keywords characterising the documents' contents. These keywords are also a way to retrieve methods for system family engineering. Click into the icon. |
|
