Cloud Computing and SOA Convergence in Your Enterprise: A Step ...

Defining the Holistic Value 77
Step 3: Model “As Is”
Modeling the “as is” means that we create a logical model of the current architecture
within the domain, including all relevant systems, data, processes,
services, and any other details that should be defined. Since this is really not
an exercise in enterprise architecture, but an exercise in creating a business
case, what is important about this step is that we have a clear understanding
of the existing IT systems and what they do.
Step 4: Model “To Be”
Once we have modeled the as is, it’s time to model the “to be.” Again, this is
not an architectural exercise—we talk about doing that during the remainder
of the book—but you do need to define the to-be architecture so that the
business case can be created. In other words, things are this bad (steps 1–3);
we propose a solution that will make things better (step 4 ); and this is how
much that solution will save us (steps 5–8).
This is where you propose the SOA using cloud computing solution if it
is indeed needed, using the architectural guidelines provided in the remainder
of the book—in essence, what the new architecture will look like, its
components, its location, and so on. Consider that you are likely presenting
this proposal to businesspeople, so too much talk about technology will not
have the desired effect.
Step 5: Define Value Points
During this step, you define the value of the to-be architecture at a high level.
For example, for many cloud computing solutions, the value points will be
everything we presented at the beginning of this chapter, including
Ongoing operational cost reduction
The value of preserving capital
The value of upsizing on demand
The value of downsizing on demand
The value of shifting the risk
The value of agility
The value of reuse
The value of innovation