Telos
Engine 03 / 05 · Requirements · Independent
Requirements held to engineering rigour —
each one made verifiable before it reaches the bench.
Explore more ↓THE REQUIREMENTS LIFECYCLE
From a drafted requirement to a traceable test
Draft requirements
Writes requirements in the discipline's form — single behavior, measurable bound, declared condition.
Quality checks
Flags ambiguity, untestable phrasing, compound clauses, and missing tolerances — before review.
Bidirectional trace
Parent ↔ child ↔ test linkage maintained and audited; orphans and childless parents surfaced.
Convert to test cases
Derives test cases with inputs, expected results, and pass criteria from each requirement.
Coverage & change impact
Reports trace coverage and shows exactly which artifacts a requirement change touches.
A WORKED ARTIFACT
Requirements verified before they cost you
TELOS reports the drafted statement, the quality findings, the bidirectional trace, and the derived test case — a record an assessor can follow from parent requirement to executed check.
DRAFT REQ-GNC-014 · "The FCC shall limit pitch rate to ±12 °/s within 40 ms of command receipt."
CHECK unambiguous ✓ · verifiable ✓ · atomic ✓ · bounded ✓
TRACE parent SYS-022 ↑ · child SW-FCS-031 ↓ · coverage 100 %
CONVERT TC-GNC-014-01 · step 20 °/s → expect clamp at 12 °/s ≤ 40 ms
EXPORT ReqIF · CSV · test procedure skeleton
VERIFIED · TRACEABLE TO FIRST PRINCIPLES
ELSEWHERE IN AETHER
Four more, each self-contained
There is no prescribed order. Select the engine suited to the problem at hand.
TELOS · AEROSPACE INTELLIGENCE