Requirement Properties

Requirement properties differ slightly from the properties of other elements; they include information related to the Type, Status, Difficulty and Priority of the Requirement. The Notes field is also important, as it describes precisely what requirement the element represents. Requirement naming can also require careful consideration and could reflect either a categorical naming convention, or simply a loose English description of the Requirement.

Access:     Requirement Element Context Menu | Properties

Use to:

  • Document requirements
  • Set Requirement features such as Type, Status and Priority
  • Set other element properties common to both Requirements and other model Elements




See Also

Short Description

The name of this requirement, which could include numbering, plain English description or some other formal specification



An alias to be used for this requirement

Auto Counters


The current status of this requirement

Color Code Requirements


An estimate of the difficulty in meeting this requirement. Enterprise Architect supports the values 'Low', 'Medium', 'High'



The relative importance of meeting this requirement compared to other requirements; select from:

  • Low
  • Medium
  • High'



The author of this requirement


Key Words

A set of words that could be used to index or define the subject of this requirement



The type of this requirement.  This is typically used as a category for the requirement.

Requirement Types


The phase of this requirement.



The version of this requirement.


Last Update

Read-only field specifying when this requirement was last changed.



Read-only field specifying when this requirement was first created.



The description of this requirement.

Note Editors, Linked Documents


  • 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 topic

Learn More