Prev | Current Page 418 | Next

Tim Weilkiens

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


Operations are not permitted. Functional requirements are described in more
detail in other model elements, such as use cases or interfaces, but not by using
operations with the requirement element itself. Attributes are not permitted either.
These two properties of a requirement (ID, text) are not attributes of the
requirement itself, but modeled as attributes of the stereotype ?«requirement?» .
Other properties, such as a priority, can be introduced over an independent
FIGURE 4-4
Example for a requirement diagram.
req [package] On-board computer requirements [selection]
?«requirement?»
id  ???REQ2.1???
text  ???The central unit of the onboard
computer has to fit in a
DIN compartment.???
?«requirement?»
Enclosure size central unit
?«requirement?»
DIN compartment
?«deriveReqt?»
?«requirement?»
id  ???REQ2.2???
text  ???The central unit of the onboard
computer must not exceed
the admissible weight of 2.5 kg.???
?«requirement?»
Weight central unit
?«usabilityRequirement?»
Display size
?«deriveReqt?»
?«trace?»
?«requirement?»
Resolution
229
extension of the stereotype.


Pages:
406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430