Making SOA a Reality for Federal Government Agencies

1,053 views

Published on

Published in: Business, Career
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,053
On SlideShare
0
From Embeds
0
Number of Embeds
19
Actions
Shares
0
Downloads
30
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Making SOA a Reality for Federal Government Agencies

  1. 1. Melvin Greer Chief SOA Architect SOA Chief Architect Senior Research Engineer Lockheed Martin, IS&GS Making SOA a Reality for Federal Government Agencies
  2. 2. Key Issues <ul><li>What are common SOA disorders and SOA Competency Center Drivers? </li></ul><ul><li>What is a SOA Competency Center, and how do different models compare? </li></ul><ul><li>What symptoms suggest use of a SOA Competency Center and what psychological behaviors are encouraged? </li></ul><ul><li>What Business outcomes drive SOA Competency Center development? </li></ul>
  3. 3. SOACC Drivers <ul><li>The pressure is on for IT to deliver applications that can change on a dime - evolving as quickly as the business evolves even in the face of uncertain requirements. </li></ul><ul><li>Business expects IT to support Rapid Response to Change with Optimal Efficiency in Motion, Economy of Effort, Energy in Execution, and Efficacy of Impact </li></ul>
  4. 4. Common SOA Based Disorders <ul><li>Technology Altar Syndrome: </li></ul><ul><ul><li>Where IT sacrifices business focus on the technology altar; all focus is on technical purity and a single IT &quot;truth&quot; for the enterprise </li></ul></ul>
  5. 5. Common SOA Based Disorders <ul><li>Technology Altar Syndrome: </li></ul><ul><ul><li>Where IT sacrifices business focus on the technology altar; all focus is on technical purity and a single IT &quot;truth&quot; for the enterprise </li></ul></ul><ul><li>Organization / Financial Disorder </li></ul><ul><ul><li>Where organizational and financial systems impair enterprise thinking and development </li></ul></ul>
  6. 6. Common SOA Based Disorders <ul><li>Technology Altar Syndrome: </li></ul><ul><ul><li>Where IT sacrifices business focus on the technology altar; all focus is on technical purity and a single IT &quot;truth&quot; for the enterprise </li></ul></ul><ul><li>Organization / Financial Disorder </li></ul><ul><ul><li>Where organizational and financial systems impair enterprise thinking and development </li></ul></ul><ul><li>NIH Dementia </li></ul><ul><ul><li>Part of Control Phobia, impacts naming and reuse capability </li></ul></ul>
  7. 7. Common SOA Based Disorders <ul><li>Technology Altar Syndrome: </li></ul><ul><ul><li>Where IT sacrifices business focus on the technology altar; all focus is on technical purity and a single IT &quot;truth&quot; for the enterprise </li></ul></ul><ul><li>Organization / Financial Disorder </li></ul><ul><ul><li>Where organizational and financial systems impair enterprise thinking and development </li></ul></ul><ul><li>NIH Dementia </li></ul><ul><ul><li>Part of Control Phobia, impacts naming and reuse capability </li></ul></ul><ul><li>SOA Governance Hypersensitivity </li></ul><ul><ul><li>Deviant of enterprise policies, standards, and methods </li></ul></ul>
  8. 8. What is a SOA Competency Center? <ul><li>The SOA competency center unites a diverse set of skills coming from application development, architecture, operations, external vendors, business people, security, marketers and administration. </li></ul><ul><li>It is a federated environment geared up to make SOA based application development and integration as fast and smooth as possible. </li></ul>By year-end 2008, approximately 67 percent of very large companies will have an SOACC, up from approximately 40 percent at the beginning of 2005. By 2010, more than 80 percent of very large companies and 50 percent of large companies will have a SOACC. - Gartner
  9. 9. SOACC Functional Capabilities
  10. 10. SOACC Models
  11. 11. SOACC Model Comparison
  12. 12. Symptoms suggesting you need a SOACC <ul><li>Hundreds of services, but no one is looking for them or no one can find them </li></ul>Behavioral Change Required
  13. 13. Symptoms suggesting you need a SOACC <ul><li>Hundreds of services, but no one is looking for them or no one can find them </li></ul><ul><li>Service reuse rate is less than 5% </li></ul>Behavioral Change Required
  14. 14. Symptoms suggesting you need a SOACC <ul><li>Hundreds of services, but no one is looking for them or no one can find them </li></ul><ul><li>Service reuse rate is less than 5% </li></ul><ul><li>Impaired ability to estimate cost, time, resources for SOA projects </li></ul>Behavioral Change Required
  15. 15. Symptoms suggesting you need a SOACC <ul><li>Hundreds of services, but no one is looking for them or no one can find them </li></ul><ul><li>Service reuse rate is less than 5% </li></ul><ul><li>Impaired ability to estimate cost, time, resources for SOA projects </li></ul><ul><li>Orchestration and Choreography are theatre terms </li></ul>Behavioral Change Required
  16. 16. SOACC’s encourage Behavioral change <ul><li>Business focused approach to SOA </li></ul><ul><li>Creating a common language for SOA approach </li></ul><ul><li>Drive discovery and composition </li></ul><ul><li>Rightsize SOA Governance </li></ul><ul><li>SOA testing is a business issue </li></ul><ul><li>Develop pragmatic incremental targets </li></ul>
  17. 17. Side Effects and Interactions are not mild <ul><li>Increased interaction with Business: </li></ul><ul><ul><li>Learn a new language, get new measurement tools </li></ul></ul>
  18. 18. Side Effects and Interactions are not mild <ul><li>Increased interaction with Business: </li></ul><ul><ul><li>Learn a new language, get new measurement tools </li></ul></ul><ul><li>Technical Complexity rises </li></ul><ul><ul><li>Architecture, Application, Security, Infrastructure convergence </li></ul></ul>
  19. 19. Side Effects and Interactions are not mild <ul><li>Increased interaction with Business: </li></ul><ul><ul><li>Learn a new language, get new measurement tools </li></ul></ul><ul><li>Technical Complexity rises </li></ul><ul><ul><li>Architecture, Application, Security, Infrastructure convergence </li></ul></ul><ul><li>Scarcity of Qualified Resources </li></ul><ul><ul><li>Retention, training, and workload balance </li></ul></ul>
  20. 20. Side Effects and Interactions are not mild <ul><li>Increased interaction with Business: </li></ul><ul><ul><li>Learn a new language, get new measurement tools </li></ul></ul><ul><li>Technical Complexity rises </li></ul><ul><ul><li>Architecture, Application, Security, Infrastructure convergence </li></ul></ul><ul><li>Scarcity of Qualified Resources </li></ul><ul><ul><li>Retention, training, and workload balance </li></ul></ul><ul><li>Build it and they will come </li></ul><ul><ul><li>More work than you can manage </li></ul></ul><ul><ul><li>New business models </li></ul></ul>
  21. 21. SOACC Management: Mental State for Success <ul><li>Develop a Business Orientation </li></ul><ul><li>Listen with adaptation in mind (organizational / cultural) </li></ul><ul><li>Establish a technology convergence strategy </li></ul><ul><li>Determine key metrics to communicate </li></ul>
  22. 22. Business Outcomes <ul><li>SOA and Business process management get to innovation </li></ul><ul><li>Deeper focus on governance from a business services perspective </li></ul><ul><li>Increase business growth, ability to move to adjacent markets, and increased productivity </li></ul><ul><li>The challenges are many, but the business value that the SOACC’s return, mainly in terms of quicker time to market and reduction in maintenance costs, guarantees that they are worth the hassle of building and operating them. </li></ul>
  23. 23. Thank You! <ul><li>Melvin Greer </li></ul><ul><li>Chief SOA Architect </li></ul><ul><li>Senior Research Engineer, Principal </li></ul><ul><li>Lockheed Martin, IS&GS </li></ul><ul><li>[email_address] </li></ul>

×