The architectural consideration of SOA in the preceding chapter offers advice
on what directions to choose and how to define the strategic goals for an SOA
project. This chapter takes the next step toward execution by focusing on how
to plan an SOA project. The topics in this chapter constitute the best
practices we have uncovered for forming a project office (see Section 4.1),
how to define the phases of SOA adoption, the need for and mechanisms of SOA
governance, and finally, the various project roles and how they interact with
each other.
This is not intended to be a complete template for a project plan, nor do we
intend to show the optimal organizational structure for the parties involved
in SOA projects. Based on our vigorous experience with different clients in
various industries around the world, we are fully aware that there is no
one-size-fits-all solution... (more)
When the programming model shifted from the traditional procedural model to
that of object-orientation, a major paradigm shift occurred in the world of
IT development. The focus was on encapsulating the state and behavior of
entities and calling that encapsulation a class. Instances of a class were
called objects, which occupied some space in the memory. Object orientation
(OO) brought in concepts of inheritance, encapsulation, and polymorphism that
could be applied to define relationships between classes. With the prevalence
of the use of OO in the programming world, developers ... (more)
Service Oriented Modeling and Architecture (SOMA) is a modeling and design
technique developed by IBM that provides prescriptive steps for how to enable
target business processes by defining and developing a service-based IT
solution. SOMA provides the communication link between the business
requirements and the IT solution. It provides guidance on how to use business
model and information as inputs to derive and define a service-based IT
model. SOMA, as a methodology, addresses the gap between SOA and object
orientation. This methodology approach provides modeling, analysis, des... (more)
Normal 0 false false false MicrosoftInternetExplorer4
In SOA, the main emphasis is on the identification of the right services
followed by their specification and realization. Although some might argue
that object-oriented analysis and design (OOAD) techniques can be used as a
good starting point for services, its main emphasis is on microlevel
abstractions. Services, on the other hand, are business-aligned entities and
therefore are at a much higher level of abstraction than are objects and
components.
In Part 1 of this book excerpt, we discussed the different layers of an SOA ... (more)
Keith Jones, PhD, IT architect at IBM Enterprise Integration Solutions, focuses on helping customers define and implement service-oriented architectures.
Scott Sellers
Anthony Franco
Daniel Morris
Wayne Walls
Niki Acosta
Jereme Hancock
Oren Michels
Marvin Wheeler
Douglas Kim
