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 |
||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
A Package is a namespace as well as an element that can be contained in other package's namespaces. A Requirement defines a requirement of a system. Note that there are several different requirement types, 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. An Object is an instance of a Class.
|
|
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 |
The material ("material" includes all pages, documents and on-line graphics) on this web site is protected by copyright law. (C) 1998-2013 Sparx Systems Pty Ltd.
