Date: Thu, 28 Mar 2024 14:25:27 +0100 (CET) Message-ID: <635276692.404.1711632327256@nm-docs> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_403_476732074.1711632327255" ------=_Part_403_476732074.1711632327255 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Description
System interface description (NSV-1) addresses the composition and inter= action of resources. For NMM, NSV-1 incorporates the human elements Po= sts, Organizations, and Roles.
A resource interaction is a simplified representation of a pathway or ne= twork, usually depicted graphically as a connector (for example, a lin= e with possible amplifying information).
In addition, the Capability Configuration concept is used as a wrapper t= o bring together resources to satisfy a Capability.
Implementation
NSV-1 can be represented using:
Sample
Related views
An NSV-1 can optionally be adorned with nodes originally specified in an= NOV-2. In this way, traceability can be established from the logical = NOV structure to the physical NSV structure.
An interaction, as depicted in the NSV-1, is an indicator that informati= on passes from one resource to another. In the case of systems, this c= an be expanded into further detail in an NSV-2. Resource Interactions are s= ummarized in a Resource Interactions Matrix (NSV-3).
The functions performed by the resources are specified in an NSV-4 Resou= rce Functionality Description, but may optionally be overlaid on the R= esources in the NSV-1.
An Operational View (NOV) suite may specify a set of requirements =E2=80= =93 either as a specific operational plan, or a scenario for procureme= nt. As NOV-2 and NOV-5 specify the logical structure and behavior, NSV-1 an= d NSV-4 specify the physical structure and behavior (to the level of d= etail required by the architectural stakeholders).