PracticalGuidetoSOAImplementation

Practical Guide to SOA Implementation    (3BQW)

Progression:    (3G7U)

• 3rd SOA for E-Government Conference, May 1-2, 2007: Bringing Together Global Information Grid Community, W3C Workshop on Web of Services for Enterprise Computing, and Service Systems    (3G7V)
• SOA CoP Demo Phase 3: Open Source SOA Infrastructure (IONA and others)    (3G7W)
  • March 1, 2007 2-3 pm EST, Webcast: Is Your Agency Ready for Open Source SOA?    (3GEL)
  • IONA Jumpstart Roadmap:    (3G8I)
    • Design and develop “sandbox”    (3G8J)
    • Design semantics/vocabulary:    (3G8K)
      • Use SICoP Semantic Wikis    (3G8L)
    • Design object registration and location services    (3G8M)
    • Map technologies to design    (3G8N)
    • Develop    (3G8O)
    • Test iteration    (3G8P)
    • Incrementally adopt additional services and technologies    (3G8Q)
• Joint Task Force on SOA Management and PGFSOA Infrastructure Team    (3G7X)
  • Knowledgebase Approach by SICoP. See February 6th Special Conference.    (3G7Y)
  • SOA Practitioners Guide:    (3G7Z)
    • Part 1: Why Services-Oriented Architecture? It provides a high-level summary of SOA.    (3G80)
    • Part 2: SOA Reference Architecture provides a worked design of an enterprise-wide SOA implementation, with detailed architecture diagrams, component descriptions, detailed requirements, design patterns, opinions about standards, patterns on regulation compliance, standards templates, and potential code assets from members.    (3G81)
    • Part 3: Introduction to Services Lifecycle provides a detailed process for services management though the service lifecycle, from inception through to retirement or repurposing of the services. It also contains an appendix that includes organization and governance best practices, templates, comments on key SOA standards, and recommended links for more information.    (3G82)
• OMG SOA Information Day, December 4, 2006: Collaboration and SOA Consortium    (3G83)
• Second SOA for E-Government Conference, October 30-31, 2006: Opening Keynote (Zapthink) and SOACoP Demo Phase 2 and Closing Keynote (David Linthicum)    (3G84)
  • 5 Ways to Make Your SOA a Success:    (3G85)
    • Understand the pain.    (3G86)
    • Define the value.    (3G87)
    • Focus on understanding (Steps to SOA).    (3G88)
    • Remember the people.    (3G89)
    • Focus longer term.    (3G8A)
• First SOA for E-Government Conference, May 23-24, 2006: Opening Keynote (Zapthink) and SOACoP Demo Phase 1 and Closing Keynote (OMG)    (3G8B)

Joint Task Force on SOA Management:    (3G8C)

• Architecture & Infrastructure Committee:    (3BR5)
  • Data Architecture Subcommittee    (3BR6)
  • Emerging Technology Subcommittee    (3BR7)
  • Governance Subcommittee    (3BR8)
  • Services Subcommittee    (3BR9)
• Best Practices Committee:    (3BRA)
  • SOA CoP    (3BRB)
  • SICoP    (3BRC)
• ACT/IAC:    (3BRD)
  • EA SIG    (3BRE)
  • SOA Committtee    (3BRF)
• Standards Organizations:    (3BRG)
  • OASIS SOA RM TC OASIS Reference Model for Service Oriented Architecture V 1.0 - Official Committee Specification approved Aug 2, 2006. (Normative PDF)    (3BTT)
  • OMG SOA SIG and White Paper    (3BRH)
  • Open Group    (3BRI)
  • SOA Alliance    (3BRJ)
  • SOA Consortium    (3G8R)
  • ModelDriven.Org (A division of Data Access Technologies, Inc.)    (3BTU)
  • DISA Emerging Standards for SOA    (3BTV)
  • AFEI SafeSOA    (3BTX)
  • Open SOA    (3CED)
  • Etc.    (3BRK)

A Collaborative Authoring and Editing Project to Bring Knowledge Management to EA and SOA Using Wiki Technology to Support a Community of Practice (e.g. the Data Reference Model 2.0): Version 0.2 in Word, December 19, 2006.    (3BRL)

• Preface    (3CMM)
• Credits    (3CMN)
• 1. Introduction    (3CMO)
  • 1.1. Purpose    (3CMP)
  • 1.2. Scope    (3CMQ)
  • 1.3. Audience    (3CMR)
  • 1.4. Document    (3CMS)
  • 1.5. How to Use this Guide    (3CMT)
  • 1.6. Related Documents    (3CMU)
