Thomas Clarke - Global Justice Reference ArchitecturePresentation Transcript
Global Justice Reference Architecture Why we need it. What it is. Who is working on it.
Focus on the Business– Process and Services Application a Application c Application b Application logic Source: Service-Oriented Architecture, Thomas Erl Business logic
Focus on the Business– Process and Services Application layer Services interface layer Business process layer Application-oriented services Business-oriented services .NET J2EE Legacy Source: Service-Oriented Architecture, Thomas Erl
Focus on the Business– Process and Services Application layer Services interface layer Business process layer .NET J2EE Legacy Source: Service-Oriented Architecture, Thomas Erl orchestration service layer business service layer application service layer
System Integration: Principles
Minimize the dependencies between integrated information systems (“loose coupling”).
Favor technologies that leverage open industry standards.
Promote the treatment of integration interfaces as sharable enterprise assets.
Promote the one-time entry (or update) of information.
System Integration: Business Drivers
The enterprise will implement technology capabilities incrementally.
Enterprise solutions will continue to exhibit a mix of commonly-provisioned and agency-unique capabilities.
The enterprise will continue to rely on a diverse set of software platforms and development technologies.
Conceptual Reference Architecture
A reference architecture establishes key concepts, relationships, and high-level components to support integration
Identifies specific areas where we need more work, but demonstrates how everything fits together to satisfy requirements
Capabilities and Services
Interfaces and Interaction
Service Interaction Profiles
Policies, Contracts, Agreements
Business Processes / Service-Capability Hierarchy
Edge vs. Common Capabilities
At least 9 groups are working on different pieces of the architecture.
One of those groups doesn’t yet exist.
Some pieces of the architecture are not yet being worked on by anyone.
There are at least 8 different points of potential technical interoperability issues.
There are 3 broader points of disconnect.
This is a work in progress.
The concepts may change incrementally, but the basic approach is set.
Unofficial efforts to collaborate with broader communities.
Official efforts to brief broader communities.
OASIS SOA Reference Model Technical Committee, www.oasis-open.org
Scott Came, email@example.com
Tom Clarke, firstname.lastname@example.org
Scott Fairholm, email@example.com
Thomas Erl, Service-Oriented Architecture: concepts, technology and design.