Manual. PREEvision. Variant management Version 5.0 Beta English

Transcription

1 Manual PREEvision Variant management Version 5.0 Beta English

2 Imprint Vector Informatik GmbH Ingersheimer Straße Stuttgart, Germany The information and data contained in this documentation may be changed without prior notice. Without the express written permission of Vector Informatik GmbH, no part of these documents may be duplicated or transmitted for any purpose, regardless of the manner or medium, electronic or mechanical, in which this occurs. All technical details, drawings, etc. are subject to the protection of copyright law. Copyright 2011, Vector Informatik GmbH. Printed in Germany. All rights reserved.

3 Contents Contents 1 Variant management concepts Variant management artifacts Basic knowledge: the variant management structure 8 2 Variant management perspective VM Architecture View VM Group Structure Variant Structure VM Propagation Rule Preview Template View Set Content View Conflict highlighting and solving in the Set Content View Template Compare View Variant Rule Group View 27 3 Variant preferences 31 4 The variant management example 33 5 Step 1: Creating a variant model 35 6 Step 2: Creating feature concepts for the variant 37 7 Step 3: Defining variant configurations Variant permutation Refining variants 42 8 Step 4: Connecting the variant model with the E/E model 45 9 Step 5: Creating variant conditions About guards Step 6: Using of variants Working with the variant diagram Using parameters variant specific 65 Vector Informatik GmbH Version 5.0 Beta - 3 -

4 Contents 13 Propagating variants 67 Index Version 5.0 Beta Vector Informatik GmbH

5 Variant management concepts Variant management concepts Overview The variant management provides a highly configurable mechanism to model variants based on the E/E architecture. Product lines of an E/E architecture are modeled in PREEvision as 150%-model that mean the model includes all components that can be tailored into different subsets. These subsets the variants are representing specific products of one product line. Equipment aspects of variant management Technical aspects of variant management Use Cases The equipment part is used for specifying which features should be included in an architecture variant as standard equipment and which are to be optional. A single type may have more than one equipment concept available. A common example is the availability of low and high equipment concepts. As equipment concepts determine what to include in an architecture variant, technical concepts represent the implementation itself. Thus, equipment concepts build one starting point for architecture analysis. In development projects, hundreds of thousands of architecture artifacts represent a single type product. For product line architecture, the number of artifacts is higher although the reuse of common parts avoid a linear growth over the number of product types. To keep track of all the artifacts and their composition to at least parts of technical concepts the artifacts can be structured in sets. These sets can be composed to technical alternatives for each of the concepts to be implemented. A choice of alternatives represents a complete architecture variant (in a technical manner). > Architecture analysis One objective of modeling variants is the exploration of the architecture design with the focus to optimize it. Almost everything is possible to analyze: what is the best software concept or the best bus communication, which variation of the geometry Vector Informatik GmbH Version 5.0 Beta - 5 -

6 Variant management concepts is the cheapest, how much is the wiring harness, and so on. With the analysis of existing architecture variants it is possible to benchmark how well an architecture variant meets requirements. > Architecture evaluation Run an evaluation to verify if the architecture design is valid and consistent. > Compare models One point is to compare different architectures (e.g. different partitioning scenarios or network concepts) with each other and to take the best solution after the comparison into account for further modeling. > Group artifacts It can also be used to group model artifacts and make them easily accessible. > Quick variant generation An independent variant model allows a flexible variant modeling. Key data of variants A variant can be 100% or 120% out of the 150% model. > Build variants by using automatic propagation (defined by rules). > Use variant-conditions to define dependency or exclusion. > Use consistency-checks to verify variant-conditions. > Content of variants can be highlighted in all diagrams. > Different variants can be evaluated. Example: Design various alternatives to test one function on different ECUs (bus load). Design alternatives that describe different approaches of realization Version 5.0 Beta Vector Informatik GmbH

7 Variant management concepts 1.1 Available artifacts for the variant management Variant management artifacts Artifact Description Concept Space Concept Template Alternative Equipment Template The Concept Space represents a bundle of technical concepts that are available for a vehicle and must be considered for a variant. It is the base for creating an Architecture Variant. The specific concepts are represented by the Concept Template artifacts. It is possible to create many Concept Spaces with different Concept Templates assigned to it. One Concept Template can be part of different Concept Spaces. That allows a very flexible architecture setup. The Concept Template is standing for the technical partial solution. It describes all possible implementations of a certain assembly (Concept Space) of the vehicle. They hold their Alternatives and let the user choose exactly one Alternative for one Concept Template. The Concept Templates are directly associated with a Concept Space. There exists Concept Template and Equipment Template Alternatives. The Concept Template Alternative represents one specific technical solution for a Concept Template. The Equipment Template Alternative represents the available vehicle configurations. For every template exactly one Alternative can be selected by the user. Alternatives are created for the according template. The Equipment Template describes equipment characteristics from the customer point of view. It holds its Alternatives and lets the user choose exactly one of them for one Architecture Variant. Based on the chosen Equipment Template Alternative, the according Concept Template Alternatives, the implementation for the feature, are assigned. The result is standing for exactly one Architecture Variant. There may exist different implementation concepts for the same equipment concept. The Equipment Template isn t directly assigned to the Concept Space because it represents the features and requirements the customer can experience and it is not part of the technical solution. It s also possible to create options for different trim levels of a vehicle, e.g. Equipment Template VehicleEquipmentOptions with the three Alternatives FullEquipment, MostSoldEquipment and BaseEquipment. Vector Informatik GmbH Version 5.0 Beta - 7 -

