MapleMBSE 2024.1 Application
Guide

Copyright © Maplesoft, a division of Waterloo Maple Inc.
2024

MapleMBSE 2024.1 Application Guide

Contents
Introduction ................................................................................................. vii
1 Blocks in MapleMBSE ................................................................................... 1
1.1 Blocks Table .......................................................................................... 1
Creating a Block ..................................................................................... 2
1.2 Creating Association, Aggregation and Composition ..................................... 3
1.3 Creating Direct Association, Aggregation and Composition ............................ 4
1.4 Block Generalization, Values and Operation ................................................ 6
1.5 Constraint Blocks ................................................................................... 8
1.6 Blocks Hierarchy .................................................................................... 9
1.7 Nested Hierarchy .................................................................................. 10
2 The Fitness Tracker Model ............................................................................ 13
2.1 Packages ............................................................................................. 13
2.2 Requirements Table ............................................................................... 14
Creating Requirements ........................................................................... 14
2.3 Use Case Table ..................................................................................... 16
Creating a Use Case Table ...................................................................... 17
2.4 Blocks Table ........................................................................................ 18
Blocks Tree .......................................................................................... 18
Block Satisfaction Matrix ....................................................................... 25
2.5 Internal Blocks Table ............................................................................. 25
Block Property Table ............................................................................. 26
Property Connector Table ....................................................................... 27
2.6 Activity Diagram .................................................................................. 28
Creating Actions for an Activity ............................................................... 28
3 State Machine Diagram ................................................................................ 35
3.1 How to Create a State Machine Diagram ................................................... 36
3.2 How to Create States and Transitions ........................................................ 36
3.3 How to Create Triggers with Signal Events ................................................ 37
4 Countdown Timer Model .............................................................................. 39
4.1 Requirements Table ............................................................................... 40
4.2 UseCase Table ...................................................................................... 40
4.3 CountDownTimer Table ......................................................................... 41
Signal Table ......................................................................................... 42
Time Event Table .................................................................................. 43
4.4 Timer Behavior Table ............................................................................ 44
4.5 StateMachine Properties Table ................................................................. 45
Transition Table ................................................................................... 46
4.6 ActivityNodeTable ................................................................................ 47
Opaque Behavior Table ......................................................................... 47
Activity ObjectFlow Table ..................................................................... 49
Activity ControlFlow Table .................................................................... 49iii

iv • Contents

4.7 State Behavior Table ............................................................................. 51
State Behavior ControlFlow Table ........................................................... 52
State ControlFlow Condition Table .......................................................... 53
5 Turbofan Engine Model ................................................................................ 55
5.1 Introduction ......................................................................................... 55
5.2 Turbofan Model .................................................................................... 55
5.3 Requirements ....................................................................................... 55
5.4 ValueType ........................................................................................... 56
5.5 Constraint Blocks .................................................................................. 56
5.6 System Model ...................................................................................... 56
5.7 Results ................................................................................................ 56
5.8 References ........................................................................................... 57
6 UAV Model ................................................................................................ 59
6.1 Introduction ......................................................................................... 59
6.2 Analyze Stakeholder Needs ..................................................................... 59
6.3 Mission Requirement ............................................................................. 60
6.4 System Requirements ............................................................................ 60
System Behavior ................................................................................... 60
Weight Estimation ................................................................................. 60
Wing Area Estimation ............................................................................ 61
6.5 References ........................................................................................... 61
7 FMEA Template .......................................................................................... 63
7.1 Introduction ......................................................................................... 63
7.2 FMEA ................................................................................................ 63
7.3 Recommended Action ............................................................................ 64
7.4 References ........................................................................................... 64
8 Interface Definition Template ........................................................................ 65
8.1 Introduction ......................................................................................... 65
8.2 The InterfaceRequirements Matrix ........................................................... 66
8.3 ComponentsInteractionTable ................................................................... 66
8.4 References ........................................................................................... 67
9 Cost Analysis ............................................................................................. 69
9.1 Introduction ......................................................................................... 69
9.2 Results ................................................................................................ 69
9.3 Visualization ........................................................................................ 69
10 Variant Management Template ..................................................................... 71
10.1 Introduction ....................................................................................... 71
10.2 FeatureMatrix ..................................................................................... 71
10.3 VariantCheckTable .............................................................................. 72
10.4 References ......................................................................................... 72
11 Default Value Generation ............................................................................ 73
11.1 Introduction ....................................................................................... 73
11.2 Generating the Default Values ................................................................ 73

Contents • v

11.3 Requirement ID generation .................................................................... 74
12 Instance View ........................................................................................... 75
12.1 Introduction ....................................................................................... 75
12.2 The MatrixTemplate Worksheet ............................................................. 75
12.3 Instance Multiplicity Table .................................................................... 78
13 Spacecraft Model ...................................................................................... 79
13.1 Introduction ....................................................................................... 79
13.2 SPCUseCase Template ......................................................................... 79
13.3 SPCValueType Template ....................................................................... 79
13.4 SPCStructure template ......................................................................... 80
14 Telescope Model ........................................................................................ 83
14.1 Introduction ....................................................................................... 83
14.2 TMT_Predicate Template ...................................................................... 83
14.3 TMT Activity Template ........................................................................ 84
14.4 Signal Interface ................................................................................... 85
14.5 TMT_OBSE Template ......................................................................... 85
14.6 TMTInstance ...................................................................................... 85
15 Turbojet Model: Formula Evaluation ............................................................. 87
15.1 Introduction ....................................................................................... 87
15.2 Instance Specifications and Constraint Properties ...................................... 88
15.3 Instance Matrix ................................................................................... 89
16 Variant Management:MBPLE with MapleMBSE ............................................ 91
16.1 Introduction ....................................................................................... 91
16.2 Feature Model .................................................................................... 91
16.3 Configurations .................................................................................... 93
16.4 Variation Points .................................................................................. 94
16.5 Vehicle Analysis ................................................................................. 96
17 Downloading sysML Diagrams .................................................................... 99
17.1 Introduction ....................................................................................... 99
17.2 TWCsysML Example ........................................................................... 99
18 Relations Matrix ...................................................................................... 101
18.1 Verify Matrix with Hierarchy ............................................................... 101
Verify Matrix with Hierarchy ................................................................. 101
18.2 Multiple Relations in Matrix ................................................................ 101
19 Predicates ............................................................................................... 105
19.1 Introduction ...................................................................................... 105
20 Matrices With Different Element Types ........................................................ 107
20.1 Introduction ...................................................................................... 107
Index ........................................................................................................ 109

vi • Contents

Introduction
MapleMBSE Application Guide Overview
MapleMBSE™ gives an intuitive, spread-sheet based user interface for entering detailed
system design definitions, which include structures, behaviors, requirements, and parametricconstraints.
The Application directory of your MapleMBSE installation contains six applications. Eachof the chapters in this guide corresponds to one of the applications:
Chapter Application Name
1
Working With Blocks in MapleMBSE

2

3

4

5

6

7

8
9

Description
The first application uses the
TWCSysML-Structure.mse file to demonstrate
the use of blocks in MapleMBSE
Creating a Model in MapleMBSE (Fitness This model uses the TWCSysML-Model.mse
Tracker Model)
and TWCSysML-ModelActivity.mse files todemonstrate how to create a model in
MapleMBSE which can be exported to the No
Magic server.
Working With State Machine Diagrams in The example in this chapter defines how to
MapleMBSE
create states, define their transitions and theevents that trigger these transitions using
MapleMBSE.
Count Down Timer Model
This chapter contains a model of Countdown
Timer that uses TWCSysML-Timer.mse to
create a simulatable Timer model.
Turbofan Engine Model
This example model is used to identify design
points of a turbofan engine. MapleMBSE andCameo Systems Modeler™ were used to create
a turbofan example model
UAV ModelThis model uses Object Oriented System
Engineering Methodology (OOSEM) to designa conceptual model of an Unmanned Aerial
Vehicle (UAV).
FMEA Template
This model is used to perform FMEA analysis
by accessing SysML model elements from theNo Magic server.
Interface Definition Template
This template is used to show details on theinterfaces between the systems
Cost Analysis
This example illustrates cost analysis applied
to materials used in a turbofan engine.

vii

viii • Introduction

10

Variant Management Template

11

Default Value Generation

12

Instance Table Template

13

Spacecraft Model

14

Telescope Model

15

Turbojet Model

16

Variant Management

17

Downloading sysML Diagrams

18

Relations Matrix

19

Predicates

This example illustrates how to identify themultiple variants in the product line and theirdependencies, to manage complexity.
The model in this chapter is used to illustrate
the use of the Default Value Generation feature.
This example illustrates how the InstanceTable
template makes it easier to filter and review
information on instances, gained from theMatrixTemplate worksheet.
This example illustrates the use of MapleMBSE
to explore this SysML-based model.
This example provides a different view of themodel and illustrates the use of Predicate
Filtering.
This example illustrates the use of the Formula
Evaluation feature in the context of an instancematrix.
Using the Model-Based Product LineEngineering profile and MapleMBSE to createa variant of a model.
Configuring the MapleMBSE sysML Diagrams
plugin to view sysML model diagrams in a
MapleMBSE worksheet.
This example displays the Verify relation
between Component Value property andRequirements.
Predicates defined with stereotypes allow you
to add new elements to the model.

