System Context Diagram Use Case Diagram

bdd System Context SYSMOD uc

SYSMOD SYSMOD
SYSMOD
«system process»
SYSMOD «continuous use case» System Process
Continuous
External System Use Case
Environmental
Effect SYSMOD «include»
Sensor
«system» Use Case
System «user»
User
SYSMOD SYSMOD «include»
Information Flow SYSMOD

Specialized «secondary use case»

SYSMOD Secondary
Mechanical Use Case Use Case
System «user» Actuator
User

Block Definition Diagram Ports Standard Port

Atomic
«block» Interface Flow Ports
{encapsulated} Flow Port
Block
name5:Type
values name1:Flow-
Value val1:Type Specification name3:Type
distribution «block»
«uniform» {mean=2, stdDeviation=0.1} val2:Type System Block
name2:Flow- name4:Type
operations Specification
op1(param1:Type, param2:Type):Type «junction port» name7:Document
Conjugated name6:Type SYSMOD
constraints Flow Port SYSMOD
{val1 > 0}
parts
p1:Block «flowspecification» «interface»
name:SystemBlock [Multiplizität] FlowSpecification Interface
references
r1:Block
flow properties op1(param:Type):Type
in p1:Type op2(param:Type):Type
bdd out p2:Type
1..* Simple association 1..* inout p3:Type
«block» role1 role2 «block»
Block 1 Block 2 Flow Direction
1..* 1..*
role3 SYSMOD SYSMOD
role4
«block» «domain» «systemContext»
Association Specialized SystemContext
Block Block Element
«block» «block»
Block 1 Block 2 SYSMOD
Navigable
Association «subsystem» «stereotype»
Subsystem Block
«block» «block»
Whole Aggregation Part
«block»
«block»
Block
Block
«block» «block» {abstract}
Whole Composition Part of Composite p:FS
Standardport Interface 0..*
role1
«block» «block»
Dependent Independent «dimension»
Block Dependency Block Length
Information Flow
«block» «block» «unit»
Specialized General Meter
Block Generalization Block
«unit»
0..1
dimension=Length
role2
«valueType» «enumeration»
ValueType «block» «block»
EnumerationType
Block Block
operations
name(param:Type):Type Literal1
structure namespace
Literal2
properties
name:Type «block» «block»
t1:Part 1 t2:Part 2
«dataType» c:Association Block 1 Block 2
«valueType» DataType
unit=aUnit

