Choose and Confirm the Aircraft for This Flight

Overview

User capability

Choose a supported aircraft for the planned flight and confirm its model and flight parameters.

User

An AeroSim player

What the user can do

Choose a supported aircraft for the planned flight and confirm its model and flight parameters.

Why the user benefits

The player receives one coherent, observable capability.

User need

The player needs AeroSim to list supported aircraft, accept one flight selection, and apply its confirmed model and flight parameters.

In scope

Choose a supported aircraft for the planned flight and confirm its model and flight parameters.

• StatusProposed
• OwnerAeroSim Scope (proposed; not accepted)
• Parent EpicAEROSIM-EP-5
• Depends onNone

Tasks

AEROSIM-TS-8Planning status: Done

Present, select, and confirm a supported aircraft

The player can identify supported aircraft by governed characteristics, select one, and visibly confirm it for the planned flight.

• ComponentWeb Application — Pre-flight configurator
• Depends onNone
• RequirementsFR-0012

AEROSIM-TS-114Planning status: Done

Encode the confirmed aircraft and parameters in the launch configuration

The immutable launch configuration contains exactly the confirmed aircraft model identifier and governed flight parameters.

• ComponentWeb Application — Pre-flight configurator to Flight shell boundary
• Depends onAEROSIM-TS-8
• RequirementsFR-0013, NFR-0011

AEROSIM-TS-115Planning status: Done

Instantiate the confirmed aircraft model and flight parameters

The launched session uses the confirmed visual aircraft model and the corresponding deterministic flight parameters.

• ComponentWeb Application — Deterministic flight runtime and R3F flight scene
• Depends onAEROSIM-TS-114
• RequirementsFR-0013, NFR-0011

AEROSIM-TS-116Planning status: Done

Verify aircraft-selection performance, resource, and browser compatibility

Aircraft listing, confirmation, and launch pass the declared timing, browser-resource, namespace-resource, and compatibility checks.

• ComponentWeb Application — Pre-flight and flight integration test suites
• Depends onAEROSIM-TS-115
• RequirementsNFR-0001, NFR-0005, NFR-0006

AEROSIM-TS-122Planning status: Done

Conform all Hangar aircraft-selection states to the approved design

Trainer, Jet, and Utility selection states match the approved cards, imagery, active treatment, confirmation, and navigation.

• ComponentWeb Application — Release 1.0.0 user journey
• Depends onAEROSIM-TS-116
• RequirementsFR-0012, FR-0013, NFR-0001, NFR-0005, NFR-0006, NFR-0011

AEROSIM-TS-133Planning status: Done

Select an aircraft during Flight Setup

Start Your Flight opens Flight Setup directly, where the player can select and confirm a supported aircraft alongside the other flight configuration choices.

• ComponentFlight Setup aircraft selection
• Depends onNone
• RequirementsFR-0012

Acceptance outcomes

1. 01

   The player can list, choose, and confirm a supported aircraft for the planned flight.

2. 02

   Launch applies the confirmed aircraft model and flight parameters.

Functional requirements and measurable criteria

FR-0012

list supported aircraft

The system shall list each supported aircraft with identifiable characteristics.

Acceptance 01

Givena valid current Feature configuration and defined initial state

Whenthe relevant user action or simulation step occurs

Thenthe observable result must list each supported aircraft with identifiable characteristics

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.

FR-0013

apply chosen aircraft

The system shall apply the chosen aircraft model and flight parameters.

Acceptance 01

Givena valid current Feature configuration and defined initial state

Whenthe relevant user action or simulation step occurs

Thenthe observable result must apply the chosen aircraft model and flight parameters

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

• NFR-0001 — Performance

  Maintain responsive rendering and simulation.

• NFR-0005 — Resource governance

  Keep browser and deployed workload consumption within explicit budgets.

• NFR-0006 — Compatibility

  Support the declared browser and input compatibility matrix.

• NFR-0011 — Faithful pre-flight configuration

  Every launch establishes one session whose canonical configuration equals the reviewed pre-flight summary.

Risks

• Risk

  Prototype behaviour may not meet the current acceptance outcomes.

Original source and prototype evidence

• discord: Authoritative clean-slate Scope recommendation.
• discord: Clean-slate Scope discussion 1.
• discord: Clean-slate Scope discussion 2.
• discord: Clean-slate Scope discussion 3.
• discord: Agreed eight-Epic portfolio and Feature decomposition.
• discord: Agreed eight-Epic portfolio and Feature decomposition continuation.
• discord: RootAtSkic directed publication of the agreed Scope update.

Prototype and discovery boundary

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