Related Products
MapleMBSE 2024 requires the following products:• Microsoft® Excel® 2010 Service Pack 2, Excel 2016 or Excel 2019.
• Oracle® Java® SE Runtime Environment 8.
Note: MapleMBSE looks for a Java Runtime Environment in the following order:
1) If you use the -vm option specified in OSGiBridge.init (not specified by default)2) If your environment has a system JRE ( meaning either: JREs specified by the environment
variables JRE_HOME and JAVA_HOME in this order, or a JRE specified by the Windows
Registry (created by JRE installer) ), MapleMBSE will use it.
3) The JRE installed in the MapleMBSE installation directory.

Introduction • ix

If you are using IBM® Rational® Rhapsody® with MapleMBSE, the following versions
are supported: Rational Rhapsody Version 8.15, 8.3 and 8.4• Teamwork CloudTM server 2021.x, 2022.x and 2024.x• Magic Collaboration Studio 2021.x, 2022x and 2024.x
If you are using Eclipse CapellaTM with MapleMBSE, the following version is supported:• 5.x
If you are using EclipseTM, the following version is supported:• 2020-3
Note that the architecture of the supported non-server products (that is, 32-bit or 64-bit)must match the architecture of your MapleMBSE architecture.

Related Resources
Resource

MapleMBSE Installation
Guide

Description
System requirements and installation instructions for
MapleMBSE. The MapleMBSE Installation Guide is available
in the Install.html file located in the folder where you installed
MapleMBSE, or on the website.

https://www.maplesoft.com/documentation_center/
MapleMBSE User Guide Instructions for using MapleMBSE software. The MapleMBSE
User Guide is available in the folder where you installed
MapleMBSE.
MapleMBSE Configuration This guide provides detailed instructions on working withGuide
configuration files and the configuration file language.
Frequently Asked
You can find MapleMBSE FAQs here:
Questions
https://faq.maplesoft.com

Release Notes

The release notes contain information about new features, known
issues and release history from previous versions. You can findthe release notes in your MapleMBSE installation directory.

For additional resources, visit http://www.maplesoft.com/site_resources.

Getting Help
To request customer support or technical support, visit http://www.maplesoft.com/support.

x • Introduction

Customer Feedback
Maplesoft welcomes your feedback. For comments related to the MapleMBSE productdocumentation, contact doc@maplesoft.com.

Copyrights• Microsoft, Windows, and Excel are registered trademarks of Microsoft Corporation.
• No Magic Server, Cameo Systems Modeler, and MagicDraw are registered trademarksof No Magic, Inc.
• Eclipse and Eclipse Capella are trademarks of Eclipse Foundation, Inc.
• UML is a registered trademark or trademark of Object Management Group, Inc. in the
United States and/or other countries.
• Java is a registered trademark of Oracle and/or its affiliates.
• IBM, Rational, and Rhapsody are registered trademarks of IBM Corporation.

1 Blocks in MapleMBSE
1.1 Blocks Table
The block diagram shown below is created using MapleMBSE and syncing it to the Teamwork Cloud. This chapter will explain how to work with blocks in MapleMBSE.

This example is created with the following package structure:
Model+ Structure
The list of features available in MapleMBSE to define blocks are:
• Association• Aggregation• Composition• Generalization• OwnedEnd Multiplicty• Constraint• Property• Value12 • 1 Blocks in MapleMBSE• Operations• Redefine Value

The configuration file, TWCSysML-Structure.mse defines seven worksheet templates towork with blocks:• The BlocksTree and BlocksTreeDirect worksheets are used to create blocks and theirrelationships.
• The BlockProperties worksheet is used to create generalizations, values and operations.
• The Redefines worksheet is used to specify values and redefine values to blocks.
• The ConstraintTable worksheet is used to create parameters, opaque expressions anddefine constraint blocks.
• BlockConstraintTable is used to create a direct association between Blocks and Constraint Blocks.
• Parametric Table is used to create a binding connector between the constraint parameters.

Creating a BlockTo create a block, enter a name for the block in the column C insertion area (the Block Top
Level column) as shown below. A block called Aeroplane is created.

To create a relation between blocks, they must first be created in the Block Top Level
column before they can be added in the second level.
Blocks can be created in all worksheets except for the ConstraintTable worksheet.

1.2 Creating Association, Aggregation and Composition • 3

1.2 Creating Association, Aggregation and Composition

To create relations without direction, use the BlocksTree worksheet. The blocks need tobe created as shown below.
To create Association relations:
1. Enter the block name in the Block Top Level column.

2. The row is highlighted as a duplicate key to indicate the block already exists. Enter the
related block name in the Block 2nd Level column, in the same row.

4 • 1 Blocks in MapleMBSE

3. MapleMBSE checks if the entry is valid by comparing it with existing blocks and will
add none in the Aggregation column by default.

To create Aggregation and Composition relations, follow the previous steps by entering theowned end block (the class that has an association owned by another class) in column C,
replace none with composite in the Aggregation column to create a composition relationand shared to create an aggregation relation.

1.3 Creating Direct Association, Aggregation andComposition
Use the BlocksTreeDirect worksheet to create relations with direction. Both tables are
similar in defining relations, the type of relation differs based on the entry in the Aggregation
column. Enter the class name in the Block Top Level column and enter the name of the
Attribute class in the Block 2nd Level column and specify the aggregation type. The figure
below shows relations between blocks with navigability.

1.3 Creating Direct Association, Aggregation and Composition • 5

The following table shows the necessary information needed to create a relation between
blocks and their corresponding worksheet. The Class and Attribute Class columns imply
that the class and its related class should be created first and then the respective aggregation
type.

To represent multiplicity, at the Association level, enter a value for the respective blocks
in the Multiplicity column as shown below.

6 • 1 Blocks in MapleMBSE

1.4 Block Generalization, Values and Operation
To generalize a block, enter the name of the generalizing block in the Block Top Level
column of the BlockProperties worksheet and a corresponding value in the Generalization
Block column.

Use the same worksheet to add a value property to a block. Enter the block name in the
Block Top Level column and then enter the value in the Value column.

Similarly, to add operations to the blocks, enter the block name in the Block Top Level
column and the operation name in the Operation column.

1.4 Block Generalization, Values and Operation • 7

In the Redefines worksheet, to enter a numerical value for Value Property use the Valuecolumn, as shown below.

To redefine a property of an existing block, type a new value in the Value column alongwith information about the block from which the value is redefined. For example, Aeroplane
has value properties: Range, Vcruise, Vmax, wing span and Wtotal. These properties are
not defined with numerical values, as shown above (these fields can hold numerical values).
The Boeing 747 block is generalized to Aeroplane. To redefine the values from Aeroplane
to Boeing 747, enter the same value for Boeing 747 properties as that of Aeroplane. In the
Value column, enter the desired values. Now to redefine, enter the block from which thevalue is redefined and the name of the value being redefined as shown below.

8 • 1 Blocks in MapleMBSE

1.5 Constraint Blocks
The process for creating constraint blocks, relations and parameters is similar to that ofworking with blocks in the previous section.

In the Constraint Block Top Level column, enter a constraint block and its breakdown in
the Constraint Block 2nd Level column. This creates a direct composition relation between
the blocks. In order to create different relations between the constraint blocks the configuration file has to be edited. To create parameters, enter the respective block in the Constraint
Block Top Level column and the parameter name in the Constraint Parameters column.
To add an equation to a constraint block, enter the block name followed by the name of theconstraint in the Constraint Name column, as shown above. Enter the constraint blockname in the Constraint Block Top Level column and a name for the specification equationin the Specification column. MapleMBSE accepts the entry. The corresponding field in theOpaque Expression column is empty. Enter an expression, as shown in the figure.
To create a direct association between the blocks and Constraint Blocks select the BlockConstraintTable worksheet. Next, enter the block name in the Block Name column andConstraint Block in the Constraint Block Name column, as shown below.

1.6 Blocks Hierarchy • 9

To create a binding connector between the parameters of the Constraint Blocks, you mustfirst open the ParametricTable worksheet. Enter the Constraint Block and the parameter ofthe constraint that has to be connected in the Constraint Parameter Column, followed by
the Constraint Block name and the target parameter in the respective column. MapleMBSE
will automatically create a binding connector between the two parameters of the constraint
blocks specified.

1.6 Blocks Hierarchy
This template is used to create hierarchies with a direct composition relationship. In previous
sections, the sub-blocks(subcomponents) should be created first before you add a relation
between the blocks. This specific worksheet will allow you to create a new component andrelations without the need to create the subblocks(subcomponents) first. To create a newcomponent in the hierarchy enter the top-level component in the Components column andadd the subcomponent name in the Sub-Components L1 column. The top-level block andthe sub-blocks will be added to the same package in the model.

10 • 1 Blocks in MapleMBSE

1.7 Nested Hierarchy
This template will also create the hierarchy with the direct composition relationship but it
differs from the previous template by adding the new blocks with a nested structure in themodel. As shown in the image below.

1.7 Nested Hierarchy • 11

12 • 1 Blocks in MapleMBSE

2 The Fitness Tracker Model
The Excel Workbook template, TWCSysML-Model.xlsx, arranges the display of the elements in worksheets as defined in the configuration files.
The Package structure of the model is displayed in the Packages worksheet.
The Requirements packages are defined hierarchically; defining a top-level requirement,
decomposing the requirements into groups and finally stating the requirements.
Once the requirements are defined, actors and their interactions with the system are createdin the Actors and UseCases worksheets.
The BlockTree and BlockProperties worksheets are used to display information about thesystem context, specifications and relations.
The BlockConnectorTable and BlockPropertyTable worksheets create connections
between block properties.
Once the structural aspects are defined, the system's behavior are defined by using the
TWCSysML-ModelActivity.mse configuration file.
This example was created with the following package structure:
Model- Requirements- Use Case
- Structure- Behavior

