Aerospace Garage

Upskill / Regulation & business / Systems engineering for aircraft: requirements, architecture and the V-model (ARP4754B)

Systems engineering for aircraft: requirements, architecture and the V-model (ARP4754B)

How aircraft and systems are developed and assured: functions and requirements, validation and traceability, architecture and budgets, integration and verification, and change control, following one brake-by-wire system. Part 1 of the Systems engineering and safety series.

By Aerospace Garage Desk · In practice · 50 minutes · 24 narrated pages

What you will be able to do

  • ✓ Explain where ARP4754B and ED-79B sit, how EASA and the FAA recognise them, and what development assurance is for.
  • ✓ Break aircraft functions into system functions and write requirements that are single, measurable and verifiable, including derived requirements and assumptions.
  • ✓ Validate a requirement set with traceability, review and other methods, and measure traceability coverage.
  • ✓ Compare architectures with a weighted trade study and allocate mass and reliability budgets with margin.
  • ✓ Plan integration and verification, build a verification matrix, and sort test failures by cause.
  • ✓ Control baselines and changes with process assurance, independence and change impact analysis.

Course content

Session 1 · Why aircraft need systems engineering

1.1

  1. Many parts, one aircraft · free preview
  2. Where ARP4754B fits
  3. The V-model: down to design, up to proof
  4. Worked example: meeting Halny Aero Systems and its brake-by-wire system
Session 2 · Functions and requirements

1.2

  1. From aircraft functions to system functions
  2. Writing requirements that can be proved
  3. Derived requirements, assumptions and the certification basis
  4. Worked example: turning a stopping requirement into brake energy
Session 3 · Validating requirements

1.3

  1. Validation and verification: two different questions
  2. Validation methods and the trouble with assumptions
  3. Traceability, orphans and coverage
  4. From the investigation file: an assumption that was never validated, Roswell 2011
Session 4 · Architecture and allocation

1.4

  1. From functions to architecture, by trade study
  2. Redundancy, independence and the fail-safe toolbox
  3. Interfaces, interface documents and the N-squared chart
  4. Worked example: a mass budget and a reliability allocation
Session 5 · Integration and verification

1.5

  1. Integration: building up the right arm
  2. Verification methods and the verification matrix
  3. From verification to compliance
  4. Worked example: running the verification campaign
Session 6 · Configuration, assurance and change

1.6

  1. Baselines and configuration management
  2. Process assurance and independence
  3. Where the series goes next: safety, software, hardware and models
  4. Worked example: a change request and its impact analysis
  • MRO deals and approvals, 5-11 Nov 2026

    3 · World n/a

    Aviation Week and AviTrader, 9-11 Nov 2026

Market Pulse →

Who this course is for

  • Systems, avionics and design engineers at airframers and suppliers who write requirements, choose architectures and plan verification
  • Certification and airworthiness engineers who must judge development assurance evidence against EASA and FAA guidance
  • Engineering and programme managers who own budgets, interfaces, test campaigns and change control on aircraft system projects

You need: A working knowledge of aircraft systems; Part 21: design and production approvals explained is useful background.

Upskill courses are for professional development and are not approved by any aviation authority. Learner Terms

Course content © Aerospace Garage Limited. All rights reserved.