View NAF:NSV-4 System Functionality Description Subview
Overview
The NSV-4 System Functionality Decsription subview is part of the NATO System View.
It is one of the 47 NATO Architecture Framework subviews.
Version & Date
Version 3.0
See NAF Release History.
Purpose
From the NATO Architecture Framework v3, CHAPTER 4, Section 4.7.4
The primary purpose of the System Functionality Description is to:
- Describe systems that are outlined in NSV-1 in more detail, both in terms of structure (functional decomposition of systems) and behaviour (data flows between system components that realize certain system functions).
- Develop a clear description of the necessary system data flows between systems in accordance with NSV-11 data definitions.
- Clearly describe the allocation of system functions to specific systems, system components and/or nodes and thus clearly delineate lines of responsibility.
- Analyze the construction of NSV-1 systems to provide a basis for the determination of the quality requirements for systems (refer to NSV-7) and making decisions about streamlining, combining or omitting system functionality.
- Provide a necessary foundation for depicting system constraints and the sequencing and timing aspect in NSV-10a, NSV-10b, and NSV-10c Systems Event-Trace Description Subview.
Covered by NATO release conditions.
Definition
From the NATO Architecture Framework v3, CHAPTER 4, Section 4.7.4
To delineate a system’s components, the NSV-4 product supports the development of system functional hierarchies and system functions. The intention is to identify components by assigning the sole and exclusive responsibility for a certain systemfunction to a system component. NSV-4 also addresses collaboration between components through describing the system data flows between the system components that realize certain system functions. In effect, this accomplishes a description of larger-grained systems in terms of structure (delineation of systems into functional components through hierarchical decomposition of system functions), and behaviour (data exchanges between the various functional components, and, in effect, also between systems). As a consequence, NSV-4 must be in accordance with other NSV subviews, such as NSV-1 (systems and interfaces), NSV-3 (system dependencies), NSV-6 (system data exchanges), and NSV-11 (data definitions).
Through functional decomposition of NSV-1 systems and addressing collaboration between the components in terms of data exchange, NSV-4, in fact, treats NSV-1 systems as white boxes and thus addresses the construction of an NSV-1 system.
It must be noted that other behavioural aspects, such as sequencing and timing issues are not addressed in NSV-4, but rather in NSV-10. This division between NSV-4 and NSV-10 is analogues to that for operational activities in NOV-5 and NOV-6, respectively. It must also be noted that quality of service requirements are also not addressed in NSV-4, but rather in NSV-7. As a consequence, NSV-4 must be used in conjunction with NSV-7 to fully achieve NSV-4’s purpose.
System functions are not limited to internal system functions and can include Human Computer Interface (HCI) and Graphical User Interface (GUI) functions or functions that address the consumption or production of system data from/to external systems. The external system data sources and/or sinks can be used to represent the human that interacts with the system or external systems. The system data flows between the external system data source/sink (representing the human or system) and the internal system that realizes the HCI, GUI, or interface function can be used to represent human-system interactions, or system-system interfaces. Standards that apply to system functions, such as HCI and GUI standards, are also specified in this product.
Covered by NATO release conditions.
From the NATO Architecture Framework v3, CHAPTER 5, Section 5.2.6.4
The data in an NSV-4 can include:
- Function
- Functional Resource (system, role, capability configuration)
- Data Element
Covered by NATO release conditions.
Comments
Would expect that any standards that apply to an interface should be defined using the NTV-1 rather than rely on colour as suggested.
Functions can only be allocated to the System, Role and Capability Configuration elements. Although some representation of a GUI is possible using Role and Resource Interaction it isn’t possible to characterise the exchanges by attaching Protocol(s) since a Role cannot support a port connection. NAF::System is defined such that it cannot have any human component (always external to the system) - it is defined as a physical artefact so the suspicion is that Capability Configuration is being referred to as a ‘system’.
Other Frameworks
See also:
- DNDAF::SV-4 Systems Functionality Description Subview
- DODAF::SV-4 Systems Functionality Description Model (deprecated in favour of DODAF::SvcV-4 Services Functionality Description Model)
- MODAF::SV-4 Functionality Description View
- TRAK::SV-04 Solution Function View
References
- Section 4.7.4 (page 247 of pdf) of APPENDIX 1 TO ANNEX 1 TO AC/322-D(2007)0048. NATO Architecture Framework Version 3.
- Section 5.2.6.4 (page 413 of pdf) of APPENDIX 1 TO ANNEX 1 TO AC/322-D(2007)0048. NATO Architecture Framework Version 3.
Category:Framework -> View
Category:NAF -> Subview
Category:Solution