2.1 Packages
The Packages worksheet is used to organize the model elements into respective Packages.
The user can create packages by specifying a name for the package under the Name column
in the Packages worksheet. Packages are created as shown in the figure below. The configuration (.mse) file is configured in such as way so that when a user begins working directly
in a worksheet, without creating any packages beforehand, the packages are automaticallycreated and elements are displayed under the packages corresponding to the worksheet.

1314 • 2 The Fitness Tracker Model

2.2 Requirements Table
The requirements defined for a system are used to identify the behavior, constraints, system
specifications, etc. for which the system is modeled. Requirements can be categorized orgrouped based on their definition of the system such as: performance, functional, constraints,
etc.
This example was created with requirements in three levels, as shown in the Excel file below.
The number of levels and appearance of the Requirements worksheet is controlled by theconfiguration (.mse) file and can be changed by editing the configuration file.

Creating Requirements
Requirements contain a unique ID, Name and Specification field to identify and name eachrequirement with a brief description.

2.2 Requirements Table • 15

To enter a new requirement:
1. Enter an ID for a top level requirement in the ID column, as shown above. MapleMBSE
checks for duplicate entries and adds a row for the corresponding ID, enabling the user
to enter a name and specification for the requirement.
2. To create a second level requirement, use the same ID and name as for the top-level requirement. MapleMBSE will detect it as a duplicate entry and highlight it as a duplicate
key. Type an ID for the requirement in the ID column, of the Requirement 2nd Level
section (column E), as shown above. MapleMBSE considers this to be a unique entry
and enables the corresponding row to accept a name and description for the requirement.
3. To create a third-level Requirement, follow step 2, then enter a new ID in column H.
Follow the above steps to create any number of requirements. Excel identifies the ID columns
as text format fields. The figure below shows the requirements created for the Fitness
Tracker model, using the steps above.

16 • 2 The Fitness Tracker Model

2.3 Use Case Table
The Use Case table describes the goals and interactions of the system model with external
users (stakeholders).
To create a use case table, the actors of the system are identified, then the goals of the systemand other functionality expected by the user.

2.3 Use Case Table • 17

Creating a Use Case Table
Use cases and actors are identified by unique names. The configuration file is created insuch a way that two different tables are needed to create the use case table. The Actors
worksheet is used to list the identified actors of the system. The UseCases worksheet isthen used to create the interaction between actors and use cases.
To create a Use Case table:
1. Create actors in the Actors worksheet as shown below.

2. In the UseCases worksheet, type the name of the actor to create a use case or select aname from the list. Type the use case in the UseCase1 column as shown above.
3. To relate use cases, enter the actor name and corresponding use case in columns C and
D respectively. MapleMBSE will highlight this as a duplicate key. Enter the other use
case in the Associated UseCase2 column (column E). This entry is considered valid androws are automatically created to show that the association is bidirectional.
The Use Case table created for the Fitness Tracker is shown below. The Associated
UseCase3 column is automatically generated by MapleMBSE based on the input in theother columns. To associate use cases, they must already exist in the UseCase1 column.

18 • 2 The Fitness Tracker Model

2.4 Blocks Table
Blocks are created in a predefined package named Structure. From the configuration file,
three worksheets are created:• BlockTree to create blocks and parts,• BlockProperties to create operations, generalizations and to create values for the blocks,
and• BlockSatisfiesMatrix to validate the model against the requirements to identify if all
requirements have been met.
To make the example model simpler, only direct composition and generalization relations
between blocks are used.

Blocks Tree
Blocks are identified uniquely by their names and can be accessed between worksheets. To
identify the scope and working environment of the system, the mission context table iscreated using the BlockTree and BlockProperties worksheets.
Once the system scope is defined, a black-box specification for the system of interest is
created in terms of values and operations. These operations defined for the system are used
to work with the behavior of the system defined in a different configuration file.
On defining activities of the system using the behavior configuration file, logical blocks
are defined in the same table using BlocksTree. Finally, parts of the system are defined at

2.4 Blocks Table • 19a physical level to meet the requirements specifications and also to satisfy the behavioral
aspect of the system modeled.
1. To create a block, enter a name for the block in the Block Top Level column (column
C), as shown below. Every unique entry in this column creates a block. Text entered iscase sensitive so to create properties for a block in the second level, the block nameshould be accessed with the same case.

20 • 2 The Fitness Tracker Model

2. To create a direct compostion between blocks or to assign a block as part of anotherblock type, enter the name of the block for which a part has to be created in the Block
Top Level column followed by the part name in Block 2nd Level, as shown above. Now
a direct association is created between Mission Context and Activity Tracker.
3. Blocks can be created at a third level in two ways: similar to adding blocks at the second
level, specify the top level block, then the second level block, and finally the third level2.4 Blocks Table • 21

block name. The figure below illustrates this way of adding a third level block. Since
Screen is already a part property of Activity Tracker, physically adding a part to Screen,
as shown in row 9, will automatically create row 6 and vice versa.

To create generalizations, the BlockProperties worksheet is used. Similar to the above step,
once blocks are created in the top level column, enter the block name in Block Top Leveland the generalizing block in the Generalization Block column (cell D6). In the table,
Android and IOS are generalized to Smartphone.

To create the value and operation property of a block, in the BlockProperties worksheetenter the name of the block that you want to assign a value. Since the block already exists,
the row is highlighted as a duplicate key. Type the value in the Value column (column E),

22 • 2 The Fitness Tracker Modelas shown below, to add a value to the block, Activity Tracker for this example. Noticecells E6 to E12 have values assigned to Activity Tracker.

In a single row for the block, either value or operation can be assigned to it. To assign operation to a block, a similar procedure is followed. Enter the block to which an operation has
to be created in the Block Top Level column and enter the operation name in the Operation
column (column F), as shown below.

2.4 Blocks Table • 23

Using the steps mentioned above, the Activity Tracker is created and the block table atthe physical level is shown while the rest of the inputs are filtered.

24 • 2 The Fitness Tracker Model2.5 Internal Blocks Table • 25

Block Satisfaction Matrix
The Block Satisfaction Matrix is used to verify whether the blocks created satisfy the requirements. The matrix template is created automatically using the information from theBlocks and Requirements worksheets.

To create a satisfy relation between the blocks and requirements, identify the block thatsatisfies a requirement and in their intersection of row and column, enter 'x' to indicate thatthe corresponding requirement has been met. This creates a satisfy relation between blockand requirement.

2.5 Internal Blocks TableIn the previous sections the system of interest has been defined with operations, values, andby different parts of the system. In this section, we will define how these parts of the system
and its properties, will interact with each other.
To define ports through which the system interacts with other parts and subsystems, wecreate ports to blocks and then represent how these ports are connected. As shown in the
diagram below, we can represent the interaction of block properties using ports and connectors.

26 • 2 The Fitness Tracker Model

Block Property Table
This worksheet displays the blocks and their part properties based on how they are definedin previous worksheets. In addition to the part properties, you can create ports by using the
PortProperty column.
Creating an entry is similar to entries discussed in other sections:
1. Specify the block to which a port has to be created
2. In the PortProperty column, enter a name for the port.
In the example below for the Activity Tracker- Physical block, the PropertyName column
displays the existing part properties from previous worksheets. To create ports, enter theblock name in the Block Name column (column D) and the port name in the PortProperty
column (column G).

2.5 Internal Blocks Table • 27

Property Connector Table
The Property Connector Table is used to connect part properties within the block, as shown
below.
To create a connector between the ports of the different system example between Activity
Tracker – Physical’s port Bluetooth out to the Process Subsystem bluetoothout port, in the
Block Name column enter the name of the block in this case it is the Activity Tracker –Physical and the port details in the Port Name column this entry will be highlighted as duplicate by MapleMBSE cause this relation already exist in the model now in the Property
Connector columns enter the Block and port to which the connector has to be created.

28 • 2 The Fitness Tracker Model

2.6 Activity Diagram
An Activity Diagram is used to define system behavior. The top level system functionality
is initially defined and these defined actions are further decomposed to show the logicalbehavior of the system.
Only call behavior actions with pins are used in this model.

Creating Actions for an Activity
Using the Use Case diagram, we have identified that the basic use case for the model is to
track daily activity.
The ActivityTable worksheet is used to create activities, action, control flow and object
flows. To create an activity diagram named track daily activity, enter the name in the
ActivityName column, as shown below. Once we create the actions for the activity, weneed to now create flow between the actions. In this model, control flows are used only torepresent the start and end of an activity.
To create control flows to denote the start and end of the activity, use the ControlFlowName
column. Following the creation of the control flows, object flows can be created in the sameworksheet.

2.6 Activity Diagram • 29

Enter a name for the object flow in the ObjectFlowName column. As shown in the diagram
below, control flows and object flows are created for the activity diagram, track daily
activity. Linking these flows with actions is discussed in the following section.
Creating Actions for an Activity
Using the Use Case diagram we have identified the basic use case for our model is to trackdaily activity. The ActivityTable worksheet is used to create activities, action, control flow
and object

flow.s
To create an Activity Diagram, first create an activity and its elements in ActivityTable.
Enter the name of the activity in column D (ActivityName) as shown above. Once anactivity is created we can create its initial node, final node and its actions in the respective
column as shown. Use column H (Behavior) to allocate a behavior to the actions we created.
In order to allocate a behavior, it should exist as an activity in the ActivityName Column.
Adding New Duration Constraints
The DurationConstraint worksheet is used to define the constraints in terms of durations
for the activities. The Activities column displays the list of all the activities defined for themodel.
To add a new duration constraint, enter the activity in the first column followed by the nameof the duration in the Duration column. This will create a duration for the activity but does

