Building NSV-12 Service Provision diagrams for NAF 3
While the NAF Service Oriented Views (NSOVs) enable you to model services from an implementation independent view (what a service is to do and how it presents its functionality to consumers), you can use the NSV-12 to specify how a service is to be implemented in an architecture, by mapping the service to the resources that provide it.
Service is related to Resource Type, which is an abstract type instantiated by concrete definitions such as Capability Configuration, Artefact, Organizational Resource, and Software.
You can model the following artifacts on an NSV-12 diagram:
Service
A high-level Service.
Resource Type
A general Resource (keyed by Physical Asset) that should have a one-to-one correspondence to a concrete resource that can be drawn on an NSV-1 diagram. Concrete resources include the following elements: Capability Configuration, Artefact, Software, System Resource, Physical Asset, Platform, Role Type, Organization Type, and Post Type.
Service Level line
Drawn between a Resource Type symbol and a Service symbol, it is 'keyed' to both definitions. You should name the line for the 'deployed service level'. When drawn, you can examine the Service Level definitions in the Explorer (Browser) to quickly see 'deployed' service levels, and see what Resource deploys what Service.
Note The Resource definition does not have a property that lists Services. To see what Resources deploy what Service, you can run a report that captures the information of what Service Level lines connect what Resource to what Service, through the Reporting system or the Explorer diagram.