Software Testing Requirements Management methods

In the course of the project, software testing requirements are not unchanged, with the project, the project "Business Requirements Specification", "Software Requirements Specification", "Interface Specification", "design specifications" are likely to change, the corresponding software testing requirements may also change; In addition, software testing strategy, The adjustment of the software testing method may lead to the adjustment of the test requirement, which needs to be managed by the standard method, including four test requirements management activities: Requirement review, requirement change control, requirement tracking and requirement consistency check.

Test Requirements Review

After the user acceptance test requirements analysis and export process, users will receive the first draft test requirements. The Business Management Department shall organize the relevant business personnel, technical personnel, environmental management personnel, testers and other relevant personnel to conduct user acceptance test needs review to ensure agreement.

Similarly, the test Management department should organize the relevant technicians, environmental managers, testers and other relevant personnel to the system connectivity test requirements analysis derived system connectivity test requirements, the system integration test requirements Analysis of the system integration test requirements to review, and indeed Security system connectivity test requirements and system integration test requirements pass the review.

For internal test requirements analysis, the internal testing requirements should be organized by the Quality Control Department of the Development Center to evaluate the relevant business personnel and development project team to ensure agreement.

When all kinds of test requirements pass the review, they will be imported into the MQC for version identification and unified management.

Test requirement Tracking

The tracking of test requirements is achieved by establishing a two-way tracking relationship between the test requirements and the source and the test cases. The specific:

1, the establishment of user acceptance test requirements and business requirements specifications, and user acceptance test cases between the two-way tracking relationship;

2, the establishment of system integration testing requirements and software requirements analysis specifications, and system integration test cases between the two-way tracking relationship;

3, establish (System) connectivity test requirements and outline design specifications, and (System) connectivity test cases between the two-way tracking relationship;

4, the establishment of unit test requirements and detailed design specifications, and unit test cases between the two-way tracking relationship;

5, the establishment of internal testing requirements and software requirements analysis specifications, and detailed design specifications, and internal test cases between the two-way tracking relationship.

When a requirement change occurs, the change impact scope can be analyzed based on this bidirectional tracking relationship. For a change to a business function, you can analyze which software requirements functions this change will affect, whether these software features need to be changed, which design modules, code files, test requirements, test cases will be affected, and whether they need to be changed.

QC can manage the bidirectional tracking relationship between test requirements and test cases, but cannot manage the bidirectional tracking relationship between system outline design specifications, System detailed design specifications, software requirements analysis specifications, business requirements specifications and their test requirements. This requires separate requirements management tools, such as Telelogic Doors or requirements management tools such as IBM Rational Requesitepro, and can be manually managed using Excel tables, without these professional requirements management tools.