View DNDAF:SV-4 Systems Functionality Description Subview

dnd.gif

Title

SV-4 Systems Functionality Description   Subview

Version & Date

1.6 See DNDAF Release History

Introduction

The SV-4 subview is part of the DNDAF System View.

The System View-4 (SV-4): Systems Functionality Description is required to represent systems functional hierarchies along with systems functions, and the data flows between them, inside and between the nodes as defined in OV-2 for the architecture project.

Purpose

The primary purposes of the Systems Functionality Description sub-view are to

  • Develop a clear description of the necessary information (data flows) that are required by and output from each system,
  • Ensure that the functional connectivity is complete, i.e., that a system’s required inputs are all satisfied, and
  • Ensure that the functional decomposition is to an appropriate level of detail.

 

Background

The existence of multiple heterogeneous systems within DND/CF makes it very difficult to provide an optimal support and accurate analysis of the current systems functional hierarchies. For that purpose the content of the SV-4 sub-view reveals the current functionalities and assists in planning, documenting and developing new functionalities.

Description

Definition

The Systems Functionality Description documents systems functional hierarchies and systems functions, and the data flows between them. The Systems Functionality Description is a composite view that graphically illustrates “how” (system functions) and “what” (details of Systems Data Exchanges) data elements of an architecture project, should be considered at the designer and builder’s level of detail.

Detailed Description

This product focuses on describing the flow of data among system functions and is the system view counterpart to the OV-5a Operational Activity Model of the OV. The Systems Functionality Description may be represented in a format similar to data flow diagrams. Like the Operational Activity Model, the Systems Functionality Description may be hierarchical in nature and may have both a hierarchy or decomposition model and a flow model. In the case of the Systems Functionality Description, the flow model is the minimum required if the product is used. The scope of this product may be enterprise wide or it may be system specific. Variations may focus on intra-nodal data flow, inter-nodal data flow, data flow without node considerations, and function-to-node allocations.

The system functions documented in the flow model are not limited to internal system functions and can include Human Computer Interface (HCI) functions. The external data sources and/or sinks can be used to represent the human that interacts with the system; and the data flows between the external data source/sink (representing the human) and the HCI function can be used to represent human-system interactions.

...
The hierarchy model documents a functional decomposition. The functions decomposed are system functions.

...

The flow model documents system functions, the flows of data between those functions, the internal system data repositories or data stores, and external sources and sinks for the data flows.
...

Subview DADM Elements

The DADM entities and attributes provided below are the elements that this sub-view is responsible for creating:

 

 

Presentation

  • hierarchy - functional decomposition
  • data flow diagram
  • UML class diagram
  • UML collaboration diagram
  • UML Use Case

Examples

See:

  • p99 Figure 3.17.1 in DND/CF Architecture Framework (DNDAF)  Volume 2: DND/CF Views and Sub-Views

Prerequisites

The SV-1 and OV-5a are the prerequisites for this sub-view:

  • SV-1. Defines the systems under consideration. It sets the scope for this sub-view.
  • OV-5a. Provides business functions that are or will be described and mapped into systems functions.

 

See DNDAF Subview Dependencies

 

Comments

 

Other Frameworks

See also:

References


Category:Framework -> Specification
Category:Framework -> Subview

Categories:

 

© 2010 Eclectica Systems Ltd.