Future views of EA components and artifacts at the Information Level of the EA3 framework reflect changes that are anticipated in the collection and flows of information that are needed to support changes in business services (upward alignment) or changes that are anticipated at the Systems/Services Level or the Technology Infrastructure level of the EA3… Continue reading How can changes in information flows and data structures be reflected in future views at the Information Level of the EA3 framework?
The Systems/Services level of the EA 3 Cube Framework is organized around integrated plug-and-play components that are based on open standards, and reusable objects of code that underlie and enable a component-based and service-oriented approach to EA, as is promoted in the EA \n3 Cube Framework. \nVarious EA artifacts are used to document the future… Continue reading How can changes in applications and functionality be reflected in future views at the Systems and Services Level of the EA3 framework?
The Technology Infrastructure level of the EA 3 Cube Framework documents components such as the enterprise’s voice, data, and video networks, as well as the security solution that protects them. In that one of the goals of EA is to promote the integration of these networks into one seamless technology backbone, the future view of… Continue reading How can changes in voice, data, and video networks be reflected in future views at the Network Infrastructure Level of the EA3 framework?
The framework should identify the areas of the enterprise that the EA will cover, and how those areas relate. For example, the EA3 framework identifies five functional areas and three ‘thread’ areas to be documented, organizes different types of components, and then orients the components into lines of business. These relationships are important in conveying… Continue reading What is the role of an EA framework within the EA methodology?
Analysis and documentation, as organized through an EA framework, provides standardized, hierarchical views of the enterprise from an integrated strategy, business, and technology perspective
The EA framework defines what the EA program will document, and the EA methodology defines how that documentation will be developed and used. By defining what parts of the enterprise are included in the EA, the framework defines the scope of the architecture. The design of the framework communicates the relationship of the areas of… Continue reading What are some of the basic characteristics of an EA 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… 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?