Requirements

You use the Requirements page of the element Properties dialog to create requirements that this element is designed to meet.

Requirements are of two types:

  • Internal requirements (responsibilities) and
  • External requirements (system requirements, elements connected to the element by a Realize connector)

Enterprise Architect shows both types, but you can only edit the internal type from the Requirements page.

You can show the requirements for an element on the diagram directly, using the Feature Visibility function; it is also possible to show inherited requirements in this way.

Field/Button

Usage

See Also

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 or cost effective

 

Last update

Specify the date of the last requirement update

 

Status

Specify the current status of the requirement

 

Difficulty

Identify the difficulty of implementing the current requirement

 

Priority

Specify how urgent the requirement is

 

Stability

Specify the estimated stability of the requirement

This is an indication of the probability of the requirement - or understanding of the requirement - changing; high stability indicates a low probability of the requirement changing

 

Notes

Record details of the requirement

You can format the notes text using the Notes toolbar at the top of the field

NotesToolbar

Move External

Make an internal responsibility into an external requirement

Make Internal Requirement External

New

Create a new requirement

 

Save

Save changes to requirements

 

Delete

Delete a selected requirement

 

Defined

List the defined requirements associated with this element

 

Learn More: