1


                 Primary Contributors2
                                     :

                                       ...
2Washington State Enterprise Architecture Program        December 10, 2008
 3SOA Readiness Awareness Tool                 ...
7Washington State Enterprise Architecture Program        December 10, 2008
 8SOA Readiness Awareness Tool                 ...
12Washington State Enterprise Architecture Program        December 10, 2008
13SOA Readiness Awareness Tool                ...
17Washington State Enterprise Architecture Program        December 10, 2008
 18SOA Readiness Awareness Tool               ...
22Washington State Enterprise Architecture Program        December 10, 2008
 23SOA Readiness Awareness Tool               ...
27Washington State Enterprise Architecture Program        December 10, 2008
 28SOA Readiness Awareness Tool               ...
32Washington State Enterprise Architecture Program        December 10, 2008
 33SOA Readiness Awareness Tool               ...
37Washington State Enterprise Architecture Program        December 10, 2008
 38SOA Readiness Awareness Tool               ...
42Washington State Enterprise Architecture Program        December 10, 2008
 43SOA Readiness Awareness Tool               ...
47Washington State Enterprise Architecture Program        December 10, 2008
 48SOA Readiness Awareness Tool               ...
Upcoming SlideShare
Loading in …5
×

SOA Readiness Awareness Tool (doc)

761 views

Published on

Published in: Technology, Health & Medicine
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
761
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
59
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

SOA Readiness Awareness Tool (doc)

  1. 1. 1 Primary Contributors2 : 3 Jerry Britcher Department of Social and Health Services4 Paul Warren Douglas 5 Department of Information Services 6 David Jennings 7 Department of Health JoAnne Kendrick8 Department of Information Services Noel Morgan 9 Service-Oriented Architecture (SOA) Department of Transportation 10 Readiness Awareness Tool Douglas McGregor 11 Department of Licensing 12 EA Committee Endorsed Documenter Team EA Committee 13 Version 3.0 14 Stewards: 15 December 10, 2008 Bill Kehoe 16 Department of Licensing 17 Frank Westrum Department of Health Reviewers: Documenter Team Enterprise Architecture Committee Information Services Board Enterprise Architecture Committee Frank Westrum, Department of Health Rob St. John, Department of Social and Health Service Co-Chairs Paul Warren Douglas, Acting Enterprise Architect 1
  2. 2. 2Washington State Enterprise Architecture Program December 10, 2008 3SOA Readiness Awareness Tool EA Committee Endorsed Version 3.0 4 18Table of Contents 191. Purpose...................................................................................................................................................3 202. SOA Readiness Awareness and Discovery Questions............................................................................4 21 2.1. Enterprise SOA Committment and Business Case..........................................................................4 22 2.2. Funding Models ...............................................................................................................................4 23 2.3. Roadmap..........................................................................................................................................4 24 2.4. Maturity Model..................................................................................................................................4 25 2.5. Collaboration and Communication...................................................................................................5 26 2.6. Governance......................................................................................................................................5 27 2.7. Infrastructure and Technologies.......................................................................................................6 28 2.8. Processes and Framework...............................................................................................................7 29 2.9. Reference Architecture....................................................................................................................7 30 2.10. IT Business Transformation ..........................................................................................................8 313. Glossary.................................................................................................................................................10 324. References............................................................................................................................................10 335. Document History..................................................................................................................................11 346. Document Context.................................................................................................................................11 357. Documenter Team.................................................................................................................................11 36 37Terms & Definitions 38Terms noted in BOLD throughout document are generally SOA Glossary document entries or Section 4 39References. 5 Page 2 of 11 6
  3. 3. 7Washington State Enterprise Architecture Program December 10, 2008 8SOA Readiness Awareness Tool EA Committee Endorsed Version 3.0 9 40 1.Purpose 41This document is a conceptual tool to identify the structure and capabilities necessary for initiating Tier 42One enterprise Service-Oriented Architecture (SOA) development. 43This document is designed to. 44• Provide initial EA Committee awareness and 45 understanding of the various components 46 needed to implement a Tier One SOA 47 strategy. 48• Focus discussions in potential areas needing 49 future decisions in order to develop and 50 maintain a shared services environment. 51• Provide a roadmap for the Documenter Team. 52• Build on the SOA initiative charter and 53 business case to identify initiative goals and 54 key issues or decisions to be addressed. 55This document is not a maturity assessment. An Federal SOA Readiness, PGFSOA 56SOA maturity model is expected to be an initiative 57deliverable or architectural recommendation. 58Note:The concepts and questions within this document are expected to evolve through the initiative 59process. 10 Page 3 of 11 11
  4. 4. 12Washington State Enterprise Architecture Program December 10, 2008 13SOA Readiness Awareness Tool EA Committee Endorsed Version 3.0 14 60 2.SOA Readiness Awareness and Discovery Questions 612.1.Enterprise SOA Committment and Business Case 62 Does the state enterprise have a Tier One SOA vision and strategy? 63 2.1.1. Enterprise and Organizational Commitment 64 What enterprise and organizational commitment exists at the Tier One level? 65 o The enterprise strategic IT plan does not promote common IT practices, data sharing, and 66 reuse. 67 o The state has an enterprise strategic IT plan, yet does not include SOA strategies. 68  The state strategic IT plan includes goals to promote common IT practices, data sharing, 69 reuse and other SOA strategies. 70 2.1.2. Business Case 71 Does the state have a documented enterprise SOA Business Case? 72 o There are no plans to proceed with the SOA, or pursue as a Tier One Enterprise Initiative. 73 o There are plans to develop an SOA business case, yet the state plans to put SOA on hold for 74 now. 75  The state has completed a Business Case for enterprise SOA. 762.2.Funding Models 77 Does the state have a diversity of funding models to support Tier One SOA strategy? 78 o Yes 79 o In Progress 80 o No 81 o Other 822.3.Roadmap 83 Has the state developed a Tier One enterprise SOA strategy (e.g. conceptual implementation 84 approach?). 85 o Yes 86 o In Progress 87 o No 88 o Other 892.4.Maturity Model 90 Has the state defined a Tier One SOA maturity model? 91 o Components are not yet defined and expected to be an outcome or recommendation of the 92 initiative. 93 o The maturity model has performance measures and desired outcomes. 94 o Maturity model components are defined and operational within an enterprise SOA program. 95 o Other 15 Page 4 of 11 16
  5. 5. 17Washington State Enterprise Architecture Program December 10, 2008 18SOA Readiness Awareness Tool EA Committee Endorsed Version 3.0 19 962.5.Collaboration and Communication 97What is the extent of business and IT inter-agency SOA collaboration and communication? 98 2.5.1. State Agency Awareness - An enterprise plan and communication model exist to 99 implement and govern shared services. 100 o Yes 101 o In progress 102 o No 103 o Other 104 2.5.2. Business and IT Communication - Private and public sector best practices have been 105 identified to engage and educate the business community and agencies. 106 o Yes 107 o In progress 108 o No 109 o Other 110 2.5.3. Collaboration - Communication channels and processes are in place to enable the multi- 111 agency enterprise to share services. 112 o Yes 113 o In progress 114 o No 115 o Other 1162.6.Governance 117 What expected Tier One SOA governance components exist? 118 2.6.1. SOA-based Integration Governance Standards and processes.. 119 o Yes 120 o In progress 121 o No 122 o Other 123 2.6.2. The state has an SOA Competency Center/Integration Competency Center (ICC) to 124 support Tier One services. 125 o Yes 126 o In progress 127 o No 128 o Other 129 2.6.3. Governance roles and responsibilities are defined to enable the creation and 130 maintenance of Tier One services. 131 o Yes 132 o In progress 133 o No 134 o Other 20 Page 5 of 11 21
  6. 6. 22Washington State Enterprise Architecture Program December 10, 2008 23SOA Readiness Awareness Tool EA Committee Endorsed Version 3.0 24 135 136 2.6.4. SOA program requirements are defined to assist in education, identification, creation 137 and use of Tier One shared services. 138 o Yes 139 o In progress 140 o No 141 o Other 142 2.6.5. Policies and standards for SOA planning and governance are defined for Tier One 143 business analysis, procurements. 144 o Yes 145 o In progress 146 o No 147 o Other 148 2.6.6. State standards and laws, federal mandates, or other policies impacting the delivery of 149 shared services are identified. 150 o Yes 151 o In progress 152 o No 153 o Other 154 2.6.7. Sustainable support and funding have been identified for shared services, components 155 and infrastructure. 156 o Yes 157 o In progress 158 o No 159 o Other 160 2.6.8. Other governance components to consider. (e.g.IT Business related and others.) 161 o 162 o 163 o 164 2.7.Infrastructure and Technologies 165 What expected Tier One SOA infrastructure and technologies exist? 166 2.7.1. The state enterprise has the necessary Tier One infrastructure and technologies to 167 support SOA. 168 o Yes. Enterprise infrastructure and technologies are available to enable SOA such as: 169 o data integration 170 o integration middleware 171 o metadata repositories and management 172 o enterprise service bus 173 o message brokering service 174 o support services 25 Page 6 of 11 26
  7. 7. 27Washington State Enterprise Architecture Program December 10, 2008 28SOA Readiness Awareness Tool EA Committee Endorsed Version 3.0 29 175 o In progress 176 o No 177 o Other 178 2.7.2. Security and reliability requirements for sharing services are defined. 179 o Yes 180 o In progress 181 o No 182 o Other 183 2.7.3. Industry standards, best practices, and tools are defined as Tier One standards or 184 guidelines for business modeling, data modeling, data integration, data descriptions, 185 and data storage. 186 o Yes 187 o In progress 188 o No 189 o Other 190 2.7.4. Tier One services are governed, maintained, and available within a state enterprise 191 registry repository. 192 o Yes 193 o In progress 194 o No 195 o Other 196 2.7.5. Shared services are available for use at the Tier One level. 197 o Yes 198 o In progress 199 o No 2002.8.Processes and Framework 201 2.8.1. Are Tier One elements in place to address SOA strategic planning, design guidance, 202 SOA implementation and maintenance, service granularity, service interoperability, 203 service identification, and sustainable support? 204 o Yes 205 o In progress 206 o No 207 o Other 2082.9.Reference Architecture 209 2.9.1. Is an enterprise Reference Architecture available to support Tier One SOA services? 210 o Yes 211 o In progress 212 o No 30 Page 7 of 11 31
  8. 8. 32Washington State Enterprise Architecture Program December 10, 2008 33SOA Readiness Awareness Tool EA Committee Endorsed Version 3.0 34 213 o Other 214 2152.10.IT Business Transformation 216What expected areas and components for IT business transformation exist? 217 2.10.1. IT Business planning, project management, and procurement include identification and 218 use of Tier One shared services. 219 o Yes 220 o In progress 221 o No 222 o Other 223 2.10.2. Risk mitigation strategies are defined when adding shared services to existing 224 business process functions or legacy applications. 225 o Yes 226 o In progress 227 o No 228 o Other 229 2.10.3. Fiscal benefits are identified to invest in developing Tier One SOA shared services. 230 o Yes 231 o In progress 232 o No 233 o Other 234 2.10.4. Potential services candidates (short-term and long-term) are identified and prioritized. 235 o Yes 236 o In progress 237 o No 238 o Other 239 2.10.5. IT business processes are being transformed from stand alone, replicated processes 240 into highly leveraged shared services. 241 o Yes 242 o In progress 35 Page 8 of 11 36
  9. 9. 37Washington State Enterprise Architecture Program December 10, 2008 38SOA Readiness Awareness Tool EA Committee Endorsed Version 3.0 39 243 o No 244 o Other 245 40 Page 9 of 11 41
  10. 10. 42Washington State Enterprise Architecture Program December 10, 2008 43SOA Readiness Awareness Tool EA Committee Endorsed Version 3.0 44 246 3.Glossary 247Note: The EA Service-Oriented Architecture (SOA) initiative Glossary of terms is available in the main 248SOA Glossary document designed to meet the Charter objective: 249• Establish common terminology and key concepts 250The Glossary is expected to be developed and refined by the multi-agency Documenter Team throughout 251the initiative process. 252FutureSOA Initiative document deliverables are expected to refer to and help populate the document 253where possible. 254 4.References 255Gartner Gartner Group Research Service, retrieved 2007 256 Building a Service-Oriented Architecture Business Case: 257 Effective Communication is the First Step, Gartner, March 2007 258Forrester The Elements of SOA Maturity, Major Checklist Categories for 259 Developing Your SOA Strategy, Forrester, 2005 260 NASCIO National Association of Chief Information Officers, 261 Enterprise Architecture Tool Kit v 3, October 2003. 262ISB EA Standards and ICC Information Services Board (ISB) Enterprise Architecture (EA) 263 Integration Architecture Standards and Solution Sets and 264 Integration Competency Center conceptual design at: 265 http://isb.wa.gov/policies/eaprogram.aspx 266PGFSOA A Roadmap for SOA Adoption, Practical Guide to Federal 267 Service Oriented Architecture (PGFSOA), retrieved 2008 268Other materials reviewed for conceptual information. 269BEA SOA Readiness Self-Assessment, BEA/ORACLE, retrieved 2008 270Everware-CBDI SOA Readiness Assessment, Everware-CBDI, retrieved 2008 271IBM Service-Oriented Architecture (SOA) Readiness Assessment, 272 retrieved 2008 273IOWA IT Enterprise Service-Oriented Architecture SOA Readiness 274 Assessment Checklist v1.0, 2006 275Microsoft Service-Oriented Architecture (SOA), retrieved 2008 276Open Group Service-Oriented Architecture (SOA), Open Group SOA Working 277 Group, 2007 278 279 45 Page 10 of 11 46
  11. 11. 47Washington State Enterprise Architecture Program December 10, 2008 48SOA Readiness Awareness Tool EA Committee Endorsed Version 3.0 49 280 5.Document History Date Version Editor Primary Changes June 18, 2008 1.0 Ed Tolentino Initial Draft October 27, 2008 2.0 Paul Warren Douglas Document rewritten based on current best practices. (Team: David Jennings, Noel Morgan Douglas McGregor, Jerry Britcher, & JoAnne Kendrick. November 10, 2008 2.1 Paul Warren Douglas DT edits and request for endorsement. Revised Purpose, Governance, and Infrastructure sections. December 1, 2008 2.2 Paul Warren Douglas EA Committee edits and DT edits. Revisions: Changed Title Assessment to Awareness; Revised Purpose, Funding Model, added Other to responses. December 10, 2008 3.0 Paul Warren Douglas EA Committee edits and Endorsement. Section headers up level, Funding Model title and question, IT business to Governance, and added IT to Business section header, and project mgt to IT Business. 281 6.Document Context 282The SOA initiative will help guide decision-making and implementation of SOA solutions. This document 283is a deliverable identified within the Initiative Charter adopted on July 10, 2008 by the Information 284Services Board (ISB). The charter is available at: 285http://dis.wa.gov/enterprise/enterprisearch/soa_initiative.aspx 286This document has EA Committee Endorsed status. For more information about the ISB EA Committee 287and initiatives, please visit the EA Committee website at: 288http://isb.wa.gov/committees/enterprise/index.aspx. 289 7.Documenter Team 290Stewards: 291• Bill Kehoe, Department of Licensing 292• Frank Westrum, Department of Health 293Architect: 294• Paul Warren-Douglas, Department of Information Services 295Documenter Team 296• The Documenter Team members are listed in the initiative Charter Appendix A at: 297 http://dis.wa.gov/enterprise/enterprisearch/soa_initiative.aspx 50 Page 11 of 11 51

×