Move Requirements Internal

There are a number of situations where it is useful to define requirements inside an element.  Requirements are typically created as elements in the Specification Manager, or as part of a Requirements diagrams or directly in the  Project Browser. Enterprise Architect allows you to move (copy) an External Requirement into an element creating an Internal Requirement. This is quite commonly done so down-process workers like developers can see the Functional and Non Functional Requirements when working with a Use Case or Component. It can also be used as a device to list a series of applicable requirements under an element in a report. For example high level Business Requirements could be moved internal to a Business Process and if a report were generated the Business Requirements would be listed directly under the Business Process.

Change an element's internal requirement into an external requirement element




Ensure you have a diagram open with the element you wish to be the container for the Requirements visible.


In the Project Browser select the External Requirement you wish to change to an Internal Requirement.


Drag and drop the Requirement from the Project Browser on top of the element in the diagram.


A new Requirement element is created in the target element, with a Realization connector from the target element to the External Requirement.


  • When an external requirement is made into an internal requirement element it is still viewable within the Project Browser. Any change to the external requirement will be reflected in the internal requirement and vice versa.