Information Technology Reference
In-Depth Information
existing user familiarities that comprise the bulk of the current environ-
ment and then working to incorporate the remaining 20%. This is not
to say that majority should rule, but it does reflect the value that exists
within an established solution. If a technology were wholly without value,
it would not likely be fulfilling a role in the existing architecture.
Expectations from Architectural Change
Before delving into specific metrics that can be used to assess the
impact of enterprise architectural realignment, it is useful first to
understand some of the common expectations that may be held by stake-
holders. Table 4.1 details some of these expectations.
Table 4.1 Common Stakeholder Expectations
of Architectural Realignment
Operation
Expectations
Standardization and consolidation
Reduced complexity will require less
training, management, and support.
Reduced product count will streamline
purchasing and acquisitions.
Less effort will be required for installation
and patch management.
Integration will be simplifi ed among
elements of the enterprise.
Modernization and reorganization
Capacity will be increased for information
storage, processing, and delivery.
Improved or updated feature sets will be
present.
Simplifi ed organization will improve agility
with regard to new technology initiatives.
Integration and federated identity
management
Data sharing and availability will be
increased.
Barriers between authentication pools will
be reduced or eliminated (the “single
sign-on” wish).
Interface consistency will improve access
and availability for partners and external
consumers.
Collaboration will be improved, either
internally or externally.
