Prev | Current Page 434 | Next

Tim Weilkiens

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


The columns of a requirements table represent the properties of the ID and
the requirement text ( Figure 4.19 ) as well as the relationships of that requirement
to other requirements ( Figure 4.20 ).
4.4 Allocation
An allocation is a general mechanism from the field of systems engineering to
interconnect elements from different model areas. For example, binding an item
flow in the internal block diagram, which occurs in a different form, as an object
flow, in an activity diagram ( Figure 4.21 ). Such a binding is normally present
in a complete model through a wealth of details and deeply hidden paths, and
not visible at a glance. A systems engineer cannot penetrate these detail depths.
Nevertheless, they want to model the connections, even in an early project phase.
There are different types of allocations. SysML proposes three general types and
let ??™ s the developer introduce additional project-specifi c variants. The predefi ned
types are behavior allocation, structure allocation, and object fl ow allocation.
FIGURE 4-19
Table notation for requirements.


Pages:
422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446