The Require tab of the element Properties dialog is shown below. Use this page to create requirements that this element is designed to meet. Requirements are of two types: internal requirements (responsibilities) and external requirements (system requirements). Enterprise Architect shows both types, but you can only edit the internal type from this tab.
Internal requirements form the functional requirements of the system to be built. The meaning of the requirement can vary depending on which element is the host; for example, a business process requirement might mean something different to a Use Case requirement, which again might mean something different to a Class requirement. Use these as best suit your model.
Use the Specify Feature Visibility function to show the requirements for an element on the diagram directly (it is also possible to show inherited requirements in this way).
Note: |
External requirements are those linked to this element using a Realization link. |
Option |
Use to |
Requirement |
Enter the name and high level detail of the requirement. |
Type |
Specify the type; for example, Functional or Non-functional. Functional requirements are things that the system must do, such as identify franked, unfranked and total credit for a dividend; non-functional requirements are things that the system must be, such as reliable, cost effective. |
Status |
Specify the current status of the requirement. |
Difficulty |
Identify the complexity of implementing the current requirement. |
Priority |
Specify how urgent the requirement is. |
Last update |
Specify the date of the last requirement update. |
Notes |
Record details of the requirement. You can format the notes text using the Rich Text Notes toolbar at the top of the field. |
Make an internal responsibility into an external requirement. |
|
New |
Create a new requirement. |
Save |
Save changes to requirements. |
Delete |
Delete a selected requirement. |
Defined |
List the defined requirements associated with this element. |