Abstract
In this paper, the verification approach developed in accordance with the DO-178B certification requirements of the software of the Unmanned Aerial Vehicle’s (UAV) Flight Control Computer (FCC) and the lessons learned from this approach are presented. The software verification process is a process that is used to verify how the aircraft's flight control computer behaves according to specified requirements and is used to verify that it does not produce unexpected results. The paper will first describe the software architecture, and then the types of tests developed in accordance with the software architecture. Then, test levels will be compared according to different testing parameters. Afterwards, the information regarding the management of test cases will be reviewed in detail with their different scenarios. The traceability controls and the importance of using traceability while writing the test cases and how to blend a traceability inside a test case will be explained. The studies on structural coverage analysis will be covered in a different section. This whole process can be made automated. To help automate the process, various tools are used. These tools also need to be tested, meaning they need to be qualified. Section 8 talks about this. Finally, lessons learned from the DO-178B certification process will be presented at the end of the paper.
Highlights
The level of development of software and complex hardware that must be complied with according to STANAG 4671 applicable to Fixed Wing Military Unmanned Aerial Vehicle (UAV) is given in Table 1: STANAG 4671 Development Assurance Level Targets [1]
Flight Control Computer Software is in the “Catastrophic” category according to the safety analysis and needs to demonstrate the highest level of Development DAL-B
The Independence Level criterion on the Table of Requirements according to DO-178B Critical Levels Table 2 is requested as “Medium” this level is provided as “High” for our UAV, so that errors can be detected earlier and an independent perspective can be provided while reviewing the products of other individuals [22]
Summary
The level of development of software and complex hardware that must be complied with according to STANAG 4671 applicable to Fixed Wing Military UAVs is given in Table 1: STANAG 4671 Development Assurance Level Targets [1]. DO-178 Feature Independence Level Software Plans Software Standards Structural Statement Coverage Structural Decision Coverage Modified Condition Decision Structural Coverage Verifiable High Level Requirement Verifiable Low Level Requirement / Code High Level- Low Level and Low Level-Code Traceability Low Level Requirement Test Coverage Code Review Configuration Management Software Quality Assurance Transition Criteria Architecture, Algorithm Verification. The criterion for software plans to be in process is provided by the fact that the software plan documents of all processes in the software development life cycle are present and accessible to all These are; plan for software Aspects of Certification (PSAC), software quality assurance plan, software configuration management plan, software development plan and software verification plan. All software products (code, test, plan documents, requirements, etc.) are kept in configuration management tools [7]. The lessons gained from the DO178B certification process will be presented [8, 9]
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
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 call
