Some commonly used list of software design documents:
1) the structure of the document
Overall design of the software described in the document, including all software, as well as a description of the main part of the interaction between
2) data flow diagram
That the process of how data flows in the formal diagram. Sometimes referred to as a bubble diagram, because he is a circle and line painting
3) state transition diagram
Decomposition of the software as the basic state or condition of a formal diagram, indicate the different ways the state of inter-conversion
4) flow chart
Graphic description of the procedure with the traditional logic, are now popular in the
5) code Notes
Embedded in software code useful is extremely important to note, making it easier for programmers to maintain code code easily grasp the content and means of implementation.
Second, test documents
More important to submit a list of test
1) test plan (test plan): description of the software used to validate compliance with product specification and customer requirements of the program. Including quality objectives, resource requirements, schedule, task allocation, the method
2) test cases (test cases): the projects listed in the test, described in detail the steps to verify software
3) bug report (bug report): description of the implementation of test cases to identify problems, they can be recorded on paper, but through the records in the database.
4) testing and automated testing tools (test tools and automation): If the test group to test the use of automated software testing tools, whether it is prepared to buy or own the tools, the document must be recorded
5) Measurement, statistics and summary (metrics, statistics, summaries). A summary of the testing process, the use of graphics, tables, forms and reports.
Third, the software development life cycle model
Four kinds of the most commonly used model, other models of knowledge of these patterns only
1) Big Bang model
2) mode of writing and reform
3) Waterfall model
4) spiral model
Testers may experience all of the above model, you need to be taken in accordance with the model of the current project to customize the test method.
Fourth, small test
1, out in the programmers write code before the beginning of what tasks to complete?
Development teams need to understand customer needs, as defined in the product manual features. Detailed progress should be established to enable team members to know what have been done and what we need to do. Software system should be formed, after the design, testing, team members should begin to plan the work.
2, the formal and lock statement can not be changed whatever the shortcomings of the product?
If in the process of software development market to other customers, or to change direction, there will be no adjustment of the flexibility of software.
3, the Big Bang model of software development of what is the biggest advantage?
Simple, while others only.
4, and reform the use of writing mode, How do I know if the software release time?
Writing mode while no real change from the standard, unless the person or decided to put an end to progress.
5, why is it not good to use waterfall model?
Like salmon, it is very difficult to upstream. Followed every step of the step are independent, discrete process. If you come to find that some of the first things should be done earlier, I would like to retire on too late.
6, software testers favorite spiral mode why?
They have long been involved in the development process, have the opportunity to identify problems as soon as possible for the project to save time and money.







