COST EFFECTIVE ASSURANCE OF HIGH INTEGRITY SOFTWARE
If you need to develop control software for aerospace, be that manned, unmanned, civil or military, then DO-178C/ED-12C is likely to be the standard to be met.The D-RisQ tools have all been developed to help users meet this standard through their automation and unique technical approach.
The major aim is to reduce the time and cost of development while providing the right evidence that the software is compliant and only does what is required and nothing else.
Automatic Requirements Verification
Requirements will always need to change to reflect the reality of a changing environment. Kapture® has been specifically designed to enable users to write accurate, verifiable, consistent, complete and unambiguous software requirements. Additionally, credit claims for standards compliance against DO-178C can be made as a by-product of the use of Kapture®.
Automatic Design Verification
A design in Simulink / Stateflow can be automatically, independently checked against the requirements using Modelworks®. The checks show that the design either satisfies the requirements or not and targets where non-compliances exist. The tool shows the exact requirements that are not satisfied by the specific area of the design. In this case, claims for credit against DO-178C can be replaced with claims against DO-333, the formal methods supplement to DO-178C, as Modelworks® is a formal methods based tool,.
Future Code Verification
D-RisQ has also developed CLawZ® as an independent automatic proof check demonstrating that autocode produced by the dSpace TargetLink C coder correctly, completely and accurately implements the design. CLawZ avoids the time and cost of undertaking unit test because it automatically proves that the automatically generated code correctly, completely and accurately implements a design expressed in Simulink/Stateflow.
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 MOREThe 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 safety
DISCOVER 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
Privacy Policy | Terms & Conditions
Drisq Ltd 2024. All rights reserved. Design by Design in the Shires
