Migrating to Cloudware - Guide to Cloud Computing for Business and Technology Managers - page 433

and efficiently to support the business. In this sense, we need to logically
group applications in terms of capabilities that manage the data objects
defined earlier in the data architecture to support the business functions
in the business architecture. Although generally these application building
blocks are stable and remain relatively unchanged over time, we are seeking
fresh opportunities to improve, simplify, augment, or replace components
for the target cloud-enabled systems landscape. The business architecture
and the application portfolio analysis in the as-is assessment earlier will
inform the list of affected or required logical and physical components in
the application stack.
20.4.2.3 Technology and Infrastructure for the Cloud
This aspect of to-be analysis is concerned with defining target cloud technol-
ogy portfolio components. In this exercise, we map underlying technology
and respective application components defined in the application architec-
ture depending on the cloud model of choice. Depending on the business
vision, and business architecture and business and technology maturity, the
technology deployment may be a hybrid configuration, which means that
cloud will coexist within a modified current technology architecture. In this
manner, we are making the technology platform cloud enabled to make nec-
essary exchanges across a heterogeneous environment not only possible but
optimized for business efficiency and effectiveness. In case of full migration
to a new cloud platform again, we need to assess the technology and busi-
ness readiness.
This element of the to-be analysis is essential for the realization phase.
20.4.3 Realization
Realization plan consists of the activities that the organization needs to
maintain to close any strategic and delivery gaps identified in its adoption,
utilization, and management of cloud as an IT resource. The key components
of this aspect of the cloud plan primarily draw on the iterative assessment
of fit-gap analysis in as-is and to-be analyses. Any gaps and dependen-
cies and appropriate solutions need to be identified, analyzed, and consoli-
dated ensuring that any constraints on the adoption or migration plans are
addressed.
An important activity here involves assessment, validation, and consoli-
dation of business, functional, and systems requirements through review-
ing cloud technology requirements and gaps and solutions proposed. Once
consolidated, it is important to identify functional integration points. As
cloud services are delivered based on shared services and shared resources,
it is important to assess the need and scope for reuse and interoperability.
It is likely that business is not fully migrating to cloud and there is still
need for utilizing bespoke, COTS (commercial off the shelf), or third-party