100% (1)
Pages:
2 pages/≈550 words
Sources:
3
Style:
Other
Subject:
Technology
Type:
Essay
Language:
English (U.S.)
Document:
MS Word
Date:
Total cost:
$ 10.8
Topic:

Enterprise Architecture: Developing Future Architecture Views

Essay Instructions:

Enterprise Architecture

Why Several Different Artifact types Needed for each EA6 Level

In documenting the architecture  for an enterprise, several different artifact types are needed for each EA6 Level for flexible changes in the future. "Documentation of the current EA is important to an enterprise because it provides a set of baseline reference information/artifacts for planning and decision making" (Bernard, 2020. 150). In this case, the enterprise can change, improve, or remove any artifact over time. Therefore, an organization can adopt the most efficient artifacts after testing their effectiveness to the efficiency of the enterprise

Essay Sample Content Preview:

Chapter 8: Enterprise Architecture
Name
Institution
Course
Instructor
Date
Enterprise Architecture: Developing Future Architecture Views
When the EA Future Views should Attempt to Provide documentation
The EA's future views should aim to provide documentation during the establishment of the EA framework. "Changes to current and future views are collected for four to five months and then published in the sixth month as the new release of the enterprise EA" (Bernard, 2020, p. 179). This period is one of the initial stages of the EA implementation period, usually from 5 to 6 months. "The future of the EA documents the IT resources that will be active in the operating environment for several years. This is also known as the "to-be" view, as opposed to the "as-is" view that documents the current IT resources" ( Bernard, 2020, p. 173). The EA's future views guide the probable and unforeseen changes in the enterprise. In this case, a firm should provide the basis to amend these changes within any period. Notably, this period comprises the subsequent years after the establishment and implementation of the EA framework. In brief, the enterprise should provide documentation for the EA's future views during the initial stages of the EA implementation period.
Reason Enterprises should Maintain the same Documentation Technique
Enterprises should use the same documentation technique in an EA component's future and current view to maintain its objectives and plan. "EA stakeholders come to expect the new releases and know they can rely on the information not changing in the EA repository for the next few months. Special releases can be made if there is an important change in the middle of the normally static period. Without this version control, the EA repository, where no one is sure where changes will appear, detract from the perceived value of EA information." (Bernard, 2020, p. 179). Usually, these documentations contain the organization's whole plan, including the probable future changes. Since the documentation accommodates all the possible changes, it should maintain the same documentations to attain the desired outcome from the initial plan. Equally important, the organization may deviate from its objectives if it adopts a di...
Updated on
Get the Whole Paper!
Not exactly what you need?
Do you need a custom essay? Order right now:
Sign In
Not register? Register Now!