You are on page 1of 4

System Context Diagram Use Case Diagram

bdd System Context SYSMOD uc


SYSMOD SYSMOD
SYSMOD

SYSMOD
Continuous System Process
Use Case
External System
Environmental
Effect SYSMOD «include»
Sensor
«system» Use Case
System User
SYSMOD SYSMOD «include»
Information Flow SYSMOD

Specialized Secondary
Mechanical Use Case Use Case
Actuator
System
User

Block Definition Diagram Ports


Atomic
«block» Interface Flow Ports
{encapsulated} Flow Port
Block
Standard Port
values name1:Flow- name3:Type
Value val1:Type Specification «block»
distribution «uniform» {mean=2, stdDeviation=0.1} val2:Type
name2:Flow - SystemBlock
operations Specification name4:Type
op1(param1:Type, param2:Type):Type
constraints Conjugated
{val1 > 0} Flow Port
parts
p1:Block «flowspecification» «interface»
name:SystemBlock [Multiplizität] FlowSpecification Interface
references
r1:Block
flow properties op1(param:Type):Type
in p1:Type
bd d 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 Navigable Block 2 SYSMOD

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
InformationFlow
«block» «block»
Specialized General Meter
Block Generalization Block
«unit»
0..1
dimension=Length
role2
«enumeration»
«block» «block»
«valueType» EnumerationType
Block Block
ValueType
Literal1
operations structure namespace
Literal2
name(param:Type):Type
«block» «block»
properties t1:Part 1 t2:Part 2
«dataType» c: Block 1 Block 2
name:Type
DataType

OMG Systems Modeling Language (OMG SysML™) 1.0 (http://www.omgsysml.org) Reference card, page 1/4
incl. SYSMOD stereotypes (http://www.system-modeling.com) © 2007 by oose GmbH, www.oose.de
Tim Weilkiens, Systems Engineering with SysML/UML, Morgan Kaufmann, 2008 Translation Thomas 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"
defaultValue
text="The System..." text="The System..." val1:Type=42
val1=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
«refine» «requirement» Requirement X «viewpoint»
«requirement» Viewpoint
Use Case
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.0 (http://www.omgsysml.org) Reference card, page 2/4
incl. SYSMOD stereotypes (http://www.system-modeling.com) © 2007 by oose GmbH, www.oose.de
Tim Weilkiens, Systems Engineering with SysML/UML, Morgan Kaufmann, 2008 Translation Thomas Netter
Sequence Diagram
sd
sd

role1:Type role2:Type
role2:Type
role1:Type
ref LifelineDecomposition

Combined fragement alt [a<b]


asynchronous message (alternatives)
ref
SeqABC

Focus of control synchronous message


[else]

reply ref
SeqXYZ
message to self
Elaborated sequence
Destroy Instance diagram of referenced
interaction SeqXYZ sd 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]
Action «continuous»
Continuous
Flow Final Node Step Object
SYSMOD Action [State]
«essential» {control}
Essential «controlOperator» Action name :
Step Action Behavior name
Pin «localPostcondition»
«localPrecondition» Condition SYSMOD {probabiliy=0.25}
Condition «secondary» [ y < 0]
Secondary
Step
Send name:Type [else]
Action
Signal [State] {probability=0.75}
name:Type

Object

Activity Parameter Activity Parameter Activity Parameter


Node Node Node

bdd Function Tree Comments


«activity»
Activity «rationale»
Description of Comment
rationale

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

OMG Systems Modeling Language (OMG SysML™) 1.0 (http://www.omgsysml.org) Reference card, page 3/4
incl. SYSMOD stereotypes (http://www.system-modeling.com) © 2007 by oose GmbH, www.oose.de
Tim Weilkiens, Systems Engineering with SysML/UML, Morgan Kaufmann, 2008 Translation Thomas 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
Logi cal 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.0 (http://www.omgsysml.org) Reference card, page 4/4
incl. SYSMOD stereotypes (http://www.system-modeling.com) © 2007 by oose GmbH, www.oose.de
Tim Weilkiens, Systems Engineering with SysML/UML, Morgan Kaufmann, 2008 Translation Thomas Netter

You might also like