The Design And Realization Of JBFT

With the greater scale of software system and the expanding of the complication, the request to the software quality is getting more and more. With the development of the technology in software project, as a good way to ensure the software quality, the purpose of the software test is to find and modify the mistakes in software as much as possible, which is very complicated and important in software life circle and very meaningful in ensuring software quality.On the base of the development of black test and white test, many new software test methods have been developed recently, such as fault-oriented method,object-oriented method,security test and so on. The advantage of the fault-oriented method is following:(1) Good direction and easy testing for the defined fault pattern.(2) The problem, that the test methods can not detect the fault like memorizer leak once, can be resolved.(3) The situation, that efficiency of the other test methods to detect the fault which appears rarely is very low, can be voided.Because of the above advantages, this method has been applied and developed quickly. The key to the application of the method is to define the fault which is practical, measurable and precise.The actuality of the software test technology and the meaning of software test were analyzed at first, and the definition of the software test was presented. Then some methods and model of software test were introduced, especially static test and fault-oriented methods. My main work was discussed at chapter 3 and chapter 4. Two aspects were studied, one is about the design of JBFT and the other is about fault pattern.At chapter 3, the whole design of JBFT was analyzed at first and then elaborated on the abstract syntax tree,control graph,symbol table,accounting detect point was introduced briefly.At chapter 4, the patterns, including fault pattern,security vulnerability,performance fault pattern and subsequence fault pattern in Java were elaborated on, whose general form and attribution were introduced and the importance of guaranteeing the software quality was analyzed.