30 • 2 The Fitness Tracker Model

not add the duration specification. Use the Specification column to add the duration specification in the format min..max where min is the minimum constraint value and max isthe maximum constraint value. The min and max value are joined by the double period (..).

Creating Flows
Using the ObjectFlow and ControlFlow Table we can now complete the activity diagram.
To create an object flow between two actions in the ObjectFlow Table, Enter the activity
under which the action was created in ActivityTable under Column D and the action namein Column E(Action Name Column) and the other action to be link with in Column G and
its activity in Column F. Now MapleMBSE will create the input and output pins for the respective actions. In the case of Behavior being allocated to the action being links,
MapleMBSE will automatically create parameters.

2.6 Activity Diagram • 31

To create control flow between nodes we follow the same steps we used for creating object
flow, In ControlFlow Table, enter the activity name in Column C(ActivityName) and thenode in Column D(Activity Node) and the action node to be linked with in Column F and
its activity in Column E. Similarly we can link nodes and actions with Control or object
flows.

32 • 2 The Fitness Tracker ModelTo create an object flow between parameter and an action we use the same method we used
for creating object flow between actions, MapleMBSE will automatically identify the element
type and create the corresponding links.
Allocate Actions to Swim Lanes

2.6 Activity Diagram • 33

Before we can allocate actions to a swim lane. We first create swim lanes and assign a blockto the swim lane. BlocksTable tab displays the list of available blocks that can be assigned
to a swim lane. In SwimLanesTable tab ActivityName column displays the activities createdusing previous tables. To create a swim lane enter a name in Column G (Swim Lane) andthe block it represents in Column H(Representing Block). Now we have created the swim
lanes with the respective blocks it represents. To allocate an action enter the name of theactivity in column F(Activity Name) and the swim lane name in column G. MapleMBSE
will highlight this record as duplicate field, enter the action to be allocated in column J andthe activity in column I to complete the allocation. MapleMBSE will now accept this as avalid record and remove the error. Similar we can access different activities we created andallocate the actions to swim lanes.

34 • 2 The Fitness Tracker Model

3 State Machine Diagram
This section defines how to create states, define their transitions and the events that trigger
these transitions using MapleMBSE. The configuration file, TWCSysML-StateMachines.MSE defines four worksheets that can be used to create states and define theirtransitions. The TWCSysML-StateMachines.MSE file is located in the Application subdirectory of your MapleMBSE installation directory. This example only covers the casewhere a transition is triggered by a signal event. The following package structure is followed:- Model-Package+StateMachine+Region+SignalEvent35

36 • 3 State Machine Diagram

3.1 How to Create a State Machine Diagram
In the StateMachines worksheet enter Package name as Package, and StateMachine nameas StateMachine. These naming conventions can be changed by modifying the configuration
file.

Once the state machine is created, we have to define a region in which states will be created.
To create a region, use the Pseudo State Properties worksheet. Enter a name for the region,
as shown in the table below (Region1 is used as default as defined in configuration file).
This table is also used to create the pseudo state (PseudoState column) and final state (FinalState column) that defines the start and end of the state machine. Enter a name for thestates, as shown below. We define the transition from the pseudo state in this worksheet,once we have created other states, and its transition in the Transition Matrix Table worksheet.

3.2 How to Create States and Transitions
To create a transition between states in the State Transition Table, enter the source statein the SourceState column and the target in the TargetState column, as shown below.
Once we create these transitions between the states, we can edit the properties of thesetransitions in TransitionProperties worksheet.

3.3 How to Create Triggers with Signal Events • 37

3.3 How to Create Triggers with Signal Events
Initially, the Transition Name column will be displayed as a blank column since we haven’t
named the transitions. Enter a name for the transitions so they can be identified to create a
trigger and assign a signal event. Enter the Transition name in the Transition Name column
followed by the Signal Event name we created in StateMachine Table. MapleMBSE will
accept this as a valid input and automatically populate the other fields.

38 • 3 State Machine Diagram4 Countdown Timer Model
The example is create with the following package structure
Model-Requirements-Use Case-TimerTo create a Timer model we define the simplest requirements that is expected of the Timer.
The model is required to have functions that enable the user to start, reset, pause, and stop
the timer. When Timer reaches zero, the user must be notified and the timer should continue
counting down. Keeping these as the only requirements, a Requirements table is initiallycreated. From these requirements we identify the actors and use cases. We create a Timerblock to define its behavior based on these identified Use Cases.
To define the Timer properties, we create operations and properties to the Timer block. To
enable the user to reset, stop, pause, etc., we create these as signals so the user can command
the system when it is being executed. State Machine and Activities are used to define thesystem behavior and its different states of operation.

The RequirementsTree and UseCases worksheets are used to define the requirements thatshould be met by the model and its use cases. The CountDownTimer, SignalTable, andTimeEventTable worksheets are used to create blocks and events that will trigger the system
to transition to a different state.

The TimerBehavior worksheet is used to create a StateMachine that will define the states
at which the system will exist and its behavior at different states. It is also used to create
operations and activities that will define system behavior. The StateMachineProperties
worksheet is used to create the states and the TransitionTable worksheet is used to define
their transition and events that triggered them.

ActivityNode Table and OpaqueBehavior Table are used to create activity nodes and behaviors. ActivityObjectFlow table and ActivityControlTable are used to create flows between
the actions and nodes created in previous tables.

3940 • 4 Countdown Timer Model

The StateBehaviorTable, StateBehaviorFlowTable and StateControlFlowCondtionTable
worksheets are similar to that of previously mentioned worksheets. The only difference
being that they are used to create activity flows that define states entry behavior.

4.1 Requirements Table
The Requirements Table worksheet is used to create Requirements. The configuration fileis defined in a way that this table can be use to create two levels of requirements. As shown
below, requirements for the system are created.
RequirementsSatisfy Table worksheet is used to create a Satisfy relation between the Requirements, Blocks and its properties. This table will be used to verify if the requirements
are met once the system has been created.

4.2 UseCase Table
The Actors tab is used to identify the actors, while the UseCases tab is used to associatethese Actors with UseCases.
To create an association between Actor and UseCase, enter the Actor Name in the Actor
column, followed by the UseCase in UseCase1 column.
To create an association between UseCases, Enter the Actor name in Actor column followedby the UseCase name in the UseCase1 column and associating UseCase in the AssociatedUseCase2 column.

4.3 CountDownTimer Table • 41

The UseCases table is created as shown below:

4.3 CountDownTimer Table
This table is used to create the Timer block, signals, and events that will be used later increating the model.
To create a block, enter the name in the Block Name column.
To create signals, enter a name for the signal in the Signals column, and its package namein the PackageName column.

42 • 4 Countdown Timer Model

Note: Two kinds of events can be created in this worksheet, Signal events and Time events.
These events are created based on the signals that are being used.

Signal Table
The Signal table is an extension of the previous section. Here, we relate the signals thatwere created with the SignalEvent. Later in the model, we will use these signal events as
triggers to define transition between states.
To assign a signal to SignalEvent, enter the SignalEvent name from the previous table andits corresponding signal in the Signals column.

4.3 CountDownTimer Table • 43

Time Event Table
The Time Event table is used to create the duration for the timed event.
Enter the event name in the Timed Event column, followed by a name for the duration in
the Expression Name column.
Next, enter the required time duration in the Duration column. Assign the duration to the
TimeEvent by entering the event and expression name in their respective columns.

44 • 4 Countdown Timer Model

Now we have created the necessary Events and Signal that will be used to define the Stateand Transition for the system.

4.4 Timer Behavior Table
Using the Timer Behavior table, we will define properties, operations and the behavior aspectof the system using State Machines and Activities.
To create a property, enter the block in the Block Name column and its property in the
Block Property column.
Based on the use case, we will create the operations expected of the system: restart, countdown and notify.
To create operations, enter a name for the operation and the block in the respective columns.
Next, we will create a StateMachine to define the system.
Enter the block name in the Block Name column and, in the same row, enter a name for
the StateMachine in the StateMachine column. This will create a StateMachine for theTimer Block as shown below.
To make sure that the Timer Block exhibits the behavior of the StateMachine entered in theprevious step, enter the StateMachine in the Block StateMachine Behavior column. In
doing this, we are defining the state machine as a classified behavior.
Next, we create activities based on the operations created for the block.

4.5 StateMachine Properties Table • 45

Enter the block name in the Block Name column and the activity name in the Activities
column, we have now created activities for the block Timer. In the Block Operations Behavior column, enter the respective operations for the activities created.

4.5 StateMachine Properties Table
Next, we define the states and region for the TimerState we created previously.
Enter the StateMachine name followed by the region name in the Region column.
Create the Initial and Final states and the states at which the system will exist in respective
columns, as shown below.

46 • 4 Countdown Timer Model

Transition Table
To create a transition between states with triggers, enter a name for the transition in theTransitions column (a row will be added with Source and Target state cells highlighted).
Enter the source state in the Source State column and the target state in the Target State
column to create a transition between them.
To add a trigger that starts the transition, enter the transition name and trigger name. The
source and target state fields will be updated automatically. To add an event to the trigger,
enter the event name in the appropriate column. For example, to assign startEvent as a
trigger between the start and ready states, enter the transition name, then provide a namefor the trigger. Since startEvent is a signal event, it is populated in the Signal Event column,
as shown.

4.6 ActivityNodeTable • 47