8 Variant management concepts Artifact Description Architecture Variant Set The Architecture Variant is one specific variant. It consists of exactly one equipment concept that describes the features that are included in the variant (Equipment Template Alternative). Also one or more technical implementation concepts for the feature are assigned (Concept Template Alternatives). The sum of the chosen Concept- and Equipment Template Alternatives results in one concept implementation variant of the according Concept Space. To structure variants in a well arranged way it is possible to create many Architecture Variants. Sets are used as a structure element. They can be filled with artifacts for grouping them and it is possible to nesting them into each other. Sets allow quickly change a variant s content. They are highly reusable if they are modeled in the right granularity. One Set may and should be used by multiple templates. Further information > Variant management concepts > Variant management perspective > Working with the variant diagram > Variant preferences > Basic knowledge: the variant management structure Version 5.0 Beta Vector Informatik GmbH

9 Variant management concepts 1.2 Basic knowledge: the variant management structure The variant model The variant model is modeled separately from the E/E model. The connection between both models occurs later when the variant concept is completed. The structure of the variant model starts with a Concept Space (bundle of technical implementation concepts). To the Concept Space the technical implementation concepts, the Concept Templates, and the Architecture Variants (one specific variant) are assigned. To an Architecture Variant one or more Concept Templates may be assigned. For every Concept Template exact one Alternative may be chosen. The Equipment Templates are independent from the Concept Space. Equipment Templates describes the customer features to be represented by the variant. Exactly one Equipment Template can be assigned to an Architecture Variant. Equipment Templates also contains Alternatives. For an Equipment Template one Alternative may be selected. The Set is the connection between the variant model and the E/E model. The Set can be assigned to an Architecture Variant. The assigned Set in turn contains assigned E/ E artifacts. So the E/E artifacts are indirectly linked to the variant. At the end every Architecture Variant is one certain combination of one Equipment Template Alternative and one or more Concept Template Alternatives. These combinations represent several different 100% models. Further information > Variant management concepts > Variant management perspective > Working with the variant diagram > Variant preferences > Variant management artifacts Vector Informatik GmbH Version 5.0 Beta - 9 -

10 Variant management concepts Version 5.0 Beta Vector Informatik GmbH

11 Variant management perspective Variant management perspective Overview The Variant Management perspective provides all views that are used for creating and editing an Architecture Variant with all its content. Open the Variant Management perspective via the icon in the main toolbar. Activate or switch a variant via the drop-down list. Also parts of a variant can be activated, e.g. Alternatives. The Model View provides an overview of all variant artifacts in a hierarchical structure. The views provided in the Variant Management perspective are displayed in this area. In the table below you will find an overview of the available variant management views. Vector Informatik GmbH Version 5.0 Beta

12 Variant management perspective Views of the Variant Management perspective View Variant Management Architecture View Use The VM Architecture View can be used to: > configure Concept Alternatives > and Equipment Alternatives for an Architecture Variant. VM Set Structure The VM Group Structure can be used to: > get a list of all variant artifacts in a tree view. > model a hierarchical view of the variant artifacts. Variant Structure The Variant Structure can be used to: > get an overview of the templates and its Alternatives of the currently active variant. > get an overview which Sets are contained in the Alternatives. VM Propagation Rule Preview The VM Propagation Rule Preview can be used to: > get a preview of a Propagation Rule that is selected in the Model View. Template View The Template View can be used to: > add content to a Concept or an Equipment Template, e.g. a Set. > organize the content of templates Version 5.0 Beta Vector Informatik GmbH

13 Variant management perspective View Set Content View Use The Set Content View can be used to: > assign content to variant artifacts, e.g. Sets or Alternatives. > get the information which are included or excluded artifacts of the selected artifact. Template Compare View The Template Compare View can be used to: > get an overview which artifacts are contained in which template. Variant Rule Group View The Variant Rule Group View can be used to: > create new variant propagation rule groups. Variant Propagation Rules can be assigned and run as group for the variant propagation. Vector Informatik GmbH Version 5.0 Beta

14 Variant management perspective 2.1 VM Architecture View Overview The VM Architecture View is the central element for setting up a single, valid Architecture Variant that is built up on Concept Templates and their instances and one Equipment Instance. It consists of different sections. The first section lets the user choose the Architecture Variant that is about to be configured. The second section lists all Concept Templates and the according Concept Template Alternatives. The user can choose exactly one Alternative for each Concept Template. The third section lists the Equipment Templates with its Alternatives where exactly one can be chosen. See the next figure for an overview. Description of the areas Area Architecture Variant Select the Architecture Variant that is to be set up here. All its Concept Templates and Concept Template Alternatives will be available for set up in the area Concept Templates. The assigned Concept Space is shown. Area Concept Template This area holds all Concept Templates with the according Concept Template Alternatives that are assigned to the selected Architecture Variant's Concept Space. On the left side of the area the Concept Templates are listed as clickable hyperlinks leading directly to the Concept Templates in the Model View when they are clicked. The drop-down lists on the right to the Concept Templates provide the Concept Template Alternatives. One may choose exactly one Concept Template Alternative per Concept Template for the currently selected Architecture Variant (selected in area 1). Area Equipment Template This area lists all Equipment Templates on the left side and the according Equipment Template Alternatives on the right side. Only one Equipment Template Instance can be selected over all Equipment Templates for the selected Architecture Variant Version 5.0 Beta Vector Informatik GmbH

15 Variant management perspective Icons Navigates to the currently chosen artifact in the Model View. A new Concept Template Alternative can be created. Deletion of the currently chosen Concept Template Alternative. Creates a new Architecture Variant based on the actual chosen Architecture Variant. It will contain the same Concept Templates inclusive the selected Alternatives. Further information > Variant management perspective > Variant management concepts > Working with the variant diagram > Variant preferences Vector Informatik GmbH Version 5.0 Beta

16 Variant management perspective 2.2 VM Group Structure Overview The VM Group Structure view provides two different views: > The standard view shows the hierarchical structure of the Variant Packages with the contained Concept-/ Equipment Templates, Concept-/ Equipment Template Alternatives, Systems and Sets. The shown hierarchical tree visualizes the associations between the single variant artifacts as a composite tree. (See figure below on the left side) > The activatable view shows the structure sorted by kind of artifact. (See figure below on the right side) The complete Variant Package structure is shown as the root of the tree. The better the Variant Packages were organized; the better is the readability and structure of the tree shown in the VM Group Structure view. If the [Switch View] button is activated the Variant Packages are not shown. The Architecture Variants contain the active Concept Template Alternatives that were explicitly selected for them. The Sets that are contained by the Concept Template Alternatives are shown as children of them. Nested Sets are shown, too. This structure lets the user navigate through a Concept Template Alternative's associated contents - beginning from the Architecture Variant down to the Sets Version 5.0 Beta Vector Informatik GmbH

