Which of the following would you NOT usually find on a software incident report?

Question

Options

• AThe name and/or organisational position of the person raising the problem.
• BVersion of the Software Under Test.
• CSuggestions as to how to fix the problem.
• DActual and expected results.

• A
  4% (1)
• B
  8% (2)
• C
  72% (18)
• D
  16% (4)

Explanation

Option C is correct because a software incident report (also called a defect or bug report) is a factual document - its purpose is to describe the problem objectively, not to prescribe a fix. Suggesting how to fix the problem is the responsibility of developers during the resolution phase, not the reporter's job when logging the incident.

Why the distractors are wrong:

• A is expected on an incident report - you need to know who raised it for accountability and follow-up.
• B is essential - without knowing which software version is affected, the defect cannot be reliably reproduced or tracked.
• D is the core of any bug report - the gap between what actually happened and what should have happened defines the defect itself.

Memory tip: Think of an incident report as a journalist's account - it answers Who, What, and Where (reporter, version, actual vs. expected results), but it does not editorialize by telling developers how to solve the problem. "Report the bug, not the fix."

No community discussion yet for this question.