4.6 ActivityNodeTable
Next, we define the activity created in the TimerBehavior table.
To create actions and flow for an activity, enter the name of activity to which the above
mentioned elements will be created.
In the Call Behavior Actions column, enter a name to create call behavior actions.
Similarly, this table is used to create initial and final nodes, forks, opaque behaviors, decisionnodes, and send signal actions. Each of which can be created by providing a name for thenode and its activity.
To assign the signal that will be sent when a signal action is invoked, enter the name in the
Send Signal Action column and the signal that will be sent in the Signal column (signalsthat were created in CountDownTimer table).

Opaque Behavior Table
This sheet is used to assign OpaqueBehavior to an action and define its parameter andequation.

48 • 4 Countdown Timer Model

To assign OpaqueBehavior to an action, enter the Opaque Behavior created in previous
table in the Opaque Behavior column.
Note: The available actions will be automatically listed in Opaque Action column, as shown
below.

4.6 ActivityNodeTable • 49

To create an equation, enter it in the Opaque Equation column.

To manipulate the parameters and direction, we first need to create links between the actions.

Activity ObjectFlow Table
This table is used to create object flow between activities.
To create object flow between actions, enter the source action name in column E (Activity
Node column) and its activity in the ActivityName column followed by the target action
information in column G(ActivityNode column) and its activity in the Activity Namecolumn.
The object flows between the actions are created, as shown below.

Activity ControlFlow Table
The Activity Control Flow table works similar to the Object Flow table,

50 • 4 Countdown Timer ModelEnter the source action and activity name in the first two columns, followed by the target
activity and action name.

Once we have completed the Behavior flow tables, we have to sync the input and output
flow of Opaque Behavior and its call action. To do this, go back to the Opaque Behavior
table.
The Input and Output pins will be displayed as argument and result by default. We change
this value based on the Opaque Equation parameter. Rename the argument in both tables
to time_in and time_out instead of result and argument for the Opq_behavior.

4.7 State Behavior Table • 51

We have created state machines and activities to define the behavior of the system. As of
now StateMachine and the activities are defined as separate behaviors of the same system.
In the following section, we will define how the system behaves at each state using theactivities we created.

4.7 State Behavior Table
The State Behavior table will list the states created in the StateMachine Properties worksheet.
Next, we will assign an entry behavior to the system.
In the example, we will create an entry behavior to the running state. Enter the state namein the State Name column.
In the State Entry Behavior column, enter a name to create an entry behavior (decreasein this example).
Next, we will define nodes and actions to the entry behavior, as shown below.
To assign a behavior to the call actions we created in an earlier section, enter the behavior
you want to assign in the Behavior column adjacent to the call actions.

52 • 4 Countdown Timer Model

State Behavior ControlFlow Table
Creating behavior control flows is similar to creating activity control flows.
Enter the source action and activity in the first two columns and target action and activity
in the next column.

4.7 State Behavior Table • 53

We have now created the control flows. When we defined a requirement initially, we statedthat the system should notify the user when time reaches zero and should continue counting
down even after reaching zero. To achieve this, we will set a guard condition to the control
flow of the merge node created in earlier sections. In a previous section, we have alreadycreate a notify behavior to the state and to send a signal to user.

State ControlFlow Condition TableIn the ControlFlow Condition table, existing control flows will be listed based on previous
inputs.
To create a guard condition, enter the state activity name in the State Activity column followed by the source and target activity node information and enter a guard condition.

54 • 4 Countdown Timer Model5 Turbofan Engine Model
5.1 Introduction
This example model is used to identify design points of a turbofan engine. MapleMBSE
and Cameo Systems Modeler™ were used to create a turbofan example model. The design
point calculations are based on ideal gas turbine cycle analysis.
Initially, a mission statement is defined to specify the scope of the model and to identify
design points at Mach number 0.8 and operating altitude between 35000ft to 45000ft witha bypass ratio between 6-8.

5.2 Turbofan Model

The turbofan system is defined as shown in the diagram above. The system consists of atwin-spool configuration, with a high pressure turbine driving a high pressure compressor,
a low pressure turbine driving a low pressure compressor, and a fan. Temperature andpressure are identified at the design points, as shown in the figure. The primary goal is to
identify the design points with optimum SFC (specific fuel consumption) value.

5.3 Requirements
Once the mission statement is defined, system requirements for the turbofan are also statedfor each subcomponent in terms of target efficiency, pressure ratio etc., which have to besatisfied. The SystemRequirements worksheet in MapleMBSE is used to define the specifications and target values that have to be achieved. In addition to the system specifications,55

56 • 5 Turbofan Engine Model

analysis requirements are created to define the input values which will be used to analyze
the model.
To maintain traceability between system level requirements and mission level requirements,
the DeriveRequirements worksheet in MapleMBSE is used to create derived relationships
between requirements.

5.4 ValueType
The ValueTypesTable and UnitQuantityKindTable worksheets are used to define units
and type of values that will be used to define the system. These valuetypes are used to specify
the type of value properties of the system to be modeled.

5.5 Constraint Blocks
Constraint blocks are created and constraints that will be used in the system are captured
using the ConstraintProperties worksheet. Similar to value types, these blocks are used
to specify the type the constraint property of the system that will be defined.

5.6 System Model
The Turbofan Blackbox is used to specify the properties of the turbofan in terms of values,
subcomponents and ports through with the system will interact.
Once the subcomponents are created we now define the values and constraint properties,
then type them to valuetypes and the constraint block created. A specific worksheet viewis created in MapleMBSE to show components values, constraints and their types.
An Analysis block is created to provide value exchange between the subcomponents. The
Analysis block provides the default values with which the analysis is performed and also
receives the results of analysis.

5.7 Results
The InstanceResults table is used to display the results of analysis performed in the modelusing simulation toolkit in Cameo Systems modeller. In MapleMBSE the results are mapped
to Excel graph for visualization. This results worksheet is treated as read-only and used toonly visualize the results of analysis at different altitudes.

5.8 References • 57

To create a new instance:
1. Create a new instance specification by providing a name in the Instance Specification
column in InstanceTable worksheet and type “Analysis Block” as the name of the blockin the Instance of Block column.
2. Define the feature and corresponding value with which the new analysis has to be performed, required input values to be created are ByPassRatioA and targetEfficiency_hpTurbine.
3. Once the analysis block is defined, specify the inlet properties by creating a new instancefor the InletConditions block, similar to the above method. The required values in thiscase are Ta(inlet static temperature in K) and Pa (inlet static pressure in bar).
4. Commit the changes to the No Magic Server.
5. Open the model in Cameo or Magic Draw, then create a new block diagram in the
NewInstance package, drag and drop the analysis block instance.
6. Drop the inletConditions instance into the analysis instance to create a new feature instancefor the Analysis block.
7. Right-click the analysis instance and select simulate to run the analysis.
8. Export the results of analysis as new instance into the Result package under NewInstancethen commit to the No Magic Server.
9. Reload MapleMBSE to see the results in the NewInstanceResults worksheet.
To maintain the traceability between the requirements and the modeled system modeled,use VerifyRequirementsMatrix to have a verify relationship between system requirements
and value properties of the block. By creating this verify relation, now we have traceability
from system values to system requirements and from system requirements to mission requirements.
The RequirementsTraceability worksheet displays all the requirements from the modeland its relationships such as trace, verify, derived with other model elements.

5.8 References
1. Cohen, H. Rogers. G. and Saravanamuttoo, H. (1996). Gas turbine theory. Harlow:
Pearson education.
2. Sanford Friedenthal. (2015). A Practical Guide to SysML, 3rd Edition. Morgan Kaufmann
Publishers.

58 • 5 Turbofan Engine Model6 UAV Model
6.1 Introduction
This model uses the Object Oriented System Engineering Method (OOSEM) to design aconceptual model of an Unmanned Aerial Vehicle (UAV). The primary use of UAV in
consideration is to assist forest fire fighting operations in remote areas. The sample modelshows a part of the OOSEM workflow to identify system requirements.

6.2 Analyze Stakeholder Needs
To identify the needs of stakeholders, in this case the fire department, the current operating
domain is modeled to find the existing limitations and expectations of the fire department.
The existing domain is captured using the block definition diagram represented in a tableformat in the OperatingDomain worksheet. A causal analysis is performed to identify thefactors that are of interest to the fire department operation [6]. This causal analysis also reveals the present limitations in the fire department operation. At this stage, we have identified
the needs of stakeholder based on which we will derive the mission requirements.

5960 • 6 UAV Model

6.3 Mission Requirement
To determine the scope and mission of the UAV model, we first identify the measure ofeffectiveness based on the stakeholder needs analysis. Secondly, we define the operating
domain in which the system to be modeled will operate. The operating domain is represented
using a block diagram and shown in table format using the OperatingDomainUAV worksheet. We identify the use cases to determine the high level behavior of the system and its
interaction. Next, from the measure of effectiveness and the operating domain, we can define
the Mission Requirements and stakeholder requirements from the stakeholder needs that
we identified.

6.4 System Requirements
Before identifying the system requirements, we define units, and interfaces that will be usedby the system of interest. A separate package called Interface is create using the InterfaceTable to contain the flows and signals that will be used in the model.

System Behavior
To find the system requirements, we initially define the UAV blackbox that displays: ports
through which the system interacts, its parts, and its values. In addition, we also define theoperations that are expected of the system, and the method to achieve it in terms of activities.
The UAVBlackBox worksheet displays the model elements mentioned above. Now wedefine the system behavior and represent states at which the system will operate and its
events. On identifying the mission profile of UAV, we create detailed states at which thesystem should operate. Following this, we use activities to define system behavior. Basedon the use cases, we create the activities since our mission is to control forest fires and weare still in the conceptual phase. We define system behavior based on this activity.