17 Variant management perspective The Sets with their nested Sets, if existing, are shown in the parent Variant Package. All in the Variant Package contained Systems are shown. Every Concept Template Alternative that exists in the Variant Package is shown. The Alternatives are structured independently of any assigned Architecture Alternative. So it is an overview of all Alternatives that are provided for the user. The Equipment Template Alternatives of all in the Variant Package contained Equipment Templates are shown. Caution: Since Sets can be nested into each other it is possible to create a containment cycle. See the following example: 1. Set 1 is nested in Set Set 2 is nested in Set 1. This cases a never ending sub tree in the tree of the VM Group Structure view. One should avoid such cycles since the resulting Architecture Variant implements this cycle, too. It results in a multiple association of model artifacts into one Architecture Variant. Icons Collapses the tree. Removes the parent reference of the selected artifact. This is mainly used to remove nested Sets. Switches the view from the Variant Package oriented view to an object type oriented view where all elements are grouped by their types. Shortcut menu The first two options provide the undo/redo functionality of PREEvision. The menu entry New can be used to create new Systems, Variant Packages and Sets. This option is only available if a suitable parent object is selected and the according model part is checked out (when a database is used). Remove Parent Reference removes referenced objects from their parents in the view's tree - as described above this feature is mainly used for removing nested Sets. Sets can be nested into other Sets by moving them via drag and drop on the target Set. Further information > Variant management perspective > Variant management concepts > Working with the variant diagram > Variant preferences Vector Informatik GmbH Version 5.0 Beta

18 Variant management perspective Version 5.0 Beta Vector Informatik GmbH

19 Variant management perspective 2.3 Variant Structure Structure of active variant The Variant Structure view displays associated Concept- and Equipment Template Alternatives and Sets for the currently active Architecture Variant. The presented tree structure is the same as described in VM Group Structure. The only difference is that the Variant Structure view focuses only on the activated variant artifact. See the next figure showing the Variant Structure view. Icons Collapses the tree. Removes the parent reference of the selected artifact. This is mainly used to remove nested Sets. Further information > Variant management perspective > Variant management concepts > Working with the variant diagram > Variant preferences Vector Informatik GmbH Version 5.0 Beta

20 Variant management perspective 2.4 VM Propagation Rule Preview Overview The VM Propagation Rule Preview visualizes a Propagation Rule's diagram with the short and a long description for it. When a propagation rule is selected in the Model View the according rule is shown in the VM Propagation Rule Preview. The preview shows the rule diagram, its name, a short and a long description. The rule can not be edited in this view you have to change into the Propagation Rule Editor perspective to edit. Further information > Variant management perspective > Variant management concepts > Working with the variant diagram > Variant preferences Version 5.0 Beta Vector Informatik GmbH

21 Variant management perspective 2.5 Template View Overview The Template View provides an overview of the existing Sets in the variant model and their usage. You can also create new variant artifacts, e.g. Alternatives or Architecture Variants, in this view and edit existing ones. The drop-down list provides all templates in the model. Select the Concept Template or Equipment Template for editing or viewing. With the icon you navigate to the selected template in the Model View. The Number of units may be optionally used to enter a unit count that is valid for the whole template. In combination with this count the percentages of the Sets unit count can be determined (see 4). The column Model Groups lists all Sets that are assigned to the selected template. The Nr of units column holds the absolute amount of units for this Set. The column Nr of units in % shows the relative amount of units for this Set. This information is used for e.g. cost analyses. The column Containment indicates - if activated - that this Set inclusive all Alternatives is assigned to this template. All template Alternatives are dynamically shown as columns. The name of the Alternative is used as column header. For each Set the Alternatives can be chosen by selecting or unselecting the checkboxes. The view's toolbar actions are listed in the following table: Toggles automatically all features that belong due to conditions to the actual selected or unselected feature. Starts the propagation for multiple selected features at once. Highlights how the new selected feature affects the variant. Switches the selected Alternative (table row) as active variant. Toggles the table view between a list without checkboxes and a list with preceding checkboxes. Exports the actual shown table into an Excel file. Removes the reference betweens a Set and the selected template. The removed Set is afterwards not included to the template anymore. Creates a new Architecture Variant artifact. For that action an Equipment Template has to be chosen in the drop-down list because an automatic propagation is started based on this template. Also select an Alternative column. The new created Architecture Variant will contain the active Alternatives of the chosen column. Vector Informatik GmbH Version 5.0 Beta

22 Variant management perspective Creates a copy of an Alternative, e.g. if you want to develop a variant based of an existing familiar Alternative. Creates a new Alternative artifact for the chosen template (concept/ equipment) in the drop-down list. Create an Architecture Variant The dialog opens via the button in the Template View toolbar described in the table above. Field to enter the new Architecture Variant name. The new Architecture Variant is created based on an Equipment Alternative. In this area you choose one Alternative of the existing ones. You can filter all existing Alternatives by enter a text string into the text field. A rule that shall be executed can be selected. Here it is also possible to filter by the name of the rules. The newly created Architecture Variant is placed in the Variant Package where the selected Equipment Template is located Version 5.0 Beta Vector Informatik GmbH

23 Variant management perspective Add/remove Artifacts to the Template View Further information Sets or other compatible artifacts can be added to the Template View via drag and drop from the Model View. Assigned artifacts can be removed via shortcut menu or by pressing <Del>. > Variant management perspective > Variant management concepts > Working with the variant diagram > Variant preferences Vector Informatik GmbH Version 5.0 Beta

