SEF9 - 54 About software testing, software errors, testing documents

SOFTWARE ERRORS AND RELATED TERMS
===========================================================

SOFTWARE ANOMALY (IEEE)
==================================
anything observed in the documentation or operation of software that deviates from expectations based on previously verified software products or reference documents.

SOFTWARE BUG
==================================
(1) things the software does that it is not supposed to do, [or] something the software doesn't do that it is supposed to.

(2) a fault in a program which causes the program to perform in an unintended or unanticipated manner.

(3) any deviation between the customer's expectation, the specification, and/or implementation.

SOFTWARE CRASH (IEEE)
==================================
the sudden and complete failure of a computer system or component.

SOFTWARE DEFECT
==================================
(1) (IEEE) a product anomaly;

(2) synonymous with fault, both imply a quality problem discovered after the software has been released to end-users (or to another activity in the software process); [Pressman, 203]

(3) fault; [SWEBOK, Ch.5, p.6]

(4) error, fault, or failure;[SWEBOK, Ch.11, p.9]

(5) non conformance to requirements.

(6) a deviation between the specification and the implementation, detected after release to the customer (or the next activity in the software process).

SOFTWARE ERROR
==================================
(1) (ISO) a discrepancy between a computed, observed, or measured value or condition and the true, specified, or theoretically correct value or condition;

(2) a quality problem discovered by software engineers (or others) before the software is released to the end-user (or to another activity in the software process). [Pressman, 203]

(3) any observed event (incident) or detected deviation between the specification and the implementation.

SOFTWARE EXCEPTION (IEEE)
==================================
an event that causes suspension of normal program execution; types include addressing exception, data exception, operation exception, overflow exception, protection exception, underflow exception.

SOFTWARE FAILURE (IEEE)
==================================
the inability of a system or component to perform its required functions within specified performance requirements.

SOFTWARE FAULT
==================================
an incorrect step, process, or data definition in a computer program which causes the program to perform in an unintended or unanticipated manner.

SOFTWARE MISHAP (DOD)
==================================
an unplanned event or series of events resulting in death, injury, occupational illness, or damage to or loss of data and equipment or property, or damage to the environment.

SOFTWARE MISTAKE (IEEE)
==================================
a human action that produces an incorrect result, and the subject of the quality improvement process.

SOFTWARE RISK (IEEE)
==================================
a measure of the probability and severity of undesired effects; often taken as the simple product of probability (CHANCES) and consequence (IMPACTS).

SOFTWARE SIDE EFFECT
==================================
an unintended alteration of a program's behavior caused by a change in one part of the program, without taking into account the effect the change has on another part of the program.


===========================================================
IEEE 829 test plan structure
===========================================================

IEEE 829-2008, also known as the 829 Standard for Software Test Documentation, is an IEEE standard that specifies the form of a set of documents for use in defined stages of software testing, each stage potentially producing its own separate type of document.[1]

Test plan identifier
Introduction
Test items
Features to be tested
Features not to be tested
Approach
Item pass/fail criteria
Suspension criteria and resumption requirements
Test deliverables
Testing tasks
Environmental needs
Responsibilities
Staffing and training needs
Schedule
Risks and contingencies
Approvals


===========================================================
See the attachments.


--
WASSALAM
wruslan.hahaha

Attachments:
Example-Test-Log.png
Example-Test-Schedule.png
Example-Test-Specification.png

Full Version with Microsoft Word Version and Attachments
Return to Software Engineering Fundamentals (SEF9MMUWRY)
Previous Topic: IEEE Software Test Documentation Standards (What and Why)
Next Topic: 55 Programming Concepts Lesson 04 (Floating Point numbers are not exact)