NSV-1 System Interface Description
The NSV-1 metamodel is used to describe resource architectures, artifacts and applications. Resource architectures and artifacts are described using a component structure approach. Resource architectures are composed of physical assets (typed by artifacts), human assets (typed by org-units) and architecture uses (typed by resource architecture). The objects are typed through the Deployed Resource association. Only physical assets and human assets can be localized (linked to Site).
NSV-1 Metamodel for Resource Architectures
NSV-1 Example Including All Kind of Objects in a Resource Architecture
The metamodel that describes artifacts is similar to the resource architecture metamodel. The items included in this metamodel are artifact components (Artifact type) and application host (Application type).
Artifacts are deployed within the context of resource architectures. Their items are deployed in the same manner therefore there are no sites in this metamodel.
NSV-1 Metamodel for Artifact Structure
The example below is of an artifact that contains a sub-artifact (via an Artifact Component) and an application (via an Application Host).
NSV-1 Example Showing an Artifact Assembly Diagram
System Interface
The interfaces between NSV-1 items are described via service and request points. Information is exchanged via interaction-connected service definitions (protocol in HOPEX vocabulary). The NSV-1 metamodel is similar to the NOV-2 metamodel.
In the figure below, the pink highlighted sections indicate the notions used to model interactions.
The NAF Architecture View Type property is set to System to identify system data models.
NSV-1 Metamodel for Interactions
NSV-1 Interaction Example
