Reference Architecture for SOA OASIS Service Oriented Architecture - PowerPoint PPT Presentation

Reference Architecture for SOA OASIS Service Oriented Architecture Reference Model TC 1

Systems and eco- systems Multiple ownership domains No one entity controls everything Parallel development, deployment and usage of services A medium for people* to get their business done * We include organizations and robots, but the canonical use case is people using an SOA-based system as a medium to `act at a distance’ 2

What is a Reference Architecture? A reference architecture models the abstract architectural elements in the domain independent of the technologies, protocols, and products that are used to implement the domain. 3

Where we fit 4

What is this RA? This Reference Architecture is an abstract realization of SOA. We focus on the elements and their relationships needed to enable SOA- based systems to be used, realized and owned 5

Goals of the Architecture 6

Architectural Principles Technology Neutrality We want to focus on the issues Parsimony Ockham’s razor at work Separation of Concerns Pieces that are independent are kept separate Applicability We are looking for the 80/20 rule 7

Views and Viewpoints ANSI/IEEE Std 1471 - 2000 A view is a representation of the whole system from the perspective of a related set of concerns. A viewpoint is a specification of the conventions for constructing and using a view. 8

Three views of SOA Using a SOA-based system Captures what SOA means for people conducting their business Realizing a SOA-based system Deals with the requirements for constructing a SOA Owning a SOA-based system What are the issues involved in owning a SOA- based systems 9

Business via Services Stakeholders and Participants Resources and Ownership Needs and Capabilities Acting in a Social Context Semantics of Communication Roles, responsibilities, Governance 10

Stakeholders and Participants We use a lot of UML in this RA 11

Resources and Ownership Ownership is foundational to using a SOA Resources are foundational to the RA as a whole 12

Needs and Capabilities Needs and Capabilities speak to participants’ motivations 13

Acting in a Social Context It is all about getting things done, in a social It is all about interaction context and communication 14

Semantics of Communication Communication is founded on vocabulary, semantics and intention 15

Roles, Responsibilities and Governance There is a social context for everything we do Clarity in rights and responsibilities is the foundation for security 16

Governance 17

Realizing SOA View Service Description Visibility Interacting with Services Policies and Contracts 18

Model for Descriptions 19

Service Descriptions 20

Service Description and Action 21

Service Interface Model 22

Service Reachability Model 23

Visibility Model 24

Awareness Model 25

Description and Willingness 26

Policies and Contracts 27

Interacting with Services 28

Message Exchange 29

Policies and Contracts A Policy is an enforceable constraint on the behavior and states of participants and resources that is adopted by a stakeholder A Contract is an enforceable constraint on the behavior and states of participants and resources that is agreed to by two or more participants 30

Policy Constraints Its all about constraints 31

Enforcing Policy Constraints Obligation Enforcement is based on audit 32

Owning SOA-based systems Focuses on functions required in achieve value for the enterprise by owning a SOA-based system Significantly different challenges to owning other complex systems -- such as Enterprise suites Strong limits on the control and authority of any one party when a system spans multiple ownership domains Applicable when multiple internal stakeholders involved and no simple hierarchy of control and management 33

Governance of SOA- based systems Governance about how decisions are made Management is about how decisions are realized Nested – management at one level is governance at another 34

Motivation for Governance 35

Setting up Governance 36

Implementing Governance 37

Management Management of Services rather than simply IT Management 38

Security Security Concepts e.g., Confidentiality, ..., Availability Threat Model e.g., Spoofing, Repudiation,...,UnAuthorized actions Mitigation Model e.g., Policies for security, Explicit Rights, Responsibilities 39

Trust 40

Where we are Been active for nearly two years Most of the material is in place 100+ page document Plan to issue first OASIS Public Review in early May Emphasis on the relationship between people and the systems they live with 41

Relationship to Agent Oriented Systems Service Oriented Architecture is like a requirements architecture. We focus on what problems are needed to be solved Agent Oriented Systems are implementation architectures Most businesses would not know a belief, desire or intent if one landed on their heads 42

Any Questions? 43