View NAF:NSV-11b Physical Data Model Subview

NATO_logo.gif

Overview

The NSV-11b Physical Data Model subview is part of the NATO System View and one of the 47 NATO Architecture Framework subviews. It is 1 of the 2 subviews within the NSV-11 System Data Model Subview.

Version & Date

Version 3.0

See NAF Release History.

Purpose

From the NATO Architecture Framework v3, CHAPTER 4, Section 4.7.10.2

Physical data models allow analysis of a system’s data implementation aspect, with consideration for a specific product.

Other purposes can be found in:
• Providing as much detail as possible on data elements exchanged between systems, thus reducing the risk of interoperability problems.
• Providing data structures for use in the system design process, if necessary.
• Providing a common dictionary of data implementation elements (e.g. tables and records in a relational database schema) to consistently express subviews wherever physical-level data elements are included in the descriptions.

Covered by NATO release conditions.

Definition

From the NATO Architecture Framework v3, CHAPTER 4, Section 4.7.11.2

The physical data model specifies how the logical data model will be instantiated in a particular product. The most predominant of such products are the relational database management systems, such as supplied by Oracle and Microsoft (in which case the physical data model is often called a ‘database schema’). Object repository products also exist, but are less often encountered. In addition, this subview may employ other technology mechanisms, such as flat files.

The essential elements of a physical data model (in the case of a relational database) are: tables, records and keys. In a true object-oriented data model, all data elements are expressed as objects; whether they are classes, instances, attributes, relationships, or events.

Covered by NATO release conditions.


From the NATO Architecture Framework v3, CHAPTER 5, Section 5.2.6.11

While the mapping between the logical and physical data models is relatively straightforward, the relationship between the components of each model (e.g. entity types in the logical model versus relational tables in the physical model) is frequently one-to-many or many-to-many.

The data in an NSV-11b can include:
• System Data Entity


Covered by NATO release conditions.

Comments

 

Other Frameworks

See also:
• MODAF SV-11 Physical Schema View

References

•  Section 4.7.11.1 (page 261 of pdf) of APPENDIX 1 TO ANNEX 1 TO AC/322-D(2007)0048. NATO Architecture Framework Version 3.
•  Section 5.2.6.11 (page 418 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

Categories:

 

© 2010 Eclectica Systems Ltd.