|
A large scale Aero Engine product was in the latter stages of development and was entering the maintenance stage. The embedded software resided within the Full Authority Digital Engine Controller (FADEC) and controlled the engine in response to pilot commands, ambient conditions and feedback from the engine itself. The software was written to DO- 178B, level A using the Yourdon design methodology and a bespoke programming language.
role was, the total responsibility for one of the software subsystems, from top level design through to unit test and also to support the client in completion of some of the other subsystems. Software changes were identified by the client’s system design team and were documented in “Change requests”. responsibility was to perform the Top Level Design (Yourdon), Detailed Design (M-Spec), Implementation (Bespoke language) and Unit Test (Bespoke language) for each change and to deliver back to the client the completed software to agreed timescales. The project is ongoing, with phased deliveries as new features are added.
The software subsystem that resource engineering projects was responsible for controlled the reporting of faults detected within the engine system and the FADEC itself. Any faults were annunciate in the aircraft’s cockpit and also stored within the FADEC to be downloaded and further examined by the ground crew at the next service period.
The software was designed using the Yourdon design methodology and the Select Yourdon PC based tool. From this top level design a number of lower level module specifications ( M-Specs ) were written which defined the operation of each module in sufficient detail to allow the item to be coded and verified. Following the coding each item was module tested. Each module test was written using a custom tool that provided an interface to the software under test and allowed the tester to generate multiple test cases to fully exercise and verify the software.
Each stage within the software lifecycle was formally reviewed before proceeding to the subsequent stage and the review records formed part of the software delivery to the client. Formal metrics were used to ensure Quality and Efficiency targets were met.
|
Over 10 years experience of software design for aerospace applications using experienced project management and engineers, able to work remotely from the client’s site but still fit in with the client’s procedures and processes. |
|
took total responsibility for the full software lifecycle, from design through to unit test for one of the subsystems. |
|
Quality product guaranteed. Audits passed as a matter of course. |
|
Time and Materials project. The client required a team of people to be available to work on this sub-system and also to be available to help out on other subsystems as the clients peaks occurred. |
|