24 Variant management perspective 2.6 Set Content View Overview The Set Content View displays the model artifacts that are assigned to a variant Set. The next figure shows the Set Content View with an exemplary input. The view shows which model artifacts are part of a selected Set. Detail information about in-/exclusion of a model artifact in the current Set is given. Also the information in which Sets each single artifact is associated. Drop-down list to select a Set. Also other variant artifacts, e.g. Alternatives can be selected. The first column with the header Mode shows the containment mode of each associated artifact of the selected Set. The green in icon means that the artifact is included to the Set. The red ex icon explicitly excludes the artifact from the Set. A double click on the icon changes the Mode (works only if the according element is checked out). The second column shows the artifacts contained in the selected Set. For every artifact the parent artifact is shown as well as the Set in which the shown artifact is included. The toolbar of the Set Content View: Propagates artifacts into the selected Set via propagation rules. Therefore an active variant must be set in order to find the included or excluded model elements. The small arrow beside the button opens a list of available Variant Propagation Rules (see also Variant Propagation). Shows selected artifact in the Model View. If the option is activated artifacts will be added to the selected Set as soon as they are modified. If the option is activated artifacts will be added to the selected Set as soon as they are created. Pins the currently selected Set. If another artifact is selected in the Model View the selected Set in the Set Content View doesn't change Version 5.0 Beta Vector Informatik GmbH

25 Variant management perspective Removes the selected model artifact from the currently selected Set. A click on the arrow opens the filter option. The options shown on the following figure are available: Further information > Conflict highlighting and solving in the Set Content View > Variant management perspective > Variant management concepts > Working with the variant diagram > Variant preferences Highlighting conflicts Conflict highlighting and solving in the Set Content View There may be some inconsistencies while setting up the variant Sets and filling them with the according model elements. The Set Content View uses a highlighting mechanism to indicate problems. See the next figure showing such a highlight. The VM Group Content view uses different methods to indicate an inconsistency for assigned model elements. > Orange background color The artifact is assigned multiple times to the Set. The affected Set listed in the Contained in column. > The artifact is both included and excluded in the Set. Both inconsistencies are only possible if at least one model element is indirectly included by a nested Set. Solving conflicts The conflicts that were highlighted in the Set Content View can be solved in a semiautomatic way. Vector Informatik GmbH Version 5.0 Beta

26 Variant management perspective 1. Open the shortcut menu on a conflicted element. 2. Select Solve Variant Conflict. The dialog Solve Variant Conflict is opened. 3. Select an option that shall be the solution. The Modus shows if the listed model element is included or excluded in the according Set. The in- or excluded artifact. The Set to which the listed artifact is assigned. The solution can be selected by choosing one option. All other assignments are removed from the model. After the conflict was solved only the selected assignment remains (see the red boxed element in the next figure) Version 5.0 Beta Vector Informatik GmbH

27 Variant management perspective 2.7 Template Compare View Overview The Template Compare View provides an overview or rather compare of all templates and Sets. It is easy to see which Set is assigned to which template. See the next figure. All existing Sets are listed in the first column. The templates are shown as column headers. This matrix shows for each template the containment of a Set: > Green Hook without box The Set is always contained > Green box The Set is partly contained. > Black box with green dash The Set is not part of the template. Further information > Variant management perspective > Variant management concepts > Working with the variant diagram > Variant preferences Vector Informatik GmbH Version 5.0 Beta

28 Variant management perspective 2.8 Variant Rule Group View Overview The Variant Rule Group View shows the hierarchical Variant Rule Package structure only regarding Propagation rules and Rule groups (please refer to the Variant Propagation section) and lets the user edit the Rule groups. Rule groups are used to act as executable containers for Propagation rules. The Rule groups may be nested and can be switched to runnable or not-runnable. Only the runnable Rule groups can be executed later when propagating the variant. The complete Variant Rule Package structure is shown in the Variant Rule Group View. The easiest way to use the Rule group is that it contains exactly one Propagation rule and its flag is set to runnable (blue arrow: ). In this case the group executes the assigned rule when it is started for propagation. This Rule group contains two Propagation rules and is not runnable. This means that this group can not directly be started for a propagation. The only way to run not-runnable Rule groups is to nest them in another, runnable Rule group which is runnable. Three other Rule groups (two runnable and one not-runnable) are nested In this runnable Rule group. When it is executed all the contained Propagation Rule groups are executed. The view provides the following buttons in its toolbar: Version 5.0 Beta Vector Informatik GmbH

29 Variant management perspective Removes a reference between two Rule groups or between a Propagation rule and a Propagation Rule Group. Deletes the selected object from the model. Creates a new Rule group. This is available on a Variant Rule Package or on another Rule group. In the case that the creation is started on another Rule group the new group is directly nested in the selected Propagation Rule Group - but the new object is placed in the parent Variant Rule Package. Shortcut menu The view's shortcut menu is shown in the next figure. It contains the undo/redo actions as well as the same actions that can be found in the view's toolbar. The menu also contains an item that can be used to switch a Propagation group's runnable flag. Further information > Variant management perspective > Variant management concepts > Working with the variant diagram > Variant preferences Vector Informatik GmbH Version 5.0 Beta

30 Variant management perspective Version 5.0 Beta Vector Informatik GmbH

31 Variant preferences Variant preferences Preferences Dialog for variant management Activates the Change Active Variant dialog that advises the user that it may takes some time if you switch the variant while diagrams are open. Considers not only the options set by active checkboxes. Considers also options that are defined by propagation rules. Deactivates the standard highlighting, e.g. if a highlighting rule is defined and the standard isn t needed any more. Activates a preview of a wanted propagation. If the standard functions are not enough Rule Groups may be defined and chosen to be used for highlighting and propagation. Limits the propagation iterations for avoiding infinite loops. Transparency in variants Model artifacts that are visualized in diagrams have a transparent appearance if they are not included in the active Variant. The transparency level can be adjusted using the Preferences. Select the category PREEvision Highlighting and open the group Common Highlights in order to activate or deactivate the variant highlight and to set the transparency level (Alpha Channel). Vector Informatik GmbH Version 5.0 Beta

