Shulou(Shulou.com)06/03 Report--

1. Definition:

In addition to writing the case according to the requirements documents, the testers did not add the case formed by other project plans, development documents, etc.

Second, the period of occurrence

Always

Third, trap performance

1. Quality requirements (ease of use, reliability, robustness, portability, security, maintainability, etc.)

two。 Data requirements (e. G. statistical requirements)

3. Interface requirements (for example, when there are few iterative requirements, it is easy to ignore subtle new interfaces, or testers believe that the baseline functionality will not be affected)

4. Forced response to abnormal system (common machine stutter when submitting form, network exception)

IV. Negative consequences

1. Requirements-based testing does not show omitted behavior and characteristics.

two。 Management or other developers believe that the delivered system will work properly.

3. Testers must often discuss with the product or customer the requirements for omissions identified during testing.

4. The omitted requirements were not found during testing and the deployment system was delivered.

5. Omission of requirements leads to inadequate architecture design, which makes it more difficult for developers to troubleshoot Bug.

Fifth, the cause of emergence

1. The product personnel are not trained professionally, so that the logic of the requirements document is insufficient, such as not understanding the quality model and not describing the quality characteristics of the system.

two。 When missing requirements are found, the product staff does not update the demand pool and PRD in time.

3. The test case only defines the normal use case path, and the fault and failure tolerance are not fully defined.

4. Requirements have not been reviewed by other project managers

5. The product does not have sufficient time and resources to analyze the product.

VI. Suggestions

1. Preparation stage

Train the product related to the demand process for the missing requirements identified.

two。 Enable Pha

Provide professional training for product personnel to identify missing requirements.

Ensure that the test schedule includes sufficient time to resolve missing requirements found during testing.

3. Execution phase

The main contents are as follows: (1) the method of identifying missing requirements: end-to-end task thread model, use case modeling, quality model.

(2) static testing of requirements documents, taking into account errors, failures, and failure tolerance.

(3) the contents of requirements documents and requirements pool need to be reviewed by experts or business representatives.

(4) the omissions found in the testing process should be notified to the product in time.

4. Verification phase

(1) check whether there is enough requirement modeling.

(2) check whether the requirements take full account of errors, failures, and failure tolerance.

(3) check whether the appropriate quantity of quality and data requirements are included in the demand pool.

(4) check whether the requirements have been reviewed by a sufficient number of relevant personnel in the system.

(5) check whether product personnel have been notified of all missing requirements found during testing.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.