You can model two types of services: high-level and low-level services.
In System Architect, you use different methods to model the different service levels:
▪High-level Services are modeled using the Service definition
▪Low-level Services are modeled using a Class definition with the «Service» stereotype
Service definition
Service Type
You can specify whether the Service is an external service or a standard internal service.
Capabilities
You can relate the high-level Services to Capabilities. In the MODAF tab of the Service definition, note that there is a property called Capabilities, in which you can specify the Capabilities that the Service contribute to the achievement of. This is part of the NSOV-3 view.
Service details
Related Low-Level Service
In this property, you can specify an indirection relationship between a high-level Service and a low-level Service, which is a Class definition of stereotype <<Service>>. Such classes must be created first, and dragged into the property via the list box opened by clicking the Choices button.
High-level Services are modeled on the following matrix:
▪SV-3 Service to Resource matrix
Low-level Services are modeled on the following diagrams:
▪NSOV-1 Service Taxonomy diagram
▪NSOV-2 Service Interface Specification diagram
▪NSOV-4a Service Constraints
▪NSOV-4b Service State Model
▪NSOV-4c Service Interaction Specification diagram
▪NSOV-5 Service Functionality diagram
Service Interfaces
Provided and Required Service Interfaces: You can optionally specify that the Service provides or requires Service Interfaces, rather than linking to other Services.
Viewpoint
You can specify that a Service is part of the Strategic View, Operational View, or System View.
Class definition stereotyped «Service»
You model Services as classes of stereotype «Service» on NSOV-1 Service Taxonomy and NSOV-2 Service Interface Specification diagrams.