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

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

view aebsExecutionEnvironmentAssuranceViewsource ↓

ViewpointselectedArgumentationAssuranceViewpoint (ArgumentationAssuranceViewpoint)
ConcernargumentationAssuranceConcern
RenderasTreeDiagram
ExposesDE4SDV_AEBSExecutionEnvironment::*
Sourcetextual-notation-of-model/packages/features/aebs/aebs_execution_environment.sysml:80
diagram-aebsExecutionEnvironmentAssuranceView.svg
«view» aebsExecutionEnvironmentAssuranceView expose DE4SDV_AEBSExecutionEnvironment::* «part def» AEBMaintainedJetsonEnvironmentContext :> AEBTwoSystemSimulationDeployment doc Exact maintained System 2 environment context associated with INC-AEBS-009A. The current maintained host is an NVIDIA Jetson Orin Nano Engineering Reference Developer Kit Super (8 GiB class), running Ubuntu 22.04 with Tegra kernel integration and native linux/arm64 OCI execution. Historical 009A runtime artifacts identify only a Jetson 8 GiB host; they do not identify the exact SKU or prove identity continuity to this post-merge snapshot. The two dependency sets preserve that boundary. INC-AEBS-009C has merged bounded partial evidence. INC-AEBS-009B has executed scenario evidence pending review and retains its own environment and execution-identity trace; neither increment changes the 009A claim boundary. parts executionEnvironment : INCAEBS009AJetsonExecutionEnvironment runtimeLockEvidence : TestedExecutionEnvironmentEvidence containerIdentityEvidence : TestedExecutionEnvironmentEvidence readinessEvidence : TestedExecutionEnvironmentEvidence environmentIdentityEvidence : InspectedExecutionEnvironmentEvidence ^candidateVehicleSystem1 «concern» physicalStructureConcern : PhysicalStructureConcern subject ref stakeholders systemsEngineer : SystemsEngineer reviewer : OpenSourceReviewer require constraints ^doc Reviewer question: What physical hardware, software, and mechanical elements make up the candidate system, and in which internal roles are they used? «concern» argumentationAssuranceConcern : ArgumentationAssuranceConcern doc Evidence-based assurance claims and their supporting argumentation. require constraints ^doc Reviewers need claims, arguments, evidence, and gaps linked in an assurance argument for the increment. = «end» ::> candidateVehicleSystem1.host «end» ::> executionEnvironment

Hover a model element for details open raw SVG.

Source

1package DE4SDV_AEBSExecutionEnvironment {2  private import SAF_Viewpoints::*;3  private import DE4SDV_Stakeholders::*;4  private import Views::*;567  private import DE4SDV_AEBSSimulationDeployment::*;8  private import DE4SDV_ExecutionEnvironments::*;9  private import INCAEBS009AJetsonExecutionEnvironment;1011  part def AEBMaintainedJetsonEnvironmentContext12    :> AEBTwoSystemSimulationDeployment {13    doc /*14     * Exact maintained System 2 environment context associated with15     * INC-AEBS-009A.16     *17     * The current maintained host is an NVIDIA Jetson Orin Nano Engineering18     * Reference Developer Kit Super (8 GiB class), running Ubuntu 22.04 with19     * Tegra kernel integration and native linux/arm64 OCI execution.20     *21     * Historical 009A runtime artifacts identify only a Jetson 8 GiB host;22     * they do not identify the exact SKU or prove identity continuity to this23     * post-merge snapshot. The two dependency sets preserve that boundary.24     * INC-AEBS-009C has merged bounded partial evidence. INC-AEBS-009B has25     * executed scenario evidence pending review and retains its own environment26     * and execution-identity trace; neither increment changes the 009A claim27     * boundary.28     */2930    part executionEnvironment : INCAEBS009AJetsonExecutionEnvironment;31    bind candidateVehicleSystem1.host = executionEnvironment;3233    part runtimeLockEvidence : TestedExecutionEnvironmentEvidence {34      doc /*35       * implementation/aebs-autoware-executable-bench/runtime-lock.yaml36       */37    }3839    part containerIdentityEvidence : TestedExecutionEnvironmentEvidence {40      doc /*41       * implementation/aebs-autoware-executable-bench/evidence/container-identity.json42       */43    }4445    part readinessEvidence : TestedExecutionEnvironmentEvidence {46      doc /*47       * implementation/aebs-autoware-executable-bench/evidence/readiness.json48       */49    }5051    part environmentIdentityEvidence : InspectedExecutionEnvironmentEvidence {52      doc /*53       * implementation/aebs-autoware-executable-bench/evidence/execution-environment-snapshot.json54       * Post-merge host identity supplement; it does not rewrite historical55       * 009A runtime evidence.56       */57    }5859    dependency historicalRuntimeEvidence60      from runtimeLockEvidence,61           containerIdentityEvidence,62           readinessEvidence63      to candidateVehicleSystem1;6465    dependency maintainedHostIdentity66      from environmentIdentityEvidence67      to executionEnvironment;68  }6970  concern physicalStructureConcern : PhysicalStructureConcern {71    subject;72    stakeholder systemsEngineer : SystemsEngineer;73    stakeholder reviewer : OpenSourceReviewer;74  }7576  concern argumentationAssuranceConcern : ArgumentationAssuranceConcern {77    doc /* Evidence-based assurance claims and their supporting argumentation. */78  }7980  view aebsExecutionEnvironmentAssuranceView {81    viewpoint selectedArgumentationAssuranceViewpoint : ArgumentationAssuranceViewpoint {82      frame argumentationAssuranceConcern;83    }8485    expose DE4SDV_AEBSExecutionEnvironment::*;86    render asTreeDiagram;87  }88}89