Differences
This shows you the differences between two versions of the page.
| dido:03-dido-te:99-annexes:annex-b-references:dte-006 [2026/08/07 12:28] – created nick_dido | dido:03-dido-te:99-annexes:annex-b-references:dte-006 [2026/08/08 02:17] (current) – nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== [DTE6] Structured Information Processing Reference Architecture (SIP-RA) ====== | ====== [DTE6] Structured Information Processing Reference Architecture (SIP-RA) ====== | ||
| - | [[dido: | + | [[dido: |
| - | ===== Reference | + | ===== Reference ===== |
| - | DIDO-TE: [DTE6] | + | Dido Solutions, Inc. and Jackrabbit Consulting, Inc. // |
| - | ===== Citation | + | ===== Bibliographic Information |
| - | Dido Solutions, Inc. and Jackrabbit Consulting, Inc. // | + | ^ Attribute ^ Value ^ |
| + | | Reference Identifier | [DTE6] | | ||
| + | | Title | Structured Information Processing Reference Architecture (SIP-RA) | | ||
| + | | Filename | Record the authoritative filename. | | ||
| + | | Artifact Type | Reference Architecture | | ||
| + | | Version | Record the authoritative version. | | ||
| + | | Document Date | Record the authoritative document date. | | ||
| + | | Preparing Organisations | Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | | ||
| + | | File Format | Record the authoritative file format. | | ||
| + | | Status | Record the authoritative status. | | ||
| + | | URI | Record the canonical | ||
| - | ===== URI ===== | + | ===== Scope ===== |
| - | < | + | The Structured Information Processing Reference Architecture (SIP-RA) defines an implementation-independent architecture for the governed processing of structured information. |
| - | Add the canonical | + | |
| - | </ | + | |
| - | ===== Note ===== | + | SIP-RA establishes architectural concepts, terminology, |
| - | This reference provides the architectural foundation for the Structured Information Processing Reference Architecture (SIP-RA). | + | DIDO-TE uses SIP-RA as an architectural foundation for the design, implementation, |
| - | DIDO-TE derives architectural concepts, terminology, | + | ===== Architectural Content ===== |
| - | Requirements derived from this reference identify the applicable section, clause, figure, table, or other source location. | + | SIP-RA addresses architectural subject areas associated with: |
| - | Examples include: | + | * Structured information processing |
| + | * Reference Architecture | ||
| + | * Conceptual, logical, and physical models | ||
| + | * Architectural components and relationships | ||
| + | * Information-processing pipelines | ||
| + | * Data and metadata | ||
| + | * Processing lifecycle governance | ||
| + | * Traceability | ||
| + | * Validation | ||
| + | * Conformance | ||
| + | * Conformance criteria | ||
| + | * Conformance points | ||
| + | * Implementation profiles | ||
| + | * Evidence | ||
| + | * Auditability | ||
| + | * Reproducibility | ||
| + | * Interoperability | ||
| + | * Security | ||
| + | * Governance | ||
| + | |||
| + | DIDO-TE applies the SIP-RA concepts relevant to a distributed Test Environment and specialises them where DIDO-TE requires test-specific architectural meaning. | ||
| + | |||
| + | ===== Relevance to DIDO-TE ===== | ||
| + | |||
| + | This reference provides part of the architectural foundation for DIDO-TE. | ||
| + | |||
| + | DIDO-TE uses [DTE6] to: | ||
| + | |||
| + | * Establish architectural concepts and terminology | ||
| + | * Preserve separation among conceptual, logical, and physical models | ||
| + | * Structure information-processing responsibilities | ||
| + | * Establish traceability between requirements and architectural elements | ||
| + | * Define inspectable conformance points | ||
| + | * Establish conformance criteria | ||
| + | * Support validation and verification | ||
| + | * Govern the production and preservation of Evidence | ||
| + | * Support reproducible Test Environments and Test Executions | ||
| + | * Distinguish architectural requirements from implementation decisions | ||
| + | |||
| + | DIDO-TE requirements and architecture content identify any specialisation or extension of a SIP-RA concept. | ||
| + | |||
| + | ===== Citation Use ===== | ||
| + | |||
| + | DIDO-TE pages cite this reference using: | ||
| + | |||
| + | [[dido: | ||
| + | |||
| + | A citation identifies the applicable SIP-RA section, clause, requirement, | ||
| + | |||
| + | For example: | ||
| + | |||
| + | <code dokuwiki> | ||
| + | [[dido: | ||
| + | </ | ||
| + | |||
| + | When a DIDO-TE requirement derives from a SIP-RA requirement, | ||
| + | |||
| + | When DIDO-TE specialises or extends a SIP-RA concept, the citation identifies the original concept and records the resulting DIDO-TE specialisation or extension. | ||
| + | |||
| + | ===== Source Treatment ===== | ||
| + | |||
| + | DIDO-TE preserves the meaning of architectural concepts derived from [DTE6]. | ||
| + | |||
| + | The derivation process: | ||
| + | |||
| + | * Identifies the precise SIP-RA source location | ||
| + | * Preserves the original architectural meaning | ||
| + | * Identifies the applicable DIDO-TE context | ||
| + | * Records any terminology normalisation | ||
| + | * Records any DIDO-TE specialisation or extension | ||
| + | * Provides a rationale for each specialisation or extension | ||
| + | * Maintains traceability between the source concept and the resulting DIDO-TE content | ||
| + | * Distinguishes source requirements from derived DIDO-TE requirements | ||
| + | * Distinguishes architectural constraints from implementation decisions | ||
| + | |||
| + | A DIDO-TE specialisation narrows or contextualises a SIP-RA concept for the DIDO Test Environment. It does not alter the historical SIP-RA source. | ||
| + | |||
| + | ===== Conformance Content ===== | ||
| + | |||
| + | SIP-RA supplies architectural concepts associated with conformance, | ||
| * [[dido: | * [[dido: | ||
| Line 31: | Line 118: | ||
| * Architectural conformance | * Architectural conformance | ||
| * Conformance points | * Conformance points | ||
| + | * Implementation conformance | ||
| * Requirements traceability | * Requirements traceability | ||
| - | Where DIDO-TE | + | DIDO-TE |
| + | |||
| + | A DIDO-TE conformance statement identifies the applicable | ||
| + | |||
| + | ===== Relationship to Other References ===== | ||
| + | |||
| + | [DTE6] supplies architectural concepts that complement the DIDO-TE-specific source material recorded in other references. | ||
| + | |||
| + | See: | ||
| + | |||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | |||
| + | [DTE1] records patented subject matter. [DTE2] and [DTE3] describe proposed applications of DIDO-TE. [DTE4] supplies a historical Conceptual Model. [DTE5] records source requirements. [DTE6] supplies the broader architectural framework within which DIDO-TE requirements and architecture content are organised. | ||
| + | |||
| + | Cite the reference that directly supports the applicable statement, architectural concept, or requirement derivation. | ||
| + | |||
| + | ===== Status ===== | ||
| + | |||
| + | Record | ||
| + | |||
| + | A later SIP-RA revision does not automatically supersede the revision cited by existing DIDO-TE | ||
| + | |||
| + | Record the relationship between revisions before changing the authoritative source used by DIDO-TE. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ===== Notes for Editors ===== | ||
| + | |||
| + | Preserve `[DTE6]` | ||
| + | |||
| + | Preserve | ||
| + | |||
| + | Record the authoritative filename, version, date, file format, publication status, | ||
| + | |||
| + | Identify | ||
| + | |||
| + | Do not cite [DTE6] without a precise source location when a more precise citation is available. | ||
| + | |||
| + | Preserve the original SIP-RA meaning in the source record. Record DIDO-TE terminology and specializations separately. | ||
| + | |||
| + | Do not classify a change to architectural meaning, scope, responsibility, | ||
| + | |||
| + | Document each DIDO-TE specialization | ||
| + | |||
| + | Do not introduce implementation-specific products, technologies, | ||
| + | |||
| + | Preserve the distinction among conceptual, logical, and physical models. | ||
| + | |||
| + | Record the revision, provenance, and supersession relationship before replacing [DTE6] with another SIP-RA revision. | ||
| + | |||
| + | Preserve [DTE6] when existing requirements, | ||
| ---- | ---- | ||