• 2. Definitions, Drivers, and Principles    (3CMV)
  • 2.1. Service Oriented Architecture Defined    (3CMW)
    • Example of (1) Concept, (2) Definition, and (3) Specific Instance:    (3CQ8)
      • (1) Concept: Service Oriented Architecture (SOA)    (3CQ9)
      • (2) Definition: Software architecture that defines the use of services to support the requirements of software users Also see SOA Wiki Glossary and SOA CoP Glossary    (3CQA)
      • (3) Specific Instance 1: Bob Brown, US Patent & Trademark Office, News Story, Word Document and Slides    (3CQB)
        • Source: 2nd SOA for E-Government Conference, October 30-31, 2006    (3CQC)
  • 2.2. The Benefits of Service Oriented Architecture [and vision of service oriented enterprise]    (3CMX)
  • 2.3. Origin and Evolution of SOA    (3CMY)
  • 2.4. Service Architecture Principles    (3CMZ)
  • 2.5. The Service Oriented Solution Delivery Life Cycle (SDLC)    (3CN0)
  • 2.6. Service Orienting Your Enterprise Architecture    (3CN1)
  • 2.7. Risks and Challenges of Doing SOA    (3CN2)
  • 2.8. Successes in Implementing SOA    (3CN3)
• 3. Clarify the Rationale for SOA    (3CN4)
  • 3.1. Understand and validate the strategic context    (3CN5)
    • 3.1.1. Align with IT Strategic Plan    (3CN6)
    • 3.1.2. Align with Performance Architecture    (3CN7)
  • 3.2. Establish Clarity around Benefits    (3CN8)
    • 3.2.1. Metrics and Methods with Information Sharing    (3CN9)
    • 3.2.2. Metrics and Methods with Increased Flexibility    (3CNA)
    • 3.2.3. Metrics and Methods with Reuse    (3CNB)
    • 3.2.4. Metrics and Methods with Composition    (3CNC)
  • 3.3. Risks and Mitigations    (3CND)
    • 3.3.1. Planning and Enterprise Architecture    (3CNE)
    • 3.3.2. Delivery and Solution Architecture    (3CNF)
    • 3.3.3. Adoption and Governance (I)    (3CNG)
    • 3.3.4. Evolution and Governance (II)    (3CNH)
    • 3.3.5. Technology Standards    (3CNI)
  • 3.4. Financing SOA    (3CNJ)
    • 3.4.1. Adoption Phase    (3CNK)
    • 3.4.2. Steady State Phase    (3CNL)
  • 3.5. Maturity-Model Roadmap for SOA    (3CNM)
    • 3.5.1. Address Mitigations Before Promising Benefits    (3CNN)
    • 3.5.2. Linkage between Achievable Benefits and In-Place Risk Mitigations    (3CNO)
  • 3.6. Presenting the Rationale for SOA    (3CNP)
    • 3.6.1. Building the Case for SOA Through Extending the Case for Shared Services    (3CNQ)
    • 3.6.2. Packaging the Rationale    (3CNR)
• 4. Establish Service Oriented Architecture Environment    (3CNS)
  • 4.1. Obtain Executive Buy-in and Support    (3CNT)
    • 4.1.1. Present SOA Business Case    (3CNU)
    • 4.1.2. Issue Update to Enterprise Architecture Policy    (3CNV)
    • 4.1.3. Obtain Support from Senior Executives and Business Units    (3CNW)
  • 4.2. Modify Architecture Management Processes and Structure (Architecture Governance)    (3CNX)
    • 4.2.1. Update Technical Review Committee Charter    (3CNY)
    • 4.2.2. Update Capital Investment Council Charter    (3CNZ)
    • 4.2.3. Update EA Executive Steering Committee Charter    (3CO0)
    • 4.2.4. Update Enterprise Architecture Program Management Office Charter    (3CO1)
  • 4.3. Establish Governance Policies and Compliance Processes and Procedures (SOA Governance)    (3CO2)
    • 4.3.1. Service Management governance structures    (3CO3)
    • 4.3.2. Quality of Service (QOS) and SLA processes and policies    (3CO4)
    • 4.3.3. Charge-Back and Infrastructure-based Cost Recovery Framework    (3CO5)
    • 4.3.4. Change and Configuration Management    (3CO6)
    • 4.3.5. In sourcing-based Framework for Terms and Conditions    (3CO7)
