Prev | Current Page 431 | Next

Tim Weilkiens

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


req [package] Functional requirements [car usage without staff]
Start car usage
End car usage
Show car
usage data
?«refine?»
?«functionalRequirement?»
Car usage without staff
?«refine?»
?«refine?»
FIGURE 4-15
Test case example.
req [package] Test [send messages]
?«testCase?»
SendMessagesTest
?«verify?» ?«functionalRequirement?»
Car usage without staff
A requirement is a rather coarse model element. In addition to the name and an
ID, you can add some text to describe a requirement. This is not suffi cient for a
detailed description.
For example, a functional requirement can be refi ned by one or more use
cases ( Figure 4.16 ).
This relationship is used only within the model. It does not serve for refi ning
by external sources, such as a requirement management tool. For this purpose,
you ??™ d use the text property of the requirement, which references an external
source.
SysML takes this relationship unchanged from UML, but it adds an alternative
notation that let ??™ s you denote the relationship within a comment symbol ( Figure
4.


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