Prev | Current Page 433 | Next

Tim Weilkiens

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


4.3.10 Table Notation
Many people like to represent requirements in pure text form??”most frequently
in tables??”rather than in graphical form. This is meaningful mainly when you
want to display total overviews of several hundred or thousand requirements
(requirements list). SysML offers a table notation. The table is a diagram extension
4.3 The Requirement Diagram
FIGURE 4-17
Alternative notation for refi ne.
req [package] Functional requirements [alternative notation refine]
Refines
?«requirement?» Car usage without staff
Start car
usage
?«functionalRequirement?»
Car usage without staff
RefinedBy
?«usecase?» Start car usage
?«usecase?» End car usage
?«usecase?» Show car usage
FIGURE 4-18
Example for a trace relationship.
req [package] On-board computer requirements [example trace]
?«usabilityRequirement?»
Display size
?«trace?»
?«usabilityRequirement?»
Usage concept
central unit
238 CHAPTER 4 SysML??”The Systems Modeling Language
that cannot be defined by stereotypes. It has to be explicitly supported by the
modeling tool.


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