This sequential software life cycle model moves through its phases in a fixed order, with each phase completed before the next begins.
Waterfall
This architecture pattern splits a system into two roles: one that requests services and one that provides them.
Client-server
This term refers to a deviation from expected behavior that causes the software to fail to meet requirements.
Defect
This document laid out Agile's 4 core values and 12 principles.
Agile Manifesto
This SQL command retrieves/reads data from a database table.
SELECT
Name the five phases of the Waterfall software life cycle, in order.
Concept → Requirements → Design → Development → Test → Maintenance
This design quality means breaking a system into smaller, independent, self-contained components or modules.
Modularity
This activity asks "Are we building the product right?" and checks the software against its given specifications.
Verification
This Scrum role is described as the coach, facilitator, and conflict negotiator for the team.
Scrum Master
This is the software system used to store, manage, and interact with databases (e.g., MySQL).
DBMS (Database Management System)
These requirements describe what the system must do (its features and behavior), as opposed to qualities like performance or security.
Functional requirements
UML diagrams split into these two broad families: one showing the system's static structure, the other showing how it behaves over time.
Structural vs. behavioral diagrams
This testing level focuses on the smallest, isolated piece of software, a single module or function, with no dependencies.
Unit testing
This Agile approach uses a board with columns and limited work-in-progress to visualize flow, drawing on lean principles.
Kanban
This key uniquely identifies each record in a table.
Primary Key
The system has shipped, and your team is now handling change requests and bug reports from users. Which Waterfall phase is this?
This design principle says to reduce the gap between real-world problems and the software solution, making the design easier to understand.
Reduce intellectual distance
In top-down integration testing, these placeholder pieces of code stand in for lower-level modules that aren't ready yet.
Stubs
This estimation technique has team members privately pick cards from a Fibonacci-like sequence (1, 2, 3, 5, 8, 13…) to size work.
Planning Poker
This SQL operation combines rows from two or more tables based on a related column between them.
JOIN
What are the 3 characteristics of a good requirement?
Complete, Consistent, and Unambiguous
This architecture pattern structures an application as a collection of small, independently deployable services rather than one single unit.
Microservices
This form of testing is performed by the customer or end-user to confirm the system meets business needs and the desired UX
User Acceptance testing
Name any three of the five Scrum events/ceremonies.
The Sprint, Daily Scrum, Sprint Planning, Sprint Review, Sprint Retrospective (any three)
This key is a column in one table that references the primary key of another table, linking the two together.
Foreign Key