Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
The Matrix: Remixed BPM + SOA = Results-Oriented Architecture Linus Chow Charles “Flip” Medley Clay Richardson
The Problem <ul><li>There is an “operational disconnect” between Business and IT </li></ul><ul><ul><li>Business missions d...
The Blue Pill:  Business <ul><li>“ I need situational awareness tools that can give me the information to do my job…” </li...
The Red Pill:  IT <ul><li>“ I need detailed use cases so I can build the right solution…” </li></ul><ul><li>“ I need the r...
The Common Questions <ul><li>“ What am I supposed to do?” </li></ul><ul><li>“ How many resources am I being allocated to a...
Are you fighting with your solutions? <ul><li>Poorly implemented “solutions”: </li></ul><ul><ul><li>May not solve the orig...
Have we been here before? <ul><li>BPM is not BPR! </li></ul><ul><ul><li>“ Let’s refine your org charts…” </li></ul></ul><u...
Have we been here before?
Have we been here before? <ul><li>SOA  is not  a technology-centric approach: </li></ul><ul><ul><li>“ Thanks to  OO  we ca...
SOA: Baseline
SOA: Orchestrate
SOA: Compose
SOA: Results
SOA + BPM <ul><li>BPM is a foundational component of an SOA </li></ul><ul><ul><li>The big secret: SOA = BPM + … </li></ul>...
SOA + BPM = Results
Results-Oriented Architecture Service Infrastructure Application Infrastructure Service Service Service Service Service Se...
Results-Oriented Process <ul><li>Engage  stakeholders throughout the  mission context  during the development process </li...
“This time, it’s going to be different…”
Upcoming SlideShare
Loading in …5
×

The Matrix: Remixed BPM + SOA = Results-Oriented Architecture

4,513 views

Published on

Government and Commercial organizations are facing constant challenges to increase agility, efficiency and effectiveness. Focused on results, IT and mission managers are struggling to bridge historical differences when building solutions to solve their problems. With BPM and SOA, technologies and methodologies have
finally evolved to enable a successful results-oriented architecture to bridge this gap. This collaborative presentation walks through Best Practices that overcome the normal struggle between IT and mission, including examples from both government and commercial implementations.

Published in: Business, Technology
  • Be the first to comment

The Matrix: Remixed BPM + SOA = Results-Oriented Architecture

  1. 1. The Matrix: Remixed BPM + SOA = Results-Oriented Architecture Linus Chow Charles “Flip” Medley Clay Richardson
  2. 2. The Problem <ul><li>There is an “operational disconnect” between Business and IT </li></ul><ul><ul><li>Business missions demands more capable systems and greater automation from IT </li></ul></ul><ul><ul><li>IT wants more resources to support efforts to build better solutions </li></ul></ul><ul><li>Both want to do the right thing and work together, but… </li></ul>
  3. 3. The Blue Pill: Business <ul><li>“ I need situational awareness tools that can give me the information to do my job…” </li></ul><ul><li>“ I need the tools to execute my missions as quickly & efficiently as possible” </li></ul>
  4. 4. The Red Pill: IT <ul><li>“ I need detailed use cases so I can build the right solution…” </li></ul><ul><li>“ I need the resources to do my job… people, processes, and infrastructure.” </li></ul><ul><li>“ I’ll build it and come back to you with a finished product…” </li></ul>
  5. 5. The Common Questions <ul><li>“ What am I supposed to do?” </li></ul><ul><li>“ How many resources am I being allocated to accomplish this task?” </li></ul>
  6. 6. Are you fighting with your solutions? <ul><li>Poorly implemented “solutions”: </li></ul><ul><ul><li>May not solve the original problem(s) the business is facing </li></ul></ul><ul><ul><li>Adds cost and complexity </li></ul></ul><ul><ul><li>Limits the business’ ability to do its job well </li></ul></ul><ul><ul><li>Lack the flexibility to cope with change </li></ul></ul>
  7. 7. Have we been here before? <ul><li>BPM is not BPR! </li></ul><ul><ul><li>“ Let’s refine your org charts…” </li></ul></ul><ul><ul><li>“ Let’s analyze your processes and then we’ll make some recommendations…” </li></ul></ul><ul><ul><ul><li>“… and good luck implementing them after we leave!” </li></ul></ul></ul><ul><ul><ul><li>“… and we’re not going to show you how to enact those recommendations, since that’s not our area of expertise.” </li></ul></ul></ul><ul><li>BPM is about enabling business agility by insinuating the business in to every element of the development lifecycle </li></ul><ul><li>Keep the focus on getting results! </li></ul>
  8. 8. Have we been here before?
  9. 9. Have we been here before? <ul><li>SOA is not a technology-centric approach: </li></ul><ul><ul><li>“ Thanks to OO we can make systems that mimic your business concepts…” </li></ul></ul><ul><ul><li>“ Now that we have CORBA …” </li></ul></ul><ul><ul><li>“ Java will allow us to…” </li></ul></ul><ul><ul><li>“ Now that we have web services …” </li></ul></ul><ul><li>SOA is all about finding and building reusable services from your IT application infrastructure </li></ul><ul><li>These services can be leveraged directly by your BPM processes. </li></ul>
  10. 10. SOA: Baseline
  11. 11. SOA: Orchestrate
  12. 12. SOA: Compose
  13. 13. SOA: Results
  14. 14. SOA + BPM <ul><li>BPM is a foundational component of an SOA </li></ul><ul><ul><li>The big secret: SOA = BPM + … </li></ul></ul><ul><li>BPM encourages a results-oriented focus encourages best practices and reuse of artifacts across mission stakeholders </li></ul>
  15. 15. SOA + BPM = Results
  16. 16. Results-Oriented Architecture Service Infrastructure Application Infrastructure Service Service Service Service Service Service BPM End-Users Community Community Community Solution Governance IT Asset Governance Service Governance Enterprise Security Infrastructure Service Bus Service Management Service Registry Service Repository
  17. 17. Results-Oriented Process <ul><li>Engage stakeholders throughout the mission context during the development process </li></ul><ul><li>Propagate design artifacts across the entire mission context </li></ul><ul><li>Maintain the visibility of all artifacts across missions to promote reuse </li></ul>
  18. 18. “This time, it’s going to be different…”

×