Support was given to a partner developing high integrity (DO-178C Level A) Flight Control Systems (FCS). The initial work, focused solely on the control law, interfaces and voting mechanisms and took around 2 days to write using Kapture®. The more detailed work was completed by the D-RisQ team in around a month, who assisted in writing the 23 system and 400 software requirements, using Kapture® tools as the enabler.DISCOVER MORE
The major problem with unmanned air vehicles is knowing what they will do once they are Beyond Visual Line of Sight (BVLOS), when situational awareness is difficult to obtain and even when communications are interrupted. The software produced by D-RisQ allowed the unmanned air vehicle to comply at all times with the rules-of-the-air. In an evolution from USMOOTH, we added an extra capability which ensured that the vehicle behaved as though it was piloted.
Safety Monitor: High assurance software for autonomous systems air safetyDISCOVER MORE
This case study focused on the difficulty and cost associated with developing software for use in an uncertain environment. The requirement was that the software must satisfy “that the estimated Ground Velocity shall be within 3 km/hr of the true velocity of the aircraft at some moment within the past 3 seconds". This seemingly straightforward requirement leads to some subtle issues about the physical environment that the software must deal with. For example, what is meant by the true velocity of the aircraft? It is difficult to define a specification generated before the software has been tested on an aircraft.DISCOVER MORE