System context diagram Use case diagram

bdd [package] Context [System context] uc [package] Use case [Use case]

*
«block» «block»
Context Environment Use Case
«extend»
Optional Use Case
* extension points
User optional
«block»
External system «include»
*
1

«block»
System
Specialized Use Case Secondary Use Case

User

bdd [package] Ports [Ports]

bddBlock definition
[package] Block definitiondiagram
diagram [Diagramme de Définition de Blocs] Ports
Full port Conjugated
«block»
(SysML 1.3+) Port
{encapsulated}
Proxy port
Block
(SysML 1.3+) «full» name1 : Block name2: ~Block flow ports
val1: Type (SysML 1.1/1.2)
Value distribution on val2
«uniform» «proxy» name9 : «block»
Constraints:
val2: Type Interface Block System Block «flowPort»
{mean=2, stdDeviation=0.1}
name3: Type
op1(param1: Type, param2: Type): Type
name8: Block
constraints «flowPort»
{val1 > 0} nameA name4: Type

properties
nameB «flowPort»
p1 : Bloc
name5: Type
references
r1 : Bloc Nested ports name7: Block name6: Block
bdd [package] bdd [bdd]

«block» +role1 Simple association +role2 «block»

Block 1 Block 2 «block» «interfaceBlock»
1..* 1..* Block Interface Block
+role3 +role4 value: int «DirectedFeature»
1..* 1..* prov operation(): Type
«DirectedFeature»
prov op1(params): Type Provided and
flow properties
«block» requested
reqd op2(params): Type inout flow 1
Association Block features
in flow 2
directed features
prov name : Type
«block» «block»
Navigable association flow properties
Block 1 Block 2
in p1 : Type input, output,
inout p3 : Type in/out flows
out p2 : Type

«block» Aggregation «block»

Block 1 Block 2
bdd [package] bdd2 [bdd2]

«quantityKind» «block»
«block» «block»
Composition Length Abstract block
Block 1 Block 2

«unit»
«block» Dependency «block» {quantityKind = Length} +role1 0..*
Block 1 Block 2 Meter
Item Flow

«ValueType»
«block» Generalization «block» Type
Block 1 Block 2

+role2 0..1

«block»
«valueType» Block
Type
«block» namespace
- name: Type Block
«enumeration»
«block» «block»
+ name(param: Type): Type EnumerationType c
t2: Part2 Block 1 Block 2
t1: Part1
quantityKind = Literal1
unit = aUnit Literal2

