Requirements and expected behavior
Requirements, constraints, acceptance criteria and traceability to the solution. An implementation task references a requirement.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
Bundle → Layer → Finding → Questions Missing, in the backlog
Not described yet. This gap is in the card backlog.
Note: Research contour: bundles not designed yet; questions are listed as open questions.
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 Derived, awaiting review
- The requirement version is pinned at acceptance
- A closed task does not prove fulfillment
- A conflict does not erase the alternative
What robots and AI may and may not do Derived, awaiting review
Must not
- Negative case: Moving a ticket to Done automatically confirms all linked requirements.
Note: Negative case of the research brief, not yet a rule for agents.
Moral aspects Missing, in the backlog
Not described yet. This gap is in the card backlog.
Owners Filled
Steward
Руководитель продукта
Master systems
- Каталог продуктов
- discovery
- PLM
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 Incomplete
Identity and identifiers required Derived, awaiting review
- Requirement
- AcceptanceCriterion
- RequirementBaseline
- TraceLink
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Hazards and failure modes required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Context of use required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Sources Filled
- 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
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
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.