1. Harald Fusdahl Architect Microsoft Corporation
Service Oriented Architecture The re-birth of business process modeling
Harald Fusdahl
Architect
Microsoft Corporation
© 2006 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

2. Disclaimer #1 Disclaimer #2
5/27/2018
Disclaimer #1
The opinions expressed in this presentation are the opinions of the presenter and not necessarily those of Microsoft!
As a matter of fact, nobody “important” has reviewed it..
Disclaimer #2
“Never make forecasts, especially about the future!” - Samuel Goldwyn 2
© 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

3. Relevance Panic!! Process-Views-Services: A Better
Design Paradigm For Applications
(February 12, 2008 FORRESTER)
The next Revolution in productivity
(1 June, 2008 Harvard Business Review)
Bli skeptisk straks du hører SOA
(23 Mai, Digi – Helge Skrivervik)

4. Video

5. Goal of today’s talk Introduction to SOA and BPM
Show that the modeling part of Business Process Management is the common battlefield of IT and Bizz
Show how you can leverage Business Process modeling and Service Orientation in your next engagement

6. Terminology: Service
A service is work done by one or more applications that benefits another application
These services can be composed into application which implement new or existing business processes
© 2006 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

7. Terminology: Service Oriented Architecture
Service Oriented Architecture is a set of recommended practices to get services working in the enterprise
Security
Governance
Domain usage
Development practices
Consumption …
© 2006 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

8. How are applications made?
The irresistible beauty of programming consists in the reduction of complex formal processes to a very small set of primitive operations
Business people do not see this beauty

9. Terminology: Business process modeling
BPM is the activity of representing current and future company processes trough a modeling language…
Into a model template to identify unique, measurable and consistent processes

10. Business Process Modeling Language standards
Business process Modeling Notation (BPMN)
Business Process Execution Language (BPEL)
Unified Modeling Language (UML)
Object Process Methodology (OPM)

11. Business Process Model Example

12. How is business done?
You make something, somebody wants it, you sell it to them and make some more.
It looks like a formal process, but business are goal driven not process driven so it changes all the time developers don’t get this (and business will not acknowledge it..)

13. What are we trying to solve?

14. So the problem with today's “SOA” projects
Vendor driven SOA
Solution confusion and technology driven
Project driven SOA
Given the choice between “can we use some extra money and do it right” vs. “give the business what they want the cheapest and fastest way”
Bottom –UP SOA
Data driven and miss match towards process

15. Claims - AuthZ (WS-Trust/WS-Federation) Resources (LOB Domain Objects)
Workflow
Human Task
Human Task
Canonical
Domain Model
(Documents)
Orchestrations
Events
Composite Services / Service Bus
Events
Services
Formal Process
Activity
Entity
Capability
Resources (LOB Domain Objects)
LOB Systems

16. The Cloud is Coming

17. How do I know? Because we are building it. And so are Google Amazon
IBM
SAP
Salesforce …

18. The “Real” Cloud
Lines of business will likely adopt the cloud before central IT.
This always happens when the Internet meets the Enterprise.
Seeing this today with SaaS providers
Salesforce.com etc.
mms://wm.microsoft.com/ms/msnse/0804/33036/MMS2008-Day3-Keynote-debrac.wmv

19. The “Real” Cloud
Choosing to put stuff in the cloud is just as likely to be a business decision as a technical one.
The cloud offers value (greater efficiency and reliability and lower cost, etc.) through economies of scale.
Lines of business will likely adopt the cloud before central IT.
This always happens when the Internet meets the Enterprise.
Seeing this today with SaaS providers
Salesforce.com etc.
mms://wm.microsoft.com/ms/msnse/0804/33036/MMS2008-Day3-Keynote-debrac.wmv

20. Why use Modelling? Models are dynamic (live) Enable (automate)
Managed (Documented)
Version controlled
Workflow enabled
Accessible
Enable (automate)
Visibility
Into business process
Meaningful representation of the information at different levels
Forward-Engineering
Automation of generating partially-complete artefacts (source code, configuration, document etc.)
Backward-Traceability (reversible)
Models are connected to each other

21. What does this approach mean to you?

22. What does this mean If you are a developer
Learn to model
Understand model driven architecture
Deployment models, business models etc..
You must be a “mini”-architect
Governance, Security, standards etc..
In other words you can not be a code-monkey, to be a developer today is actually harder than yesterday.

23. What does this mean If you are a business representative
Learn to model (not the whole of BPMN, which is 300+ pages..)
Understand “the cloud” and your outsourcing strategies
You will not be a developer yet

24. What does this mean In your next SOA project
Find and model your formal business processes (capabilities, goals)
Pick a candidate which brings most value to the business
Make a service model (function, architecture, deployment)
Repeat

25. What does this mean If you are Microsoft?
Global datacenter construction
Service Management strategy with Systems Center Operations Manager
Utilization and capacity management strategy with Systems Center Virtual Machine Manager
Expanding service programming model, .NET, from device to server to cloud
Extending the application platform with cloud services
Internet scale service communications bus with BizTalk Services
Converging Environment/Services/Application modeling efforts and modeling platform strategy with “Oslo”

26. Summary
After 8+ years, the time is right for business process modeling
Modeling supports a middle out approach
Business process modeling is not a business or an IT task, it’s a joint adventure

27. References Seven fallacies of BPM
Computer Science Education: Where Are the Software Engineers of Tomorrow
InfoWorker Solutions: Business Modeling Taxonomy & Ontology: Domain Objects, Lifecycles, Processes

28. Questions?

29. 5/27/2018 4:44 AM
© 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
© 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.