Header image
Oxford Architectural Design & Consulting
 
 
(EA)2 User's Guide
Quick Links

Enterprise Architect provides an easy method for drawing relationships between model elements called Quicklinks. When you click on an element in a diagram, you will notice a small arrow just beyond the top-right corner of the element. This is the Quicklinker. When you drag the arrow to another element, you are presented with a list of connector types that are allowed to be drawn from the source element to the target element. (EA)<sup>2</sup> provides numerous Quicklinks for controlling the connections between the various (EA)<sup>2</sup> architectural elements. These connector types will have an (EA)<sup>2</sup> prepended to their name in the Quicklink menu, e.g. (EA)<sup>2</sup>: Provides App Capability. To ensure that you use the correct type of connectors, you should use the Quicklinker and select one of the (EA)<sup>2</sup> connectors in the Quicklink menu, if any.

The Quicklinker will also correct directional errors. For example, if you draw a quicklink from a ProvidedInterface to a RequiredInterface and then select an (EA)<sup>2</sup> link, the arrow will point from the RequiredInterface to the ProvidedInterface to show the true nature of the dependency.

See Arrow Direction on the Creating and Connecting Exposed Interfaces page for more information on connectors.

A list of the Quicklinks follows.

Active/Active Failover
This connector is drawn from an EA2 Server or EA2 Mainframe to another and indicates that they provide failover for each other.
Active/Passive Failover
This connector is drawn from one EA2 Server or EA2 Mainframe to another and indicates that the target is takes over for the source should it go down.
Application Component
Drawn from the an application component, e.g. a EA2 Work Session, to the owning application, e.g. an EA2 Business App.
Ends
Drawn from an EA2Receive Event to an EA2 Process or EA2 Activity and indicates that the event ends the target.
Governs
Drawn from an EA2 Policy or EA2 Rule and indicates that the source governs aspects about the target.
Impacts
Drawn from an EA2 Receive Event to an EA2 Process or EA2 Activity and indicates that the event impacts the processing of the target. For example, a Close Normal Registration event may cause the Registration Process to charge a higher fee for registrations.
Implements
Content
Initiates
Drawn from an EA2 Receive Event to an EA2 Process or EA2 Activity and indicates that the event initiates the processing of the target. For example, an Open Registration event initiates the Registration Process.
Network
Drawn from the port on one network node, e.g. EA2 Server, EA2 Firewall, etc, to a port on another network node. There are several connector choices to choose from namely; Internet, Intranet, Extranet, DMZ, and Untyped. For more information go to the Sites and Network Topologies page.
Nested Activity
Drawn from an EA2 Activity to an EA2 Process and indicates that the Activity is a component of the Process.
Produces
Drawn from an EA2 Process to an EA2 Policy and indicates that the Process produces the Policy.
Provides App Capabilitiy
Drawn from an EA2 Business App to an EA2 Process or EA2 Activity and indicates that the Business App provides an application capability that is captured as a tagged value on the connector.
Provides IT Capability
Drawn from IT Software (EA2 IT App, EA2 O/S, EA2 App Server, EA2 Browser, EA2 DBMS), to an EA2 Process or EA2 Activity and indicates that the IT Sofftware provides an infrastructural capability that is captured as a tagged value on the connector.
Realizes
Drawn from an EA2 Process to an EA2 Business Capability or from an EA2 UCR to an EA2 Use Case and indicates that the source realizes the needs of the target.
Specifies
Drawn from an EA2 Use Case to an EA2 Process or EA2 Activity and indicates that the Use Case specifies the automation of part or all of the target.
System Component
Drawn from a system component, e.g. EA2 Business App or EA2 DB Schema, to the owning EA2 Business System and indicates that the source is a component of the target. The connector is required because system components may not all reside within the Project Browser under the Business System. For example, DB Schemas may be kept in the Data Architecture area of the model.
 

All Rights Reserved.