Process & Safety Management — SW-Development Air Traffic Management
Process & Safety Manager
Reading Time: 2minutes Implementing a DO-178B, DO-178C/ED-12C compliant software development process model for air traffic management systems developer. Moderating, and documenting safety workshops.
My direct client was an IT-department of a national air traffic management authority. They develop software to serve the own air traffic controlling demands. In addition, they sell customised variants and individualised implementations to other international ATM authorities. An international air traffic management authority was the end client of my client. They planed to replace their own system with a new, enhanced one. For this, they ordered from my client an individual customisation.The challenges for the devteam of my client were
to implement all operational procedures valid for the target airspace (80% functionality of the system to be rebuild).
to keep the existing system architecture design;
to fulfill operational safety requirements for the existing and added/rebuilded functionality system-wide;
to setup a SW development process compliant to DO-178B, DO-178C/ED-12C in addition to their own, ISO 9000 certified, quality management system and process model.
My responsibility as external consultant was
to design, implememnt, and document for the project a system development process with all artefacts needed to be n compliant with DO-178B, DO-178C/ED-12C and the existing process model of my client. (Process Management)
to implement, monitor, and verify activities needed for the safety validation process; (Safety Management)
to assist and coach the devteam in applying the new/changed processes (Coaching).
Safety Management Responsibilities
To fulfill the safety requirements we implemented joined workshops with developers, designers, and testers. In these workshops we analysed the existing implementation as well as the planned changes resp. new implementations to be valid with safety objectives given by the end client.
The workshop method to investigate systems safety were a combination of
repeatedly 5-Why-Questions drilled down from architectual design, code (component, modul level implementation)
imaginating worst case scenarios: "What is the consequence if function X /code segment Y in module Z fails?", or "Which components/functional code have to fail, that safety objective n.m.l is not fulfilled?"
The insight and results of these safety workshops led directly to new or changed functional requirements and/or test cases. I monitored and tracked their status with a DOORS database.
Process Management Responsibilities
The process model I designed and implemented covered
the safety objectives for all development and testing activities;
additional activities, roles, and artefacts needed for DOD/ED compliance.