You can use the Service-Oriented Views (SOVs) to specify services that are to be used in a Service-Oriented Architecture (SOA). The views focus on the requirements services fulfil by describing the specification of these services, how services are orchestrated together for a purpose, the capabilities that services deliver and how services are implemented.
The Service-Oriented View provides these views:
SOV-1 Service Taxonomy
You use the Service Taxonomy View (SOV-1) to specify a hierarchy of services. You can model the taxonomy of your services using the SOV-1 Service Taxonomy diagram.
SOV-2 Service Interface Specification
In the Service Interface Specification View (SOV-2), you specify the interfaces presented by a service to consumers. You also specify how the service uses interfaces exposed by other services. You can model the SOV-2 using the SOV-2 Service Interface Specification diagram.
SOV-3 Capability to Service Mapping
The SOV-3 Capability to Service Mapping specifies what Services contribute to the achievement of a Capability. You can relate the high-level Services to Capabilities using the SOV-3 Capability to Service Mapping matrix.
SOV-4a Service Constraints
The SOV-4a Service Constraints specifies constraints that are placed on a Service. You can add constraints as an attribute of a «Service» class.
SOV-4b Service State Model
In the Service State Model View (SOV-4b), you specify the possible states a service may have, and the possible transitions between those states. You can model the SOV-4b using the SOV-4b Service State Model diagram.
SOV-4c Service Interaction Specification
In the Service Interaction Specification View (SOV-4c), you specify how a service interacts with external agents, and the sequence and dependencies of those interactions. You can model the SOV-4c using the SOV-4c Service Interaction Specification diagram, which is a type of sequence diagram.
SOV-5 Service Functionality
The SOV-5 is used to model the required functionality that an implementation of a service is expected to have. You can model the SOV-5 using the Service Functionality diagram, which is a type of activity diagram.