In: Computer Science
1) How could information flows and data structures be reflected in future views at the Data and Information level of the EA3 Cube Framework?
2) How and should the ongoing transition between the current and future EA views be managed?
Q1) How could information flows and data
structures be reflected in future views at the Data and Information
level of the EA3 Cube Framework?
Answer:------------
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 Cube Framework.
Q2) How and should the ongoing
transition between the current and future EA views be
managed?
Answer:------------
At some point the new components and artifacts in the future view
of the EA become implemented and therefore should be documented as
part of the current view of the EA. These ongoing changes to the EA
represent a challenge in terms of how best to show at any given
time what is current and what is planned. \nPerhaps the simplest
and most effective way to approach this is to ‘freeze’ the current
and future views of the EA at regular periods (e.g., twice each
year). This promotes clarity and supports EA version control.
\nUsing this example, changes to current and future views are
collected for four to five months and then are published in the
sixth month as a new release of the enterprise’s EA. EA
stakeholders come to expect the new releases and know that they can
then rely on the information not changing in the EA repository for
the next few months. Special releases can be made if a there is an
important change in the middle of the normally static period.
Without this type of version control, the EA repository becomes a
free-for-all whereby no one is sure when and where changes will
appear, and this will detract from the perceived value of EA
information.