In practice, carried out with using the embodiment of FIG brain design, the need to come out first two centers: "needs analysis" and "module cases analysis" .
For a clear demand, the main reference indicators summarize the following points:
Software Development Contract
Project Development Plan
System / subsystem design documents
Software requirements specification (including Interface Requirements Specification)
User requirements specification
Software Design Description
For inheritance demand , mainly upstream content of the project or product needs or existing indicators, which together often overlooked is the easiest place to come up with statistical analysis so alone. As before doing the project, there have been a version exists, and after a lot of testing and practice, but also made various modifications and improve demand, then in the design of this project needs analysis properties, it should inherit the previous version available or demand indicators, but avoid analysis is not in place, resulting in project quality, but off a clear need for this project.
Therefore, the reference index inherited demand, summed up the following points:
Related products or on a version of the software requirements specification
Related products or on a version of the test requirements or test report
Related product or a previous version and encountered summary of issues to be addressed in the course of
Implied demand indicators need to think very experienced test designers, project or product to be very familiar with, and even the product Quantity clarity.
The main references such as:
For product usage scenarios combing data
The product relevant industry standards
Non-professionals do not know the characteristics of the indicators (such as six requirements, stability requirements)
Installation testing and quality characteristics of the sub-aspect of the ease of installation (portability), respectively.
Installation testing has two purposes:
The first is to ensure that the software can be installed properly under different conditions normal and abnormal situations: for example, for the first time to install, upgrade, complete or custom installation, the installation can be carried out successfully. Complete or custom uninstall, can be unloaded. Abnormal conditions include insufficient disk space, lack of directory create permissions, etc., can be normal or in response to treatment.
The second purpose is to verify the software is running properly immediately after installation. This usually refers to a large number of test cases to run functional tests developed.
Installation tests include testing and installation manual installation code: installation manual on how to install, install the code to install some programs to run to provide the basic data.
Installation according to conventional test object is mounted can be seen to be covered of the following types:
installation
upgrade
Uninstall
