← Back to catalogue
Published

Requirements and expected behavior

EM-PRD-03 · em-prd-03

Requirements, constraints, acceptance criteria and traceability to the solution. An implementation task references a requirement.

Enterprise profiles Enterprise subject EnterprisePRD

Bundle → Layer → Finding → Questions Filled

3 bundles · 3 layers · 5 findings · 10 questions

Requirements Needs turned into requirements with acceptance criteria.

Requirement record

A requirement as distinct from a need, feature or task.

Requirement type

Need, requirement, feature and task kept apart.

  1. Is this record a need, a requirement, a feature or a task?
  2. Which stakeholder raised the requirement, and on what basis?

Acceptance criteria

How fulfilment is judged.

  1. Which acceptance criteria define fulfilment of this requirement?
  2. Which version of the requirement was pinned at acceptance?
Baselines and conflicts Approved sets of requirements and conflicts between them.

Baseline

A frozen set of requirement versions.

Baseline change

What moves when a new baseline is set.

  1. Which requirements changed between these two baselines?
  2. Are the two baselines compatible for the release in question?

Conflict

Conflicting requirements from different stakeholders.

  1. Which requirements conflict, and are both alternatives still recorded?
  2. Who decided the conflict, and on what grounds?
Traceability Links from requirements to solution, tasks and tests.

Trace links

Evidence of fulfilment beyond task status.

Fulfilment evidence

Tests and reviews that show a requirement is met.

  1. Which tests and reviews show that this requirement is fulfilled?
  2. Does a closed task linked here prove anything about fulfilment?

Classifiers Filled

Family
Enterprise profiles
Category
Enterprise subject
Entry kind
subject
Domain
EnterprisePRD
Industry
Cross-industry
Tags
EM-PRD-03W1subjectRequirementAcceptanceCriterionRequirementBaselineTraceLink

What it is Filled

Requirements, constraints, acceptance criteria and traceability to the solution. An implementation task references a requirement.

Why it exists Filled

Requirements, constraints, acceptance criteria and traceability to the solution. An implementation task references a requirement.

Distinguishing features Filled

  • The version of a requirement is pinned at the moment of acceptance.
  • Closing a task does not prove that a requirement is fulfilled.
  • A resolved conflict keeps the alternative that was not chosen.
  • Distinct from work items, which reference requirements, and from the product, which owns the intent.

What robots and AI may and may not do Filled

Must not

  • Confirm linked requirements because a ticket moved to done.
  • Delete the losing alternative when a conflict is resolved.
  • Change an accepted requirement in place instead of creating a new version.
  • Mark a requirement fulfilled when a linked test failed.

Only with a human decision

  • Approving a new requirement baseline.
  • Resolving a conflict between requirements of different stakeholders.
  • Accepting a requirement as fulfilled.

May

  • Trace a requirement to its tasks, tests and acceptance results.
  • Compare two baselines and list changed and conflicting requirements.
  • Flag requirements marked fulfilled without a passing test or review.

Moral aspects Filled

  • Unverified requirements in safety or regulated systems can put people at risk.
  • Dropping one stakeholder's requirement silently removes their voice from the decision.

Who is affected

  • Stakeholders who raised requirements
  • Users of the delivered system
  • Delivery and test teams

Owners Filled

Steward

The product owner or requirements engineer who answers for the requirement baseline.

Master systems

  • Requirements management tool
  • Issue tracker
  • Test management system

Links to other meta-models Filled

neighbor

  • EM-OPS-01
  • EM-PRD-01
  • EM-TEC-01
  • EM-TEC-08

references

  • WM-REC-006 - conceptual-candidate
  • WM-KNW-013 - conceptual-candidate

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Identified by requirement identifier and version, with baselines identified by name and date.

Direct properties not applicable Not applicable

Not applicable

Enterprise record contour: physical properties belong to referenced world models.

Recognition optional Filled

  • A record states expected behaviour, acceptance criteria and trace links.
  • Often confused with tickets, user stories or features.

Capabilities and actions required Filled

  • Trace requirements through tasks and tests to acceptance.
  • Compare baselines and keep conflicting alternatives.

Hazards and failure modes required Filled

  • Ticket status used as proof of fulfilment.
  • Requirement drift after acceptance without a new version.

Standards and interfaces required Filled

  • ISO/IEC/IEEE 29148 requirements engineering.
  • Requirements Interchange Format (ReqIF) from the Object Management Group.
  • SysML from the Object Management Group for requirement models.

Context of use required Filled

  • Used in product development, contracting, regulated engineering and acceptance testing.
  • Safety-critical and regulated domains require traceability from requirement to test.

Sources Filled

  1. TM Forum SID: product/service/resource and commercial roles
  2. IDTA AAS: physical assets and composite descriptions
  3. Product management and engineering configuration; compare selected PLM and software practices
  4. OMG Requirements Interchange Format (ReqIF) - Checked live (HTTP 200) on 2026-10-07.
  5. OMG Systems Modeling Language (SysML) - Checked live (HTTP 200) on 2026-10-07.
  6. IDTA Asset Administration Shell Specifications - Checked live (HTTP 200) on 2026-10-07.

Open 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?
  • Установить границу и решение reuse/extend/new по действующим спецификациям.
  • Подтвердить semantic crosswalk, права и source mastership.
  • Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.

Machine files

Provenance

enterprise research programme · published-partial

Built from: enterprise/models/em-prd-03/brief.json, ver-cy/world-models/card-supplements/em-prd-03.json

Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.