Category Archives: Sequences

A6 – Architecture Versions

NAF v3: NAV-1 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

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

S6 – Service Interactions

NAF v3: NSOV-4c MODAF: SOV-4c

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 purpose of the Service Interactions View (S6) is to specify how a service interacts with external agents, and the sequence and dependencies of those interactions.

Background

An S6 product does not specify the sequencing of an orchestrated set of services (see L6 – Logical Sequence). Its purpose is to specify the general sequence of interactions that are possible for a given service.

Usage

Representation

Detailed View Description

s6-example-1

Key Elements and Their Relationships

s6-hlmm

Meta-Model

The detailed meta-model for S6 can be viewed here

L6 – Logical Sequence

NAF v3: NOV-6c MODAF: OV-6c

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 L6 Logical Sequence view provides a time-ordered examination of the exchanges between participating Operational Nodes as a result of a particular scenario. Each event-trace diagram will have an accompanying description that defines the particular scenario or situation.

Background

Operational Event-Trace Descriptions, sometimes called sequence diagrams, event scenarios or timing diagrams, allow the tracing of interactions between nodes in a scenario or critical sequence of events. The node interactions may correspond to flows of information, energy, materiel or people specified in the L2 – Logical Scenario. The L6 can be used by itself or in conjunction with an L5 – Logical States to describe the dynamic behaviour of nodes. The diagram below shows the components of an L6. The items across the top of the diagram are operational nodes.
Each node has a vertical timeline associated with it. Specific points in time can be labelled running down the left-hand side of the diagram. Directed lines between the node time lines represent interactions (e.g. information exchanges) between nodes, and the points at which they intersect the timelines represent the times at which the nodes become aware of the events.

Usage

• Analysis of operational events.
• Sequences of interactions between nodes
• Behavioural analysis.
• Identification of non-functional user requirements (input to URD).
• Operational test scenarios.

Representation

Detailed View Description

Key Elements and Their Relationships

l6-hlmm

Meta-Model

The detailed meta-model for L6 can be viewed here