Architecture Modeling - SPES 2020

6.1.1.1.1
Attribuute
Definit tion and SSemantics
There are
three kinds
of attribu utes that aree
used in th he functional
patterns: EEvents,
Inter rvals and
Conditions.
In most ccases
these attributes arre
intuitive to o use and no o special knoowledge
is necessary n
to speciffy
requiremeents.
This se ection defines
the exact syntax and semantic of basic and advanced a
features of the attribuutes
and its possible p connversions
and d combinatio ons.
6.1.1.1.1.1
Evennts
Events aare
signals thhat
occur at a defined pooint
in time. Examples ar re messagess
that get se ent over a
bus systtem,
sporadic
signals fr rom sensorss
or even us ser interactio on like presssing
a butto on. While
specifyinng
events thhe
names ca an be choseen
by the re equirements engineer, bbut
have to be used
consistently,
i.e. samme
events ha ave to have the same id dentifiers. If there
exists aan
architectu ure these
names hhave
to be mapped
to the e correspondding
parts in the t design model m in laterr
design stag ges.
Specifyy
locationn
of event occurrencce
It is posssible
to specify
for each event e the loccation
where it occurred.
A compoonent
can reefer
to system m componennts
like “Brak ke Actuator” or “Engine CController”
bu ut also to
non systtem
artefactss
like “Driver r” or “Passennger”.
It is hig ghly recomm mended to usse
the same identifier
for samee
componentts.
In later ddesign
steps the compon nent identifierrs
can be ma apped to the actual archiitecture
of the
system
to start aanalysis
taskks.
Even the consistent uuse
of identif fiers can be one o of the poossible
analy yses, it is
not part of the speciffication
langu uage to guaraantee
consis stency, but allow
the checcking
of it.
The termm
“Componeent”
can be fu urther refinedd:
and
The requesst
event star rts the patterrn
and requires
a respon nse in the defined
time frame. Is
there no request
event there is no specification n for the occurrences
of tthe
response
events.
There mighht
be such an n event or noot.
But of courrse
there might
be otheer
patterns th hat restrict the t occurrennces
of the response
event.
Event on
whenever GearUp on ShifttPaddleCon
ntroller
occurs duuring
[0ms s,100ms].
Event on
Event on
Component t
user User r
system Sy ystem
Architecture Modeling
Component
Useer
System S
occurs oopen
on
clutch
It is posssible
to use component and user or system. The e later ones can be usedd
to explicitly y mention
user inteeraction
or syystem
behav vior.
111/ 156