Design And Implementation Of Automated Code Rule Inspection System

With the rapid development of software technologies, people have a more strict demand on the security and quality of software products. However, the source code even after successful compilation cannot necessarily ensure zero defects in it, which indicates that it still has the possibility of imperfections in security, design or style of the source code. Due to these potential defects, the source code may become less readable or more seriously, some problems such as memory leakage, null pointer misuse may occur while running the program. Code rule based automatic inspection, which can execute code inspection in the early phase of software development cycle, is of vital importance for improving software quality, besides; it can also improve quality and effectiveness of software testing, and reduce testing cost.Based on the idea of continuous integration, the automatic code rule inspection system built in this thesis integrates a variety of code rule inspection tools to achieve code rule inspection by use of automatic drive, which enables inspection of code defects. This system is designed and developed based on the principle of componentization, modular and layered implementation, which not only supports the development process for developers and integrates Klocwork and Testbed source code analysis tools, but also supports rule set configuration and function of analyzing source code from Subversion configuration management tool and file directory monitoring. With the built automatic code rule inspection system, the code can be examined upon written, which can help developers to find and solve code defects effectively.This system is mainly built by the following scheme:system platform interface of the functional layer allows creating a new user, setting up user role, creating a new project and configuring rule set file, then the interface and data engine of the application service layer submits user and project information to the database of the storage layer. Once a new task is initiated by the user terminal, system platform will invoke the version control software client server through its engine to inspect the code changes. After extracting the updated code from the configuration management repository, build tools engine will invoke the IDE commands to compile the program and code analysis tool will be also invoked by its engine to execute code rule inspection. Lastly, the inspection results are submitted to the database of the storage layer by data engine, then the results are shown graphically to the user by the graphic engine of application service layer, and user can check project information and inspection history records through functional layer. By implementing the code analysis engine and improving the engines of version control software and build tools, functions such as monitoring code update, compiling source code and code rule inspection are enabled in the built system.Through practical projects verification, the built code rule automatic inspection system, which relies on little artificial participation, can find most of the code defects and problems, saving the code testing time for developers and reducing the potential risk. As a consequence, this system is of great importance for improving test efficiency and effectiveness.