FAQ Category: Components

Enterprise Architecture Professionals

How might an EA artifact change between the current and future view of an EA component?

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

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?

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…
Read more

Why is the same documentation technique used in the current and future view of an EA component?

It allows direct comparison of EA artifacts in the current and future views.

What are EA components and how do they relate to a framework?

While an EA framework provides an overall structure for modeling the enterprise’s business and technology operating environment, EA components are the working elements of the framework at each level. In other words, EA components are building blocks that create discrete parts of the overall IT operational capability. EA artifacts describe EA components.

What are EA artifacts and how do they relate to EA components?

EA artifacts are types of documentation that describe components, including reports, diagrams, charts, spreadsheets, video files, and other types of recorded information. High-level EA artifacts are often text documents or diagrams that describe overall strategies, programs, and desired outcomes. Mid-level EA artifacts are documents, diagrams, charts, spreadsheets, and briefings that describe organizational processes, ongoing projects,…
Read more

Why can an enterprise’s business processes be viewed as EA components?

Because business processes change and/or are replaced over time. An enterprise’s key business and support processes are documented at the Business level of the EA framework. EA components at this level include business process documentation and an IT capital planning portfolio that provides business case documentation on each investment in IT that meets operational and…
Read more

Why can an enterprise’s information flows and data objects be viewed as EA components?

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…
Read more

Why can an enterprise’s software applications and networks 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…
Read more

Why are national and international standards important to EA components?

Open standards at the national and international level promote EA component interoperability.

Which elements of an IT security program can be viewed as EA components?

IT security related processes, information flows, applications, systems, and network hardware and software.