Table 2.20 Summary: Modeling system structures.
Reference card: Model system structures.
Incoming and outgoing data
System context [interfaces]:
System with interface description of the
interaction points.
Use cases:
Services provided by the system.
System structures:
Description of the static structures of the
system.
Motivation/description
Why? The system structures form the static design of the system.
What? Model the blocks and their relationships in suffi cient depth of details as
required by the entire system to meet the project requirements.
How? Determine the required blocks and structures for each use case or
requirement, and model all these in block diagrams.
Where? The blocks of the system design can, in turn, describe the system in a
discipline-specifi c development project, e.g., a software application or a hardware
component.
Guiding questions
?– What blocks are required to realize the use cases/requirements?
?– How is a block composed?
?– How are the blocks interconnected?
?– What interaction points and interfaces do the blocks have?
SysML elements
Block defi nition diagram, internal block diagram, block, interface, association,
connector, port, information object fl ow.
Pages:
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262