Book a Demo

Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.

Prev Next

Requirements Diagram

Getting to Know the Requirements Diagram

Introducing the Requirements Diagram

The Requirements diagram provides a visual representation of how Requirements are related to each other and to other elements in the model, including Business Drivers, Constraints, Business Rules, Use Cases, User Stories, design Components and more. The diagram is one of Enterprise Architect's extended diagram types. It provides an appealing graphical representation of Requirements, that will be a welcome change for Requirements Analysts who are accustomed to working with text based tools.

Example of Requirements traceability, modeled in Sparx Systems Enterprise Architect

Where to find the Requirements Diagram

Browser window Context Menu : Add Diagram : Hamburger icon | Manage | Show All Perspectives | Extended | Requirements

Usage of the Requirements Diagram

One usage is to show how Requirements are connected together in a hierarchy or, even more importantly, how Requirements are connected to other elements. The experienced modeler will define and manage the Requirements in the Specification Manager and then use the Requirements diagram to show how each Requirement is related to upstream process elements such as Business Drivers, and downstream process elements such as Use Cases, User Stories, User Experience designs and solution Components.

Options for the Requirements Diagram

The appearance of a diagram can be changed to suit the audience, and details can be included, suppressed or altered to ensure the diagram meets its main objective of communication. There is a wide range of options, ranging from creating a Hand Drawn style of diagram to filtering diagram content.

Diagram appearance properties in Sparx Systems Enterprise Architect. 

Learn more about the Requirements Diagram

Working In Diagrams