32 Variant preferences Note: Transparent objects are not selectable if the boundary for selectable transparent objects prevents it (see Highlight Dependent Object Selection) Version 5.0 Beta Vector Informatik GmbH

33 The variant management example The variant management example Description Constrains To illustrate the concepts and the doing a simple example is used. The example includes the Product Line Vector with a Hardware Architecture layer and an explicit variant model. Not all possible subsets of a Product Line make sense. In the Hexagon example the variants have to fulfill the following constrains: > Diesel ECU and Gasoline ECU exclude each other. > ABS ECU and ESP ECU exclude each other. > Automatic transmission and manual transmission. Therefore the Transmission ECU is optional. > Instrument Cluster is always part of a variant (also known as base content or mandatory content). The example also shows how different hardware equipment optional may be modeled: > Climate Control > Navigation System > Cell Phone These variant constraints are specified in PREEvision by a variant model (also known as concept model or feature model). How to model such a variant is described in the next chapters. Vector Informatik GmbH Version 5.0 Beta

34 The variant management example Version 5.0 Beta Vector Informatik GmbH

35 Step 1: Creating a variant model Step 1: Creating a variant model Variant Perspective Variants in the Model View For variant modeling the Variant Management perspective is available. Variant models are stored in a separate layer Variant Package in a Product Line. The example Creating a variant Structure The description how to use the variant management is based on an example. You can read the single chapters stand-alone, but you will get a better understanding if you know what is really done. You can model variants via creating all artifacts manually, or you can use a wizard that supports you creating a variant structure. In the following steps the creation via wizard is described. 1. Switch into the Variant Management perspective (toolbar icon ). 2. Open the shortcut menu on a Variant Package and select New Variant Structure. The Create Variant Structure wizard is opened. 3. Select a radio button to enter a new Concept Space or to use an existing one and continue with [Next >]. 4. Press the [+] to add a Concept Template. Each Concept Template to be created is described in one row. 5. Enter the number of Alternatives and Sets for the Concept Template and select the Variant Package, in which the artifacts shall be created. Vector Informatik GmbH Version 5.0 Beta

36 Step 1: Creating a variant model 6. Continue with [Next >]. 7. Choose the number of how many Architecture Variants shall be created. 8. Press [Finish] and the variant model structure will be created. Now you have modeled a technical concept bundle (Concept Space) with its technical implementation possibilities (Concept Templates and its Alternatives). Also Architecture Variants are built but the content is not defined yet. You have also provided a basis for the connection of the variant model with the E/E model (Sets). The Sets are not assigned to a template and have no assigned technical model artifacts. Note: If you want to structure your variant artifacts with folders you have to create them manually before you run the wizard. The wizard doesn t create the folders. Alternatively you can move the created artifacts in a later step into a package structure. Note: The wizard does not only create the artifacts. It also creates the assignment between the artifacts. So it assigns the Concept Templates and the Architecture Variants to the Concept Space. The assignment of the Alternatives to the Concept Templates must be done manually, e.g. after the renaming step. Next steps Renaming the artifacts > Renaming Alternatives, Architecture Variants, Sets > Defining feature concepts > Defining the specific variant combinations After the initial variant structure is created, it is useful to rename the artifacts with names according to their meaning, e.g.: Version 5.0 Beta Vector Informatik GmbH

37 Step 2: Creating feature concepts for the variant Step 2: Creating feature concepts for the variant Creating Equipment Templates Creating Alternatives Equipment Template artifacts are created in the Model View in a Variant Package via shortcut menu. For creating Alternatives for an Equipment Template you have to do the following steps: > An Equipment Template must already exist. 1. Go in the Variant Management perspective to the Template View. 2. Select the Equipment Template in the drop-down list for which you want to create an Alternative. 3. Press the button in the views toolbar. The Create Alternative dialog is opened. 4. Enter a name for the new Alternative. Chose the option Copy parts of variants from below selected artifact if you want to take over the settings of an existing Alternative. 5. Finish with [OK]. The new Alternative artifact is created and visible in the Model View (not in the Template View, where the button was activated). When the Equipment Template is placed in a folder in the Model View, the Alternative also is created in the same folder. The Alternative is automatically assigned to the Equipment Template. Assigning an Equipment Template to an Architecture Alternative 1. Open the VM Architecture View in the Variant Management perspective. Vector Informatik GmbH Version 5.0 Beta

38 Step 2: Creating feature concepts for the variant 2. Select the Architecture Variant in the drop-down list to which you want to assign the Equipment Template Alternative. 3. Select an Alternative option in the Equipment Template area. Note: In the Equipment Template area all existing Equipment Templates in the top level Variant Package are listed. Assigning Features to the Equipment Template 1. Open the Template View in the Variant Management perspective. 2. Select the Equipment Template in the drop-down list to which you want to assign Customer Features ( ). 3. Drag the Customer Features from the Model View and drop them into the Template View ( ). 4. Activate the checkboxes to define which features should be available in which Architecture Variant ( ). The rows represent the amount of available equipment (in the majority of cases by the use of Customer Features/- Sets). The columns represent the equipment combination. If the Containment column is checked the features belongs to the standard equipment of a vehicle (or product) Version 5.0 Beta Vector Informatik GmbH

39 Step 2: Creating feature concepts for the variant Note: Only Customer Features and Customer Feature Sets can be assigned to Equipment Templates but no Requirements because the Equipment Templates represent the available customer observable features of a vehicle. Also Sets can be assinged to Equipment Templates. Note: It possible to make consistency checks for an Equipment Template and its assigned features. For example: the coverage of all features through a technical implementation. Vector Informatik GmbH Version 5.0 Beta

40 Step 2: Creating feature concepts for the variant Version 5.0 Beta Vector Informatik GmbH

41 Step 3: Defining variant configurations Step 3: Defining variant configurations Defining the Architecture Variant In this step the variant structure is already created by the wizard. Now, Architecture Variant combinations have to be created that makes sense. 1. Select the Architecture Variant in the drop-down list for that you want assigned its content ( ). 2. Select the Concept Template Alternatives in the drop-down lists to define them as 3. content of the Architecture Variant ( ). Choose one Equipment Template Alternative option ( ). Now, you have defined that the 100 % Architecture Variant VectorCoupeBasicA that contains the Alternatives ABS, Automatic and Diesel. It is based on the Equipment Template VectorCoupeBasic. Vector Informatik GmbH Version 5.0 Beta

42 Step 3: Defining variant configurations 7.1 Variant permutation Variant permutation information There are a lot of possible Architecture Variants if all variant options are combined. In the example there are three Architecture Variants each with two Alternatives. The result is 2 3 = 8 permutations (see table below). In the most cases it doesn t make sense to create all possible Architecture Variants. In this case the wizard supports the manual definition of the number how many Architecture Variants shall be created. Further information > Step 3: Defining variant configurations > Variant management concepts > Step 4: Connecting the variant model with the E/E model Version 5.0 Beta Vector Informatik GmbH

43 Step 3: Defining variant configurations 7.2 Refining variants Overview A possibility to refine a variant configuration is to extend the Alternatives of a template with an entire different variant model. The concept is shown in the figure below: One Alternative of a Concept Template is refined by the blue colored Architecture Variant; the second Alternative is refined by the orange colored Architecture Variant. How to refine variants? > Two different variant models in different concept spaces do exist. 1. Open the Template View. 2. Select the Concept Template in the drop-down list that you want to refine. 3. Drag the Architecture Variant of the second variant model and drop it into the Main Groups column. 4. Select which Alternative shall be refined by the Architecture Variant. Vector Informatik GmbH Version 5.0 Beta

44 Step 3: Defining variant configurations Version 5.0 Beta Vector Informatik GmbH

45 Step 4: Connecting the variant model with the E/E model Step 4: Connecting the variant model with the E/E model Overview Defining Set content The variant model is completed now. But there are no relations to the technical hardware model defined, yet: e.g. to the Hardware Architecture layer. This relation can be created by using Sets. With the help of Sets you can group artifacts that always are used together. For instance you can group all hardware artifacts that belong to one function e.g. like the TubodieselEngine in the figure below. To assign artifacts of the E/E model to a specific Architecture Variant you first have to add the hardware artifacts to a Set and then assign the Set to one or several templates. 1. Open the Set Content View. 2. Select the Set in the drop-down list you want to define content for. 3. Go to the Model View and drag and drop all necessary artifacts into the Set Content View. 4. If necessary change the Mode via double click (the default is the green in for included). Note: Alternatively you can select the artifacts in e.g. a Network Diagram and press <F10> to add them to the Set. Highlighting Set content When you select the Set in the Model View and e.g. the Network Diagram is opened, from that some artifacts are content of the Set these artifacts are highlighted then in the diagram. Vector Informatik GmbH Version 5.0 Beta

46 Step 4: Connecting the variant model with the E/E model Creating relation between a Set and a template 1. Open the Template View. 2. Select the template in the drop-down list to that you want to assign a Set. 3. Drag one or several Sets in the Model View and drop them into the Template View ( ). 4. Activate the checkboxes for the Alternatives which should be active for which Set for the active template ( ) Version 5.0 Beta Vector Informatik GmbH

47 Step 4: Connecting the variant model with the E/E model Example: Define optional equipment with Sets. Define a Set for the feature ClimateControl. Put the needed hardware for the navigation function into the Set (as described in this chapter) and assign the Set to an Equipment Template. Hint: you can define different Equipment Templates, e.g. BaseEquipment, FullEquipment and MostSoldEquipment. The Equipment Template has to be assigned to an Architecture Variant. When the active variant is selected now also the optional equipment is considered and highlighted. Vector Informatik GmbH Version 5.0 Beta

48 Step 4: Connecting the variant model with the E/E model Version 5.0 Beta Vector Informatik GmbH

49 Step 5: Creating variant conditions Step 5: Creating variant conditions Conditions for Features Creating conditions in Variant Diagram Conditions for variants can be modeled in different ways and for different use cases. The creation of conditions in the Variant Diagram is explained with the example of Customer Features: 1. Navigate in the Model View to Product Line Variant Package. 2. Create a Variant Diagram via shortcut menu in the Variant Package of your own choice. 3. Open the diagram by double click. 4. Drag the existing Customer Features from the Model View (Product Line Product Goal Customer Features) and drop them into the diagram. 5. Create the Variant Condition via Palette or pop-up bar. 6. Create the Variant Condition Assignment. Creating conditions in Customer Feature table Conditions between Customer Features can especially be created in a predefined table. > A predefined table must already exist (Customer Feature Package Available Tables CustomerFeatureConditions). 1. Open the table via double click. 2. Press in the Condition columns the <+> key. 3. Double click in the drop-down list and select the condition you want to model for the Customer Feature. 4. Press in the ObjectFeature column the <SPACE> key and select the target Customer Feature in the drop-down list that is affected by the condition. Creating conditions with State Definitions A further way to create conditions is State Definitions and guards. State Definitions are available for Customer Features, guards may be used for State Values and Variant Conditions. 1. Navigate in the Model View to Product Goal Customer Features. Vector Informatik GmbH Version 5.0 Beta

50 Step 5: Creating variant conditions 2. Create a State Definition via shortcut menu New State Definition on a Customer Feature. 3. Create a State Value via shortcut menu on a State Definition. The name of the State Value equates the value itself. 4. Go to the Property View General of the State Value. 5. Insert the condition as Boolean value into the Guard field. E.g. cf{ name }.is{ 4 }. Example: 6. For using the State Definition in variants drag the State Values in the Model View and drop them into the Set Content View. 7. Go to the Template View and select in which Alternative the State Value shall be available. The State Values that are not available for an Alternative are grayed out. So you get a good overview about the containments in a variant. Note: Guards are also available for Variant Conditions Version 5.0 Beta Vector Informatik GmbH

