Category Archives: Processes

A4 – Methodology Used


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

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

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

S4 – Service Functions

NAF v3: NSOV-3 MODAF: SOV-5

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 Service Functions View (S4) defines the behaviour of a service in terms of the functions it is expected to perform.

Background

S4 is the key behavioural specification for services. Equivalent in nature to L4 (Logical Activities) and R4 (Resource Functions), it specifies a set of functions that a service implementation is expected to perform.

Usage

Representation

Detailed View Description

s4-example-1

Key Elements and Their Relationships

s4-hlmm

Meta-Model

The detailed meta-model for S4 can be viewed here

L4 – Logical Activities

NAF v3: NOV-5 MODAF: OV-5

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 L4 Operational Activity Model describes the operations that are normally conducted in the course of achieving a mission or a business goal. It describes operational activities (or tasks), Input/Output flows between activities and to/from activities that are outside the scope of the Architecture.

Background

L4 describes the operational processes and activities that are being conducted within the mission or scenario. L4 can be used to:
• Clearly delineate lines of responsibility for activities when coupled with L2 – Logical Scenario.
• Uncover unnecessary Operational Activity redundancy.
• Make decisions about streamlining, combining, or omitting activities.
• Define or flag issues, opportunities, or operational activities and their interactions (information flows among the activities) that need to be scrutinised further.
• Provide a necessary foundation for depicting activity sequencing and timing in L8 – Logical Constraints, L5 – Logical States, and L6 – Logical Sequence.

L4 activity models describe the business processes associated with the architecture, as well as the:
• Relationships or dependencies among the business processes.
• Information exchanged between business processes.
• External interchanges (from/to business processes that are outside the scope of the model).

An operational activity is a logical process, specified independently of how it is carried out. To maintain this independence from implementation, logical nodes in L2 are used to represent the structure which carries out the operational activities. Operational activities are realised as functions (R4) which are the “how” to the Operational Activities’ “what”. That is, they are specified in terms of the resources that carry them out.

Usage

Representation

Detailed View Description

Key Elements and Their Relationships

l4-hlmm

Meta-Model

The detailed meta-model for L4 can be viewed here

C4 – Standard Processes

NAF v3: NCV-6 MODAF: StV-6

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

The C4 specifies standard (e.g. doctrinal) operational activities, and optionally traces them to the capabilities they support.

Concerns Addressed

Background

Some processes are standard across the whole enterprise, or even more than one enterprise. The C4 specifies Standard Operational Activities that can be re-used across multiple logical architectures (e.g. in L4).

Usage

  • Specification of doctrine
  • Tracing capabilities to enduring tasks.
  • Tracing capabilities to standard operational activities
  • Capability audit.

Representation

  • Table.
  • Tracing Diagram.

Detailed View Description

The C4 view specifies the Standard Operational Activities, and the Enduring Tasks and Capabilities they support.

It is created as part of the conceptual Architecture (i.e. before the creation of supporting Logical Views), and will consist of a library of pre-defined activities taken from Doctrine. Consequently, the Operational Activities in the L4 should, therefore, be specialisations of the Standard Operational Activities from the C4.

An C4 is usually shown in the form of a table, optionally listing the supported capabilities and enduring tasks.
c4-example-1

Key Elements and Their Relationships

c4-hlmm
The data in a C4 can include:

  • Standard Activities
  • Capabilities
  • Enduring Tasks
  • Activity Groups

Meta-Mode

The detailed meta-model for C4 can be viewed here