Prototyping and Quality Assurance

These flashcards cover key concepts related to software prototyping and quality assurance, focusing on techniques, methodologies, and definitions essential for understanding the topic.

Software Quality Assurance

A set of activities that define and assess the adequacy of software processes to ensure the delivery of software products of suitable quality.

Prototyping

A method of building software prototypes that display the functionality of an application under development.

Throwaway Prototyping

A prototyping method that generates insights about design and is discarded after obtaining feedback.

Evolutionary Prototyping

A prototyping approach where prototypes are reused and modified according to test results, evolving into the final product.

Low-Fidelity Prototyping

Prototypes that are designed to check visual appearance and user flows, often using paper-based or sketch techniques.

High-Fidelity Prototyping

Prototypes that are closely aligned to the final product and usually created in the form of programming code.

Fagan Inspection Methodology

A formalized peer review process developed to identify and remove errors in software products.

Software Artifacts

Documents and materials produced during software development that can be inspected, such as requirements documents and source code.

Structured Walkthrough

A peer review process where the author of a deliverable guides reviewers through the work to gather feedback.

Code Review

The act of systematically checking each other's code to ensure it adheres to quality standards.

Tool-Driven Code Review

An approach to code reviewing that relies on automated tools to identify potential issues in the source code.

Developer-Driven Code Review

A manual process where developers assess each other’s code for issues before deployment.

Technical Debt

The implied cost of future rework caused by choosing an easy solution now instead of a better approach that would take longer.

Pull-Based Development

A development approach where changes are proposed through a pull request for review before being integrated into the central repository.