As an analysis step, often it is desirable to capture simple system requirements. These are eventually realized by Use Cases.
Requirements Toolbox pages
Except where discussed here, each element and relationship that you can create using these Toolbox pages is described in the UML Elements and UML Connectors sections of the Help.
A Requirement is a custom element used to capture system requirements external to individual UML elements; a Requirement expresses required system behavior that can cross several Use Cases. You can create a number of specific types of stereotyped Requirement from their own element icons.
Requirements Checklist is a stereotyped Checklist, and is rendered as this element:
A Feature is a small client-valued function expressed as a requirement. Features are the primary requirements-gathering artifact of the Feature-Driven Design (FDD) methodology.
A Risk element represents an identified risk to the project.
You can also add structures of Functional and Non-Functional Requirements to your diagram, each with a Checklist, using the two Requirements Patterns.
|Requirement Behavioral Diagram Elements Structural Diagram Elements Feature Risk UML Connectors|