Abstract
The purpose of this paper is to propose design and development methodology, in terms of robustness, of unmanned vehicles (UV) software development, which minimizes the risk of software failure in both experimental and final solutions. The most common dangers in UV software development were determined, classified and analysed, on the basis of literature studies, and the author's own experience in software development and in analysis of open-source code. As a conclusion, “good practices” and failure countermeasures were proposed.
Highlights
The purpose of this paper is to propose a design and development methodology in terms of robustness of unmanned vehicle (UV) software development, which minimizes the risk of software failure in both experimental and final solutions
The problem had not been detected before the mission launch and manifested itself during the Mars orbit insertion maneuver
A guidance system was designed to lead the spacecraft into the orbit 160 km above the Mars ground level in order to perform aerobraking
Summary
Software for application in the unmanned vehicles (UV) is usually developed not by professional Functional Safety (FuSa) developers, but rather by people coming from other technical backgrounds related to the currently developed unmanned vehicles. As long as standards such as DO-178C do not forbid modern software development techniques such as Test-Driven Development (TDD) to be used alongside the formal, certified ones, the accepted techniques and tools may still not cover many useful features and capabilities of modern languages. This situation makes mentioned small UAVs to be excellent prototyping platforms for aviation software of the future. Let us first remain with the end to which simple bugs might lead
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
