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.
Category: Enterprise Architecture Management