Category Archives: Physical

P5 – Resource States

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

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 P5 Resource States view describes how Resources change state in response to events and other stimuli.

Background

A P5 view identifies the states a Resource can be, the allowable changes between those states, and the triggers that cause the state changes.

Usage

  • Definition of states, events and state transitions (behavioural modelling).
  • Identification of constraints (input to System Requirements Document).

Representation

Detailed View Description

Key Elements and Their Relationships

p5-hlmm

Meta-Model

The detailed meta-model for P5 can be viewed here

P6 – Resource Sequence

NAF v3: NSV-10c MODAF: SV-10c

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 P6 Resource Sequence view provides a time-ordered examination of the interactions between Resources. These are usually depicted as event-trace diagrams and will have an accompanying description that defines the particular scenario or situation.

Background

P6 products are valuable for moving to the next level of detail from the initial solution design, to help define a sequence of functions and system data interfaces, and to ensure that each participating resource or system port role has the necessary information it needs, at the right time, in order to perform its assigned functionality.

Usage

  • Analysis of resource events impacting operation.
  • Behavioural analysis.
  • Identification of non-functional system requirements (input to System Requirement Document).

Representation

Detailed View Description

Key Elements and Their Relationships

p6-hlmm

Meta-Model

The detailed meta-model for P6 can be viewed here

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

P8 – Resource Constraints

NAF v3: NSV-10a MODAF: SV-10a

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 P8 Resource Constraints view specifies functional and non-functional constraints on the implementation aspects of the architecture (i.e. the structural and behavioural elements of the Resource viewpoint).

Background

The P8 describes constraints on the resources, functions, data and ports that make up the Resource architecture. The constraints are specified in text and may be functional or structural (i.e. non-functional).

Usage

  • Definition of implementation logic.
  • Identification of resource constraints.

Representation

Detailed View Description

Key Elements and Their Relationships

p8-hlmm

Meta-Model

The detailed meta-model for P8 can be viewed here

Pr – Configuration Management

NAF v3: NSV-8 MODAF: SV-8

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 Pr Configuration Management view depicts the whole lifecycle view of a Resource, describing how its configuration changes over time.

Background

The Pr view provides an overview of how a capability configuration structure changes over time. It shows the structure of different versions of Resources (usually Capability Configurations or Service Implementations) mapped against a timeline.

Usage

  • Development of incremental acquisition strategy.
  • Planning technology insertion.

Representation

Detailed View Description

Key Elements and Their Relationships

pr-hlmm

Meta-Model

The detailed meta-model for Pr can be viewed here

L4-P4 Activity to Function Mapping

NAF v3: NSV-5 MODAF: SV-5

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 L4-P4 Function to Operational Activity / Service Function Traceability Matrix provides two alternate views:

This view can also support a Service Oriented approach by allowing service functions as well as Operational Activities.

Background

The L4-P4 view depicts the mapping of functions (and optionally, the resources that provide them) to operational activities or service functions. For operational activities it thus identifies the transformation of an operational need into a purposeful action performed by a system or solution. For service functions it provides the link between the services used at the operational level and the specific functions provided by the resources supporting the services.

During requirements definition, L4-P4 plays a particularly important role in tracing the architectural elements associated with system requirements to those associated with user requirements.

Usage

  • Tracing functional system requirements to user requirements.
  • Tracing solution options to requirements.
  • Identification of overlaps.

Representation

Detailed View Description

Key Elements and Their Relationships

Meta-Model

The detailed meta-model for L4-P4 can be viewed here

P1 – Resource Types

NAF v3: NAV-2, NSV-7,9 MODAF: AV-2, SV-7,9

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 P1 view specifies the types of Resources, Technology and Competences required for the architecture. It can also be used to specify properties of Resources.

Background

The P1 view collects together all the Resource Types in the architecture. It can also be used to identify Technologies and Competences and map these to resource types. Technologies and Competences can also be set against a timeline indicating when they are expected to be in use.

Usage

  • Identifying Resource Taxonomies.
  • Forecasting technology readiness against time.
  • HR trends analysis.
  • Recruitment planning.
  • Planning technology insertion.
  • Input to options analysis.
  • Definition of performance characteristics.
  • Identification of non-functional requirements (input to SRD).

Representation

Detailed View Description

Key Elements and Their Relationships

p1-hlmm

Meta-Model

The detailed meta-model for P1 can be viewed here

P2 – Resource Structure

NAF v3: NSV-1/NOV-4 MODAF: SV-1/OV-4

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

A P2 Resource Structure view addresses the composition and (high-level) interaction of resources.

Background

The P2 links together the operational and systems architecture views by depicting how resources are structured and interact in order to realise the logical architecture specified in an L2 – Logical Scenario. A P2 may represent the realisation of a requirement specified in a L2 (i.e. in a to-be architecture) and so there may be many alternative Resource view suites that could realise the operational requirement. Alternatively, in an as-is architecture, the L2 may simply be a simplified, logical representation of the P2 to allow communication of key information flows to non-technical stakeholders.

A P2 can be used to specify typical (or template) organisation structures, and also identify how human resources interact with each other and with systems.

