Embraer Speeds Requirements Engineering and Prototyping of Legacy 500 Flight Control System
Accelerate development of the flight control system software for the Legacy 500 midsized business jet
Use Simulink to model the system and the aircraft dynamics, run requirements-based test simulations, and speed the delivery of mature, internally validated software requirements
- Development time shortened by at least six months
- Delays due to requirements issues minimized
- Models reused for real-time testing
The Embraer Legacy 500 is the first midsized business jet with intelligent flight controls and full fly-by-wire technology. This technology, which replaces mechanical controls in the flight control system (FCS), enables more control surfaces to be actuated simultaneously, leading to smoother flights, reduced pilot workloads, and increased safety.
Embraer used MATLAB® and Simulink® to speed up the development and validation of well-defined low-level requirements for the Legacy 500 FCS, and to increase requirement quality.
“With Simulink we could prototype several solutions rapidly, test them all, and then pick the best one,” says Rodrigo Fontes Souto, product development engineer at Embraer. “As a result, the supplier who implemented the FCS reported significantly fewer issues. With fewer issues to resolve, we have more time to work on new features, and we can deliver a more mature product on time and at lower cost.”
Embraer worked with customers to develop high-level requirements for the Legacy 500. They used this customer input to produce the aircraft’s clean-sheet design. A principal challenge for the engineering team was translating the high-level requirements into well-written low-level requirements for the supplier who would develop the FCS software.
The Legacy 450 and Legacy 500 are clean-sheet designs with extensive innovation in technology and aircraft features, including state-of-the-art fully digitally controlled systems never used before in the mid-light and midsize jet categories. The design goals and deadlines for entering a mature product into service on time meant that the design team had to create a very detailed product development plan and look for tools and partners that could both shorten the development cycle and mitigate development risks.
On early designs developed without the intensive use of modeling and simulation, it was difficult to ensure consistency in the specification of low-level requirements. As a result, requirements sometimes had to be rewritten after they were delivered to the supplier, wasting time and increasing costs.
Embraer engineers used modeling and simulation with Simulink to define the low-level requirements for the Legacy 500 FCS.
Working in Simulink, the modeling group created a detailed model of the FCS, as well as models of the aircraft dynamics and pilot inputs. The complete model comprises more than a million blocks and dozens of components, many with more than 700 inputs and 500 outputs.
The modeling group created functional test cases to verify that the high-level requirements were being met and to validate the low-level requirements.
Test automation was another key to development success. The group set up workstations to run more than 1500 test cases continuously, and wrote MATLAB scripts to automate tasks in the testing process. Using Simulink Coverage™ the engineers analyzed model coverage and identified untested elements of the model, refining and extending their test cases until they achieved 100% coverage.
Model reuse saved significant time and improved quality. Simulink Coder™ was used to generate code from their Simulink model, which the group used in their flight simulator and their iron bird hardware-in-the-loop test environment.
After validating the low-level requirements internally, Embraer delivered the written requirements to the supplier, who performed their own validation before using Simulink and Embedded Coder® to implement the system according to DO-178 Level A and other aviation standards.
The Legacy 500 received certification from the Federal Aviation Administration and the Brazilian Civil Aviation Agency on schedule, and the aircraft is currently in production.
- Development time shortened by at least six months. “We estimate that modeling and simulation with Simulink enabled us to deliver requirements to the supplier three months earlier than would have been possible using a traditional approach,” says Souto. “Because the requirements we delivered were mature, the supplier had fewer questions and issues, reducing development time by an additional three months.”
- Delays due to requirements issues minimized. “Our group produced twice as many requirements, and had 50 times fewer issues per requirement, than was typical when we used a traditional methodology to develop and validate requirements,” says Julio Graves, product development engineer. “The longest requirements-related delay using a Model-Based Design was one day, whereas the shortest delay using a document basis was two weeks.”
- Models reused for real-time testing. “With Simulink Coder we generated code for real-time tests from the same Simulink models that we had developed for requirements validation,” notes Miguel Teruel, product development engineer. “We plan to reuse the models again to accelerate development by generating production code for various systems with Embedded Coder.”