Requirements Engineering
Requirements engineering is the discipline of eliciting, analyzing, prioritizing, and maintaining what a product must do — turning fuzzy needs into clear, testable, traceable requirements.
Good requirements are specific and testable, prioritized against value and effort, and traceable back to the evidence and problem that justify them. Poor requirements are vague, unprioritized, and disconnected from why they exist.
The hardest part is not writing requirements once, but keeping them coherent as they change — which requires traceability between a requirement and everything it affects downstream.
A requirement "users can reset their password" is refined into testable criteria (email link, expiry, rate limiting), prioritized as P0, and linked to the prototype screens and PRD section that realize it.
ArcPM analyzes requirements — prioritizing them and keeping each one traceable to its research and to the prototype and PRD that realize it — inside the Connected Product Graph, so impact is visible when anything changes.
See ArcPM