Weight Estimation
Once we have defined the system behavior we need to determine the system specificationin order to create the system requirements. To identify the general design requirements theweight of the UAV is first estimated followed by sizing and identifying critical parameters.
The WeightEstimationTable worksheet displays the value properties and constraint properties need to estimate the weight of UAV. This worksheet also has tables created in excel
that displays specifications of similar aircraft and estimation constants from historical data[1]. Based on the mission profile the parameter values can be altered based on payload,
range, endurance, etc. when satisfactory values are determined the values are updated toWeightEstimationBlock and saved to the model in the No Magic Server.

6.5 References • 61

Wing Area Estimation
To determine the sizing we initially create the constraints using the WingAreaConstraint
worksheet. Similar to the weight estimation worksheet, the WingAreaEstimation worksheet
is used to find wing area by iterating key parameters. Using the matching plot technique[2] Wing loading vs Thrust loading is plotted from which we identify the wing area.
We have estimated the weight and wing area based on which other design parameters canbe further evaluated. This example model covers the conceptual phase from stakeholder
need analysis to identify system requirements.

6.5 References
1. Austin, R. (2010). Unmanned air vehicles: UAVS design, development, and deployment.
Chichester, West Sussex, and U.K.: Wiley.
2. Raymer, D. P. (1992). Aircraft design: A conceptual approach. Washington, D.C.: AIAA.
3. Sadraey, M. H. (2017). Unmanned aircraft design: A review of fundamentals. San Rafael,
CA: Morgan & Claypool.
4. Sadraey, M. H. (2013). Aircraft design: A systems engineering approach. Hoboken, NJ:
Wiley.
5. Simard, A. J., & Forster, R. B. (1972). A survey of air tankers and their use. Ottawa:
Forest Fire Research Institute.
6. Sanford Friedenthal. (2015). A Practical Guide to SysML, 3rd Edition. Morgan Kaufmann
Publishers.
7. GLOBAL HAWK SYSTEMS ENGINEERING CASE STUDY.pdf. (n.d.). Retrieved
from https://www.scribd.com/document/409826283/GLOBAL-HAWK-SYSTEMSENGINEERING-CASE-STUDY-pdf
8. Firefighting Aircraft Recognition Guide - California - PDF Free Download. (n.d.). Retrieved from https://docobook.com/-firefighting-aircraft-recognition-guide-california.html

62 • 6 UAV Model

7 FMEA Template
7.1 Introduction
This model is used to perform FMEA analysis by accessing SysML model elements froma No Magic server. This example shows a FMEA process to identify possible failure modesof system functions defined in conceptual design of a UAV; however this template can beused to perform FMEA on different model elements by specifying appropriate path andelements in the configuration file.

The FMEA process is performed as shown in the figure, system functions from the model
are accessed and failure modes are identified. Further we identify severity, occurrence anddetection for the failure modes and calculate the RPN (Risk Priority Number). Mitigating
actions for identified failures are created as new requirements. The complete process is
saved back to the teamwork cloud model.

7.2 FMEA
The FMEAMatrix worksheet is used to identify new failure modes for the system function
and to create a dependency (identifiedFM). Once we create new failure modes, we use the
FMEATable worksheet to provide a detailed analysis of the potential failure by specifying
S, O and D from which RPN is calculated.

6364 • 7 FMEA Template

7.3 Recommended Action
In this process, recommended actions are captured as requirements that can be saved backto the model. The RequirementFMEAMatrix worksheet is used to create a custom dependency (deriveFMEA) between identified FMEA and recommended actions. The FMEARequirementTable worksheet is used to add specification to the new requirements created asa result of this analysis.
To use the custom FMEA template:
1. Add the TWCSysML.mdzip model to the No Magic server.
2. In Cameo Systems Modeler or Magic Draw, Right-click CustomStereotypes profile→
Project Usage →Export Packages to New Server project.
3. In desired project File→ Project Usage →Server Project select the exported profile fromprevious step.
4. Update path in the MSE file to get model elements.

7.4 References
1. Kratzke, R. (2018). Failure Modes Effects Analysis in MBSE. [ebook] Available at: https://www.incose.org/docs/default-source/texas-gulf-coast/tgcc-conference-2018/2018papers/kratzke-2018-incose-presentation-(for-public-distribution).pdf?sfvrsn=db4796c6_2[Accessed 22 May 2019].
2. Publishing, R. (2019). Failure Mode and Effect Analysis - FMEA - and Criticality Analysis - FMECA. [online] Weibull.com. Available at: https://www.weibull.com/basics/fmea.htm [Accessed 22 May 2019].

8 Interface Definition Template
8.1 Introduction
This template is used to show details regarding the interfaces between the systems. ICD
templates in MapleMBSE can be customized to display information that is relevant to theend users. This example shows different worksheets that can be used to update or review
interfaces and add documentation/comments.
The InterfaceTable worksheet shows the components of a simple Tablet structure, its ports
and interface type. This is a review only sheet and not to be updated.

The InterfaceClasses worksheet shows the interface definitions that are used in the previous
worksheet and can be used to add description or comments to the interfaces.
The ItemFlow worksheet is also a review only sheet that displays a list of all the item flows
in the project and their related components.

65

66 • 8 Interface Definition Template

8.2 The InterfaceRequirements Matrix
The InterfaceRequirements matrix shows the relation between the interface requirements
and the interfaces of the components of the tablet

8.3 ComponentsInteractionTable
The ComponentsInteractionTable displays the list of components of an Arduino controlled
robot and its interfaces, this worksheet shows a list of columns that can be updated by theuser to add the new interface in terms of ports and define its direction.

8.4 References • 67

8.4 References
1. Karban, R., Troy, M., Brack, G. L., Dekens, F. G., Michaels, S. B., & Herzig, S. (2018).
Verifying Interfaces and generating interface control documents for the alignment andphasing subsystem of the Thirty Meter Telescope from a system model in SysML.
Modeling, Systems Engineering, and Project Management for Astronomy VIII. doi:
10.1117/12.2310184
2. Model-based Interface Control Documents (icd) Donatas Mazeika- Saulius - https://blog.nomagic.com/model-based-interface-control-documents-icd/

68 • 8 Interface Definition Template9 Cost Analysis
9.1 Introduction
This example shows how MapleMBSE can be used to access key parameters of a turbofan
engine from a SysML model and do a trade-off with different material types.

9.2 Results
The Cost Analysis worksheet has two different tables displayed in worksheet: results fromthe preliminary analysis table shows value properties and its value based on which the costestimations are done, and the other table displays material properties and cost.

9.3 Visualization
Updating the values will automatically update related tables and graphs based on which we
can identify the cost-effective material and key-value property which will affect the overall
cost of the engine.

69

70 • 9 Cost Analysis

10 Variant Management Template10.1 Introduction
Variant management is used to identify the multiple variants in the product line and theirdependencies to manage complexity. This example shows a simplified view into identifying
the variants in a Tablet model by which the user can create new features to the tablet partsand use it to create different variations for a tablet.

10.2 FeatureMatrix
The FeatureMatrix shows the different features and their respective parts to which the featureis related. For example, the 10MP feature is related to the part Camera of the tablet. To
create a new feature user can add a new entry in the FeatureName row and assign it to thecorresponding part. The VariantMatrix displays the available configuration that was createdin the model. To add a new variant the user can provide a unique name in the VariantModelrow and built it using the available features. VariantTable shows the information from
VariantMatrix in a tabular view for review.

7172 • 10 Variant Management Template10.3 VariantCheckTable
The VariantCheckTable is a validation to identify conflicts in the feature selection. To
verify the selections first the user has to sort the table. Right-click inside the table to Sort
Vertically. In case of conflicts, the row will be highlighted as shown.

The last row is highlighted because Model B has features AMOLED & MLED which are
selected by the user belongs to the same part LED.

10.4 References
Chami, Mohammad & Forlingieri, Marco & Oggier, Philipp. (2017). Model-Based Variability Management Solution with SysML.

11 Default Value Generation
11.1 Introduction
This is a MapleMBSE feature that is used to generate default values or a sequence of textthat is pre-defined in the configuration file. Use TWCSysML-DefaultValue.MSE to view
how default generation works. This sample has two worksheets: the BlocksTable and the
AutoGenerateTable. Using the BlocksTable sheet, a user can create components and subcomponents. In the Components column, provide the name of a component and the nameof a subcomponent. Once the Component and subcomponent have been entered, the otherfields will be automatically populated. This is illustrated in the default value generation
example, where a new Chassis component is created.

11.2 Generating the Default Values
Add Chassis as a part to Car as shown below.

New value in other columns are generated automatically as shown and these generated
values can be edited if needed.

73

74 • 11 Default Value Generation

AutoGeneratedTable shows a simple BOM template using with when the name of a part isentered rest of the column are auto-generated with a default value.

11.3 Requirement ID generation
This feature extends the default value generation to generate IDs for requirements. Unlike
the above two sections, the ID values are calculated based on the latest ID in the model.
Use the TWCSysML-RequirementID.MSE to view how the IDs are auto generated. In theRequirementsTree worksheet add a new requirement by typing a name to column B, thiswill automatically get the latest ID in column C. Similarly add sub requirements to noticethe same.

In the DerivedRequirements worksheet add a new requirement, the only thing different inthis worksheet is the modeling tool user has set a specific numbering format of the requirements in the package. MapleMBSE will use the same prefix and set an ID as shown in theworksheet.

