How QA Can Effectively Participate in Technical Design Reviews

Background: As quality assurance (QA) becomes involved throughout the software development lifecycle, its role extends beyond testing to influencing project progress and quality at every stage.

Why QA should join technical design reviews: Participation helps correct misunderstandings of requirements, provides a basis for test plans, assesses impact scope, and evaluates risk, enabling early bug prevention and better test coverage.

Efficient QA involvement: The review process is divided into three phases:

Before the review: Ensure all relevant participants are notified, study requirement and design documents, and annotate questions.

During the review: Verify that the design meets requirements, examine flowcharts, system interaction diagrams, configuration components (Apollo, cache, MQ, scheduled tasks), database schema, completeness of design, reuse or modification of existing interfaces, definition of new interfaces, third‑party interfaces, external APIs, impact assessment, testability, data compatibility, and performance metrics for core interfaces.

After the review: Follow up on action items, communicate responsibilities, and design test plans (select test methods, write cases, prepare data or scripts, and assess risks).

Project practice example: In a third‑party advertising integration project, QA performed the above steps, identified inconsistencies in the flowchart, suggested lower‑impact design alternatives, evaluated two requirement points (third‑party user identification and bypassing commercial user checks), compared schema‑extension versus new table solutions, and selected the latter based on impact assessment.

Through this systematic involvement, QA clarified responsibilities, reduced test scope, achieved high project quality with minimal defects, and demonstrated the value of QA in design reviews.