Timedora
Free Online Flashcard Deck

Application Problem Reporting Free Online Flashcards

Study Application Problem Reporting with 12 free online flashcards. Review key terms, definitions, and concepts with this interactive flashcard deck.

12 cards
01
Front

What system details belong in an application problem report?

Back

Record the application name and version, operating-system name and version, and the device or environment.

02
Front

How should a triggering event be documented?

Back

Describe the exact action that triggered the problem and the result that followed.

03
Front

Why preserve an error’s exact wording and code?

Back

Preserve the exact error wording and code; different errors can indicate different failure stages.

04
Front

What timing information should a problem report include?

Back

Note when the problem began and how often it occurs.

05
Front

What should a report say about who is affected?

Back

State whether the problem affects one user or multiple users.

06
Front

Which recent changes are useful to document?

Back

Note recent changes, such as an application or operating-system update, a new driver, or a changed setting.

07
Front

What should a report say about previous troubleshooting?

Back

Record what has already been tried and what happened after each attempt.

08
Front

Why is “Installation fails” an insufficient problem report?

Back

“Installation fails” is too general; specify observable details such as the version, failure point, and error.

09
Front

What installation details make a failure report more specific?

Back

Include the application version, the point where installation stopped, and the displayed error.

10
Front

What attempt and device details can clarify an installation failure?

Back

Say how many attempts failed and identify the affected computer.

11
Front

What comparison can help contextualize an installation failure?

Back

Report whether installation succeeds on another computer with the same operating system.

12
Front

How should a user describe a problem before its cause is known?

Back

Describe what happened without assuming what caused it; an observable report is easier to test.