1/47
Looks like no tags are added yet.
Name | Mastery | Learn | Test | Matching | Spaced |
---|
No study sessions yet.
Software Quality Assurance
A set of activities ensuring the software development process and its products meet established quality standards.
Software Quality
The degree to which a software product meets the gathered requirements.
Defect Prevention, Detection, and Removal
Core activities of software quality assurance aimed at improving software quality.
Software Review and Inspection
A structured peer-review process used to detect and correct defects in software artifacts.
Software Artifacts
Documented items from the software development process like requirements, code, documentation, test plans.
Fagan Inspection Methodology
A formal software inspection process developed by Michael Fagan, focusing on error detection and process improvement.
Moderator (Fagan)
Leads the inspection team and handles logistics.
Author (Fagan)
Creator of the artifact being inspected, responsible for defect fixes.
Reader (Fagan)
Experienced peer who understands the artifact.
Tester (Fagan)
Writes and executes test cases, focuses on product testing.
Planning (Fagan Activity)
Identify roles, verify materials, distribute materials, arrange meetings.
Overview (Fagan Activity)
Author briefs participants on the artifact.
Preparation (Fagan Activity)
Inspectors prepare, read deliverables, use checklists, mark issues.
Inspection Meeting (Fagan Activity)
Inspectors identify defects, record/classify them, agree on outcomes.
Rework (Fagan Activity)
Author corrects defects and investigates issues.
Follow-up (Fagan Activity)
Moderator checks if defects have been resolved.
Process Improvement (Fagan Activity)
Root cause analysis, recommendations for process improvement.
Requirements Inspection
Finds requirement defects, confirms correctness of requirements.
Design Inspection
Finds design defects, ensures design matches requirements.
Code Inspection
Finds code defects, ensures code matches design/requirements.
Test Plan Inspection
Finds defects in test plans, ensures test cases verify design/requirements.
Structured Walkthrough
Peer review where the author presents a document or code to reviewers for feedback.
Review Leader (Walkthrough)
Chairs the walkthrough meeting.
Scribe (Walkthrough)
Records errors, decisions, and actions during the meeting.
Walkthrough Step 1
Author circulates the deliverable.
Walkthrough Step 2
Author schedules a meeting.
Walkthrough Step 3
Reviewers read the deliverable.
Walkthrough Step 4
Review leader leads the meeting.
Walkthrough Step 5
Author explains the deliverable and requests feedback.
Walkthrough Step 6
Scribe records observations.
Walkthrough Step 7
Outcome is agreed and revisions made.
Walkthrough Step 8
Deliverable is re-circulated for sign-off.
Walkthrough Step 9
Author stores comments and sign-offs.
Code Review
Systematic check of code to ensure it meets standards and is free of defects.
Tool-Driven Code Review
Uses automated tools/IDEs to find code issues.
Developer-Driven Code Review
Developers manually review code to find hard-to-detect quality issues.
Modern Code Review
Lightweight, tool-based review process that doesn’t require face-to-face meetings.
Repository-Based Review Tools
Tools like Gerrit or CodeFlow integrated with version control for code review.
Pull-Based Development
Uses pull requests for code review and integration by authorized developers.
Technical Debt
The cost of additional rework caused by choosing an easy or limited solution now instead of using a better approach.
Prototyping
Building a software model to test and clarify requirements early in the development process.
Throwaway Prototyping
Fast prototypes discarded after feedback, used in early stages.
Evolutionary Prototyping
Prototypes evolve into the final product, used in later stages.
Low-Fidelity Prototyping
Simple, rough design (e.g., paper-based) to test layout and flows.
Paper-Based Prototyping
Hand-drawn UI mockups to explore and refine ideas.
Wireframing
Visual representation of UI structure
Wireframing Tools
Balsamiq, Axure, MockFlow, Adobe XD.
High-Fidelity Prototyping
Detailed, functional prototypes using actual code and tools.