12 Instance View
12.1 Introduction
This template is used to view different instances of blocks and their value properties andallows the user to directly edit or create a new instance of the block.

12.2 The MatrixTemplate Worksheet
The MatrixTemplate worksheet displays the instances in the columns and rows represent
the blocks and their value properties. The intersection of row and column displays the valueof the block with respect to its instance. To create a new instance enter a name for the instancein the Instances column. MapleMBSE will automatically create all the instances hierarchicallyand display the related values in the cells which can be updated. New slot values can be
added to the empty cells, based on the value types defined. To delete a slot select the celland click on delete button. MapleMBSE will automatically parse these inputs to the rightvalue types.
In the image below, the L1 Sub-Component Column shows the subcomponents name alongwith their multiplicity []. The component's multiplicity can be changed using the InstanceMulti Table. In this example, vehicle_instance1 is used as reference Instance to increaseor decrease the multiplicity.
Notes:• When a user enters a string value and expected value is Real the cell will be updated withdefault value as ‘0’.
• This template is used only when the structure of the block for which is the instance iscreated is determined previously.

75

76 • 12 Instance View

In the cell with hyperlinks, as shown in the Vehicle attachment property (see above figure),a user can open the files by clicking on the hyperlink. An empty cell can only be referred
to existing files in other cells. When the file name is misspelled, a dialog box will appear
as below, with the list of files. Note that the files opened are read-only and cannot be edited.

12.2 The MatrixTemplate Worksheet • 77

Clicking cancel will display invalid attachment

78 • 12 Instance View

12.3 Instance Multiplicity Table
This worksheet is used to increase or decrease the multiplicity of the reference Instance(vehicle_instance1): To increase multiplicity of a part in the Multiplicity of Instance column,
update the number to the desired value, and then this will add new sub-instances as below.

13 Spacecraft Model
13.1 Introduction
The template files in the Spacecraft model files folder require the Spacecraft SysML model,
which can be downloaded from http://sysml-models.com/spacecraft/models.html. (Notethat the use of this model is subject to the terms and conditions set by the copyright holders.)
The templates in the folder provide a different view of the model in tabular format.

13.2 SPCUseCase Template
The Mission Failure Modes worksheet shows the mission for the Spacecraft system andassociated mission breakdowns. Identified failure modes for the activities are displayed in
the Failure Modes column. The Operational Usecase worksheet displays the use cases,
included and extended use cases.

The RequirementsTree, FRMatrix and RequirementTreeSPC worksheet show thespacecraft requirements displayed in the model.

13.3 SPCValueType Template
This template has worksheets that display all the signals and value types that are available
in the Spacecraft model. The Signals worksheet displays the components signals and its
reception. The IO definitions worksheet has the interface definitions the parameters thattypes the interface and its owner. In the table below the I-O Definition command is typed
by the argument from Manage Power. The table displays only the parameters of the Behavior that are of type displayed in the first column.

7980 • 13 Spacecraft Model

13.4 SPCStructure template
This template displays the structural aspect of the Spacecraft System. The MissionContext
worksheet shows the hierarchy of where the Spacecraft system and its subsystems are definedin the operating environment.
In the BlackBox worksheet the Value column displays the value properties of the Spacecraft
System while the Operations column has the list of operations for the Spacecraft. The Ports
column lists the different interfaces with which the system interacts with the external envir-

13.4 SPCStructure template • 81

onment. The Behaviors column shows the system behavior as activities.

The Constraint Parameter worksheet displays the constraints from the model. The Physical Decomposition worksheet shows the hierarchy of the components of the spacecraft.
The Spacecraft ConnectorMatrix and Spacecraft Connector worksheets display the same
information but as different views.

82 • 13 Spacecraft Model

The GNCInformationFlow and GNC_InterfaceMatrix worksheets show only the detailsof the GNC Subsystem. The GNC Subsystem worksheet shows all the relevant informationof the different components.

14 Telescope Model
14.1 Introduction
The TMT model is available to download from: https://github.com/Open-MBEE/TMTSysML-Model(Note that the use of this model is subject to the terms and conditions set by the copyrightholders).The Template files in the TMT model folder provide a different view of the telescopemodel. Using these templates with a model as big as the TMT, makes viewing the model
elements in a tabular format easier to visualize.
These templates will provide a compact view into the model. Since the TMT is a fairly large
model, before using the template, increase the RAM allocated to MapleMBSE. Refer to theuser guide and enable cache at login.

14.2 TMT_Predicate Template
This template is for review only and not for editing the model content. The predicates aredefined in the configuration file that effectively query the model based on Boolean conditions
and will display the results that match these conditions. In the Requirements worksheet
all the requirements in the TMT model is displayed. In the PredicateFilter worksheet, only
the requirements that don’t have Rationale are displayed. The AcceptedRequirements
worksheet will list the requirements that as a tagged value as “Accepted”.

The ValueProperty worksheet has the value properties that don’t have a datatype. The IDsof these values are displayed so that they can be easily found by searching in the modeling
tool.

83

84 • 14 Telescope Model

Similarly, the constraint blocks with parameters that don’t have a type are shown in theConstraintParameterType worksheet. The qualified name for these constraint blocks isdisplayed so you can find them easily in the modeling tool.

14.3 TMT Activity Template
This template will display the information of activities of the APS system. The APSInterchangFunction worksheet lists the different packages with activatations that send signals
to Component ports. In the figure below, Sub-Package cmd_M1CS has activities that are
defined in the Activity Column. Calibrate Warping Harness has a Send Signal action, Calibrate Warping Harness cmd, that is received by port PEAS2M1CSOut which owned byProcedure Executive and Analysis Software.

The ActivityDecomposition worksheet shows activity breakdown up to 4 level.

14.4 Signal Interface • 85

Right-click on the table and select create merged view to create a worksheet that will remove
the redundant entries. Note that this new worksheet is only an excel sheet created to simplify
the view and is not linked with the MapleMBSE syncview.

14.4 Signal Interface
This worksheet is similar to the APSInterchangeFunctions worksheet but table displays
the APSComponents and their interface (ports) which receive a signal and source of thesignal in the Send Action column

14.5 TMT_OBSE Template
This template file has the views of TMT Observatory System. TMTObservatorySystemshows the components of the observatory system. Conceptual design template displays theComponents and their attributes like ports and values. The Owned Behaviors column has
the list of behaviors that are performed by the system.

14.6 TMTInstance
The results of instances from the TMT model for different scenarios are shown in their respective worksheets. For example, in the CalibrationsDurationInstances worksheet, thecomponents and their value properties are displayed. The column represents the different
instances for the calibration scenario and the intersecting cell has a value for that instanceof the component in the rows.

86 • 14 Telescope Model

The TMTInterfaceView template has the view of interface definitions and connectors
between the components of the APS system. The APSConceptual worksheet has a matrix
view of the interface between the APS components. The SSCAssociationClass worksheet
shows a view of the AssociationBlock and their flow properties.

15 Turbojet Model: Formula Evaluation
15.1 Introduction
A Turbojet Cycle Analysis context block as shown below is defined in the model. This
context block has all the constraints that are used to calculate the specific fuel consumption(SFC). The inputs that can be changed to compute the best sfc are defined as value properties
in the component blocks. Instance specifications are created for the Turbofan Cycle Analysis
and these instances hold the values for that specific instance of the turbojet system.

8788 • 15 Turbojet Model: Formula Evaluation

15.2 Instance Specifications and Constraint Properties
This example is used to calculate turbojet design points using the formula evaluation feature.
In this example, the user can see the block hierarchy used to define the turbojet systemmodel. The design point calculations are based on ideal gas turbine cycle analysis. To use
the formula evaluation, the following conditions are to be met: The formulas are defined inconstraint properties, instances are created based on a top-level analysis context. These instances hold the components and its value properties in form of slots. A parametric diagram
is used to define the constraints between these properties.

15.3 Instance Matrix • 89

The component hierarchy worksheet shows the top-level components and their value properties. The instance matrix displays the instance specification of the top-level Turbojet Cycle
Analysis15.3 Instance Matrix
Formula evaluation can be used in the worksheet that displays the instance matrix with slots.
The rows of the matrix display the components and their value properties. The columns
display the names of the instances. The matrix displays the value in the slots corresponding
to the value properties and instances. The inputs and output values are not explicitly defined
but is understood based on the objective defined in the template or based on experience.

90 • 15 Turbojet Model: Formula Evaluation

The input values of existing slots can be changed based on these values, the output values
will be calculated. New instances can be created by adding a name for the instance in thecolumn. To run the formula evaluation, use the shortcut Ctrl + Shift + K or Add-ins selectMapleMBSE and Formula Evaluation. MapleMBSE will use excel to call the values andupdate the matrix.

16 Variant Management:MBPLE with
MapleMBSE
16.1 Introduction
Model-Based Product Line Engineering (MBPLE) is used to capture the 150% model thatis defined with all the features and different options a user has to configure a variant of a
product. This example requires the MBPLE profile to be used in the project. In MBPLE,
the user defines the Feature Model with all the available options. In the configuration part,the user selects a set of features that make up the product variant. The 150% model is definedand linked with the variation points that link the Feature model and 150% model fromwhich, based on the configuration defined, a user can generate a variant.

16.2 Feature Model
The RootFeatureTable worksheet displays the Root Feature Group and all of its features ina hierarchy. This sheet is used to add new features to the feature Groups.

9192 • 16 Variant Management:MBPLE with MapleMBSE

