Determine the software system type
Batch (general)
2. Event control
3. Processing control
4. Regulation control
5. Advanced Mathematical Model
6. Message Process
7. Diagnostic software
8. Sensor and signal processing
9. Simulation
10. Database management
11. Data acquisition
12. Data representation
13. Decision and plan assistance
14. Graphics and image processing
15. Computer System Software
16. Software Development Tool
Determine the scope of the project
The scope of the project usually defines the scope of the test. Consider the following questions:
Development of new systems:
1. Which business processing will be affected?
2. Which business areas will be affected?
3. Does the existing system have interfaces
4. Whether the existing system will be affected
Improvements to existing systems:
1. Is it just a correct error?
2. Whether to maintain redesigned standards
3. Do you find some potential defects in addition to increasing the wrong
4. Is it affected by other systems?
5. Is there a return risk?
Determine how to test
Test should be performed at all stages of the project.
A: Demand stage behavior
1. Determine the test strategy
2. Determine if the demand is appropriate
3. Create function test conditions
B: Design phase behavior
1. Determine demand design compliance
2. Determine if the design is appropriate
3. Create structure and function test conditions
C: Programming (creation) stage behavior
1. Determine the design compliance
2. Determine if the execution is appropriate
3. Create program / unit structure and function test conditions
D: Test phase behavior
1. Determine if the test plan is appropriate
2. Test application system
E: Installation phase behavior
1. Invest production of the test
F: Maintenance phase behavior
1. Modify and retest the system
Chapter 4 Determines Software Test Technology
concept
Structural testing and function test
The attributes you want to reflect the test set can be divided into the internal structure of the program in accordance with its programming function. Functional analysis is based on an error in finding a requirement or design specification.
2. Test methods can be divided into dynamic and static.
Dynamic analysis requires execution program. That is, based on the test case running program, the result is compared to the desired result value, see if it is consistent. Static analysis usually does not need execution programs, such as syntax check is one of the commonly used static analysis technology. .
3. Artificial testing and automatic test
The tests performed by the person are called manual testing, and the test automatically performs automatic testing.
Structured system test technology
1. Pressure test: Determine the system in a desired capacity (allocated enough disk space, there is a sufficient communication channel)
2. Implementation test: The system can achieve the desired proficiency (full of transaction time, good hardware and software)
3. Recovery test: After system failure can be restored to an operational status (introduction failure, evaluate the fullness of backup data)
4. Operation test: The system is executed in normal operating conditions (the determination system can run according to the document, the JCL work control language is sufficient)
5. (with the process) Consistency test: The development of the system is consistent with the standards and procedures (executed according to standards, the document is complete)
6. Safety Test: Protect the system according to the importance of the organization (access refusal, appropriate procedures)
Chapter 5 Software Test Tool Selection and Installation
Chapter 6 11 Step Software Test Process Overview
Defects in the application system include:
Inappropriate demand explanation
2. User specified error requirements
3. Did not get the needs of the correct record
4. Incorrect design specifications
5. Incorrect program specifications
6. Error program encoding
7. Error program structure or instruction
8. Error data entry
9. Error repair
10. Other defects caused by repairing the work
11 step software testing process
1. Assess development plan and status
2. Develop a test plan
3. Test software requirements
4. Test Software Design 5. Test Software Construction
6. Execute test
7. Acceptance test
8. Report test results
9. Test software installation
10. Test software change
11. Evaluation test effectiveness
Chapter 7 Evaluation of Estimation and Status of Project Management
Problem
Incorrect estimate
2. Incorrect development process
3. Incorrect status report
It is difficult to get a good estimate:
1. I don't understand the software development and maintenance process.
2. The impact of the restrictions on various technologies and management are not very understanding
3. It is considered that each project is special, thus limiting the comparison between the project.
4. Lack of historical data that can be used to check the model
5. Lack of historical data for calibration
6. Definition inadequate estimation goals
7. Insufficient estimation range specification
8. Not enough for the premise of estimates based on the premise
Test the status of the software system
For project status, the test is a simple point accumulation system for metric progress. This point accumulation system can compare the project management or account system that generates progress report. If the results obtained by the two progress metrics systems are very different, the testers have reason to question the results generated by the project management and account systems.
1. Overview of points cumulative tracking system
The increasing complexity of software systems and structural and modular design requirements are doubled, and the number of software elements that have been developed and faithd on the simulation program have increased. Increased elements, coupled with the "soft" milestone for metrics, making monitoring for software development and a large subjective color for future process time consumption, and often unreliable.
2. Typical performance metrics
