1 / 7

Lifecycle of Testing

Explore the terminology, verification and validation processes, and testing relationships in the lifecycle of software testing. Learn about static and dynamic analysis, bug, defect, fault, failure, error, and more to enhance your software quality assurance knowledge.

mohammedc
Download Presentation

Lifecycle of Testing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Lifecycle of Testing CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 6, 2007

  2. Outline • Terminology • How does V&V fit in the lifecycle? • Waterfall lifecycle • Testing Relationships

  3. Terminology from IEEE Glossary (1) • bug: See fault • defect: See fault. • fault: A manifestation of an error in software. A fault, if encountered, may cause a failure. • failure: The inability of a system to perform a required function within specified limits. A failure may be produced when a fault is encountered • error: Human action that results in software containing a fault

  4. Terminology from IEEE Glossary (2) • static analysis: The process of evaluating software without executing it. • dynamic analysis: The process of evaluating software based on its execution.

  5. Terminology from IEEE Glossary (3) • verification: The process of determining whether or not the products of a given phase... fulfill the requirements...Did we build it right? • validation: The process of evaluating software... to ensure compliance with software requirements.Did we build the right thing?

  6. Requirements High-level Design Low-level Design Code Unit Testing Integration Testing System Testing Acceptance Testing Waterfall Lifecycle

  7. Requirements High-level Design Low-level Design Code Unit Testing Integration Testing System Testing Acceptance Testing Testing Relationships

More Related