What content would be in an incident report if that incident report was based on the IEEE 829 Standard for SoftwareTest Documentation?

What content would be in an incident report if that incident report was based on the IEEE 829 Standard for SoftwareTest Documentation?

(i) Identification of configuration items of the software or system.

(ii) Software or system lifecycle process in which the incident was observed.

(iii) Description of the anomaly to enable reproduction of the incident.

(iv) Number of occurrences of the incident.

(v) Classification of the cause of the incident for metrics and for reporting purposes.

Number of correct answers: 1
A . i, ii, iii
B . ii, iii
C . i, iii, iv
D . i, ii, iii, v

Answer: C

Explanation:

According to the IEEE 829 Standard for Software Test Documentation, an incident report should contain the following information:

Identifier: A unique identifier for the incident report

Summary: A brief summary of the incident

Incident description: A description of the incident, including:

Date: The date when the incident was observed

Author: The name of the person who reported the incident

Source: The software or system lifecycle process in which the incident was observed

Version: The identification of configuration items of the software or system

Test case: The identification of the test case that caused the incident

Execution phase: The phase of test execution when the incident was observed

Environment: The hardware and software environment in which the incident was observed

Description: A description of the anomaly to enable reproduction of the incident

Expected result: The expected result of the test case

Actual result: The actual result of the test case

Reproducibility: An indication of whether the incident can be reproduced or not

Impact analysis: An analysis of the impact of the incident on other aspects of the software or system

Incident resolution: A description of how the incident was resolved, including:

Resolution date: The date when the incident was resolved

Resolver: The name of the person who resolved the incident

Resolution summary: A brief summary of how the incident was resolved

Status: The current status of the incident (e.g., open, closed, deferred)

Classification information: A classification of the cause and effect of the incident for metrics and reporting purposes

Therefore, among the options given in this question, only (i), (iii), and (iv) are part of an incident report based on IEEE 829.

Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments