You can use the Service-Oriented Views (NSOVs) 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.
High-level Services are modeled on the NSV-3 Service to Resource matrix.
Low-level Services are modeled on diagrams in for the following views:
NSOV-1 Service Taxonomy
You use the Service Taxonomy View (NSOV-1) to specify a hierarchy of services. You can model the taxonomy of your services using the NSOV-1 Service Taxonomy diagram.
NSOV-2 Service Interface Specification
In the Service Interface Specification View (NSOV-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 NSOV-2 using the NSOV-2 Service Interface Specification diagram.
NCV-7 Capability to Service Mapping
The NCV-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 NCV-7 Capability to Service Mapping matrix.
NSOV-4a Service Constraints
The NSOV-4a Service Constraints specifies constraints that are placed on a Service. You can add constraints as an attribute of a «Service» class.
NSOV-4b Service State Model
In the Service State Model View (NSOV-4b), you specify the possible states a service may have, and the possible transitions between those states. You can model the NSOV-4b using the NSOV-4b Service State Model diagram.
NSOV-4c Service Interaction Specification
In the Service Interaction Specification View (NSOV-4c), you specify how a service interacts with external agents, and the sequence and dependencies of those interactions. You can model the NSOV-4c using the NSOV-4c Service Interaction Specification diagram, which is a type of sequence diagram.
NSOV-5 Service Functionality
The NSOV-5 is used to model the required functionality that an implementation of a service is expected to have. You can model the NSOV-5 using the -5 Service Functionality diagram, which is a type of activity diagram.