Skip to content

Aviation

Requirements management for aviation teams.

Connect aircraft and system requirements to design decisions and verification evidence. Keep assurance work tied to the configuration it assesses.

02

Keep assurance connected across disciplines.

Aircraft, system, software and hardware teams contribute different parts of the review.

  1. Intent gets lost between levels

    Aircraft intent needs to remain connected to system requirements, implementation decisions and the verification that addresses it.

  2. Changes affect another discipline

    A message or interface update can alter software, hardware and supplier assumptions that need joint assessment.

  3. Results assess a different configuration

    Assurance reviewers need the requirement revision, hardware and software state and conditions represented by each result.

03

Connect aircraft intent to multidisciplinary review.

Bring requirements, implementation assumptions and verification evidence into a connected engineering record.

Aircraft and system context

Retain the reason behind the requirement.

Connect aircraft intent to system requirements, interfaces and implementation assumptions. Keep the source, rationale and responsible discipline with each record.

Arc FOREST-3 demo requirements table with REQ-013 marked Needs re-verification
Arc FOREST-3 demo. REQ-013 has a candidate change from 150 to 200 W and is marked Needs re-verification.

Design changes and agents

Review the impact across software and hardware.

Trace an interface update into the affected system and software requirements, electronic-hardware assumptions and verification work before acceptance.

Inspect the sources behind an agent finding.

Agents help check requirement quality, trace dependencies and flag verification gaps. Engineers assess the finding and proposed action in the programme’s assurance context.

Arc FOREST-3 demo impact analysis showing a proposed branch and conflict notice
Arc FOREST-3 demo. The impact view shows an unapproved branch and a conflict notice for review.

Assessed configurations and review

Keep evidence attached to the configuration assessed.

Connect each requirement to its procedure, evidence and hardware or software state. Retain pending applicability decisions when the candidate aircraft system changes.

Review with the accountable disciplines.

Bring system, software, hardware and verification owners into the same branch review. Keep the programme baseline distinct from the configuration represented by each result.

Arc FOREST-3 demo test record with a retained Pass marked Needs re-verification
Arc FOREST-3 demo. A retained Pass is marked Needs re-verification. The screenshot shows no rerun.

04

Keep applicable standards and guidance connected.

Select the standards and guidance agreed for aircraft and system development, safety assessment, software, electronic hardware and airworthiness security.

Connect technical and process obligations to requirements, discipline owners, reviews and assurance evidence. Monitor and report their status under the invoked editions, contract or certification basis, agreed tailoring and responsible acceptance authority.

The certification basis or contract determines invoked editions and required evidence. Linking records or citing guidance does not establish compliance, certification or tool qualification.

SAE ARP4754
Aircraft and system development assurance, including requirements validation and implementation verification.
SAE ARP4761
Safety assessment of civil aircraft, systems and equipment.
DO-178C
Development assurance for airborne software.
DO-254
Design assurance for airborne electronic hardware.
DO-326A
Airworthiness security addressing threats to aircraft safety from intentional unauthorised electronic interaction.

Connect assurance evidence through the API.

Keep system, software, hardware and supplier revisions with the assurance evidence they inform. Use supported API operations with agreed mappings, permissions and engineer review, retaining the requirement, procedure and assessed configuration.

API
Connect supported records and evidence references through API operations. Agree mappings, permissions and engineer review for the workflow.
Deployment and AI keys
Discuss deployment in your own AWS or Azure infrastructure under an agreed setup. Bring your own key is available for supported AI providers. Agree access, processing locations and retention for the programme.

05

Frequently asked questions

What can Arc connect for aircraft and system development?

Arc connects aircraft and system requirements, design decisions, interfaces, software and electronic-hardware references and verification evidence. Sources, revisions and owners provide context for multidisciplinary review.

How can Arc support a change affecting software and hardware?

Trace the proposed interface or requirement change into connected system requirements, software requirements, hardware assumptions and verification records. Reviewers assess the dependencies together while retaining each discipline’s responsibility.

How are ARP4754, ARP4761, DO-178C, DO-254 and DO-326A handled?

Keep their scopes distinct. SAE ARP4754 addresses aircraft and system development assurance, ARP4761 safety assessment, DO-178C airborne software, DO-254 airborne electronic hardware and DO-326A airworthiness security. Arc connects invoked obligations, requirements and evidence under the editions agreed with the programme and relevant authority.

Can verification evidence carry forward after an aircraft-system change?

Retain the requirement revision, procedure, hardware and software configuration and conditions assessed. The responsible reviewers determine what the evidence still supports and what needs further verification for the candidate design.

How can aircraft, software, hardware and supplier teams collaborate?

Use a connected record with source revisions, allocations and discipline owners. Review proposed work on a branch and retain the agreed baseline. A multidisciplinary review does not make software and hardware a derivation hierarchy. Requirements validation assesses intended needs, while implementation verification assesses whether the design satisfies them.

Can agents make development-assurance approval decisions?

Agents help inspect requirement quality, trace dependencies and flag evidence gaps. Engineers review the sources and proposed actions. Approval and assurance decisions remain with the programme’s responsible reviewers and authorities.

Can aviation teams connect tools and choose their deployment?

Supported API operations can connect engineering references through agreed mappings, permissions and review. Customer-owned AWS or Azure deployment and supported AI-provider keys are available under an agreed setup. Confirm the programme’s access and processing requirements.

What can an aviation team review in an Arc demo?

A demo can follow an aircraft-system requirement through an interface change, affected discipline records and verification-evidence review. Book a demo to discuss the assurance workflow relevant to your team.

Move faster without compromising engineering rigour.

See how requirements, discipline decisions and verification evidence stay connected through assurance review.