ARTUS FOR AEROSPACE
Every change has a flight path.
See where it leads.
Connect a proposed change to the requirements, interfaces, configuration baselines and verification evidence your programme needs to review.
DEVELOPMENT ASSURANCE CONTEXT / ARP4754 · DO-178C · DO-254
01 Changed requirement
02 Affected avionics
03 Verification evidence
01 / CHANGE INTELLIGENCE IN CONTEXT
One requirement changes.
The review reaches further.
Follow an illustrative air-data source-switching change from its origin to a reviewable evidence trail.
CR-041 · AIR-DATA SOURCE SELECTION
Revise source-switching behaviour after persistent sensor disagreement.
SOURCE / System change request
REQ-AD-042 · Rev D → Rev E
BASELINE / Proposed system baseline SB-18
Illustrative example, not a live customer programme. Relationships and applicability require engineering review.
02 / THE BASELINE BLIND SPOT
Passed is not the same as covered.
Keep verification evidence tied to its tested software load, hardware revision and system configuration.
PROPOSED CONFIGURATION
SB-18
Software load 3.7
TESTED CONFIGURATION
SB-17
Software load 3.6
EVIDENCE GAP / HIL-AD-091 does not establish coverage for SB-18.
03 / SPEAK THE LANGUAGE OF YOUR PROGRAMME
Review the work products behind the change, not just the ticket that announced it.
SYSTEM DEVELOPMENT
ARP4754
Aircraft & system requirements → allocated functions → validation records
AIRBORNE SOFTWARE
DO-178C
High-level requirements → low-level requirements → source → verification
ELECTRONIC HARDWARE
DO-254
Hardware requirements → design data → implementation → verification
Workflow context, not a certification claim. Applicable revisions, assurance levels and approval evidence are defined by your programme. Safety assessment and certification judgement remain with qualified teams and authorities.
04 / KEEP THE HANDOFF IN VIEW
Different organisations.
The same change to resolve.
Bring delivery baselines, interface assumptions and open verification actions into the same review.
01
AIRFRAMER
System requirement & acceptance criteria
Owner: systems lead · Confirm interface applicability
02
EQUIPMENT SUPPLIER
Implementation & delivery baseline
Owner: supplier lead · Identify affected software / hardware
03
VERIFICATION TEAM
Test scope & configuration-linked results
Owner: verification lead · Resolve evidence coverage
Clearer scope. Visible evidence gaps. Better-informed release decisions.
05 / START WITH A REAL ENGINEERING QUESTION
One subsystem. One change.
A clearer route to review.
Scope an evaluation around a representative change and the sources your team can share.
01
Choose the change
A requirement revision or problem report
02
Bring the context
Requirements, interfaces and configuration records
03
Review together
Impact, evidence gaps and accountable owners
