How to Build an SOA Roadmap
There are four phases to developing your SOA roadmap: SOA Planning, SOA Maturity Assessment, SOA Future Vision, and SOA Roadmap Definition.
SOA planning
During this phase, your SOA initiative is organized and defined. Stakeholders are brought into the process through communications and briefings, and mutually agreed upon priorities and parameters are set. Because this phase involves employees across your organization, clear and ample communication is critical. During this phase you will:
Define the scope of SOA.
Establish boundaries and alignments with other IT initiatives.
Appropriately showcase the business justification for SOA.
Show alignment of existing and future business initiatives.
SOA planning
During this phase, your SOA initiative is organized and defined. Stakeholders are brought into the process through communications and briefings, and mutually agreed upon priorities and parameters are set. Because this phase involves employees across your organization, clear and ample communication is critical. During this phase you will:
Define the scope of SOA.
Establish boundaries and alignments with other IT initiatives.
Appropriately showcase the business justification for SOA.
Show alignment of existing and future business initiatives.
SOA maturity assessment
During the SOA maturity assessment phase, you will establish a metric for where you are today. Here you will define what services and capabilities you currently have that can serve as a starting point for SOA, as well as identify projects that may serve as foundation projects. Through a series of interviews and questionnaires, your teams should examine the various domains—analyzing, base-lining, and validating the "as-is" current situation for each. Use BEA's Domain Model to structure your examination of the following:
Business Strategy and Process: Top-down view of business strategies and processes.
Architecture: Review of current architectures, policies, and standards.
Cost and Benefits: Overview of existing cost structures and benefits cases.
Building Blocks: Analysis of existing services, processes, tools, and technologies.
Projects and Applications: Review of existing systems, and in-flight and planned projects.
Organization and Governance: Analysis of existing governance structures and policies.
During the SOA maturity assessment phase, you will establish a metric for where you are today. Here you will define what services and capabilities you currently have that can serve as a starting point for SOA, as well as identify projects that may serve as foundation projects. Through a series of interviews and questionnaires, your teams should examine the various domains—analyzing, base-lining, and validating the "as-is" current situation for each. Use BEA's Domain Model to structure your examination of the following:
Business Strategy and Process: Top-down view of business strategies and processes.
Architecture: Review of current architectures, policies, and standards.
Cost and Benefits: Overview of existing cost structures and benefits cases.
Building Blocks: Analysis of existing services, processes, tools, and technologies.
Projects and Applications: Review of existing systems, and in-flight and planned projects.
Organization and Governance: Analysis of existing governance structures and policies.
SOA future vision
In this phase, teams use workshops to determine and define the desired "should-be" state and ensure cross-organizational buy-in.
Business Strategy and Process: Correlation of SOA future vision with business strategies and processes.
Architecture: Guiding principles, requirements, policies, standards, and reference architecture.
Cost and Benefits: Metrics and measurement requirements.
Building Blocks: Shared services infrastructure requirements and standardized tools.
Projects and Applications: SOA mapping to projects and applications.
Organization and Governance: Governance and compliance structures and policies.
SOA roadmap definition
This phase is where the SOA roadmap is initially defined. A complete gap analysis should be performed for your corporation's SOA goals and appropriate timelines, based on the information gathered in the previous three phases. Near-term events will be more detailed, while later events will be more fluid—so that they may incorporate lessons learned as you move forward.
Business Strategy and Process: Opportunity alignment by business value.
Architecture: Near-, medium-, and long-term reference architecture roadmap.
Cost and Benefits: Roadmap of future metrics, cost structures, and benefits cases.
Building Blocks: Prioritization of shared services strategy and standardized processes.
Projects and Applications: Project and application impact.
Organization and Governance: Proposed governance structures and policies.
Your SOA roadmap should be treated as a "living document" that continually captures experiences and lessons learned. As your roadmap matures, your SOA initiative will reach higher levels of sophistication in a controlled manner (see Figure 2).
This phase is where the SOA roadmap is initially defined. A complete gap analysis should be performed for your corporation's SOA goals and appropriate timelines, based on the information gathered in the previous three phases. Near-term events will be more detailed, while later events will be more fluid—so that they may incorporate lessons learned as you move forward.
Business Strategy and Process: Opportunity alignment by business value.
Architecture: Near-, medium-, and long-term reference architecture roadmap.
Cost and Benefits: Roadmap of future metrics, cost structures, and benefits cases.
Building Blocks: Prioritization of shared services strategy and standardized processes.
Projects and Applications: Project and application impact.
Organization and Governance: Proposed governance structures and policies.
Your SOA roadmap should be treated as a "living document" that continually captures experiences and lessons learned. As your roadmap matures, your SOA initiative will reach higher levels of sophistication in a controlled manner (see Figure 2).
No comments:
Post a Comment