Embedded Software Static Testing Based On Rules

With the increasingly wide field of embedded system application, the quality ofembedded software product has got much attention. Due to real time and stabilityrequirements, software testing has become an important part of the embeddeddevelopment. Embedded system has its own characteristics, traditional softwaretesting theory can not be directly used for the testing of embedded software, soembedded software testing is important.This article describes a static embedded software testing tool, this tool is designedfor the characteristics of the C code to help detect check code error, positioning errorlocation; function complexity detection; generating function call graph and generatetest reports. MISRA C rules are industry associations to help users develop security,high reliability embedded software rules set. This static testing tools support MISRAC-2004standard.According to the MISRA C,《C Check Rules》 has been worked out, which lists19of the C code specifications. Function call relationship diagram can be generatedby the compiler combining with Graphviz. Due to the requirements of the embeddedsoftware quality standards, function complexity determine the risk of error code, sothe static testing of software is necessary to calculate the number of branches in theprogram source code to measure security by the complexity of the function. Thispaper describes static test software that counts the number of program if-else branches,for loops, switch branches, while loops, and do... while loops, and consider designtest cases according to the complexity of the program.Embedded software need more reliability requirements than ordinary software,finding defects in time can ensure good software quality and make lowest influence toproducts, so static testing of embedded software becomes an important part of theembedded software development. Not yet running the program, found errors in thecode and in accordance with the rules of specification code, which improve thequality of the software reliability and normative.