EM-PRD-03 · Subject model · W1
Requirements and expected behavior
Requirements, constraints, acceptance criteria and traceability to the solution. An implementation task references a requirement.
Queued for research
Claude: not-started; Grok: not-started.
Research note, in Russian: Entire research brief pending
Subject boundary and candidate types
- Requirement
- AcceptanceCriterion
- RequirementBaseline
- TraceLink
Deep research questions
- How to distinguish a need, a requirement, a feature and a task?
- What changes when a new baseline is set?
- How to represent a conflict between requirements of different stakeholders?
Verifiable invariants
- The requirement version is pinned at acceptance
- A closed task does not prove fulfillment
- A conflict does not erase the alternative
End-to-end acceptance scenario
Verify one requirement with three tasks and a failed test, then the compatibility of two baselines.
Negative case
Moving a ticket to Done automatically confirms all linked requirements.
Approaches to compare
- TM Forum SID: product/service/resource and commercial roles
- IDTA AAS: physical assets and composite descriptions
- Product management and engineering configuration; compare selected PLM and software practices
Candidates in the live catalogue
- WM-REC-006 · Requirement · unversioned · not installed automatically
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-KNW-013 · Constraint / Requirement Rule · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card.
Result requirements
Every card is executed together with the full research contract: definitions, fields and cardinalities, lifecycle, sources, data mastership, rights, the five object facets, at least eight invariants, positive and negative examples, dependencies, migration and applicability limits.