| Prev | Next |
Requirement Properties
Requirement properties differ slightly from the properties of other elements; they include information related to the difficulty and priority of the Requirement. The 'Notes' field is also important, as it describes precisely what requirement the element represents. Requirement naming requires careful consideration and could reflect either a categorical naming convention, or simply a loose English description of the Requirement.
Access
On a diagram or in the Browser window, select a Requirement element and:
|
Ribbon |
Design > Element > Editors > Properties Dialog |
|
Keyboard Shortcuts |
|
|
Other |
Double-click on Requirement element |
Fields
Field |
Action |
See also |
|---|---|---|
|
Name |
The name of this Requirement, which could include numbering, plain English text or some other formal specification. If you have set autonaming and autonumbering, the field contains the auto-counter text. |
Set Auto Naming and Auto Counters |
|
Notes |
The description of this Requirement. |
The Notes Window Linked Documents |
|
Stereotype |
Either type in the name of a stereotype to be assigned to the Requirement, or click on the |
Stereotype Selector |
|
Alias |
An alias to be used for this Requirement. If you have set alias autonaming and autonumbering, this field contains the auto-counter text. |
Set Auto Naming and Auto Counters |
|
Status |
The current status of this Requirement. |
Color Code External Requirements |
|
Version |
The version of this Requirement. |
|
|
Phase |
The phase of this Requirement. |
|
|
Language |
Click on the drop-down arrow and select the appropriate programming language, or the <none> option. |
|
|
Filename |
Click on the |
|
|
Difficulty |
An estimate of the difficulty in meeting this Requirement; select from:
|
|
|
Priority |
The relative importance of meeting this Requirement compared to other Requirements; select from:
|
|
|
Package |
The name of the Package that contains the Requirement element. |
|
|
Complexity |
Click on the drop-down arrow and select the appropriate development complexity (used for project estimation). You normally select from three levels:
You can change your user defaults to add 'Extreme' and 'Unknown' to this list of options. |
|
|
Created |
Read-only field specifying when this Requirement was first created. |
|
|
Modified |
Read-only field specifying when this Requirement was last changed. |
|
|
Key Words |
A set of words that could be used to index or define the subject of this Requirement. |
|
|
GUID |
The globally unique identifier (GUID) of the Requirement element. |
|
|
Author |
The author of this Requirement. |
Project Authors |
button and use the Stereotype Selector to locate and select the stereotypes to assign. Notes
- In Requirement Management tools and texts, the characteristics of a requirement are commonly called 'attributes'; however, in UML the term 'attribute' refers to a different type of feature, and the Requirement characteristics are defined as 'properties' - in this Enterprise Architect documentation, the term 'properties' is used
- In a project, it might be necessary to define more information in a Requirement than is provided by the standard properties; for more information on extending the Requirement properties, see the Extend Requirement Properties Help topic