Software Error Handling

Software Review

• Software review is a systematic examination of a document to find and resolve errors and defects in the software during the early stages of SDLC.
• It is usually performed manually to verify documents like requirements, system designs, codes, test plans, and test cases.
• It improves the productivity of the development team, makes testing time and cost-effective, and reduces the cost of the whole process.

Importance of Software Review

• It helps reduce the cost of rectifying defects in the later stages.
• It trains technical authors for defect detection and prevention processes.
• It eliminates inadequacies and defects, leading to a technically sound document.
• It results in a dramatic reduction of time taken to produce a technically sound document.

Testing vs. Debugging

• Testing is a stage of SDLC, composed of validation and verification of software.
• Testing is initiated after the code is written and can be done manually or automated.
• Debugging is a consequence of testing, seeking to match symptoms with causes to correct errors.
• Debugging is always manual and cannot be automated.

Metrics and Measurement

• Metrics are used to measure attributes like weight (e.g., "Kilogram" measures weight).
• In software, metrics are used to measure attributes like "How many issues are found in a thousand lines of code?"
• Measurements are used to generate metrics, and test metrics are used to take decisions for the next phase of activities.

Test Metrics

• Examples of test metrics include "How many defects exist within the module?" and "What is Test coverage %?"
• Test metrics are used to estimate the cost and schedule of future projects, understand the improvements required to succeed, and take decisions on process or technology modifications.

Test Report

• A test report can be generated to show the number of test cases designed per requirement.
• It is calculated by differentiating between expected and actual results.
• It raises due to design issues, coding issues, or system specification issues.

Error, Fault, and Failure

• Error occurs due to design issues, coding issues, or system specification issues.
• Fault occurs due to lack of resources or not following proper steps, leading to unintended behavior.
• Failure is the accumulation of several defects, leading to software failure and loss of information.

Walkthrough

• Walkthrough is an informal process led by the authors to achieve a common understanding and gather feedback.
• It is useful for people not from the software discipline, who are not used to understanding software development processes.
• The goals of a walkthrough include presenting documents to gather information, explaining or transferring knowledge, and evaluating the contents of the document.