Session Control
Note
Insert the user-provided I/O diagram here after the Visio source and image are available.
System Role
UUID: 902664D2-B91E-4A01-8911-A7A12C89657B
Summary: The Host PC session-control system shall establish readiness, start acquisition, make accepted processed data available for inspection, stop or pause according to the approved policy, retain eligible data, and disconnect while presenting the current session state.
System Objectives
UUID: FB55B99E-7AA5-4582-A2C5-8824EF9D8B32
Objective 1: Connection readiness. Session Control shall establish a Ready connection before enabling acquisition actions.
Rationale: Requiring Ready prevents acquisition requests from being issued before the device-control path is usable.
Objective 2: Active session. Session Control shall start an acquisition session, present its current state, and make accepted processed records available for inspection.
Rationale: A visible active-session boundary ties displayed measurements to the acquisition that produced them.
Objective 3: Session termination. Session Control shall stop or pause acquisition, retain the resulting session data, expose connection loss and unavailable actions, and disconnect without representing an interrupted session as complete.
Rationale: Explicit termination handling preserves partial data while preventing an interrupted session from receiving a false successful disposition.
System Relationship
UUID: D8B9BB75-D5C6-4EFD-8D3B-D1668C6BEFB4
Documentation |
Responsibility |
|---|---|
Action, connection-status, acquisition-status, and processed-readiness boundaries. |
|
Operator workflow, conditions, and session states. |
|
Invalid-action, connection-loss, and partial-session conditions. |
|
Requirements-based session-control behavior tests. |
|
Absence of a numeric workflow calculation and open policy requirements. |
|
Local behavior claim, traceability state, and validation method. |
Integration Boundary
UUID: 1F508F0C-776A-4183-82DC-FAB83BED83DE
Summary: The Host PC session-control system consumes connection and
acquisition state from Device Control And Acquisition Coordination and
processed-data readiness from the Primary Data Pipeline, and it supplies
session context to Visualization and Export Initiation And Session Retention.
Low-level device commands remain outside this system. Session identity, pause
semantics, resume behavior, disconnect recovery, and the setup-time criterion
remain Not In Docs.