Category Archives: Connectivity

A3 – Architecure Correspondence

From ISO42010

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

The A3 Architecture Correspondence view identifies the relationships between architectural elements.

Background

ISO42010 introduces the idea of architecture correspondence and correspondence rules. Quoting from ISO/IEC42010; “A correspondence defines a relation between AD elements. Correspondences are used to express architecture relations of interest within an architecture description (or between architecture descriptions). Correspondences can be governed by correspondence rules. Correspondence rules are used to enforce relations within an architecture description (or between architecture descriptions).”

NAF has a number of relationships, used throughout the framework. Rather than identify each relationship here, those relationships are shown in each meta-model excerpt for each view. Each view shows “Key Elements and Their Relationships” and “Meta-Model Excerpt“. In the meta-model excerpt, relationships are depicted as boxes with thin borders.

Usage

Representation

Detailed View Description

Key Elements and Their Relationships

Meta-Model

a3-meta-model

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

C1-S1 Capability to Service Mapping

NAF v3: NSOV-3 MODAF: SOV-3

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 Capability to Service Mapping View (C1-S1) depicts which services contribute to the achievement of a capability.

Background

If network enabled capability is to be delivered by the orchestration of loosely couple services (i.e. a service-oriented architecture), it is important to know which services have the potential to support particular capabilities. An C1-S1 presents a simple mapping of services to capabilities, showing which services contribute to which capability.

Usage

Representation

c1s1-example-1

Detailed View Description

Key Elements and Their Relationships

Meta-Model

The detailed meta-model for C1-S1 can be viewed here

S3 – Service Interfaces

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 purpose of the S3 is to define the interfaces presented by a service. A service presents one or more interfaces to consumers (a “consumer” being any agent capable of using the service – a person, an organisation, a system or another service). In this case, the architect specifies provided interfaces. A service may also be capable of using interfaces exposed by other services, and the architect may specify these as used interfaces.

Background

Specifying the interfaces that a service provides and uses defines which services are compatible with which other services. If Service A provides an interface, X and Service B can use Interface X then Service B can call upon at least some of the functionality of Service A.

Usage

Representation

Detailed View Description

s3-example-1

Key Elements and Their Relationships

s2-hlmm

Meta-Model

The detailed meta-model for S3 can be viewed here

L3 – Node Interactions

NAF v3: NOV-2/3 MODAF: OV-2/3

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 L3 Node Interactions view addresses operational information exchanges between nodes.

Background

Information exchanges provide further detail of the interoperability requirements associated with the operational capability of interest. The focus is on information exchanges that cross the capability boundary.

Although the primary purpose of this view is to specify information exchanges, an L3 may also list flows of materiel, energy and human resources.

Usage

• Definition of operational concepts.
• Elaboration of capability requirements.
• Definition of collaboration needs.
• Associating capability with a location.
• Problem space definition.
• Operational planning.
• Supply chain analysis.
• Security models – e.g. domain-based security & entity trust models

Security Usage

Representation

Detailed View Description

Key Elements and Their Relationships

l3-hlmm

Meta-Model

The detailed meta-model for L3 can be viewed here