Because information flows and data objects change and/or are replaced over time. How an enterprise uses data and information is documented at the Data and Information level of the EA3 Cube Framework. \nEA components at this level include documentation on the design, function, and management of information systems, databases, knowledge warehouses, and data marts. It… Continue reading Why can an enterprise’s information flows and data objects be viewed as EA components?
Because software applications and networks change and/or are replaced over time. The systems and applications that an enterprise uses to support its business services, product delivery processes, and information flows are documented at the Systems and Applications level of the EA3 Framework. One of the purposes of EA is to improve the integration and efficiency… Continue reading Why can an enterprise’s software applications and networks be viewed as EA components?
Open standards at the national and international level promote EA component interoperability.
IT security related processes, information flows, applications, systems, and network hardware and software.
The current view of the EA is intended to show the IT resources that are presently active in the enterprise’s IT operating environment. This is also known as the as-is view of the EA. Depending on the amount of prior EA planning, these IT resources may or may not be aligned with the enterprise’s strategic… Continue reading What is the purpose of current views of EA components?
EA artifacts document EA components in a consistent way across the entire architecture.
The current view of the EA is intended to show the IT resources that are presently active in the enterprise’s IT operating environment. This is also known as the as-is view of the EA. Depending on the amount of prior EA planning, these IT resources may or may not be aligned with the enterprise’s strategic… Continue reading What is the difference between current and future views of EA components?
Examples of changes to components include a new strategic goal, business process, information flow, IT system, Web service, application network, security solution, standard, or workforce requirement. \nChanges to components may also reflect upgrade, integration, and retirement activities. \nProvide some examples of artifacts at the Goals & Initiatives level of the EA
The Integration Definition for Function, or IDEF technique. Developed in the mid-1970’s for modeling complex military projects, IDEF-0 uses Inputs, Outputs, Controls and Mechanisms (ICOM) to show the parts of an activity within an enterprise. IDEF-0 activity modeling is suitable for business process documentation in that it provides both high level context views, and more… Continue reading What is the IDEF-0 modeling technique and how can it be used to document EA components at the Business Level of the EA3 framework?
It allows direct comparison of EA artifacts in the current and future views.