Automated Requirements and Traceability Generation for a Distributed Avionics Platform 2019-01-1384
The development and certification process of distributed and highly safety-critical avionics systems usually implicate high efforts and risks. The resulting costs usually limit implementations like fly-by-wire systems to the military or commercial airliner domains. The aim of previous and ongoing research at the Institute of Aircraft Systems at University of Stuttgart is the reduction of these costs and therefore open up their benefits to general aviation, remotely piloted or unmanned aircraft.
An approach for cost reduction is the application of a platform based development which supports the reuse of software and hardware components. The Flexible Platform adopts this approach. It features a clear separation of applications, e.g. flight control functionality, from the system management tasks. For the applications, an API with a virtual simplex environment is provided. The system management respectively platform management (plama) encapsulates all redundancies and the whole management complexity. With the Flexible Platform, a process for the automated design and parameter instantiation, automated documentation generation and the automated generation of verification artifacts was realized by a tool suite.
This paper presents the second of the mentioned three automatization steps which realizes the generation of system and software requirement documents compliant to ARP4754A and DO-178C. The document generation is based on configurable requirement classes with which all possible instances within the plama’s usage domain can be covered. Each class consists of an instantiation condition, a textual representation for the manual validation and a formal one as an interface to the verification process. In addition, relation classes build the base for the generation of a bidirectional traceability. The implemented classes for the system and high-level software requirements as well as their instantiation with the tool suite were validated with a representative fly-by-wire system model.
Tim Belschner, Peter Müller, Reinhard Reichel