1/25
Vocabulary flashcards covering software quality assurance, prototyping paradigms and fidelities, formal software inspection techniques, and modern code review workflows.
Software Quality
The degree to which a software product meets the gathered requirements.
Software Quality Assurance
A set of activities that define and assess the adequacy of software processes to provide evidence establishing confidence that they produce products of suitable quality, involving defect prevention, detection, removal, and containment.
Technical Debt
The long-term development and maintenance costs incurred by producing poor quality software.
Software Prototyping
The process of building software application prototypes that display the functionality of the product under development, though they may not contain the exact logic of the original software.
Throwaway Prototyping
A relatively fast prototyping method focused on generating insights about design ideas, where created prototypes are discarded after testing and feedback.
Evolutionary Prototyping
A prototyping paradigm where prototypes are altered according to test results, reused across test cycles, and ultimately evolve to become the final end product.
Prototype Fidelity
The degree to which a prototype conveys the look and feel of the final product, ranging from low-fidelity to high-fidelity.
Low-Fidelity Prototyping
Prototyping focused on checking and testing the visual appearance and user flows of a software system.
Paper-Based Prototyping
A low-fidelity technique used to create prototypes based on hand drawings representing user interfaces, enabling quick exploration and refinement of designs.
Wireframe
A visual representation of a product page used by developers to arrange user interface pages and create interactive prototypes by linking them together.
High-Fidelity Prototyping
Prototypes built using programming code and Integrated Development Environment (IDE) software when developers have a solid understanding of the design and need testing with actual users.
Software Artifacts
Any items documented and stored during the software development process, including requirements documents, source code, user documentation, test plans, and test cases.
Software Inspection
A formalized peer review process for detecting and correcting defects or bugs in software artifacts.
Fagan Inspection Methodology
A formal inspection methodology developed by Michael Fagan with the objectives of removing errors from software products and identifying systematic defects in software processes.
Moderator (Fagan Inspection)
The inspection team participant who manages logistics, leads the team, keeps meetings focused, and verifies that the author resolves all defects.
Author (Fagan Inspection)
The creator of the software artifact who briefs participants, answers questions during meetings, corrects identified defects, and conducts investigations.
Reader (Fagan Inspection)
An experienced peer and subject matter expert on the software artifacts undergoing inspection.
Tester (Fagan Inspection)
The inspection participant responsible for writing and executing test cases, focusing on how the product will be tested.
Structured Walkthrough
A peer review in which an author guides one or more reviewers through a deliverable to obtain feedback on its quality and familiarize the audience with the work.
Code Reviewing
The act of systematically convening with fellow programmers to check each other's code for faults and confirm adherence to quality standards.
Tool-Driven Code Review
A code review approach utilizing automated code checkers or IDE analyzers to automatically detect problematic patterns within source code.
Developer-Driven Code Review
A manual review approach where developers read and understand the source code to evaluate its implementation, design, security, and maintainability before deployment.
Modern Code Review
A lightweight code inspection variant that operates via review tools and repository workflows instead of face-to-face meetings.
Repository
A central file storage location used by version control systems to store multiple versions of files accessible by multiple users.
Pull-Based Development
A modern development workflow enforcing code review where a developer clones a repository, makes changes, and submits a pull request rather than directly pushing commits.
Integrator
A privileged developer in pull-based development who examines pull request changes, integrates them with their local clone, and commits the code to the central repository.