Uncrewed aircraftAerospace & marine

Kestrel-1 Survey UAV

A fixed-wing survey UAV, seeded as a worked example: eight requirements, six components, four suppliers and four verifications, wired into a traceability graph, with a real ELANG system_model and an inline Technical Data Package.

DjiniousEngineeringOrchestration

The DjiniousEngineering requirements table holding eight requirements — mission, safety, regulatory, performance, environmental, payload and operational — each with its verification method, rationale, source, value, unit and tolerance, marked Agreed or Allocated.

requirements: 8requirementsWorked example
components: 6components
suppliers: 4suppliers
verifications: 4verifications

The smallest complete thread — every edge closed

Kestrel-1 exists to show the whole chain closed on a small system: eight requirements derived from the need, allocated onto six components, sourced from four suppliers, and each closed by one of four verification activities.

It is the example to read when you want to see needs → requirements → components → suppliers → verification as actual graph edges rather than a diagram of one.

Recipe and standards

Driven by the UAV recipe over the baseline lifecycle.

NASA SE Handbook Rev.2

Carried as a standard the recipe honours for this class.

EASA UAS 2019/947

Carried as a standard the recipe honours for this class.

UAV recipe over the baseline lifecycle

Take a survey UAV from need to a released baseline and Technical Data Package, with a verification activity standing behind every requirement.

Derive
Derive eight singular requirements from the mission need.
Allocate
Allocate each requirement onto a component in the architecture.
Source
Source the six components from four qualified suppliers.
Verify
Close every requirement with a verification activity of sufficient evidence class.
Release
Author the ELANG system_model and freeze the Technical Data Package.