About the Course
This course is not about ‘how to do SOA’ – Service-Oriented Architecture may be designed or realised. Any Service-Oriented (SO) architecture may be realised in several different ways. If architectural principles are preserved in realisation, one can recognise SOA through the realisation.
This course teaches architects what should be considered in the design and what should be controlled in implementation via governance when working within SO Ecosystem. SOA is not a technology; it is not the same as integration though implementation of SOA required integration, which should be done by SOA, not development rules.
This course represents the foundation view on SOA as The Open Group and OMG agreed with OASIS since 2009. For example, this means that the OASIS definition of service as a working body rather than an interface like Web Service or REST should be preserved and realised in practice.
Who is this course for?
While we welcome requests from university graduates of a wide range of disciplines, this course is particularly suited to people specialising in business and enterprise (technology) architecture, programme managers and solutions architects. Technology platform architects (in programming) and infrastructure architects are welcome as well, but they have to be ready to meet with architectural problems and concerns that are above software and infrastructure development.
The course materials and examples are developed based on personal practical experience of the authors lasting for the 19 years, OASIS SOA standards as well as personal teaching practice. The OASIS SOA-RM Technical Committee particularly underlined his “significant writing and conceptualization contributions” into standard specification Reference Architecture Foundation for SOA RAF.
Michael Poulin widely applied SO concept in his practice in financial industry; he authored or co-authored four books on the topic of architecture of business where SOA has been expanded in corporate business realm – management and architecture. He is a Board Member of the Business Architecture Society and frequent published in the LinkedIn Pulse.
Mode of study
This course is taught only in “in-class” mode.
Pre-requisites for this course are straightforward: learners have to have wide knowledge and, desirably, practical experience in architectural discipline in their organisations.
It is assumed that a group of learners gathers in an auditorium where the training will be conducted for 3 consecutive days. The course modules are mixed with exercises for the group or individual work. There will be a 1-hour lunch break and one or two 15-minute coffee-breaks in the first and second half-day periods. Overall, each day is planned for 6 to 8 hours in class depending on the number and complexity of questions.
The course comprises 16 modules and in-class exercises. The following are the core modules:
1. MODULE – Introduction
- WHAT&WHY versus HOW
- Architectural Language
- Architecture versus Technology
- Different SOA Standards
- Definitions versus Viewpoints
1. MODULE – Fundamentals
- Service-Oriented Ecosystem
- Concept of service ownership
- Abstracts versus Implementation
- Goals and Principles of Service Orientation
- Concepts and assumptions
4. MODULE – Service-Oriented Ecosystem 1
- Ecosystem Model
- Corporate Culture and Social Structure
- Stakeholders, Participants, Actors and Delegates
- Authority, Rights, Responsibilities and Roles
- Providers, consumers and ownership
5. MODULE – Service-Oriented Ecosystem 2
- Execution Context
- Trust and Risks
- Needs, Willingness and Capabilities
- Real World Effect
- Interaction versus Integration
5. MODULE – Services
- Services Description
- Functionality Outcomes
- Policy Compliance
- Contracts versus Policies
- Service Contracts in Execution Context
- Instance and State
- Usage of Service Description and Contracts
MODULE – Business Service
- Boundaries and Interfaces
- Contractual dependencies
- Supply chain model
MODULE – Patterns
- Interaction versus Design
- Enterprise Service Bus
- Resource decoupling
- Security Gateway
- Legacy Wrapper
- Data Access
MODULE – Design
- Consumer base
- Refactoring and Boundaries
- Technology ties
- Testing and Testing Proxy
MODULE – Governance and Management
- Stakeholders and Concerns
- Architectural controls and PMO
MODULE – Security
- Authentication and authorisation
- Encryption and signing
- Compliance and Execution Context
MODULE – Practices
- Version control
- Backward compatibility
- SOA in Cloud and Microservices
- Supply chain
MODULE – Business Cases
- Typical Business case
- Example: business service-process
- Service economy
- Client’s case – review