NSOV-1 Service Taxonomy
The Service Taxonomy subview is designed to organize knowledge according to the service perspective, and to facilitate the harmonization of services across several domains (or several architectures).
A taxonomy is basically a system of classification. Its general purpose is for organizing one's knowledge of something into categories of similar things, in order to understand something better through comparison with other similar things. In the Service-Oriented View, the service taxonomy represents the operational domain's knowledge, as described in the Operational View, in terms of services, structured in some useful way. The definitions of the services are defined in NSOV-2.
With HOPEX NAF, you can create services with categories.
You can also create structure and tree diagrams to decompose and represent the hierarchy of these services. Service points and service components can then be added to the diagrams.
Services can be created from the "Root Services" and "All Services" folder of the NSOV-1 Service Taxonomy folder.
Creating a service
To create a service:
1. Right click the Service folder concerned and select New > Business Service.
2. Name the Service and specify the category to which it belongs. You have the choice between:
"Application"
"Information"
"Operational".
*In this sub-view you need to select "operational".
3. Click OK.
The new service appears in the folder of the Service from which it was created as well as in the folder that corresponds to the specified category.
*All business services are also placed in the All Services folder.
If no category has been specified for the service, it will be placed in the Undefined folder.
Creating a business service structure diagram
To facilitate the description process, a service can be decomposed into sub-parts which are assembled together in an interaction system. The different service layers can be graphically described in diagrams.
To do so, you can create the business Service Structure Diagram or the Business Service Tree Diagram and add the different service points required as well as the Business service Compositions.
 
*The modeling principles are similar to those used for the operational view and service points are used to express the service exchange protocols to be fulfilled in order to benefit from the service.