Handoff to downstream engineering

Edit online

You can refine system engineering data for downstream teams by organizing it into separate models. You can also collaborate with engineering teams to design a deployment architecture for each subsystem, and allocate the refined data accordingly, ensuring it is in a usable format for effective implementation and integration.

Consider the following information for the purpose of the handoff to downstream engineering:
  • Refine the system engineering data to a form usable by downstream engineers.
  • Create separate models to hold the prepared engineering data in a convenient organizational format.
  • For each subsystem, work with downstream engineering teams to create a deployment architecture and allocate system engineering data into that architecture.

Logical Handoff operation (subsystem to system)

Logical Handoff operation is available in the contextual menu of a selected logical subsystem part. It creates a separate project of the standard harmony structure, where the selected subsystem becomes the main system.

Based on the interfaces of the selected subsystem and its behavior, the content of the new project is populated with the following elements:
  • Four top-level packages that represent the main steps of Harmony process:
    • 1_RequirementsAnalysisPkg
    • 2_FunctionalAnalysisPkg
    • 3_LogicalArchitecturePkg
    • 4_PhysicalArchirecture
  • Use cases named <use-case-name> for the <selected-subsystem-name>
  • System actors that include the system actors that interact with the subsystem and other subsystems that interact with the subsystem become system actors.
  • Bindings of use cases and system actors.
  • use case view, which is populated with the related use cases and system actors.
  • system context view, which is populated with the related system actor parts and interfaces to the system.
  • 2_FunctionalAnalysisPkg includes the following items:
    • Use cases and system actors as in 1_Requirement.
    • Use case behavior, which is the subset of the original use case action flow view associated with the subsystem.
    • Port definitions that are used in the subsystems' ports.
    • Item definitions that are used in the selected port definitions.
    • Ports of the system part and system actors.
    • Interfaces between system actors and the system part.
    • system context view populated with the related system actor parts and interfaces to the system.
  • 3_LogicalArchitecturePkg includes the following:
    • System part <subsystem-name>_logicalSystem
    • Subsystem behavior state transition view

Requirement tracing in subsystems

Subsystem handoff projects include only those requirements that are traced to the selected subsystem from the parent system model. The relevant system and stakeholder requirements are only included. You can define trace relationships by using custom, trace and satisfy links from the Harmony library. All external subsystems are automatically modeled as system actors. The use cases that apply to the subsystem are also traced directly to the corresponding requirements. These requirements are further linked by using Satisfied By relationships to specific functions, actions, and inputs, providing full traceability from high-level requirements to implementable model elements.