Presentation is loading. Please wait.

Presentation is loading. Please wait.

By Rajat Goyal. SOA SoaML Components Service Contracts, Service Architecture and Capability Models Product Comparisons (Sparx EA - RSA – Visio)

Similar presentations


Presentation on theme: "By Rajat Goyal. SOA SoaML Components Service Contracts, Service Architecture and Capability Models Product Comparisons (Sparx EA - RSA – Visio)"— Presentation transcript:

1 By Rajat Goyal

2 SOA SoaML Components Service Contracts, Service Architecture and Capability Models Product Comparisons (Sparx EA - RSA – Visio)

3

4 SOA is an architectural paradigm for defining how people, organizations, and systems provide and use services to achieve results.

5

6 SoaML provides a standard way to architect and model SOA solutions using the Unified Modeling Language® (UML®). Developed and maintained by OMG The SoaML profile uses the built-in extension mechanisms of MOF and UML to define SOA concepts in terms of existing UML concepts.

7 SoaML can leverage Model Driven Architecture® (MDA®) to help Map business and systems architectures Chart technologies that support business automation SoaML supports both Top down and bottom- up development for SOA

8

9 Service Interface Participant Port Service Request Service Channel Message Type Exposure

10 Service Interface Participant Port Service Request Service Channel Message Type Exposure

11 A ServiceInterface is a UML Class and defines specific roles each participant plays in the service interaction

12 Name of the service Service interactions through realized interfaces A detailed specification describing Capabilities and Obligations Preconditions Post conditions Inputs and outputs Exceptions that might be raised Protocol or rules for using the service Provider instructions for implementing the service Success criteria

13 Service Interface Participant Port Service Request Service Channel Message Type Exposure

14 Participants represent software components, organizations, systems, or individuals that provide and use services.

15 A participant can be a Service Provider or a Consumer, which represents roles that a Participant plays in a relationship. Internally a participant may specify a behaviour, a business process, or a more granular service contract as a Participant Architecture. Participants interact in 3 ways – Method invocation Event Handling Delegation

16

17 Service Interface Participant Port Service Request Service Channel Message Type Exposure

18 Participants have ports! Port is an interaction point where services are provided and consumed. Port can have a Provider or a Request interface on it. The type of port determines the activity that it performs.

19

20 Service Interface Participant Port Service Request Service Channel Message Type Exposure

21 Communication path between a request and a provider within an architecture. A Request is compatible with, and may be connected to a Service through a ServiceChannel if: The Request and Service have the same type, either an Interface or ServiceInterface. The type of the Service is a specialization or realization of the type of the Request.

22

23 Service Interface Participant Port Service Request Service Channel Message Type Exposure

24 A MessageType is service data object that represents information exchanged between participant requests and services.

25 Information in a message type is Data passed in Input or output or exception of operation Data in an Event Signal A MessageType is in the domain or service- specific content.

26 Service Interface Participant Port Service Request Service Channel Message Type Exposure

27 Expose dependency is a relationship between a Service Interface and a Capability it exposes or that provides it. The source of the Expose is the ServiceInterface, the target is the exposed Capability

28 A Capability represents something a Participant needs or has to have in order to achieve its goals Capabilities specify a cohesive set of functions that a participant might offer

29 Specify behaviour via ServiceInterfaces and are realized by participants

30 The services architecture is an extremely high-level view of how services work together for a purpose. A ServicesArchitecture is a network of participating roles providing and consuming services to fulfil a purpose. The services architecture may also have a business process / sequence, to define the tasks and orchestration for the architecture.

31 SAs are represented using UML Collaboration

32 SA of a participant – drill down one level

33 A ServiceContract defines the terms, conditions, interfaces, and choreography that interacting participants must agree to for the service to be enacted;

34 Both participants utilise the same port

35

36 RSA is eclipse based modelling platform and uses UML2 RSA does not support SysML Richer support for SoaML Both support model to model-to-model transformation Both support round-tripping EMF / UML2 provides a higher degree of UML conformance than EA's database-based data model.

37 Visio stensil for UML (has non confirming UML constructs) for SoaML. Validations for BPMN modelling is weak and portability is limited Limited support for SCM (enterprise version supports sharing through sharepoint) No support for Simulation

38 Windows native. External support available on other platforms?? Limited Governance Few SCM tools supported (generally enough for most organizations)

39

40


Download ppt "By Rajat Goyal. SOA SoaML Components Service Contracts, Service Architecture and Capability Models Product Comparisons (Sparx EA - RSA – Visio)"

Similar presentations


Ads by Google