51 Step 5: Creating variant conditions Common conditions xor or and trace req reqor reqxor exclude mayuse equals optional simplifies complicates triggers One of the artifacts must be an exclusive part of the current variant. One either the other must be part of the variant. All artifacts must occur together. This directed connection refers to another artifact that explains the current artifact. So dependencies can be reconstructed. This directed connection refers to one or several other artifacts which, if the current artifact is part of a variant, should also be part of this variant. This directed connection refers to n other artifacts, from which at least one must be part of the same variant as the artifact from that the connection is outgoing. This directed connection refers to n other artifacts, from which exact one must be part of the same variant as the artifact from which the connection is outgoing. This directed connection refers to n other artifacts, from that neither should be part in the same variant as the artifact from which the connection is outgoing. A usage is advised. The artifacts describe semantically the same circumstances. The artifacts could take part in the model or not. If not there would not be a semantically false model. Often used: Optional with requires. Through the selection of the amount of artifacts a simplification of the purpose artifact is estimated, based on the synergy effect. Through the selection of the artifacts amount a increase of complexity is estimated for the realization of the purpose artifact. A cascading causal chain is triggered by an event and performed by a fulfiller. Vector Informatik GmbH Version 5.0 Beta

52 Step 5: Creating variant conditions 9.1 About guards A guard is a logical expression over features and their State Value or Condition. Guards are used for defining conditions between Customer Features. They are evaluated during the variant configuration. They enabled or disable to features associated State Values or Conditions. Where can guards are defined? Guards can be defined in the Property View of > State Values and > Conditions When you click into a text field for defining guards, content proposal is available. Using guards What rules are available for guards may be seen in the Model Queries Rule Editor perspective RuleSet <ruleset> RuleGroup <tool> vptemplates and vpguards. Note: The syntax of guards will be checked when the rule is executed not when a guard is defined Version 5.0 Beta Vector Informatik GmbH

53 Step 5: Creating variant conditions Operation overview Operation Return value Description cf{ fname } MCustomerFeature The operation returns a feature object (instance of the MCustomerFeature class) that has the given feature name fname. If such a feature does not exist an error message is issued. cfactive{ fname } boolean The operation returns true, if a feature object identified by the given name fname is included in the active variant configuration. If such a feature does not exist an error message is issued and false is returned. cf{ fname }.is{ val } boolean The operation returns true, if a feature object identified by the given name fname has a state definition whose state value equals to val within the active variant configuration. Otherwise false is returned. cf{ fname }.stateint{} integer The operation returns an integer number representing the current state value of the feature object identified by the given name fname within the active variant configuration. If the value can not be acquired an error message is issued and -1 is returned. Vector Informatik GmbH Version 5.0 Beta

54 Step 5: Creating variant conditions Operation Return value Description cf{ fname }.statestring{} String The operation returns a string value representing the current state value of the feature object identified by the given name fname within the active variant configuration. If the value can not be acquired an error message is issued and (empty string) is returned. attributeint{ attrdefname, customerfeature} attributestring{ attrdefn ame, customerfeature} The operation returns an integer number of the required feature object attribute identified by the given name attrdefname. If no attribute is found or several attributes with the same name are existing an error massage is issued and -1 is returned. The operation returns a string value of the required feature object attribute identified by the given name attrdefname. If no attribute is found or several attributes with the same name are existing an error massage is issued and (empty string) is returned. Operators for guards Operator Description! Logical NOT && Logical AND Logical OR > / < / >= / <= Comparison operators: greater than / less than / greater or equal than / less or equal than Version 5.0 Beta Vector Informatik GmbH

55 Step 5: Creating variant conditions Operator Description == Comparison operator: equals!= Comparison operator: is not equal Vector Informatik GmbH Version 5.0 Beta

56 Step 5: Creating variant conditions Version 5.0 Beta Vector Informatik GmbH

57 Step 6: Using of variants Step 6: Using of variants Overview Activating variant and visualize the difference The variant model is finished. How to use the variant management is described in the next chapters. 1. Go to the PREEvision Standard perspective. 2. Select the variant to be active in the drop-down list on the toolbar. The artifacts that are part of the active variant are highlighted in the diagram. The artifacts that are not part of the active variant are faded out and are marked in the Model View with a blue exclamation mark ( ). But there is the mandatory content missing that is contained in several variants similarly. It is not very efficient to assign the same artifacts a few times to variants. Filter options By right clicking the drop-down list the offered variant entries can be limited. When a filter is active the drop-down list has another color. > Regular Expression may be entered to filter the shown elements. Further the shown elements' type can be restricted to one of the shown types. Vector Informatik GmbH Version 5.0 Beta

58 Step 6: Using of variants > If a regular expression should be used, a dialog asks for the regular expression to use as shown in the next figure. Refer to the section on Regular Expressions for more information on creating a filter. > Filter Architecture Variants The background is colored orange. > Filter Concept Templates The background is colored purple. > Filter Equipment Templates The background is colored dark yellow. Handling artifacts that are the same in all variants Some variants may contain identical come content, e.g. mandatory content. So that the user needn t to add the identical content to all variants again a Set can be created and filled with the identical artifacts. Now, the Set can be assigned to a Concept Template and be used in any Architecture Variant that assigns the Concept Template. Note: The Set with the identical artifacts for several Architecture Variants has to be assigned to one Concept Template that is assigned to all relevant Architecture Variants. And the Containment checkbox has to be checked. So the Set is available in all variants. Activating variant with Set with the identical content Now the content of the originally variant is highlighted and also the mandatory artifacts that are assigned via Set Version 5.0 Beta Vector Informatik GmbH

59 Step 6: Using of variants Vector Informatik GmbH Version 5.0 Beta