• 5. SOA Program Activities and Products (Management)    (3CO8)
  • 5.1 ??    (3CO9)
    • 5.1.1. Refine EA Marketing Strategy and Communications Plan to Incorporate Services    (3COA)
    • 5.1.2. Update EA Program Management Plan    (3COB)
    • 5.1.3. Initiate Development of the Service Oriented Architecture    (3COC)
  • 5.2. Plan and Manage SOA Adoption (Funding, Program Delivery and Performance)    (3COD)
    • 5.2.1. Performance Architecture,    (3COE)
    • 5.2.2. Results Tracking, Processes and Metrics    (3COF)
    • 5.2.3. Framework for Harvesting Cost Savings    (3COG)
    • 5.2.4. Standards development and implementation    (3COH)
    • 5.2.5. Development of services strategy; linkage to business strategy    (3COI)
    • 5.2.6. Business/IT integration    (3COJ)
    • 5.2.7. Costing/Pricing/Charging processes    (3COK)
    • 5.2.8. Federal Budget Issues    (3COL)
    • 5.2.9. Funding strategies    (3COM)
• 6. Define SOA Process and Approach (How do I implement SOA within my EA Process)    (3CON)
  • 6.1. Define the Purpose, Scope and Depth of the Architecture    (3COO)
  • 6.2. Evaluate and Select Methodological Framework    (3COP)
    • 6.2.1. Reference Architecture    (3COQ)
    • 6.2.2. Strategic/Federated Model    (3COR)
    • 6.2.3. Shared Services Model    (3COS)
    • 6.2.4. Service Model Layers    (3COT)
    • 6.2.5. SOA Architectural Patterns    (3COU)
  • 6.3. Select Modeling Standards (eg UML2, BPMN)    (3COV)
  • 6.4. Update the Target Architecture    (3COW)
    • 6.4.1. Plan Services Portfolio (Domain Based Business Service Architecture)    (3COX)
    • 6.4.2. Plan Legacy Asset Services    (3COY)
    • 6.4.3. Business Process Modeling (Service Consumption)    (3COZ)
    • 6.4.4. Modify Target Technical Architecture to Support Services    (3CP0)
  • 6.5. Refine (As-Is) Application Portfolio Assessment    (3CP1)
    • 6.5.1. Revise Assessment Criteria    (3CP2)
    • 6.5.2. Collect Additional Data    (3CP3)
    • 6.5.3. Reevaluate Application Plans    (3CP4)
  • 6.6. Revise the Sequencing Plan    (3CP5)
    • 6.6.1. Projects/Programs Based on New SO Target Architecture    (3CP6)
    • 6.6.2. Define Releases Based on Legacy Application Migration Stages    (3CP7)
    • 6.6.3. Evolve Services from Legacy to Newly Provisioned Services    (3CP8)
• 7. Service Delivery Management and Infrastructure (How do I tie my SOA implementation to my development lifecycle and infrastructure delivery process)    (3CP9)
  • 7.1. Manage the Service Lifecycle    (3CPA)
  • 7.2. SOA Asset Management    (3CPB)
  • 7.3. Modeling and Configuration Management Tools    (3CPC)
• 8. Establish Runtime Infrastructure (How do I Service Orient my infrastructure to support SOA)    (3CPD)
  • 8.1. Network    (3CPE)
  • 8.2. Operating platforms and virtualization    (3CPF)
  • 8.3. ESB implementation and use    (3CPG)
  • 8.4. Security    (3CPH)
  • 8.5. Registry, repositories and policy engines    (3CPI)
  • 8.6. Policy Management    (3CPJ)
  • 8.7. Strategic Sourcing of infrastructure services    (3CPK)
• 9. Develop Solution Composition Capability (How do I integrate my SOA implementation into actual deliverable solutions)    (3CPL)
  • 9.1. Service Oriented Solution Architecture    (3CPM)
  • 9.2. Update Solution Delivery Life Cycle (SDLC)    (3CPN)
• 10. Update Related Management Processes (How does SOA influence and how is SOA influenced by other key IT management processes)    (3CPO)
  • 10.1. CPIC Processes    (3CPP)
  • 10.2. Acquisition and Procurement Process    (3CPQ)
  • 10.3. Portfolio Management Process    (3CPR)
  • 10.4. Human Resources    (3CPS)
    • 10.4.1. Training    (3CPT)
    • 10.4.2. Position Management    (3CPU)
    • 10.4.3. Incentives    (3CPV)
  • 10.5. Program Management Operations    (3CPW)
  • 10.6. Organization    (3CPX)
    • 10.6.1. Sharing models    (3CPY)
    • 10.6.2. Structural changes    (3CPZ)
    • 10.6.3. Collaboration processes    (3CQ0)
• 11. Summary and Recommendations    (3CQ1)
• Appendix A: SOA Roles and Responsibilities    (3CQ2)
• Appendix B: Glossary    (3CQ3)
• Appendix C: Acronyms    (3CQ4)
• Appendix D: Example SOA Products    (3CQ5)
• Appendix E: Sample Policies and Principles    (3CQ6)
• Appendix F: Bibliography    (3CQ7)