Books for you

The concepts and artifacts described in the
UML chapter (Chapter 3) also apply to SysML.
4.3 The Requirement Diagram
SysML defines several elements to describe and model requirements, such as
response times, size or functions of a system, which means that it closes a gap in
UML. While functional requirements can be modeled with use cases, there is no
element in UML to explicitly describe non-functional requirements.
FIGURE 4-2
The structure of SysML.
Activity diagram
Use case diagram
State machine diagram
Sequence diagram
Block definition diagram
Internal block diagram
Parametric diagram
Package diagram
Behavior model Structure model
Diagram Model
Structure Behavior
Requirement diagram, stereotype,
model view, AP-233, XMI Metadata
Interchange format
Other
227
However, since such elements are needed in practice, a number of different
proposals emerged in the course of time to allow you to model requirements
using UML. Most of these proposals are based on the defi nition of special stereotypes.
One of these proposals is SysML.


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