Turn requirements into acceptance checks

Methods to understand

Express requirements as inputs, behavior, failure cases, and acceptance examples. A file upload needs size, format, error messages, permissions, and a visible success result. Include these requirements in the collaboration context.

Apply the method to a scenario

Requirement: implement input processing with permission checks.
Create normal, empty, oversized, and unauthorized cases.
Record actual and expected outputs and propose a minimal fix for differences.

Hands-on workshop

Write verifiable requirements for knowledge-base Q&A.

1. Define users, document scope, and questions the system cannot answer.
2. Specify normal, unanswerable, unauthorized, and outdated-material scenarios.
3. Set expected behavior, citation requirements, and failure messages for each.

Scenario: the material does not answer the question
Input: a question outside the document scope
Expected: state the evidence gap; do not invent citations
Acceptance: no nonexistent sources; identify the additional material needed

How to verify

Ask another person to judge the result using only your acceptance checklist. Record ambiguous criteria and revise them.

Practice task

Choose a case related to your work and practice "Turn requirements into acceptance checks". Submit inputs, steps, results, and verification records.

• Explain the task goal and inputs
• Provide actual results or runnable deliverables
• Identify errors, limits, and verification evidence