OMG Systems Modeling Language (OMG SysML™) 1.1 (http://www.omgsysml.org) Reference card, page 1/4
incl. SYSMOD stereotypes (http://www.sysmod.de) © 2008 by oose GmbH, www.oose.de
Tim Weilkiens, Systems Engineering with SysML/UML (http://www.system-modeling.com) Translation support T. Netter
Internal Block Diagram

ibd [block] Block Reference ibd [block] Association Block

Item Flow
Participant property
role1:Type role2:Type

name:Type «participant» «participant»

{end=role} {end=role}
connector:Association inLink1:Type inLink2:Type
Nested
Connector
role3:Type 2

0..1
roleA:Type roleB:Type role4:Type role:Type
Multiplicity

Requirements ibd [block] Block Property-specific

type
«requirement» «requirement»
Requirement X Requirement Y Master
«copy» «requirement» Requirement X role2:[Type]
«requirement» «requirement» role1:Type
id="4712" Copies relationship id="4711"
initialValues
text="The System..." text="The System..." :values
val1=42
val1:Type=42
t="text"
Unidirectional
Connector
«requirement» «requirement»
Requirement Sub-Requirement
Derived
«requirement» Requirement X Model View
«requirement» «deriveReqt» «requirement»
Requirement X Infers requirement Requirement Y
TracedTo «view»
«requirement» Requirement X {viewpoint=name}
«requirement» «trace» «requirement» View
Requirement X Traceability Requirement Y «conform»

Refines
«requirement» «refine» «requirement» Requirement X «viewpoint»
Use Case Viewpoint
Requirement X Refines requirement
«viewpoint»
Satisfies stakeholder="Who has an interest in the model view?"
«requirement» «satisfy» «block» concerns="Which requirements satisfy the model view?"
«requirement» Requirement X
Requirement X Satisfies requirement Block purpose="What objectives/purposes fulfil the model view?"
methods="What methods/processes build the model view?"
languages="What languages constitute the model view?"
Verifies
«requirement» «verify» «testCase» «requirement» Requirement X
Requirement X Verifies requirement TestCase Packages

DerivedFrom TracedFrom RefinedBy

«requirement» Requirement Y «requirement» Requirement Y «usecase» UseCase Package

Subpackage
SatisfiedBy VerifiedBy
«block» SystemBlock «testcase» TestCase

Subpackage

table Requirements Table

ID Name Text Subpackage

4711 Requirement The System...

... ... ... «block»

Block

OMG Systems Modeling Language (OMG SysML™) 1.1 (http://www.omgsysml.org) Reference card, page 2/4
incl. SYSMOD stereotypes (http://www.sysmod.de) © 2008 by oose GmbH, www.oose.de
Tim Weilkiens, Systems Engineering with SysML/UML (http://www.system-modeling.com) Translation support T. Netter
Sequence Diagram
sd SeqABC
sd

role1:Type role2:Type
role2:Type
role1:Type
ref SeqABC

Combined fragement alt [a<b]

asynchronous message (alternatives)
Lifeline Decomposition ref
SeqABC

Focus of control synchronous message

[else]
reply ref
SeqXYZ
message to self
Elaborated sequence
Destroy Instance diagram of referenced
sd SeqXYZ
interaction SeqXYZ

Create Instance role1:Type role2:Type

role3:Type message

Activity Diagram

act Interruptible Activity

Partition
Activity Region Final Node
Start Node Accept
Event
Receive
ObjectA Event
«overwrite»
Action Time Event «discrete»
Time Event «nobuffer»
{rate=1/minute}
«continuous»
ObjectB «optional» {stream}
SYSMOD Action
[else] [x > 0] «continuous activity»
Action Continuous
Step Object
Flow Final Node
SYSMOD Action [State]
«essential activity» {control}
Essential «controlOperator» Action name :
Step Action Behavior name
Pin «localPostcondition»
«localPrecondition» Condition
{probabiliy=0.25}
Condition [y < 0]
Action
Send name:Type [else]
Action
Signal [State] name:Type {probability=0.75}

Object

Activity Parameter Activity Parameter Activity Parameter

Node Node Node

bdd Function Tree Comments

«activity»
Activity «rationale»
Rationale of Comment
modeling

Constraint
Name of Name of
Object Node Action
«problem»
«block» «activity» {x > y} Problem description
Block Activity

OMG Systems Modeling Language (OMG SysML™) 1.1 (http://www.omgsysml.org) Reference card, page 3/4
incl. SYSMOD stereotypes (http://www.sysmod.de) © 2008 by oose GmbH, www.oose.de
Tim Weilkiens, Systems Engineering with SysML/UML (http://www.system-modeling.com) Translation support T. Netter
State Machines

stm StateMachineName

Entry point
History
Initial state
H Orthogonal State

State

event[guard]/behavior State
entry/behavior
State
do/behavior
exit/behavior
Junction event[condition]/behavior
State State

at(time) after(time)/behavior event[guard]

Entry point Receive

Send Signal
Composite Signal
State

Terminate Behavior
Final state [x>0] [x<-5]
stm1:StateMachine
[else]
Exit point

State

Exit point

Allocations
«allocate» «allocate»
«block» Block 1 Block 2
«block» «allocate» Physical Block Allocation
Logical Block Activity Partition
allocatedFrom
«action» Action

Action Action
act
Action

Object
Parametric Diagram
allocatedTo
«elementType» Element name

par [package] Package

ActivityName
allocatedTo
«constraint»
«elementType» Element name valueA PartB.valueC
Constraint block
Object
constraints
{x > y}
Object z1:ConstraintBlock
allocatedTo x: y:
«connector» Connector Action parameters
x:Real
b:ConstraintBlock
y:Real

OMG Systems Modeling Language (OMG SysML™) 1.1 (http://www.omgsysml.org) Reference card, page 4/4
incl. SYSMOD stereotypes (http://www.sysmod.de) © 2008 by oose GmbH, www.oose.de
Tim Weilkiens, Systems Engineering with SysML/UML (http://www.system-modeling.com) Translation support T. Netter