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
OASIS Service Oriented Architecture Reference Model TC
1
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
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
4
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
5
6
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
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.
ANSI/IEEE Std 1471
8
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
Stakeholders and Participants Resources and Ownership Needs and Capabilities Acting in a Social Context Semantics of Communication Roles, responsibilities, Governance
10
We use a lot of UML in this RA
11
Resources are foundational to the RA as a whole Ownership is foundational to using a SOA
12
Needs and Capabilities speak to participants’ motivations
13
It is all about interaction and communication It is all about getting things done, in a social context
14
Communication is founded on vocabulary, semantics and intention
15
There is a social context for everything we do Clarity in rights and responsibilities is the foundation for security
16
17
Service Description Visibility Interacting with Services Policies and Contracts
18
19
20
21
22
23
24
25
26
27
28
29
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
participants and resources that is agreed to by two or more participants
30
Its all about constraints
31
Obligation Enforcement is based on audit
32
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
domains Applicable when multiple internal stakeholders involved and no simple hierarchy of control and management
33
Governance about how decisions are made Management is about how decisions are realized Nested – management at one level is governance at another
34
35
36
37
Management of Services rather than simply IT Management
38
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
40
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
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
42
43