|
市場調查報告書
SOA 管理:使用SOA管理以確立其長期利益
SOA Governance: Applying Governance to Ensure the Long-term Benefits of SOA
| 出版商 |
Butler Group |
| 出版日期 |
2008年06月 |
商品編碼 |
71273 |
| 內容資訊 |
英文 228 pages |
| 價格 |
|
|
SOA 管理:使用SOA管理以確立其長期利益 是由出版商Butler Group在2008年06月所出版的。
這份英文市場調查報告書包含228 pages 價格從美金2995起跳。
本報告書內容包括:SOA(服務指向架構)市場調查、商業課題、SOA管理連結合作管理與IT管理的方法、如何確實針對整體組織,而非只針對服務架構訂定計畫、監測運作環境是否健全的方法、主要企業引進SOA管理的實例研究、主要企業資訊等等,內容綱要摘記如下:
第1章 總括
第2章 SOA管理囊括的商業課題
- 本書目的與結構
- SOA管理的內容構築
- SOA管理特別挑戰的東西
- 設定SOA管理的範圍
第3章 SOA計畫階段的管理
- SOA的展開與商業目的調整
- 理解SOA管理帶來的角色
- 適才適任的配置
- 構築資源比例誘因
- 開設SOA的卓越中心
- 多重組織SOA計畫的管理
- 實行管理SOA的方法論
- 建構後期階段的技術要項
第4章 設計與研發階段的管理
- 設計與研發階段的管理目的
- 建構針對相容性的框架
- 確立夥伴企業對想法的持續性
- 針對服務的參考架構
- 設計再利用
- 管理服務產品線
- 選擇應用程式產生的影響
- 訊息與傳送的管理
- 針對執行的管理政策
- 效能與可能的考慮事項
- 製作測試策略
第5章 SOA執行環境的管理
- 管理執行環境的目的
- 服務的發現
- 透過擴充環境的監測與報告
- 政策施行
第6章 變化與退去生命週期的管理
- 生命週期變化的管理目的
- 服務課題與退去
- 發現變化的影響
- 測試SOA架構的變化
第7章 製作SOA管理執行計畫
- 評估目前的易用性與成熟度
- 計畫短期的組織性變化
- 評估方法論的要求事項
- 讓計畫確立
第8章 SOA管理實例研究
第9章 市場分析
第10章 供應商資訊
第11章 用語集
Abstract
Report Synopsis
The number of SOA projects has accelerated to the point where SOA should be
considered to be in early mainstream deployment rather than a ' bleeding edge'
approach to delivering IT systems. However, alongside the success stories
there is also a significant set of organisations for which SOA doesn' t seem to
be delivering the expected benefits. Typical problems reported are that
services are not being reused and the business is not seeing the new level of
IT agility that was promised. These symptoms, disappointing as they are,
should not be taken as an indication that SOA does not deliver; rather they
should be taken as a strong indication that the governance of the SOA
initiative has not received the attention it deserves.The purpose of SOA
governance, as with any other governance implementation, is to keep the
initiative on the rails, targeted at delivering the benefits that the business
needs. Perhaps the most common error with respect to SOA is to treat this as
any other IT initiative - as something that solely concerns IT and that
should remain hidden from the business. In fact, implementing SOA without
making it a joint business/IT venture is even less likely to deliver business
benefits than would implementing a data warehouse without involving
information users from the business. Although generally considered to be a
subset of IT governance, SOA governance is better thought of as providing a
linkage between corporate governance and IT governance, and hence should be
jointly owned.
Key Findings
This Report reveals:
- How SOA governance provides linkage between corporate governance and IT
governance.
- Why people and processes are more critical to SOA governance than the
supporting technology.
- How to ensure the service architecture is designed for the benefit of the
whole organisation, not just the initial project.
- How to monitor the health of the runtime environment in a continuous
fashion.
- Why business policies should be enforced dynamically through active
runtime components.
- How to address the complexity of SOA change management.
- How leading companies have deployed SOA governance in their own
organisations.
- Which vendor solutions can be deployed to support the different phases of
SOA governance.
Table of Contents
Section 1: Management Summary
Section 2: Business Issues Around SOA Governance
- 2.1 Report Objectives and Structure
- 2.2 Setting the Context for SOA Governance
- 2.3 What Makes SOA Particularly Challenging?
- 2.4 Setting the Bounds for SOA Governance
Section 3: Governance in the SOA Planning Phase
- 3.1 Aligning the SOA Deployment with Business Aims
- 3.2 Understanding the Roles Involved in SOA Governance
- 3.3 Putting the Right People in the Right Roles
- 3.4 Building in Incentives for Sharing Resources
- 3.5 Establishing the SOA Centre of Excellence
- 3.6 Governance in Multi-organisational SOA Projects
- 3.7 Implementing a Methodology to Guide the SOA Deployment
- 3.8 Establishing the Technology Requirements for Later Phases
Section 4: Governance in the Design and Development Phase
- 4.1 The Aims of Governance in the Design and Development Phase
- 4.2 Establishing a Framework for Interoperability
- 4.3 Ensuring Continuity of Thought Between Participants
- 4.4 A Reference Architecture for Services
- 4.5 Designing for Reuse
- 4.6 Managing the Service Portfolio
- 4.7 Impact on Application Selection
- 4.8 Managing Messages and Transformations
- 4.9 Managing Policies to be Enforced at Runtime
- 4.10 Performance and Availability Considerations
- 4.11 Creating a Testing Strategy
Section 5: Governance of the SOA Runtime Environment
- 5.1 The Aims of Governance in the Runtime Environment
- 5.2 Service Discovery
- 5.3 Monitoring and Reporting Across the Extended Environment
- 5.4 Policy Enforcement
Section 6: Governance of the Change and Retirement Lifecycle
- 6.1 The Aims of Governance in the Change Lifecycle
- 6.2 Service Change and Retirement
- 6.3 Discovering the Impact of Changes
- 6.4 Testing Changed SOA Artefacts
Section 7: Creating a SOA Governance Implementation Plan
- 7.1 Assessing Current Readiness and Maturity
- 7.2 Planning Short-term Organisational Change
- 7.3 Assessing Methodology Requirements
- 7.4 Obtaining Commitment to the Plan
Section 8: SOA Governance Case Studies
Section 9: Market Analysis
- 9.1 Market Dynamics
- 9.2 Vendor Strategies
- 9.3 Future Direction
Section 10: Vendor Profiles
- Adaptive
- AmberPoint
- BEA
- HP
- IBM Corporation
- Layer 7 Technologies
- LogicLibrary
- Managed Methods
- MEGA International
- Metastorm
- Oracle
- Progress Software
- SOA Software
- Software AG
- Troux Technologies
- Vordel
- WestGlobal
Section 11: Glossary
|