60 Step 6: Using of variants Version 5.0 Beta Vector Informatik GmbH

61 Working with the variant diagram Working with the variant diagram Introduction One possibility to display an overview of a Concept Space with its context is the Variant Diagram. The box represents the Concept Space. The Concept Templates are shown as black arrows and its Alternatives as dots on the arrow. The Equipment Template is shown as green arrow and its Alternatives also as dots on the arrow. The Architecture Variant is represented by the spider web connecting the Alternatives of one Equipment Template and several Concept Templates to one valid 100% composition of the 150% model. How to create a Variant Diagram? > A variant model already exists in the Model View. 1. Create a Variant Diagram in the Model View inside a Variant Package (shortcut menu New Variant Diagram ). 2. Open the diagram via double click. 3. Drag the Concept Space artifact from the Model View and drop it into the diagram. 4. Drag and drop also the Alternatives to the corresponding Concept Template. 5. Drag and drop the Equipment Template and its Alternatives to the diagram. 6. At least drag and drop the Architecture Variants to the diagram. A variant model also can be created with the Variant Diagram. 1. Open the Variant Management perspective. 2. First create a Variant Diagram in the Model View (shortcut menu New Variant Diagram ). 3. Open the diagram with double click. 4. Create the artifacts in the following sequence via Palette or pop up bar: > Concept Space > Equipment Template > Equipment Template Alternative > Concept Template > Concept Template Alternative Vector Informatik GmbH Version 5.0 Beta

62 Working with the variant diagram > Architecture Variant 5. Place the Architecture Variant on one Equipment Template Alternative. 6. Go to the VM Architecture View and assign the Concept Template Alternatives via drop down list to the Architecture Variant. The new Architecture Variant that was created in the Variant Diagram must be selected. The created Concept Template Alternatives are available and can be selected. The Equipment Template Alternative is already selected in the Variant Diagram Version 5.0 Beta Vector Informatik GmbH

63 Working with the variant diagram The Palette elements for the variant management Create conditions by Variant Diagram In the Variant Diagram also conditions for dependencies between artifacts can be modeled. Variant Condition defines a dependency between two artifacts. There are different conditions that can be chosen, e.g. XOR, AND, EXCLUDE. Variant Condition Assignment connects the Variant Condition with an artifact. Naturally two Variant Condition Assignments must be created to connect two artifacts. It is an undirected condition and does the condition apply from one artifact to the other and vice versa. Directed Variant Condition Assignment also connects the condition with an artifact, but the direction is important. Vector Informatik GmbH Version 5.0 Beta

64 Working with the variant diagram Version 5.0 Beta Vector Informatik GmbH

65 Using parameters variant specific Using parameters variant specific Creating different parameter for different variants It is possible to define variant specific parameters and parameter values. Vector Informatik GmbH Version 5.0 Beta

66 Using parameters variant specific Version 5.0 Beta Vector Informatik GmbH

67 Propagating variants Propagating variants Why propagating variants? The manual assignment of artifacts for setting up a variant is very time intensive and the method is prone to making mistakes. To master the situation PREEvision provides a rule based variant propagation. The starting point for propagation is a Set with manually added artifacts. According to the selected rules used by the propagation different artifacts are automatically included as result: ports, mappings, mapped artifacts, etc. Caution: Keep in mind that artifacts in a variant are always related to each other and also to artifacts outside a variant. Sometimes there must be made decisions, e.g. when existing ambiguous mappings between artifacts. Also it may happen that the inclusion of an artifact can often be derived by the inclusion of conditioned artifacts. Submit such dependencies to a careful examination. Supported functions: Example for variant propagation > Automatically adding artifacts to active variants. > Definition of variant content > Manual selection > System integration > Content-based > What is included > What needs to be included > Iterative > Adding artifacts > Checking content again. There are Logical Functions mapped to Application SW Components. Now, the only the Logical Functions are assigned to a variant. The remaining artifacts shall be added to the variant by propagation. Vector Informatik GmbH Version 5.0 Beta

68 Propagating variants The next steps show how to create a Propagation Rule. The rule adds the mapping artifacts of the source artifacts (here: Logical Functions) and the corresponding mapping target (here: Application SW Components). > The source artifacts need to be contained in a variant Set (add artifact with <F10> to the Set). The Set need to be part of the corresponding variant. 1. Activate the Propagation Rule Editor perspective. 2. When no rules are displayed in the Propagation Rule Model View, load the propagation rules by pressing the toolbar button. 3. Create a RuleGroup in the Propagation Rule Editor perspective Project RuleModel RuleSet. 4. Create a Propagation Rule inside the RuleGroup via shortcut menu New Rules Propagation Rule. 5. Double click the new Rule to open it in a diagram Version 5.0 Beta Vector Informatik GmbH

69 Propagating variants 6. Define the rule. The example rule searches for mapping artifacts and the corresponding mapped artifacts. 7. Go into the Outline view and define the return values. Therefor select both artifacts. The rule blocks change the color. 8. Go to the Modified Propagation Rules view and generate the rule by pressing the following button: 9. Change the perspective to PREEvision Standard perspective. 10. Navigate in the Model View to Administration Rules Variant Rule Package, open the shortcut menu and select Synchronize Propagation Rules. 11. Activate the variant. 12. Go to the Set Content View and run your new created propagation rule by pressing and selecting your Rule Group from the list that appeared. Vector Informatik GmbH Version 5.0 Beta

70 Propagating variants Only start the propagation if a variant is active. 13. Select a container artifact of the variant management where the propagated artifacts shall be placed. It is recommended to choose different, e.g. Sets for the artifacts on that the propagation is started and the result artifacts of the propagation. The Set in which the propagated artifacts shall be placed need to be a part of the active variant! 14. Start the propagation with [OK]. The result of the propagation is shown in the figure below: Note: The propagation rule runs as long as every matching artifact is found that belongs to current active variant Version 5.0 Beta Vector Informatik GmbH