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


The analysis phase of Requirements development ensures that the Requirements discovered in the Elicitation phase have been articulated correctly and have the correct format, level of detail and properties and form a cohesive and correct set. As a result of the disparate sources and methods of elicitation the Requirements recorded in the elicitation phase will need some massaging and balancing - it is quite common for example to find repeated or overlapping requirements or for an analyst to have omitted to record the concerns of one or more stakeholders. Tools such as the Relationship Matrix and the Traceability window will reveal omissions and issues with requirements. The Discuss & Review window and the Chat & Mail window - incorporating the Model Mail facility - also provide mechanisms for discussing the Requirements with other team members.

The Relationship Matrix showing relationships between UML Use Case elements and Requirement elements, in Sparx Systems Enterprise Architect.