| Prev | Next |
Requirement Properties
Getting to Know the Requirement Properties
|
Introducing Requirement Properties |
Requirement Properties define metadata about the Requirement that is useful for the management of Requirements for the purposes of prioritization and defining work Packages for the implementation teams. All Enterprise Architect elements have standard properties such as Status, Author and Phase, and the Requirement element has additional properties such as Difficulty and Priority. User-defined properties can also be created using Tagged Values. 
|
|
Where to find Requirement Properties |
Ribbon: Design > Element > Editors > Properties Element Context Menu: Properties... | Properties... or Browser window Context Menu: Properties | Properties... |
|
Usage of the Requirement Properties |
The Properties define the important meta information about a Requirement, for the purposes of providing data to manage Requirements for prioritization, understanding which are the difficult Requirements, and managing the lifecycle by using Status to determine Requirements for implementation Packages. |
|
Options for Requirement Properties |
Enterprise Architect has a wide range of built-in properties for all elements, and a number of additional Requirement Properties. If other properties are needed by a modeler or team, such as the volatility (stability) of a Requirement, these can be added using the general-purpose UML extension mechanism of Tagged Values. 
|
|
Learn more about Requirement Properties |