A P2 can provide a simplified representation of a pathway or network, usually depicted graphically as a connector (i.e. a line with possible amplifying information). The P2 depicts interactions between resources that are of interest to the architect. Note that interactions between systems may be further specified in detail in the P3 – Resource Connectivity view.

Resources may be decomposed in a P2 to any level (i.e. depth) of decomposition that the architect sees fit. A P2 may also identify the physical asset (e.g. platforms) at which resources are deployed and can show the operational nodes that utilise those resources. In many cases, an operational node depicted in a L2 product may well be the logical representation of the resource shown in P2.

Usage

  • Definition of system concepts.
  • Definition of system options.
  • Human – System interactions.
  • Typical Organisation structures.
  • Interface requirements capture.
  • Capability integration planning.
  • System integration management.
  • Operational planning (capability configuration definition).

Representation

Detailed View Description

Key Elements and Their Relationships

p2-hlmm
The data in a P2 can include:

  • Resource Type (all subtypes thereof)
  • Configured Resource Type
  • Resource Type Configuration (whole-part relationship)
  • Resource Interaction (all subtypes thereof)

Resources are assembled as Configured Resource Types – there is one (and only one) Configured Resource Type for each usage of a Resource Type in the structure. This enables components, sub-systems, etc. of the same type but used in different positions to be be individually identified. This is particularly useful for interactions – e.g. being able to identify the connection the left-hand pump as distinct to the connection to the right-hand pump of the same type.

Meta-Model

The detailed meta-model for P2 can be viewed here

P3 – Resource Connectivity

NAF v3: NSV-2/6 MODAF: SV-2/6

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 P3 Systems Connectivity view describes communications networks and pathways that link communications systems, and provides details regarding their configuration.

Background

The networks and pathways documented through these views represent the physical implementation of the information needlines identified in an L2 – Logical Scenario or L3 – Node Interactions view.

The P3 focuses on the physical characteristics of each link by specifying attributes. An example of this might be the geographic location and layout of network components such as routers, switches, amplifiers and repeaters. Attributes such as capacities (eg bandwidth, throughput), frequencies used, security encryption methods used and other descriptive information is usually presented in a corresponding SV-6 product (though most architecture tools would prompt the architect to enter such data as the P3 products are being developed). The P3 covers the SV/NSV-2a,b,c views from previous versions of MODAF/NAF, which define the communications links between systems:

  • SV-2a System Port Specification – defines the ports on each system, and the protocol / hardware stack that is specified or implemented for each of those ports.
  • SV-2b System to System Port Connectivity – defines the connections between individual ports and shows the protocols and hardware spec used for each connection.
  • SV-2c System Connectivity Clusters – defines the bundles of system to system connections that go to make up a connection between the Artefacts that host the connected systems (see SV-1).

Usage

The purpose of P3 is to provide a comprehensive specification of how systems are connected, what interfaces each system exposes (ports), the hardware interface used and the protocols transmitted across the interface. Key elements are repeated from view to view and are also common to the P2 – Resource Connectivity view. These key elements are:

  • Artefacts (represented as Systems and Platforms).
  • Ports.
  • Protocols.
  • System Port connections.

Representation

The elements are shown in different perspectives in the different views. In an P2 the resources (including systems) are logically grouped by the artefact to which they belong (which could mean located with). The P2 view also shows how human operators (‘roles’) interact with systems. In the P3 views, more information is added; in particular, information about the ports on each system and the protocols which each port supports. In addition, the P3 views describe which protocols are supported for specific system-to-system connections. In a P3, the focus is on systems and the capability configurations they are part of.

It is important to understand the differences between P2 and P3 to ensure that the correct detail is captured in each view. In essence, the P3 series expands on the P2 by providing more detail of the physical characteristics of those interactions specified in the SV-1 that are between systems. For example, the P2 interaction perspective shows a single-line representation of interfaces between nodes, whereas the P3 would show a more detailed representation of the communications infrastructure that provides the connections.

The P3 view uses the common term ‘protocol’ as a specialisation of the NAF term ‘standard’ to describe the standards specifically used in interface and communication specifications.

Detailed View Description

Key Elements and Their Relationships

p3-hlmm

Meta-Model

The detailed meta-model for P3 can be viewed here

P4 – Resource Functions

NAF v3: NSV-4 MODAF: SV-4

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 P4 Resource Functions view addresses resource (human and non-human) functions – i.e. the activities performed by Resources.

Background

The primary purposes of the P4 are to:

  • Develop a clear description of the necessary data flows that are input (consumed) by and output (produced) by each resource.
  • Ensure that the functional connectivity is complete (i.e. that a resource’s required inputs are all satisfied).
  • Ensure that the functional decomposition reaches an appropriate level of detail.
  • Provide implementation-specific realisations of the operational activities specified in the L4 – Logical Activities view.

The Functionality Description provides detailed information regarding the:

  • Allocation of functions to resources.
  • Flow of data between functions.

The P4 is the systems view counterpart to the Activity Model (L4) of the operational view.

Usage

  • Description of task workflow.
  • Identification of functional system requirements.
  • Functional decomposition of systems.
  • Relate human and system functions.

Representation

Detailed View Description

Key Elements and Their Relationships

p4-hlmm

Meta-Model

The detailed meta-model for P4 can be viewed here