Skip to main content

End, Retry, or Restart a Flight Session

Overview​

User capability

Conclude free flight and establish a known retry or restart state

User

An AeroSim player

What the user can do

Conclude free flight and establish a known retry or restart state

Why the user benefits

The player receives one coherent, observable capability.

User need

The player needs AeroSim to conclude free flight and establish a known retry or restart state.

In scope

Conclude free flight and establish a known retry or restart state

Tasks​

AEROSIM-TS-6Planning status: Done

End a flight and record its outcome

The player can deliberately end or abort an active flight and receives one explicit recorded session outcome.

  • ComponentWeb Application — flight-session lifecycle and outcome presentation
  • Depends onAEROSIM-TS-96
  • RequirementsFR-0009, NFR-0006, NFR-0010
AEROSIM-TS-97Planning status: Done

Reinitialize retry and restart to documented starting state

Retry and restart each dispose transient flight state and establish their documented known starting state reproducibly.

  • ComponentWeb Application / Deterministic flight runtime — Shared flight-core and Web Application — session reset coordinator and state rehydration
  • Depends onAEROSIM-TS-6
  • RequirementsFR-0009, NFR-0001, NFR-0002, NFR-0005, NFR-0006, NFR-0010
AEROSIM-TS-142Planning status: Done

Conclude a flight with an outcome and retry path

END FLIGHT concludes the active session, presents its recorded outcome, and offers valid retry, restart, or exit actions instead of dropping the player into an empty setup state.

  • ComponentConclude a flight with an outcome and retry path
  • Depends onAEROSIM-TS-96
  • RequirementsFR-0009
AEROSIM-TS-156Planning status: Done

Make every flight recovery control ordinarily operable

Direct Restart, Menu/Resume, and dialog-scoped Menu/Restart are visible topmost hit targets and work through ordinary user input with scoped semantic role/name queries and no forced click.

AEROSIM-TS-159Planning status: Done

Eliminate implicit flight resets during ordinary control

A flight attempt changes identity only after an explicit visible restart or terminal recovery decision, never as a hidden response to normal pilot input.

  • ComponentWeb Application — flight recovery and attempt continuity
  • Depends onAEROSIM-TS-156
  • RequirementsFR-0009

Acceptance outcomes​

  1. 01

    The player can deliberately end a flight and see its recorded outcome.

  2. 02

    Retry and restart each establish the documented known starting state.

Functional requirements and measurable criteria​

FR-0009

complete and restart free flight

The system shall produce a clear free-flight outcome or abort and restart from the initial state.

Acceptance 01

Givena valid current Feature configuration and defined initial state

Whenthe relevant user action or simulation step occurs

Thenthe observable result must produce a clear free-flight outcome or abort and restart from the initial state

EvidenceFuture reviewed automated and browser evidence must verify this outcome against the current requirement.

Acceptance 02

Givenan invalid or unsupported input at the same boundary

Whenthe system evaluates the input

Thenthe system must reject or recover visibly without publishing a misleading result

EvidenceFuture negative-path tests and browser evidence must verify explicit failure or recovery behaviour.

Non-functional requirements

Risks​

  • Risk

    Prototype behaviour may not meet the current acceptance outcomes.

Original source and prototype evidence​

Prototype and discovery boundary

Existing application behaviour is discovery evidence only; it establishes no current Scope approval, implementation approval, acceptance, or release state.