Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-011:start [2026/07/11 12:57] – removed - external edit (Unknown date) 127.0.0.1 | dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-011:start [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | | ||
| + | [[dido: | ||
| + | |||
| + | ===== Statement ===== | ||
| + | |||
| + | The Conceptual Architecture SHALL distinguish among a [[dido: | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Part 1, Section 13.4: Core Conceptual Element Requirements. | ||
| + | |||
| + | ===== Rationale ===== | ||
| + | |||
| + | The core conceptual elements describe different architectural concerns. A Node, Node Role, Node Identity, Communication Endpoint, Data Structure Definition, Data Structure Instance, Runtime Plane, implementation artifact, and deployment artifact each serves a distinct purpose. | ||
| + | |||
| + | Distinguishing these elements prevents identity, responsibility, | ||
| + | |||
| + | ===== Applies To ===== | ||
| + | |||
| + | This requirement applies to all uses of core conceptual elements within the Conceptual Architecture. | ||
| + | |||
| + | It applies specifically to distinctions among: | ||
| + | |||
| + | * Node | ||
| + | * Node Role | ||
| + | * Node Identity | ||
| + | * Communication Endpoint | ||
| + | * Data Structure Definition | ||
| + | * Data Structure Instance | ||
| + | * Runtime Plane | ||
| + | * Implementation artifact | ||
| + | * Deployment artifact | ||
| + | |||
| + | ===== Verification ===== | ||
| + | |||
| + | Verification SHALL confirm that the Conceptual Architecture distinguishes among the named core conceptual, implementation, | ||
| + | |||
| + | Verification activities include review checks confirming that: | ||
| + | |||
| + | * Node, Node Role, and Node Identity remain distinct | ||
| + | * Communication Endpoint remains distinct from Nodes and exchanged information | ||
| + | * Data Structure Definition remains distinct from Data Structure Instance | ||
| + | * Runtime Plane remains distinct from implementation and deployment artifacts | ||
| + | * Implementation artifacts and deployment artifacts do not redefine conceptual elements | ||
| + | |||
| + | ===== Traceability ===== | ||
| + | |||
| + | Related source section: | ||
| + | |||
| + | * [[fxdemo: | ||
| + | |||
| + | Related requirement identifiers: | ||
| + | |||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | |||
| + | ===== Status ===== | ||
| + | |||
| + | Draft | ||
| + | |||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||