MPLM: MaTeLo Product Line Manager
The interest of this functionality is to have a “generic” test model associated to a product line system (for example “air conditioning”) and to extract from it a “specific” test model called usage model variant dedicated to a specific product system (for instance “air conditionning for a vehicule x”). By this way ,it is not necessary to have test models for each product but only one master test model of the product family.
The variability of the system is described with Orthogonal Variability Model (OVM formalism), with the help of Remidemmi Editor. An OVM model contains the following elements:
- Variability Points (VP)
- Variants (V) (Features)
- Variability dependencies (to associate Variability points to variants)
- Constraints (to specify interactions between the various functionalities of the variability model, for instance: require and exclude)
Figure 1: OVM model
The main functionality of MPLM consist of deriving variants of usage models dedicated to a set of configured variants from a master usage model that represent a product line.
MPLM allows to configure the product line by linking requirements with features and to configure the product list in order to be able to derive usage models variants.
Figure 2: Main steps
The links between the variability model and the test models are done thanks to the requirements. As OVM doesn’t permit traceability with the requirements, this action is done with MPLM perspective.
The configuration of the products consists in defining the different products groups and linking variants to each product feature.
Feature: “A distinguishing characteristic of a software item (e.g., performance, portability, or functionality).”
Product: A unique system or software.
Products line: A set of software-intensive systems that share a common, managed set of features satisfying the specific needs of a particular market segment or mission and that are developed from a common set of core assets in a prescribed way.
Requirement: A singular documented physical and functional need that a particular product or service must be or perform.
Usage Model: State/Event diagram which models the system external behavior system in a black box manner. It is represented thanks to states and events that define test data and usage frequencies. A usage model is made of graphs related each other by hierarchical inclusions relationships.
MPLM is integrated as a perspective in MaTeLo tool. It is possible to use this functionality to configure a strategy which permit then to create from a Master test model some products test models in an independent way.
However, when you want to generate the products test models, the master model has to be opened in the Edition perspective.
- Open the MPLM perspective
- Create or open a MPLM project
- Edit if necessary:
- Variability model to add links between variants and requirements
- Product configurations by adding variants to each product
- Edit strategies
- After selection (opening) of a Master test model in the edition perspective, generate, according a strategy.
- New test models are generated in the Edition perspective.
Select from the file menu, the “new item” and select afterwards “MPLM project”.
Figure 3: New MPLM project
To create a MPLM project you need to select a requirements file (for example “.requirementslibrary)”. The requirements library is based on a XML format compliant with MaTeLo format. It can contain the same list as the master project or can contain more requirements concerning different domains of the product line.
You need also to select an OVM model (created with remidemmi): “security.ovm”.
Then you have to choose the name or your MPLM project: “Security MPLM”.
Figure 4: configuration of the MPLM project
You need to create links between variability elements and requirements library. To do so, right click on the variability model node and add a new relation between a variant and a requirement.
Figure 5: Edit variability model
To edit this relation (from the properties view), you need to select for each variant (field key), the list of requirements related with the variant (field value).
The first level defines the domain. A domain is a group of products. You can create a new one with a right click on the Product line node.
The second level is the list of products of a specific domain.
Figure 6: create new products
To configure a specific product you have to define a set of valid variants combinations. You can add a new variant to a product (right click, new “Variant Relation”) to the list of variants and from the properties view you fill the “Variation Element” field (the appropriate variation element).
Figure 7: Product configuration
A generation strategy memorizes a list of products. When you generate according to a strategy, a test model is generated for each product linked to the strategy.
As other MaTeLo functionalities, this list of products is configured thanks to the properties view.
Figure 8: Strategy configuration and test models generation
Copyright © 1998- 2014 ALL4TEC. All rights reserved unless otherwise stated.