OMG Systems Modeling Language (OMG SysML™) 1.4 Reference card, page 1/4
(http://www.omgsysml.org) © 2017 by Tim Weilkiens, www.oose.de
Modelling tool: Sparx Systems Enterprise Architect
MBSE Blog: http://www.model-based-systems-engineering.com Author: Guillaume FINANCE (http://www.umlchannel.com)
 Internal block diagram
y ibd [block] Association Block [Association Block IBD]
ibd [block] Block [Block IBD]

Item flow Reference

participant property
role1: Type role2: Type
nom «participant» «participant»
{end=role: Type} {end=role: Type}
LienIn1 : Type LienIn2 : Type
«ValueType» Type
port «proxy» p : TypePort
Multiplicity
connector

Nested connector
port role : Type

role3: Type[2] «proxy» p : ~TypePort

role4: Type ibd [block] Bloc [IBD]

roleA: Type roleB: Type property-specific type

«ValueType»
Type

role1 role2: Type

val1 = 42 t = "text"
val1 = 42

Unidirectional
connector

Requirements
req [package] Exigences [Exigences] req [package] Exigences [Exigencesreq
A] [package] Exigences [Exigences B]

Requirement X Requirement Y
Master TracedTo TracedFrom
id = "4712" copies relationship id = "4711" «requirement» Requirement X «requirement» Requirement X «requirement» Requirement Y
Add properties
text = "The System must text = "The System must Clic droit > Features & Properties > Set Property
«copy» Par contre pas de différence sur initial values
provide details of the client." provide details of the client."

Requirement Y Requirement X
Requirement Sub-Requirement Connecteur
unidirectionnel

Derived RefinedBy SatisfiedBy VerifiedBy

«requirement» Requirement X Use Case Block TestCase
Requirement X Requirement Y
infers requirement
req [package] Exigences [Exigences C]
«deriveReqt»

«block»
Satisfies
Block
«requirement» Requirement X

Requirement X Requirement Y
traceability
«trace»
Packages
pkg [package] Paquetages [Paquetages]

Package
Requirement X
refines requirement
Use Case
«refine»

Requirement X «block» Subpackage

satisfies requirement Block
«satisfy»
Subpackage

Requirement X «testCase»
verifies requirement TestCase
«verify»

Subpackage

«block»
Block

OMG Systems Modeling Language (OMG SysML™) 1.4 Reference card, page 2/4
(http://www.omgsysml.org) © 2017 by Tim Weilkiens, www.oose.de
Modelling tool: Sparx Systems Enterprise Architect
MBSE Blog: http://www.model-based-systems-engineering.com Author: Guillaume FINANCE (http://www.umlchannel.com)
 Sequence diagram
seq [package] seq1 [seq1] seq [package] seqABC [seq]

role1: Type role2: Type

role1: Type ref seqABC

alt
asynchronous message
Lifeline Combined fragment [a<b] ref
Focus of (alternatives) seqABC
decomposition
control synchronous message

reply [else]
ref
seqXYZ

message to self

Destroy instance
seq [package] seqABC [seqXYZ]

role1: Type role2: Type Elaborated sequence diagram of

referenced interaction SeqXYZ
role3: Type
Create instance

message()

Activity diagram

act [activity] Activity [Activity]

Interruptible Partition
Start Node Activity
Accept Event
Region Activity
Final Node
Time overwrite
Event Receive Event
Time
Action rate = 1/minute; nobuffer
Event
ObjectA ObjectB «discrete»
«continuous»
"optional"
stream Action

Continuous Step
Action
[else] [x > 0]
Flow Final
Node Action Object
[State]
{ control }
Pin
Essential Step «controlOperator» Action name:
BehaviourName
Action
«Post-condition»
{Condition}
«Pre-condition»
{Condition}

Action {weight=0.25}
name: Type
Send Signal [y<0]
[State] Action {weight=0.75}
name: Type [else]

Object

Activity Parameter Node Activity Parameter Node Activity Parameter Node

act [package] activity [Activity tree]

Comments and constraints
act [package] activity [contraintes]
«activity»
Activity 1
«rationale»
Rationale of modelling Comment

action pins input/output defined but not shown on the diagram

Name of Object Node Name of Action

«problem»
{x > y}
«block» «activity» Problem description
Block Activity

Constraint

OMG Systems Modeling Language (OMG SysML™) 1.4 Reference card, page 3/4
(http://www.omgsysml.org) © 2017 by Tim Weilkiens, www.oose.de
Modelling tool: Sparx Systems Enterprise Architect
MBSE Blog: http://www.model-based-systems-engineering.com Author: Guillaume FINANCE (http://www.umlchannel.com)
 State Machines
stm [StateMachine] StateMachine [StateMachineName]

Initial state Entry point

History
Orthogonal State (parallel)

[A]
State State 3
State1
event [guard] /action entry / action
do / activity
exit / action
event[condition] / action [B]
State 4 State 5

at(time) Junction after(time) /action

Entry point event [condition]

/Send signal
Composite state
Receive Signal
[condition] /effect

stm1: Machine
Final state [x>0] [x<-5]

[else] Terminate

Exit point
State 6

Exit point

Allocations
bdd [package] allocation [allocation] act [package] activity [activity]

«block» «block» «allocated» :Physical Block 1 «allocated» :Physical Block 2

Logical Block Physical Block 1

présentation
«allocate» alternative à
AllocatedFrom Allocation
Action1 &
l'overview de l'emission Activity Partition
reception de signal

Action1 Action2

act [activity] [allocations]

Action

Object: Logical Block

Parametric diagram

«block» par [block] Block1 [Block1]

ActivityName «allocate» bdd [package] parametrique [parametriq...
Logical Block
Allocated via the
instance/classifier link «constraint» valueA PartB.valueC
Object p Constraint Block
«allocate»
constraints
{x > y}

«allocated» constraint properties x : Real y : Real

Object
p z1 : Constraint Block b : Constraint Block
{x > y}
«block» parameters
Action Logical Block B x : Real
y : Real

OMG Systems Modeling Language (OMG SysML™) 1.4 Reference card, page 1/4
(http://www.omgsysml.org) © 2017 by Tim Weilkiens, www.oose.de
Modelling tool: Sparx Systems Enterprise Architect
MBSE Blog: http://www.model-based-systems-engineering.com Author: Guillaume FINANCE (http://www.umlchannel.com)