Prev | Current Page 244 | Next

Tim Weilkiens

"Systems Engineering with SysML/UML: Modeling, Analysis, Design"

This is normally not meaningful,
since the standard fl ow is suffi cient. You should add variants only if they help you
gain new fi ndings. Otherwise, the modeling effort would rise out of proportion.
2.7.2 Derive System Interfaces
Deriving system interfaces is shown in Table 2.19 .
From the interaction models in the previous step (Section 2.7.1) we can
understand the kind of messages our system receives from the actors, and which
messages it sends to them. This provides us with an idea about the protocols that
each of the interaction points understands.
Table 2.19 Summary: Deriving system interfaces.
Reference card: Derive system interfaces.
Incoming and outgoing data
System context [interaction points]:
System with interaction points.
Interaction model [system/actor]:
Interactions between the system and its
actors.
System context [interfaces]:
System with description of interfaces for
the interaction points.
Motivation/description
Why? A specifi cation of the interfaces is required to be able to integrate the system
with its environment.


Pages:
232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256
Wczasy nad morzem kasyno kino azjatyckie bwin out of home advertising