Your SlideShare is downloading. ×
  • Like
Transitioning Enterprise Architectures to Service Oriented Architectures
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Transitioning Enterprise Architectures to Service Oriented Architectures

  • 1,268 views
Published

 

Published in Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
  • Fioricet is often prescribed for tension headaches caused by contractions of the muscles in the neck and shoulder area. Buy now from http://www.fioricetsupply.com and make a deal for you.
    Are you sure you want to
    Your message goes here
No Downloads

Views

Total Views
1,268
On SlideShare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
136
Comments
1
Likes
2

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Woody Woods Chief Enterprise Architecture Technologist SI International, Inc. SessionTitle: Transitioning Enterprise Architectures to Service Oriented Architectures
  • 2. Overview
    • What is SOA?
    • Why SOA?
    • Service Definitions
    • Example
    • Wrap-up
  • 3. What is SOA?
    • Service-Oriented Architecture (SOA)
      • A service-oriented architecture is a conceptual description of a the structure of a software system in terms of its components and the services they provide, without regard for the underlying implementation of these components, services and connections between components. [Rational Unified Process]
  • 4. Why SOA?
    • Object-Oriented Analysis and Design
    • Business Process Reengineering
    • Functional Requirements Capture
    • Loosely Coupled
      • Ease of Change
    • Effects Oriented
    • Interfaces with other Enterprises
    • Integrated Schema, Definition and Data
    • Rigorous Analysis
  • 5. Service Definitions
    • NCOW-RM
    • OASIS Reference Model for SOA v 1.0
  • 6. Service (NCOW – RM)
    • A service, in the context of the Reference Model, is:
    • A self-contained, stateless function with a well-defined interface that allows discovery and use of the service
    • A functionality (function or combination of functions) that supports the production, sharing, and consumption (use) of data, information, or other services
    • A functionality that accepts one or more requests and returns one or more responses, independent of the state of other functions or processes
    • An exposed functionality with three properties:
      • The interface contract to the service is platform independent. This means a client from any device using any operating system in any language can use the service, and that knowledge of the technical details of another service is not required to interact to it.
      • The service can be dynamically located and invoked. All applications can appear on the network as a set of services where it is possible to plug all these services into a single information bus. It is irrelevant whether the services are local (within the system) or remote (external to the immediate system), what interconnect scheme or protocol is used, or what infrastructure components are required to make the connection.
      • The service is self-contained; it maintains its own state. Services operate as “black boxes” and external components neither know nor care how they perform their function, just that they return the expected result.
  • 7. Service – OASIS Reference Model for SOA v 1.0
    • A service is a mechanism to enable access to one or more capabilities, where the access is provided using a prescribed interface and is exercised consistent with constraints and policies as specified by the service description. A service is provided by an entity – the service provider – for use by others, but the eventual consumers of the service may not be known to the service provider and may demonstrate uses of the service beyond the scope originally conceived by the provider.
    • A service is accessed by means of a service interface where the interface comprises the specifics of how to access the underlying capabilities. There are no constraints on what constitutes the underlying capability or how access is implemented by the service provider. Thus, the service could carry out its described functionality through one or more automated and/or manual processes that themselves could invoke other available services.
    • A service is opaque in that its implementation is typically hidden from the service consumer except for
      • (1) the information and behavior models exposed through the service interface and
      • (2) the information required by service consumers to determine whether a given service is appropriate for their needs.
  • 8. Defining Operational Activities Establishes the overall objectives of the architecture, its purpose, boundaries, goals, and mission. Documents the consumption and production of the enterprise, the associated roles and interfaces Establishes the scope of the activity and the responsible roles to produce the result of value. Establishes the flow of control as defined by the business rules and provides context for the business services offered by the enterprise. Documents service responsibility among the roles in the environment as defined by the activity diagrams. Documents the information requirements in the form of classes, their attributes, operations and relationships with other classes.
  • 9. Scenario
    • An individual on a surveillance team has noticed a drug deal in progress and notifies police headquarters.
    • Police headquarters notifies the FBI and requests ancillary information.
    • The result is a pinpointed location of a specific drug deal
  • 10. Process
    • Identify Roles
    • Identify Objects
    • Identify Boundary Crossings
    • Identify Potential Services
    • Identify Interfaces
  • 11. Identify Roles
  • 12. Identify Objects (1 of 2) Trigger Result of Value
  • 13. Identify Objects (2 of 2)
  • 14. Identify Initial Actions
  • 15. Complete Action Analysis
  • 16. Sequence Diagram
  • 17. Identify Boundaries
    • Each role is represented as a swim lane on the activity diagram
    • The boundaries are the lines defining each swim lane
    • The term “crossing” a swim lane boundary indicates traversal from the producing swim lane to the consuming swim lane and does not include any that are in between
  • 18. Identify Boundary Crossings
  • 19. Identify Potential Services
  • 20. Post DEA Information Request Service
  • 21. Identify System Interfaces
  • 22. Post DEA Information Interfaces
  • 23. Summary
    • This method provides a road map to transition from Enterprise Architecture to Service Oriented Architecture
      • Identifies Business Services in the context of Business Processes and Rules
      • Identifies Relationships between and among Business Actors (Roles)
      • Develops IT Services from those relationships
      • Realizes those Services with Interfaces that are platform independent
  • 24. Thank You!
    • Woody Woods
    • Chief Enterprise Architecture Technologist
    • SI International, Inc.
    • Contact Information:
    • (719) 235-4525
    • [email_address]