Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.
Requirements Toolbox
As an analysis step, often it is desirable to capture simple system requirements. These are eventually realized by Use Cases.
Requirements Toolbox pages
Image |
Detail |
See also |
||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
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. Note that there are several different types of requirement, such as:
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.
|
|
Notes
| • | To add an element to the currently-open diagram, click on the appropriate icon and drag it into position on the diagram; set an element name and other properties as prompted |
| • | To add a relationship, click on the appropriate icon, then click on the start element in the diagram and drag to the end element |
