没有合适的资源?快使用搜索试试~ 我知道了~
首页IBM公司SOA架构师资料(Governance 篇)
IBM公司SOA架构师资料(Governance 篇)

IBM公司SOA Governance 深入, SOA Governance一般是IT Governance的更宽泛领域中的特定自治域。SOA Governance由策略、框架和控制日常SOA活动的流程(这些流程由IT创建)组成。更泛地说来,SOA Governance为定义服务、获取或开发服务、将服务注册并保存在库中、控制服务的访问、发布服务、交付服务和管理服务变化提供了策略或程序(这里的程序不是计算机的程序,而是一种办事的流程)
资源详情
资源评论
资源推荐

Governance and Wrapup
Unit 5a-1
© 2007 IBM Corporation
Getting Started,
SOA Lifecycles
and Wrapup
Don Bagwell
IBM Washington Systems Center
dbagwell@us.ibm.com

Governance and Wrapup
Unit 5a-2
© 2007 IBM Corporation
2
IBM Americas Advanced Technical Support
Washington Systems Center, Gaithersburg, MD
This slide intentionally left blank

Governance and Wrapup
Unit 5a-3
© 2007 IBM Corporation
3
IBM Americas Advanced Technical Support
Washington Systems Center, Gaithersburg, MD
Going Back to Our Original “Problem Statement”
Starting out …
Do you recall the really inflexible application interconnection chart we showed
earlier? That serves as the backdrop for this discussion:
How do you approach this?
How do you make sure it’s
approached in a sensible,
controlled fashion?
How do you make sure it
works as you hoped?
This is more than just a “use product X” issue. Here we get into the issue of
planning for and executing on a plan in a defined, controlled and disciplined manner.
Way back in the first unit we presented picture that represented the typical “spaghetti code”
application design. We mentioned back then that many companies -- IBM included, by the way --
have pictures that look like that. It just something that happened over time. As we contemplate
what we’ve learned so far, and look at this picture, we’re faced with some basic questions about
approaching this and applying SOA to it. The purpose of this unit is to give you a sense of the
issues and thinking in this space.
Before we do that, it should be clear that what we’re about to talk about is not just a product usage
issue. What we’re about to talk about is really more of a high-level control and discipline approach,
aided by technology implemented in particular products. Much of this is really related to human
behavior -- tools are only as good as our willingness to use them properly.

Governance and Wrapup
Unit 5a-4
© 2007 IBM Corporation
4
IBM Americas Advanced Technical Support
Washington Systems Center, Gaithersburg, MD
Starting Out
IBM SOA lifecycles …
There are three basic ways you can approach this question …
Enterprise Level
• SOA a strategic initiative at the
enterprise level
• Suggests a broader Component
Business Modeling consulting
engagement
Line of Business
• SOA across a set of related projects
under a LOB decision maker
• Client Architecture Readiness
Evaluation
Single Project
• A way to test the waters and gain
experience
• SOA Jumpstart
No one is “best” -- it all depends on the needs of the business and the state
of SOA awareness, understanding and acceptance in the organization
There are three basic ways you can approach the topic of staring out with SOA and implementing
it. There are, of course, variations on each of these … as well as the opportunity to blend these.
But these three will serve the purpose of illustrating the basic approaches.
• Enterprise Level -- here you approach the topic from the top down. This is a kind of “all in”
strategy, where the start of the analysis is done at the highest level, and the business is
analyzed not from a technology point of view (initially), but from a business component point of
view. Clearly this would require buy-in from the highest level. IBM Business Consulting
Services has offerings to assist enterprises in assessing their business and determining how,
where and why SOA would be beneficial.
• Line of Business -- a smaller version of the Enterprise Level, here the focus is fenced within a
particular line of business (division, organization unit), or possibly related to a particular set of
projects within an enterprise (for example, the shipping function). IBM services provides an
architectural readiness evaluation to help with this process.
• Single Project -- when the desire is to start small and build experience from there. This
makes good sense in a lot of cases. Here a particular potential service is selected and the
solution is built around that. Experience is gained in a small, controlled (and often less risky)
way.
The ubiquitous “it depends” answer is given for which of these is best. A lot depends on the
business as well as the current state of mind of the business decision makers.
Let’s now see how IBM describes the “lifecycles” of SOA adoption.
剩余19页未读,继续阅读


















安全验证
文档复制为VIP权益,开通VIP直接复制

评论1