1 / 18

Global Justice Reference Architecture

Global Justice Reference Architecture. Why we need it. What it is. Who is working on it. Business logic. Focus on the Business– Process and Services. Application a. Application b. Application c. Application logic. Source: Service-Oriented Architecture, Thomas Erl.

teige
Download Presentation

Global Justice Reference Architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Global Justice Reference Architecture Why we need it. What it is. Who is working on it.

  2. Business logic Focus on the Business– Process and Services Application a Application b Application c Application logic Source: Service-Oriented Architecture, Thomas Erl

  3. Focus on the Business– Process and Services Business process layer Business-oriented services Services interface layer Application-oriented services Application layer .NET J2EE Legacy Source: Service-Oriented Architecture, Thomas Erl

  4. orchestration service layer business service layer application service layer Focus on the Business– Process and Services Business process layer Services interface layer Application layer .NET J2EE Legacy Source: Service-Oriented Architecture, Thomas Erl

  5. 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.

  6. 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.

  7. 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

  8. Capabilities and Services

  9. Interfaces and Interaction

  10. Service Interaction Profiles

  11. Policies, Contracts, Agreements

  12. Execution Context

  13. Business Processes / Service-Capability Hierarchy

  14. Edge vs. Common Capabilities

  15. Implications • 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.

  16. Status • 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.

  17. Resources • OASIS SOA Reference Model Technical Committee, www.oasis-open.org • Scott Came, scottca@dis.wa.gov • Tom Clarke, tclarke@ncsc.dni.us • Scott Fairholm, sfairholm@ncsc.dni.us • Thomas Erl, Service-Oriented Architecture: concepts, technology and design.

More Related