The maintenance of IT architectures is a fundamental requirement for UAM. IT architectures are an asset to be developed, used and maintained.
Work Breakdown Structure
Purpose
IT architectures will quickly become dated if not
maintained. They should be viewed as an asset and kept up-to-date.
Description
The three possible triggers for updates (i.e., business change, technology change or problem) are integrated
into the process. The included activities for all possible paths are:
Determine Solution & Impact – a solution to a problem is agreed and defined, and then the
impact is determined in terms of the models requiring updates. Impacts to Business models will require updates to
all perspectives; impacts to Logical models will also require updates to the Technical models.
Analyze Impact and Opportunity – the (potential) introduction of new technology to the enterprise
may have widespread impacts. These are analyzed to determine if the impact is either just to the Logical
perspective or the Technology perspective (or perhaps no impact at all), or it has an impact at the business level.
Business level impacts require a different approach, not just a simple update to the business models. The impact
may be simplification or alteration of business processes, or it may require or provide the opportunity for a new
approach, or even a new business line or division (i.e., a new product or service). The impact level and
opportunity is defined and agreed.
Update Business Models – the business perspective is updated as required by the business change or
issue resolution.
Update Logical Models – the logical perspective is updated as required by the business change or
issue resolution and the changes to the business model.
Update Technical Models – the technical perspective is updated as required by the business change
or issue resolution and the changes to the business and logical models.
Update Migration Plan – migration plans are always updated once changes to the architecture are
completed.
In addition, the updated IT architecture may then be used within enterprise IT management processes to aid in
planning and migration. See: Delivery Process: UAM in the Enterprise.
The need for maintenance of an IT architecture centers around three separate drivers for change:
An update to the business (i.e., strategy, plans, products, services, etc.);
An update to the technology used, or proposed to be used;
Identification of a problem with the existing architecture or operational system.
Each of these drivers is addressed within the defined delivery process.
If the change is minor enough, as specified by the enteprise's management parameters, then this process will not be
necessary, but existing IT architectures will have the minor updates applied. However, if the impact on the IT
architecture is substantial then this process is necessary to ensure that the IT architecture remains current and
up-to-date.
Key Considerations
If the change is minor enough, as specified by the enteprise's management parameters, then this process will not be
necessary, but existing IT architectures will have the minor updates applied. However, if the impact on the IT architecture
is substantial then this process is necessary to ensure that the IT architecture remains current and up-to-date.
