Requirements and Acceptance Criteria
Build a documentation assistant for a fictional SaaS product. It ingests Markdown, HTML, and PDF; supports updates and deletions; answers with citations; abstains when evidence is insufficient; and enforces tenant permissions. Include source registration, parse status, chunk preview, retrieval, answer endpoint, citation links, evaluation runner, and trace viewer.
Acceptance criteria must be testable: no cross-tenant results in security tests, no fabricated citation IDs in the evaluation set, and a measured recall target agreed by stakeholders.
Implementation example
INGESTION: versioned, resumable, delete-aware
RETRIEVAL: hybrid baseline + ranking experiments
ANSWERS: citations + abstention + conflict handling
SECURITY: tenant isolation + injection tests
OPERATIONS: traces + cost + rollback
EVALUATION: gold set + release gate💡 Define acceptance criteria before implementation.
Key Takeaways
- Inspect the relevant pipeline stage instead of guessing.
- Preserve source provenance, versions, and access scope.
- Measure quality on representative queries.
Knowledge Check
Which is a meaningful acceptance criterion?