L4 — Logical Activities

Purpose & Usage

The L4 Viewpoint is concerned with the identification of Logical Activities, grouping and composition of these Activities and logical flows between the Activities.

• Description of business processes and workflows.
• Operational Planning.
• Concept of Operations.
• Service Orchestration.
• Requirements capture, derivation and traceability
• Logistics support analysis.
• Information flow analysis.
• Support task analysis to determine training needs.
• Mission Threads.

Scope

• Shall contain Operational Control Flows between Operational Activities.
• Shall contain Nodes (or Roles that they hold) that perform Operational Activities.
• May show Logical Events that trigger and can be triggered by Operational Activities.
• May show Operational Flows between Operational Activities.
• May show Logical Passive Resources to Operational Activities and Operational Flows.
• May show the Capabilities the Operational Activities support.
• May trace Physical Active Resources to the Operational Activity.
• May trace Services to the Operational Activity.

Representation

• Hierarchy chart.
• Activity diagram.
• Process diagram.
• Collaboration Diagram. 134

Cut-out (Meta-model)

flowchart TB
    Node:::activity
    Role:::activity
    Capability:::naf
    OA["Operational Activity"]:::activity
    LogicalEvent["Logical Event"]:::activity
    LPR["Logical Passive Resource"]:::activity
    OpFlow["Operational Flow"]:::activity
    Service:::service
    PAR["Physical Active Resource"]:::config
    Node -->|"holds"| Role
    Node -->|"performs"| OA
    Role -->|"performs"| OA
    OA -->|"supports"| Capability
    OA -->|"aggregates"| OA
    OA -->|"operational control flow"| OA
    OA -->|"acts upon"| LPR
    LogicalEvent -->|"triggers"| OA
    OA -->|"triggers"| LogicalEvent
    OpFlow -->|"is equal to"| OA
    OpFlow -->|"conveys"| LPR
    Service -->|"relates to"| OA
    PAR -->|"enables"| OA
    classDef naf fill:#C5E0B4,stroke:#385723,color:#000
    classDef service fill:#E5C1E5,stroke:#7B4F7B,color:#000
    classDef activity fill:#9DC3E6,stroke:#1F4E79,color:#000
    classDef config fill:#F4B084,stroke:#833C0C,color:#000

NAFv4 Compliant Example

flowchart LR
    Vessel["«Node» Vessel in distress"]:::activity
    RCC["«Node» Regional Coordination Center"]:::activity
    SAC["«Role» SAR Asset Controller"]:::activity
    Waterborne["«Node» Waterborne Rescue"]:::activity
    Reports["«OA» Reports Problem"]:::activity
    Log["«OA» Log Distress"]:::activity
    Assess["«OA» Assess Situation"]:::activity
    Deploy["«OA» Deploy Assets"]:::activity
    Respond["«OA» Respond to Situation"]:::activity
    Vessel -- performs --> Reports
    RCC -- performs --> Log
    RCC -- performs --> Assess
    RCC -- holds --> SAC
    SAC -- performs --> Deploy
    Waterborne -- performs --> Respond
    Reports -- Operational Control Flow --> Log
    Log -- Operational Control Flow --> Assess
    Assess -- Operational Control Flow --> Deploy
    Deploy -- Operational Control Flow --> Respond
    classDef activity fill:#9DC3E6,stroke:#1F4E79,color:#000

Notes on the Example

This would typically be represented as Process diagram with swim lanes.