The systems architecture view shows how multiple systems link and interoperate in a domain, and describes the internal construction and operations of systems in the architecture.
For an individual system, the systems architecture view includes the physical connection, location, and identification of key nodes, including materiel item nodes, circuits, networks, and war fighting platforms. This view also specifies system and component performance parameters, such as mean time between failure, maintainability, and availability. The systems architecture view associates physical resources and their performance attributes to the operational view and its requirements according to standards that are defined in the technical architecture.
The following standards apply to the systems architecture:
▪Facilitate operational tasks and activities through the application of physical resources
▪Map systems with their associated platforms, functions, and characteristics to the operational architecture
▪Identify system interfaces and define the connectivity between systems
▪Define system constraints and the bounds of system performance behavior
▪Are technology-dependent, show how multiple systems in a subject area link and interoperate, and describe the internal components of particular systems
▪Can support multiple organizations and missions
▪Should clearly identify the time phase covered
▪Are based on and constrained by technical architectures
NSV-11 physical data models
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 depending on your project requirements. Consider the following options when creating 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
▪Interoperating 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