EA3 artifact

EA3 artifact A-5: Application Service Matrix

The Application Service Matrix relates applications/systems to services:

EA3 artifact A4 Application Data Exchange Matrix

The Application Data Exchange Matrix uses a table format to show which systems exchange particular types of data in LOBs.

The Data Exchange Matrix describes, in tabular format, data exchanges between systems within a systems node and across systems nodes. The focus of the Data Exchange Matrix is on how the data exchanges actually are (or will be) implemented, in system-specific details covering such characteristics as specific protocols and data or media formats. These aspects of exchanges, while difficult to document, are critical to understanding the potential for overhead and security constraints introduced by the physical aspects of the implementation. The Application Data Exchange Matrix relates to, and grows out of, the Information Exchange Matrix. That is, the automated portion(s) of each information exchange in the Information Exchange Matrix is associated with the system interface that carries the corresponding system data in the System Interface Description. The business characteristics for the information exchange are replaced with the corresponding system data exchange characteristics. For example, performance attributes for the business information exchanges are replaced by the actual system performance attributes for the automated portion(s) of the information exchange. Automation may introduce characteristics that are not intrinsic to the business information exchange.

EA3 artifact A-3: Application Interface Matrix

The Application Interface Matrix shows the nature and status of physical and logical interfaces between information systems throughout the enterprise.

1. Provides detail on the interface characteristics of the SA-1 artifact.
   • Allows quick overview
   • Enables rapid assessment of potential re-use or redundancies
2. Useful tool for managing the evolution of systems, infrastructures, technology insertion, functional upgrades.
3. Interface characteristics that could be captured include:
   Status (existing, planned, potential, deactivated), purpose, classification level, key interface(s)

EA3 artifact A2.2 System/Operations Matrix

The System/Operations Matrix relates operational activities to system functions within / between lines of business throughout the enterprise.

1. Relates operational activities to system functions
2. Identifies the transformation of an operational need into a purposeful action performed by a system
3. Supports decision making as follows:
   • Identify ‘stovepipe’ systems and opportunities for automation
   • Identify redundant systems and functions
   • Analyze gaps in performance
   • Target investment opportunities

EA3 artifact A2.1 System Data Flow Diagram

The System Data Flow Diagram is better known as a ‘Data Flow Diagram’ and is intended to show the processes within a system that exchange data, and how those exchanges occur.  This artifact compliments the Business Process Diagram, and can be decomposed to show additional detail.

1. Captures and describes system functions and the data flows between them.
2. Documents system functional hierarchies.
3. Primary purpose is to:
   • Develop a clear description of the necessary system data flows that are input (consumed) and output (produced) by each system
   • Ensure functional connectivity is complete
   • Support appropriate level of functional decomposition for additional detail
4. Is the systems counterpart to the Business Process Model (IDEF-0 diagram).

EA3 artifact A-2: Application Communication Diagram

The A-2 artifact compliments the A-1 Application Interface Diagram by providing a description of how data is communicated between systems throughout the enterprise, and includes specifics about links, paths, networks, and media.

EA3 artifact A-1: Application Interface Diagram

The Application Interface Diagram shows the logical and/or physical interfaces between the enterprise’s systems for information, production, etc. where information and/or other resources are exchanged.

EA3 artifact D-10: The Object Library

GEM: Generic Enterprise Model
A GEM is an object library that defines the classes of objects that are generic across a type of enterprise, such as manufacturing or banking, and can be used (instantiated) in defining a specific enterprise.

A GEM is composed of the following:

• a set of object classes structured as a taxonomy (that is, each object is linked to one or more other objects by a subclass-superclass relationship plus a definition of how a class refines its superclass);
• for each object class, a set of relations linking it to other object classes plus a definition of the intended meaning of each relation;
• for each object class, a set of attributes plus a definition of the intended meaning of each attribute.

Mark S. Fox and Michael Gruninger: Enterprise Modeling. AI Magazine Volume 19 Number 3 (1998)

EA3 artifact D-9: The Data Dictionary

The Data Dictionary provides a comprehensive listing of the data entities that are collected and maintained by the enterprise, including standards for the attribute fields, keys, and relationships. The Data Dictionary may also include a ‘library’ of re-useable Data Objects that use UML methods.

Examples

• Current view
• Future View

Daily use

EA3 artifact D-8: The Event-Trace Diagram

The Event-Trace Diagram allows the tracking of actions in a set of scenarios or operational threads. Each diagram should focus on a critical sequence of events and a description of the event scenario should be provided.

With time proceeding from the top of the diagram to the bottom, a specific diagram lays out the sequence of information exchanges that occur between business nodes for a given scenario. These information exchanges are associated with events and actions (see Information Exchange Matrix). The direction of the event arrows shows flow of control, in terms of the business process, from node to no.