Solutions · Requirements Engineering
Your ICD is static and hand-written. One engineer reads it, every reviewer re-reads it, and every gap waits days to a month for a supplier reply. Validation and quality can’t start until it’s all approved.
+
+
+
+
TODAY / ONE ICD → REQUIREMENTS
● BLOCKED
Static ICD arrives
Prose and tables, interpreted by every reader
ICD
One engineer reads and drafts
Coverage depends on a single reading
MANUAL
Gaps go to the supplier
Via the equipment owner, one query at a time
DAYS → A MONTH
Every reviewer re-reads it all
Draft and ICD, read in full several times
RE-READ ×N
Implementation and validation wait
Coding and QA can’t start until approval
WAITING
01 — THE PROBLEM
Interface behaviour lives in prose and tables. Byte order, timing, units and error behaviour are often unstated, ambiguous or contradictory, and every reader has to interpret them.
Watch how the same process runs in Lynapse™ Studio, with the reading, inspection and issue resolution automated.
+
+
+
+
+
+
+
+
STEP 01
The equipment engineer assigned to the component reads the supplier’s ICD by hand and writes the initial requirements document from that reading. There is no systematic check that every paragraph was turned into a requirement.
STEP 02
Bugs, ambiguities and missing information go to the internal equipment owner, who contacts the hardware supplier. Replies take from a few days up to a month. Questions are found, marked and escalated by hand, one reader at a time.
STEP 03
The draft is released for review. Several senior engineers re-read both the requirements and the ICD to catch errors and omissions the writer missed. Reviewer time is spent re-reading instead of on the issues that matter.
STEP 04
Implementation and validation engineers wait for the approved requirements before coding and quality assurance can start. Every review and supplier delay moves the whole schedule.
ROLES INVOLVED
Equipment engineer (writer)
Equipment owner
Senior reviewers
Hardware supplier
Validation and quality engineers
02 — THE SOLUTION
Lynapse™ Studio keeps every role and review step. It replaces manual reading with a structured digital model, moves issue finding ahead of review, and turns the review into one shared, tracked activity.
+
+
+
+
01
✕ Engineer reads the ICD by hand.
✓ The ICD is imported and AI builds a digital model of the equipment.
Model covers telemetry, telecommands, modes, timing, error handling and bus. Every element links back to its exact source in the ICD revision: paragraph, line and value. Unmapped paragraphs are flagged, so coverage is measurable.
02
✕ Issues are found during reading, one reader at a time.
✓ AI inspection flags issues before review starts.
Findings are categorised as ambiguity, missing information or contradiction, and attached to both the model element and the source paragraph.
03
✕ Every reviewer re-reads the full ICD.
✓ Engineers review together in the inspection dashboard.
ICD source and model side by side. Multiple engineers review in parallel, focusing on flagged items. Issues are marked, shared and tracked as tickets.
04
✕ Equipment owner chases the supplier, query by query.
✓ Open issues go to the supplier as one clarification list.
Answers update the model. The model is versioned, so each change is recorded against the ICD revision it came from. Once resolved, the model is finalized and approved.
05
✕ Engineer writes requirements by hand.
✓ AI drafts flight software sequences from the approved model.
A sequence describes, step by step, how the flight software must use the equipment (for example power-on, initialisation, acknowledgement, mode change). Engineers inspect and approve each sequence.
06
✕ Requirements trace back only through the writer’s reading.
✓ Each approved sequence becomes one requirement.
One requirement per sequence, traced to its sequence, model version and ICD revision.
07
✕ Senior reviewers validate; validation and quality wait.
✓ Peer validation and formal approval in the dashboard.
Produces a requirements baseline, ready for manual coding or for deterministic code generation in Lynapse™ Studio.
03 — TRACEABILITY
+
+
+
+
ROOT · ICD
Supplier ICD rev D
MODEL
INSTR · v1.3
Engineer-approved
SEQ-01
Instrument startup
REQ-FSW-031 · APPROVED
Start up the instrument: power, initialise, enter NOMINAL.
inst_status_t inst_startup(void)
/* @req REQ-FSW-031 · @seq SEQ-01
* @model INSTR v1.3 · @icd rev D §6.1 ¶3 */
SEQ-02
State monitoring
REQ-FSW-032 · APPROVED
Read the instrument state telemetry and report it to the OBC.
inst_status_t inst_read_state(void)
/* @req REQ-FSW-032 · @seq SEQ-02
* @model INSTR v1.3 · @icd rev D §6.3 ¶1 */
SEQ-03
ACK timeout handling
REQ-FSW-033 · APPROVED
If no ACK is received within 250 ms, retry INIT once, then raise a fault event.
inst_status_t inst_ack_timeout(void)
/* @req REQ-FSW-033 · @seq SEQ-03
* @model INSTR v1.3 · @icd rev D §6.1 ¶5 */
Illustrative example. IDs, values, sequences and code are invented.
+
+
+
+
Built for high stakes
Early-access trial seats for Lynapse™ Studio are limited. Seats are offered first come, first served. Request access now and tell us what you’re integrating.
Prefer to talk first?
Book a demo