Architecting and designing : NATO Architecture Framework (NAF) : NAF v3 : Creating Systems View products for NAF 3 : Creating NSV-10 System Activity Sequence and Timing descriptions for NAF 3 : Creating NSV-11 physical data models for NAF 3
  
Creating NSV-11 physical data models for NAF 3
You use the physical data model (PDM) to describe how the information represented in the logical data model is actually implemented in the systems architecture view.
The physical data model shows how the information-exchange requirements are actually implemented. It also shows how both data entities and their relationships are maintained.
There should be a mapping from a given Logical Data Model to the Physical Data Model if both models are used. The form of the Physical Data Model can vary greatly.
1 Determine the required form of the data model, depending on project requirements. Consider the following options for your physical data model:
Create an additional IDEF1X-style diagram
Use Data Definition Language in cases where shared databases are used to integrate systems
For message oriented-implementations, use references to message format standards
The message format standards identify the message types and options that are used.
Use descriptions of file formats when file passing is the mode used to exchange information
Inter-operating systems can use a variety of techniques to exchange data, and therefore have several distinct partitions in their physical data model with each partition using a different form
2 Create the physical data model.
See also
Creating NSV-10 System Activity Sequence and Timing descriptions for NAF 3