The Existence_List worksheet displays the types or variations for the feature. To add a new
type to a feature, enter the feature name in Feature Group Column and type in the Feature
Column.

16.3 Configurations • 93

16.3 Configurations
Next, define the configuration of the Feature Model. In the configuration, the user specifies
the model with features that will define a variant. The ConfigurationMatrix worksheet displays existing configurations. To add a new configuration, enter a name for the configurationin the column.

MapleMBSE will automatically populate the column with the default values. The user canselect different value for a Feature by using the drop down menu in applicable cells. The
TransmissionConfigMatrix, InteriorConfigMatrix and EngineConfigMatrix offer a similarview but give the user better control over individual configuration of the features.

94 • 16 Variant Management:MBPLE with MapleMBSE

16.4 Variation Points
In the previous sections you defined the Features and configuration from which the variants
can be created. The 150% model is already defined and our goal now is to link the Featuremodel with the 150% model.
The Existence worksheet lists all the existence that can be linked to the Feature Model using
the Feature Impact relations.

16.4 Variation Points • 95

The FeatureImpactTable links the existence with the Feature Model as shown in the image
below. In the example below, the Variation Point/Existence 2 Litre links the Feature GroupEngine Capacity. The Test for column allows the user to select the type of feature that thevariation point represents.

The next step is to apply the Existence to the 150% model. ExistenceMatrix shows the Existence in the rows of the matrix and Components in the column, “X’ in the intersecting cell
represents that an existence is applied to a component.

96 • 16 Variant Management:MBPLE with MapleMBSE

16.5 Vehicle Analysis
The Analysis worksheet is used to find the time it takes for a vehicle to reach a certain speed
in the 1st and 2nd gear. The values time, time_1, time_2, a1 and a2 are calculated and results
are updated when Formula evaluation function is used. The user can update the other values
and run the evaluation when needed. The matrix display instances of the 150% model. The
block and value properties that are needed for the analysis are in the rows of the matrix.
The instances are displayed in the column. Add a new instance and enter the values that arenecessary, to run the evaluation use the shortcut Ctrl + Shift + K or Add-ins-> MapleMBSE>Evaluate Formula. If the evaluation is successful, you will see a dialog box the current
worksheet was successfully evaluated.

16.5 Vehicle Analysis • 97

98 • 16 Variant Management:MBPLE with MapleMBSE

17 Downloading sysML Diagrams
17.1 Introduction
Using the MapleMBSE plugin a user can view the downloaded SysML diagram in the
MapleMBSE template. To configure the plugin please refer to the Getting Started with
the MapleMBSE sysML Diagram Plugin section of the MapleMBSE Installation andLicensing Guide.

17.2 TWCsysML Example
To view the diagram of the TWCSysML example, launch the TWCSysML-Diagrams fileand connect to the project. Note that the same project should be opened in CSM/MD forthe diagrams to be downloaded. Click on the hyperlink to open the diagram.

Note: In case of an error, you will see the "Unable to connect to MapleMBSE plugin" dialog.

99

100 • 17 Downloading sysML Diagrams

18 Relations Matrix
18.1 Verify Matrix with Hierarchy
Verify Matrix with Hierarchy
This example displays the Verify relation between Component Value property and Requirements. The rows display the Component Turbofan and its subcomponents, displaying
the value properties in Column H. The column displays the Requirements in a nested hierarchy as shown below.

18.2 Multiple Relations in Matrix
The TWCSysML-RelationMatrix.MSE contains the MultipleRelationMatrix worksheet.
Using this view, users can add different types of relations between elements in the sameview. Two types of relations are shown here: Verify relation (VER) and Satisfy relation(SAT). To add a new VER dependency, in the matrix cell, enter VER and then click enter.
This will add a new verify relation.

101

102 • 18 Relations Matrix

It is also possible to add multiple dependencies between the same elements. For example,
to add a satisfy relation between efficiency Combustion of Combustor and requirement
6.8.2 Combustor Efficiency, in the cell with VER, type VER, SAT and press Enter.

18.2 Multiple Relations in Matrix • 103

104 • 18 Relations Matrix

19 Predicates19.1 Introduction
In addition to the predicate samples in TMT folder, new enhancements to predicates definedwith stereotypes now allow you to add new elements to the model. Worksheet Requirements
displays all the requirements that are defined in the model. VerifiedRequirement shows
only the requirements which have verified Dependency. The ValueProperty and ConstraintParameterType worksheets display elements without a datatype defined. The PhysicalComponents table displays components that are “Blocks” with “Physical” stereotype. To
add a new element in the last two type a component name.

105

106 • 19 Predicates20 Matrices With Different Element Types
20.1 Introduction
When using matrices to illustrate relationships between elements, it is common to use thesame type of elements in either the rows or the columns. For example, when representing
a 'Satisfy' dependency, Requirements could be displayed in relation to either Classes orValue Properties. However, grouping different types of elements and displaying existing
relations has traditionally been challenging.
With the recent feature update, it is now possible to group elements based on certain criteria
and display them in the rows or columns of matrices. The TWCSysML-MultipleTypes
example illustrates this capability by displaying Requirements in the rows and Blocks alongwith Value Properties in the columns at the same level. This is achieved by grouping Blocks
and Properties and then displaying them together. It's important to note that the columns
will not allow new elements to be added to the model107

108 • 20 Matrices With Different Element Types

IndexB
Block Generalization, 7
Block Hierarcy, 9Nested, 11
Blocks in MapleMBSE, 1

C
Constraint Blocks, 8
Cost Analysis
Overview, 69
Results, 69
Visualization, 69
Countdown Timer Model
ActivityNode Table, 49
Activity ControlFlow Table, 49
Activity ObjectFlow Table, 49
Opaque Behavior Table, 47
State Behavior Table, 53
State Behavior Table,State Behavior
ControlFlow Table, 52
State Behavior Table,State ControlFlow Condition Table, 53CountDownTimer Table, 43Creating Requirements, 40
Overview, 39
Signal Table, 42StateMachine Properties Table, 45
Transition Table, 46Time BehaviorTable, 44Time Event Table, 43
UseCase Table, 40
Creating a Block in MapleMBSE, 2
Creating Aggregation, 5Creating Association Aggregation andComposition, 3Creating Composition, 5Creating Direct Association, 5Creating States and Transitions, 36, 37

D
Default Value Generation
BlocksTable Worksheet
Creating Components and Subcomponents, 73
Overview, 73
default value generation
AutoGeneratedTable, 74
Defining Blocks in MapleMBSE
List of Available Features, 1
Downloading sysML Diagrams
Example, 99
Introduction, 99

FFeature Model
Variant Management, 91
Fitness Tracker Model
Activity Diagram, 28, 33
Adding New Duration Constraints, 29Creating Actions for an Activity, 29Creating Flows, 30
Blocks Table, 23
Block Property Table, 26
Block Satisfaction Matrix, 25
Blocks Tree, 18
Blocks Tree,BlockProperties worksheet, 21
Internal Blocks Table, 27Creating Requirements, 14
Overview, 13
Packages Worksheet, 13
Requirements of the Systems, 15
Use Case Table, 17Creating a Use Case Table, 17
FMEA process illustration, 63
FMEA Template
Overview, 63
FMEAMatrix Worksheet, 63

I
Instance View109

110 • Index

Instance Multiplicity Table, 78
MatrixTemplate Worksheet, 77
Overview, 75
Interface Definition Template
ComponentsInteractionTable, 66
InterfaceRequirements Matrix, 66
Overview, 65
InterfaceClasses worksheet, 65
ItemFlow worksheet, 65

M
Matrix with mixed elements
Introduction, 107

P
Predicates
Introduction, 105

R
Relations Matrix
Multiple Relations, 103
Verify Matrix, 101
Requirements Table
Countdown Timer Model, 40

SSpacecraft Model
Introduction, 79
SPCStructure Template, 81
SPCUseCase Template, 79
SPCValueType Template, 79TTelescope Model
Introduction, 83
Signal Interface, 85
TMT Activity Template, 84
TMT OBSE Template, 85
TMT Predicate Template, 83
TMTInstance, 85
Turbofan Engine Model
Constraint Blocks, 56

ConstraintProperties Worksheet, 56
creating a verify relationship between
system requirements and value properties,
57
Defining Units and Types of Values, 56
Displaying Analysis Results, 56
InstanceResults table, 56
Overview, 55
System Model, 56
SystemRequirements Worksheet, 55
UnitQuantityKindTable Worksheet, 56
ValueTypesTable Worksheet, 56
VerifyRequirementsMatrix, 57
Turbojet Model
Instance Matrix, 89
Instance Specifications and Constraint
Properties, 88
Introduction, 87

UUnmanned Aerial Vehicle Model
Determining Scope and Mission, 60
OperatingDomainUAV Worksheet, 60
Overview, 59
Stakeholder Needs Analysis, 59
System Behavior
UAVBlackBox worksheet, 60
System Requirements, 60
System Behavior, 60
Weight Estimation, 60
Weight Estimation,WeightEstimationTable worksheet, 60
Wing Area Estimation, 61
Wing Area Estimation,WingAreaConstraint worksheet, 61
Wing Area Estimation,WingAreaEstimation worksheet, 61
UseCase Table
Associating Actors with Use Cases, 40

VVariant Management

Index • 111

Configurations, 93
Introduction, 91
Vehicle Analysis, 97
Variant Management Template
FeatureMatrix, 71
Overview, 71
VariantCheckTable, 72
Variant Points
Variation Management, 95

W
Working with State Machine Diagrams
Creating States and Transitions, 36, 37
Overview, 35, 36

112 • Index