Category Archives: Information

A7 – Architecture Meta-Data

NAF v3: NAV-1/3 MODAF: AV-1

TaxonomyStructureConnectivityProcessesStatesSequencesInformationConstraintsRoadmap
Architecture
Meta-Data
A1
Meta-Data Definitions
NAV-3
AV-1/2
A2
Architecture Products
A3
Architecture Correspondence
ISO42010
A4
Methodology Used
NAF Ch2
A5
Architecture Status
NAV-1
AV-1
A6
Architecture Versions
NAV-1
AV-1
A7
Architecture Meta-Data
NAV-1/3
AV-1
A8
Standards
NTV-1/2
TV-1/2
Ar
Architecture Roadmap

Background

Usage

Representation

Detailed View Description

Key Elements and Their Relationships

Meta-Model

P7 – Physical Data Model

NAF v3: NSV-11b MODAF: SV-11

TaxonomyStructureConnectivityProcessesStatesSequencesInformationConstraintsRoadmap
L4-P4 (NSV-5)
Physical
Resource
Specifications
P1
Resource Types
NAV-2, NSV-2a,7,9,12
AV-2, SV-2a,7,9,12
P2
Resource Structure
NOV-4,NSV-1
OV-4, SV-1
P3
Resource Connectivity
NSV-2, NSV-6
SV-2, SV-6
P4
Resource Functions
NSV-4
SV-4
P5
Resource States
NSV-10b
SV-10b
P6
Resource Sequence
NSV-10c
SV-10c
P7
Physical Data Model
NSV-11b
SV-11
P8
Resource Constraints
NSV-10a
SV-10a
Pr
Configuration Management
NSV-8
SV-8

The P7 Physical Data Model view defines the structure of data used by the Resources in the architecture.

Background

The P7 is one of the architectural products closest to actual system design in the framework. It is used to describe how the information represented in the L7 Logical Data Model is implemented.

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

Usage

Representation

Detailed View Description

Key Elements and Their Relationships

p7-hlmm

Meta-Model

The detailed meta-model for P7 can be viewed here

S7 – Service Interface Parameters

NAF v3: NSOV-2 MODAF: SOV-2

TaxonomyStructureConnectivityProcessesStatesSequencesInformationConstraintsRoadmap
C1-S1 (NSOV-3)
Service
Specifications
S1
Service Taxonomy
NAV-2, NSOV-1
AV-2, SOV-1
S3
Service Interfaces
NSOV-2
SOV-2
S4
Service Functions
NSOV-3
SOV-5
S5
Service States
NSOV-4b
SOV-4b
S6
Service Interactions
NSOV-4c
SOV-4c
S7
Service I/F Parameters
NSOV-2
SOV-2
S8
Service Policy
NSOV-4a
SOV-4a
Sr
Service Roadmap

The S7 identifies all the parameters used in Service Interfaces (see also S3).

Background

Usage

Representation

Detailed View Description

s7-example-1

Key Elements and Their Relationships

s7-hlmm

Meta-Model

The detailed meta-model for S7 can be viewed here

L7 – Logical Data Model

NAF v3: NOV-7 MODAF: OV-7

TaxonomyStructureConnectivityProcessesStatesSequencesInformationConstraintsRoadmap
Logical
Specifications
L1
Node Types
NAV-2
AV-2
L2
Logical Scenario
NOV-2
OV-2
L3
Node Interactions
NOV-2, NOV-3
OV-2,OV-3
L4
Logical Activities
NOV-5
OV-5
L5
Logical States
NOV-6b
OV-6b
L6
Logical Sequence
NOV-6c
OV-6c
L7
Logical Data Model
NSV-11a
OV-7
L8
Logical Constraints
NOV-6a
OV-6a
Lr
Lines of Development
NPV-2
AcV-2

The L7 Logical Data Model view addresses the information perspective on an operational architecture.

Background

The L7 is used to document the business information requirements and structural business process rules of the architecture. It describes the information that is associated with the information exchanges of the architecture. Included are information items, their attributes or characteristics, and their inter-relationships.

Usage

• Information architecture.
• Information product hierarchy.

Representation

Detailed View Description

Key Elements and Their Relationships

l7-hlmm

Meta-Model

The detailed meta-model for L7 can be viewed here

C7 – Performance Parameters

NAF v3: NCV-1 MODAF: StV-1

TaxonomyStructureConnectivityProcessesStatesSequencesInformationConstraintsRoadmap
ConceptsC1
Capability Taxonomy
NAV-2, NCV-2
AV-2, StV-2
C2
Enterprise Vision
NCV-1
StV-1
C3
Capability Dependencies
NCV-4
StV-4
C4
Standard Processes
NCV-6
StV-6
C5
Effects
C7
Performance Parameters
NCV-1
StV-1
C8
Planning Assumptions
Cr
Capability Roadmap
NCV-3
StV-3

C7 lists the measures of effectiveness and the Capabilities they are applicable to.

Concerns Addressed

Background

The capability requirements (and existing capabilities) are often expressed in terms of measures of effectiveness (MoE). These are high-level metrics used to judge the level of capability. A C7 view lists the MoEs against the capabilities they are applicable to.

Usage

  • Setting Capability Requirements
  • Military Estimates
  • Strategic Reviews
  • Planning Assumptions

Representation

  • Table (capabilities on one axis, measure categories on the other)
  • UML Classes with property definitions

Detailed View Description

C7 is presents measure categories that can be used to judge level of capability. It traces measure categories to the capabilities for which they are relevant.

c7-example-1

Note C7 does not present any values for measures of effectiveness, it simply specifies what types of measure apply to each Capability.

Key Elements and Their Relationships

c7-hlmm

  • Capability
  • Measure Category

Meta-Model

The detailed meta-model for C7 can be viewed here