textual-notation-of-model/packages/features/aebs/aebs_visualization_framing.sysml

1 view(s) · 52 declared member(s) Jump to source ↓

view aebsVisualizationFramingViewsource ↓

ViewpointselectedFramingViewpoint (IncrementFramingViewpoint)
ConcernvisualizationProvenanceConcern
RenderasTreeDiagram
ExposesVisualizationIncrement::*
Sourcetextual-notation-of-model/packages/features/aebs/aebs_visualization_framing.sysml:216
No committed diagram. Regenerate via the Privileged Syside Validation workflow (expected artifact diagrams/diagram-aebsVisualizationFramingView.svg).

Source

1/*2 * DE4SDV AEBS visualization increment framing model slice.3 *4 * INC-AEBS-010 frames a bounded, stakeholder-visible AEBS threat and5 * intervention visualization on an AAOS SDV display. This slice is a6 * System 2 engineering-and-evidence increment: it consumes System 1 AEBS7 * behavior but is not a product feature, not a production driver-HMI claim,8 * and not an INC-MW-010 add-on.9 *10 * Predecessor relationship: this increment is the separate capability11 * increment mandated by DE4SDV_MiddlewareVerificationEvidence::12 * successorIncrementDecision010. It does not reopen, extend, or retroactively13 * satisfy INC-MW-010 gate 8 or its retained evidence set E-MW-011..E-MW-014.14 */1516package DE4SDV_AEBSVisualizationFraming {17  private import DE4SDV_MethodContext::*;18  private import DE4SDV_MethodViewpoints::*;19  private import DE4SDV_Stakeholders::*;20  private import DE4SDV_ProductLine::*;21  private import DE4SDV_MiddlewareVerificationEvidence::*;22  private import SAF_Viewpoints::*;23  private import Views::*;2425  part def VisualizationIncrement :> EngineeringIncrement;2627  part incAEBS010 : VisualizationIncrement {28    doc /*29     * INC-AEBS-010: AEBS visualization on AAOS SDV — framing through30     * needs and System 2 requirements. Later increments in the same31     * increment chain carry architecture, configuration, implementation,32     * and evidence.33     */34  }3536  requirement visualizationProblemStatement : ProblemStatement {37    doc /*38     * How can DE4SDV demonstrate a bounded, stakeholder-visible AEBS threat39     * and intervention visualization on a real AAOS SDV display, consuming40     * live native Autoware AEB output and existing DE4SDV AEBS coordination41     * state, with explicit source provenance, freshness, invalid-input, and42     * provider-loss behavior, without making production driver-HMI, safety,43     * or compliance claims and without altering the closed INC-MW-01044     * baseline?45     */46    subject increment : VisualizationIncrement;47    stakeholder systemsEngineer : SystemsEngineer;48    stakeholder productLineEngineer : ProductLineEngineer;49    stakeholder verificationEngineer : VerificationEngineer;50    stakeholder maintainer : Maintainer;51    stakeholder reviewer : OpenSourceReviewer;52  }5354  part visualizationEngineeringQuestion : IncrementEngineeringQuestion {55    doc /*56     * Can a real pinned Autoware AEBS execution and the existing DE4SDV AEBS57     * coordination state be presented as a bounded center-display threat and58     * intervention visualization on a display-capable AAOS SDV member, with59     * honest source provenance and fail-closed degradation behavior?60     */61  }6263  part visualizationLifecycleDecision : IncrementLifecycleDecision {64    doc /*65     * Decide whether the visualization increment is framed tightly enough to66     * derive System 2 needs and requirements without dragging architecture,67     * configuration, implementation, or evidence claims into this slice.68     */69  }7071  part visualizationScope : IncrementScope {72    doc /*73     * Scope: increment framing, stakeholder concerns, operational scenarios,74     * product-line classification, stakeholder needs, and System 275     * requirement candidates for the AEBS visualization test system.76     */77  }7879  part visualizationTraceabilityShell : IncrementTraceabilityShell {80    doc /*81     * Traceability shell: INC-MW-010 successor decision -> framing ->82     * concerns/views -> operational scenarios -> classification -> needs ->83     * System 2 requirement candidates -> gaps.84     */85  }8687  /* Dependency to the mandated predecessor decision (qualified reference,88   * no restatement of predecessor content). */89  dependency successorMandate90    from incAEBS010 to successorIncrementDecision010;9192  dependency framingToProblemStatement93    from visualizationEngineeringQuestion to visualizationProblemStatement;94  dependency scopeToTraceabilityShell95    from visualizationScope to visualizationTraceabilityShell;9697  part system1ConfiguredAEBSSDVMember : System1SDVProductLine {98    doc /*99     * The configured member product whose live AEBS behavior (native Autoware100     * AEB execution plus DE4SDV AEBS coordination) is observed by the101     * visualization. No member-product behavior is changed by this increment.102     */103  }104  part system2VisualizationInstrument : System2EngineeringAndAssuranceSystem {105    doc /*106     * The visualization test system: source observation, reverse transport,107     * AAOS rendering, health supervision, and evidence recording.108     */109  }110  part system3ReviewEcosystem : System3OpenSourceGovernanceEcosystem;111112  part visualizationBoundary : OperationalScopeBoundary;113  part visualizationTestSystemInScope : InScopeItem {114    doc /* Bounded visualization test system observing System 1 AEBS behavior. */115  }116  part sourceProvenancePresentationInScope : InScopeItem {117    doc /* Per-field provenance: native Autoware, DE4SDV AEBS, display-derived. */118  }119  part failureBehaviorInScope : InScopeItem {120    doc /* Stale, unavailable, invalid, and restored display dispositions. */121  }122  part productionDriverHMIOutOfScope : OutOfScopeItem {123    doc /*124     * Production driver-HMI suitability, warning timing/modality, distraction,125     * and human-factors validation remain out of scope.126     */127  }128  part clusterDisplaySafetyOutOfScope : OutOfScopeItem {129    doc /* DriverUI, cluster, HAR, Display Safety, and tell-tale rendering. */130  }131  part mw010RetroactiveClosureOutOfScope : OutOfScopeItem {132    doc /*133     * Any retroactive satisfaction of INC-MW-010 gate 8 or extension of its134     * retained evidence set E-MW-011..E-MW-014.135     */136  }137  part fullAutowareStackOutOfScope : OutOfScopeItem;138  part safetyComplianceClaimOutOfScope : OutOfScopeItem {139    doc /* Safety, ASIL, compliance, certification, homologation claims. */140  }141142  part asmSystem1Unchanged : IncrementAssumption {143    doc /*144     * ASM-AEBS-010-001: The visualization consumes System 1 AEBS behavior and145     * changes no AEBS detection, warning, intervention, or release behavior.146     */147  }148  part asmRealSourcesRequired : IncrementAssumption {149    doc /*150     * ASM-AEBS-010-002: Displayed threat state must originate from the pinned151     * native Autoware AEB component and the existing DE4SDV AEBS coordinator;152     * AAOS-originated or display-generated AEBS state is not evidence.153     */154  }155  part asmBoundedBenchClaim : IncrementAssumption {156    doc /*157     * ASM-AEBS-010-003: Accepted claims remain limited to a deterministic158     * bench environment; no on-road, production, or fleet behavior is claimed.159     */160  }161162  part gapRealizationUnselected : IncrementGap {163    doc /*164     * GAP-AEBS-010-001: No architecture, target, transport, or application165     * realization is selected in this framing slice; deferred to the166     * architecture increment in the same chain.167     */168  }169  part gapThresholdsUnpinned : IncrementGap {170    doc /*171     * GAP-AEBS-010-002: Freshness timeouts, restoration counts, frame rates,172     * and transport parameters are named as planning targets only and remain173     * unpinned until the Phase 8/9 configuration work in the chain.174     */175  }176  part gapEvidenceUnplanned : IncrementGap {177    doc /*178     * GAP-AEBS-010-003: No verification case or evidence artifact exists yet;179     * V&V planning is deferred to the evidence increment in the same chain.180     */181  }182183  concern visualizationProvenanceConcern : ProductLineCapabilityClassificationConcern {184    doc /*185     * Reviewers need the visualization classified as System 2 engineering and186     * evidence instrumentation, not as a product feature or production HMI.187     */188    subject;189    stakeholder productLineEngineer : ProductLineEngineer;190    stakeholder systemsEngineer : SystemsEngineer;191    stakeholder reviewer : OpenSourceReviewer;192  }193194  concern visualizationBoundaryConcern : IncrementBoundaryConcern {195    doc /*196     * Reviewers need the framing slice to stay separate from architecture,197     * configuration, implementation, and evidence slices in the same chain.198     */199    subject;200    stakeholder systemsEngineer : SystemsEngineer;201    stakeholder verificationEngineer : VerificationEngineer;202    stakeholder reviewer : OpenSourceReviewer;203  }204205  concern predecessorIndependenceConcern : ArgumentationAssuranceConcern {206    doc /*207     * Reviewers need visible assurance that this increment neither reopens208     * INC-MW-010 nor claims its gate 8 reverse path retroactively.209     */210    subject;211    stakeholder systemsEngineer : SystemsEngineer;212    stakeholder maintainer : Maintainer;213    stakeholder reviewer : OpenSourceReviewer;214  }215216  view aebsVisualizationFramingView {217    viewpoint selectedFramingViewpoint : IncrementFramingViewpoint {218      frame visualizationProvenanceConcern;219      frame visualizationBoundaryConcern;220      frame predecessorIndependenceConcern;221    }222223    expose VisualizationIncrement::*;224    render asTreeDiagram;225  }226}227