A practical, copy/paste Provenance Requirements Template for business analysts, systems analysts, and product managers building AI-enabled features. Use it to specify “Why should I believe this?” as testable requirements: citations and sources, freshness SLAs, confidence/uncertainty behavior, conflict handling, “what changed” explanations, and audit export fields. Includes ready-to-fill tables and a minimum set of validation tests so provenance becomes shippable product behavior—not a vague guideline.

A copy/paste Guardrails Catalog you can use to turn vague AI “be safe” guidance into testable Allowed / Not Allowed requirements. Includes a blank catalog table plus 10 starter guardrails written in acceptance-criteria style (forbidden actions, restricted data, safe defaults, refusal wording, and validation steps). Designed for business analysts, systems analysts, and product managers shipping AI-enabled features.

The purpose of this spreadsheet is to present details of a meta-model that can and has been used to extend Requirements Management (RM) or Application Lifecycle Management (ALM) tools. The rationale for applying these extensions is discussed in the article: Tool Support for Managing Requirements [In Context]

The purpose of this spreadsheet is to present an example of detailed requirements for a data import interface. The example is part of the Trips-R-You Flight Booking Case Study. It's purpose is to provide an integrated, end-to-end set of requirement examples.