System Analysis: S/S Power-Cycle

[chgio]

Existing diagrams to extend:

• [MCB] System Capabilities
• [CSA] System Actors
• [SFBD] Root System Function Breakdown
• [SAB] System Architecture

New diagrams to create:

• [ES] Subsystem Power-Cycle Scenario:
  • placeholder for other subsystem failure + failure identification
  • failure characterisation as solvable by full subsystem power-cycle only
  • tackled by power-cycle signal GPIO -> PWR_EN line
• (Optional) [SDFB] Functional Dataflow View of Subsystem Power-Cycle
• (Optional) [SAB] System Architecture View of Subsystem Power-Cycle

Next steps:
when closing this issue, make a new issue out of the checkbox below:

• Logical Architecture: S/S Power-Cycle #48

[chgio]

just model a placeholder function for other subsystem failure and its identification, to expand as part of #38

[chgio]

at the System Analysis level, let's actually have a path to represent the telecommand/execution/report pattern, leading to "system does X" not unlike the fault identification placeholder:

• operator issues X t/c
  • g/s sends X t/c
    • system receives X t/c
    • (switch to a Downlink mode: through change mode, collect telemetry -- thanks @muhamedshaheenar for pointing this out!)
    • system does X
    • system sends X report
  • g/s receives X report
• operator interprets X report

at the other end of "system does X", a link to telemetry generation should also be made for when this function is triggered automatically and there is no option to immediately downlink the report.

[ZonaDashti]

What do you mean by placeholder for other subsystem failure? would that be an actor to represent the other subsystem? or a function within the System actor?

Where does the [SFBD] Functional Dataflow View of Subsystem Power-Cycle branch from? Is it the System Breakdown Element?

[chgio]

placeholder for other subsystem failure

by this I really just mean a function that represents that at a high level (system in this case) and doesn't get expanded in lower levels, but is still there as a "hold" for a functional chain to elaborate as part of a future extension. because this is the system level, it shouldn't actually mention subsystems (my bad) but rather just exist in the system and refer to the system like every other system-level function.

[SFBD] Functional Dataflow View of Subsystem Power-Cycle

Functional Dataflows are actually part of the System Functions, but IMO the easiest way to create one is from the Activity Explorer :)