1. The Road to a Service Oriented Architecture
Mark Adams
Education (Scotland)
Microsoft

2. What do you really mean by SOA Governance …
Speed-start Web services SOAs and Web services
What do you really mean by SOA Governance …
Processes
People
Technology
Services
Governance comes from the root word “Govern”. Governance is the structure of relationships and processes to direct and to control the SOA components in order to achieve the enterprise’s goals by adding value while balancing risk versus return
The focus of SOA is the
Services Model
Mission: Establish Service-Oriented governance baseline to measure process improvement and establish the structure allowing future initiatives to participate in a unified, company-wide service governance method.
Governance comes from the route word “Government”. Governance is the structure of relationships and processes to direct and to control the enterprise in order to achieve the enterprise’s goals by adding value while balancing risk versus return over IT/SOA and its processes.
The Service Model – the identification and definition of services – is the focal point of SOA Governance. It is the key differentiator of the Services Oriented Architecture models, and requires continuous management and
The governance model defines:
What has to be done? The Service Lifecycle – activities needed to define, specify, implement, and maintain services and their enabling components
How is it done? The governance decision path based actions – how to identify the right services, how to validate that services are created using the technology standards that have been mandated and that enable their reuse across the organization
Who has the authority to do it? The roles of the SOA CoE and the associated roles – being virtual or actual, regardless of the organizational construct that exists is put in place
How is it measured? The vitality and conformance checkpoints – extending quality assurance and architectural compliance processes that may exist in the organization, or creating new ones.
At defined points in time governance is planned and intercepts with the project:
Compliance check points deal with design direction decisions and funding.
Vitality check points help ensure the SOA architecture stays current.
Governance is not management.
Governance determines who has the authority to make a decisions. Management is the process of making and implementing the decisions.
The governance model defines:
What has to be done?
How is it done?
Who has the authority to do it?
How is it measured?
ibm.com/developerWorks/webservices - © Copyright 2004 IBM Corporation.

3. Things I musn’t say today
Leverage
Architected
Tasked
Evolution not Revolution

4. Things you should applaud
Artifacts
Abstraction
Showing of code samples

5. Only 28½ years ago…

6. IT Services Portfolio - Example

7. Services-based Enterprise Architecture (SEA)
Governance Architecture
Business Architecture
Business Services (capabilities, processes, people, metrics)
IT Services Architecture
Functional, performance and operational capabilities, Bill of material
Technology Architecture
Operations Architecture
Service implementation and life cycle
Technical design patterns
Service deployment and monitoring
Physical assets and configuration
Guiding principles, decision rights, criteria

9. Service Orientation is coming out of the “Trough of Disillusionment”
12/3/2018 4:45 AM
Service Orientation is coming out of the “Trough of Disillusionment”
Visibility
Technology
Trigger
Peak of Inflated
Expectation
Trough of
Disillusionment
Slope of
Enlightenment
Plateau of
Productivity
Maturity
©2005 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

10. But there is diversity…

11. <XML>

12. The Origins of XML Today 1998 1996 1994 1993 1989 1986 1980 1969 1967
12/3/2018 4:45 AM
The Origins of XML
Today
XML ubiquitous throughout the industry
1998
XML approved as W3C Recommendation
1996
XML proposed to W3C as a simplification of SGML, led by Jon Bosak (Sun)
1994
TBL forms the W3C with MIT and CERN
1993
CERN declares WWW free-to-all, NCSA releases Mosaic browser
1989
Tim Berners-Lee invented HTML at CERN, calls it the World Wide Web
1986
SGML approved as ISO standard (ISO 8879)
1980
First ANSI Standard Generalized Markup Language (SGML) draft released
1969
Goldfarb, Mosher, and Rice invented GML (IBM)
1967
Tunnicliffe and Rice introduce the concept of generic markup
©2005 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

13. Connected Systems The Five Pillars

15. We were asking these questions
How do we avoid making the same mistakes with service-oriented architectures that previous, hopeful initiatives have resulted in?
How do we ensure that the chosen implementation architecture relates to the actual or desired state of the business?
How do we ensure a sustainable solution that can react to the dynamically changing nature of the business. In other words, how can we enable and sustain an agile business?
How can we migrate to this new model elegantly and at a pace that we can control?
How can we make this change with good insight into where we can add the greatest value to the business from the outset?

16. SO Modelling

17. SO Modelling

18. Abstraction = Architecture

19. The “Amazing” Cartoon Syndrome

20. The Four Tenets Boundary – Boundaries are explicit.
Autonomy – Services are autonomous.
Contract – Services share schema and contract, not class.
Policy – Service compatibility is determined based on policy.

23. Modelling Business Function

24. Modelling Service Levels

25. Model the implementation

26. Pragmatic SOAD

27. Creating the Technology Model
The technology model consists of the following artifacts:
Service interface
Service implementation
Service host
Service management
Orchestration engine

28. Creating Services

29. Six Steps for Building Services
Design the data and message contract.
Design the service contract.
Create the adapters.
Implement the service internals.
Connect the internals to the adapters.
Create the transport interfaces.

30. Conclusions The technicians have delivered strongly
This stuff is a real struggle
We need to change the way we think and do
We should be working harder to tune into the non-abstract elements
We need to have a different confidence
The road is littered with personal opinions, religion and prejudice
Why am I saying this?

31. Service Orientation is coming out of the “Trough of Disillusionment”
12/3/2018 4:45 AM
Service Orientation is coming out of the “Trough of Disillusionment”
Visibility
Technology
Trigger
Peak of Inflated
Expectation
Trough of
Disillusionment
Slope of
Enlightenment
Plateau of
Productivity
Maturity
©2005 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

32. We were asking these questions
How do we avoid making the same mistakes with service-oriented architectures that previous, hopeful initiatives have resulted in?
How do we ensure that the chosen implementation architecture relates to the actual or desired state of the business?
How do we ensure a sustainable solution that can react to the dynamically changing nature of the business. In other words, how can we enable and sustain an agile business?
How can we migrate to this new model elegantly and at a pace that we can control?
How can we make this change with good insight into where we can add the greatest value to the business from the outset?

33. Questions Are we really prepared to think and design in these ways?
Do you understand these mechanisms well enough to trust for implementation?

34. Materials
Dare Obasanjo, "Designing Extensible, Versionable XML Formats",
GAT – Guidance Automation Toolkit,
Arvindra Sehmi and Beat Schwegler, “Modeling and Messaging for Connected Systems”, a webcast can be found here:

35. © 2006 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.