The formal definition of software defects meets the following five rules to call software defects: 1. Software does not meet the function of the product manual. 2. The software has shown a product manual indicating the error that does not appear. 3. Software function exceeds the product manual indicated scope 4. Software Not reaching the product manual, although not indicated, but the target, the software tester believes that the software is difficult to understand, not easy to use, slow running, or end users think bad. Software testers can find out software defects as early as possible and make sure they are fixed. Software tester should have the quality - exploration spirit (like to get new software) - Troubleshooting expert (good at discovering the problem) - unremitting efforts (non-stop attempt) - creativity (think of creative or even extraordinary means to find defects ) - Pursuit of perfection (but don't ask for something that you can't enter, you don't want to ask) - accurate (determine the test content, test time, whether the real defect) - Old practice stability (know how to tell the programmer, know how to keep enough Programmer cooperation) - persuasive (good at expressing views, why must be fixed by defecting defects by actual demo)
Software development model
The process from initial conception to the public release software product is called software development model.
-
Big stick (either success, either fail)
-
Write a modified mode (there is no time to do well, there is always a time rework)
-
Water-water (creative, analysis, design, development, testing, product step by step, can not be retired. The previous step is completed to enter the next stage)
-
Spiral (main thinking is: Start do not have to define all details. From small start, important functions, efforts to implement, accept customer feedback, then enter the next phase. A spiral includes 6 steps: 1. Determine the target, options and Restriction conditions; 2. Point out and resolve risks; 3. Assessment scheme; 4. Development and testing in this stage; 5. Plan a next stage; 6. Determine the next phase of the next phase)
Terminology - accurate VS precise
- Accurate: References are targets. The closer to the target, the more accurately - precise: the reference is the result of each implementation. The closer the results of each other, the more accurate it. But with the target may have a very far term - verify the legality check - Verification: Guarantee the process of the software in line with the product manual - legitimate examination: to ensure that the software meets the process of user requirements. Many times the product manual does not fully reflect the user's request! Terminology - Test VS Quality Judgment (QA) - Test: The object of software tester is to find software defects and make some as possible to ensure repair. - Quality judge: The main accusation of software quality judges is to create and strengthen the standards and methods of promoting software development and preventing software defects.
