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

3 view(s) · 53 declared member(s) Jump to source ↓

view aebsIncrementFramingViewsource ↓

ViewpointselectedIncrementFramingViewpoint (IncrementFramingViewpoint)
ConcernproductLineCapabilityClassificationConcern
RenderasTreeDiagram
ExposesIncrementFraming::*
Sourcetextual-notation-of-model/packages/features/aebs/aebs_increment_framing.sysml:111
diagram-aebsIncrementFramingView.svg
«view» aebsIncrementFramingView expose IncrementFraming::* «concern» productLineCapabilityClassificationConcern : ProductLineCapabilityClassificationConcern doc Reviewers need AEBS scope elements to distinguish common product-line capabilities from candidate features and later variability decisions. subject ref stakeholders productLineEngineer : ProductLineEngineer systemsEngineer : SystemsEngineer reviewer : OpenSourceReviewer require constraints ^doc Reviewers need model content to distinguish common product-line capabilities from features, candidate features, variability decisions, and deferred variability decisions. «concern» regulatoryScopeWithoutComplianceClaimConcern : RegulatoryScopeWithoutComplianceClaimConcern doc Reviewers need the UNECE R152 regulatory anchor and open compliance assumptions to be visible without treating this increment as evidence of compliance, certification, or type approval. subject ref stakeholders complianceEngineer : ComplianceEngineer verificationEngineer : VerificationEngineer reviewer : OpenSourceReviewer require constraints ^doc Reviewers need regulatory anchors, source assumptions, missing evidence, and scope boundaries to be visible without implying compliance, certification, or type approval. «concern» incrementBoundaryConcern : IncrementBoundaryConcern doc Reviewers need a small increment boundary that separates framing, operational context, functional modeling, conceptual realization, physical/software realization, and evidence work. subject ref stakeholders systemsEngineer : SystemsEngineer verificationEngineer : VerificationEngineer reviewer : OpenSourceReviewer require constraints ^doc Reviewers need each increment to separate framing, operational context, needs, requirements, functional modeling, logical realization, physical/software realization, and evidence work. «concern» methodStackConcern : MethodStackConcern doc Reviewers need to see how SAF viewpoint selection, SYSMOD method flow, DE4SDV ontology terms, SysML v2 model expression, and VSS signal catalog usage relate without collapsing them into one method blob. subject ref stakeholders systemsEngineer : SystemsEngineer reviewer : OpenSourceReviewer require constraints ^doc Reviewers need the relationship between viewpoint selection, method flow, ontology terms, SysML v2 expression, and external catalog use to remain explicit rather than collapsed into one method blob. «part» incAEBS001 : FeatureIncrement «part» system1SDVProductLine : System1SDVProductLine «part» system2EngineeringAndAssuranceSystem : System2EngineeringAndAssuranceSystem «part» system3OpenSourceGovernanceEcosystem : System3OpenSourceGovernanceEcosystem «part» safViewpointSelection : SAFViewpointSelection «part» sysmodMethodFlow : SYSMODMethodFlow «part» de4sdvOntologyKernel : DE4SDVOntologyKernel «part» sysmlv2ModelExpression : SysMLv2ModelExpression «part» vssCandidateSignalCatalog : VSSCandidateSignalCatalog «part» forwardCollisionRiskMitigation : CommonProductLineCapability «part» vehicleTargetAEBSSupport : CommonProductLineCapability «part» pedestrianTargetAEBSScope : DeferredProductLineScope «part» bicycleTargetAEBSScope : DeferredProductLineScope «comment» Native SysML v2 variation usages record unresolved AEBS variability topics without inventing a project-local variation-point part definition. The only variants in this framing slice are deferred choices; concrete sensor/evidence variants require later functional/evidence increments. «variation part» aebsSensorPackageSelection parts sensorPackageChoiceDeferred «variation part» aebsEvidenceLevelSelection parts evidenceLevelChoiceDeferred «part» firstSliceScope : OperationalScopeBoundary «part» vehicleTargetForwardCollisionRiskMitigationScope : InScopeItem «part» pedestrianTargetOutOfScope : OutOfScopeItem «part» bicycleTargetOutOfScope : OutOfScopeItem «part» complianceClaimOutOfScope : OutOfScopeItem «part» conceptualRealizationOutOfScope : OutOfScopeItem «part» physicalSoftwareRealizationOutOfScope : OutOfScopeItem «view» aebsProductLineClassificationView viewpoints selectedProductLineClassificationViewpoint : ProductLineClassificationViewpoint exposes IncrementFraming::* rendering viewRendering ::> asTreeDiagram «view» aebsRegulatoryScopeView viewpoints selectedRegulatoryScopeViewpoint : RegulatoryScopeViewpoint exposes IncrementFraming::* rendering viewRendering ::> asTreeDiagram

Hover a model element for details open raw SVG.

view aebsProductLineClassificationViewsource ↓

ViewpointselectedProductLineClassificationViewpoint (ProductLineClassificationViewpoint)
ConcernproductLineCapabilityClassificationConcern
RenderasTreeDiagram
ExposesIncrementFraming::*
Sourcetextual-notation-of-model/packages/features/aebs/aebs_increment_framing.sysml:122
diagram-aebsProductLineClassificationView.svg
«view» aebsProductLineClassificationView expose IncrementFraming::* «concern» productLineCapabilityClassificationConcern : ProductLineCapabilityClassificationConcern doc Reviewers need AEBS scope elements to distinguish common product-line capabilities from candidate features and later variability decisions. subject ref stakeholders productLineEngineer : ProductLineEngineer systemsEngineer : SystemsEngineer reviewer : OpenSourceReviewer require constraints ^doc Reviewers need model content to distinguish common product-line capabilities from features, candidate features, variability decisions, and deferred variability decisions. «concern» regulatoryScopeWithoutComplianceClaimConcern : RegulatoryScopeWithoutComplianceClaimConcern doc Reviewers need the UNECE R152 regulatory anchor and open compliance assumptions to be visible without treating this increment as evidence of compliance, certification, or type approval. subject ref stakeholders complianceEngineer : ComplianceEngineer verificationEngineer : VerificationEngineer reviewer : OpenSourceReviewer require constraints ^doc Reviewers need regulatory anchors, source assumptions, missing evidence, and scope boundaries to be visible without implying compliance, certification, or type approval. «concern» incrementBoundaryConcern : IncrementBoundaryConcern doc Reviewers need a small increment boundary that separates framing, operational context, functional modeling, conceptual realization, physical/software realization, and evidence work. subject ref stakeholders systemsEngineer : SystemsEngineer verificationEngineer : VerificationEngineer reviewer : OpenSourceReviewer require constraints ^doc Reviewers need each increment to separate framing, operational context, needs, requirements, functional modeling, logical realization, physical/software realization, and evidence work. «concern» methodStackConcern : MethodStackConcern doc Reviewers need to see how SAF viewpoint selection, SYSMOD method flow, DE4SDV ontology terms, SysML v2 model expression, and VSS signal catalog usage relate without collapsing them into one method blob. subject ref stakeholders systemsEngineer : SystemsEngineer reviewer : OpenSourceReviewer require constraints ^doc Reviewers need the relationship between viewpoint selection, method flow, ontology terms, SysML v2 expression, and external catalog use to remain explicit rather than collapsed into one method blob. «part» incAEBS001 : FeatureIncrement «part» system1SDVProductLine : System1SDVProductLine «part» system2EngineeringAndAssuranceSystem : System2EngineeringAndAssuranceSystem «part» system3OpenSourceGovernanceEcosystem : System3OpenSourceGovernanceEcosystem «part» safViewpointSelection : SAFViewpointSelection «part» sysmodMethodFlow : SYSMODMethodFlow «part» de4sdvOntologyKernel : DE4SDVOntologyKernel «part» sysmlv2ModelExpression : SysMLv2ModelExpression «part» vssCandidateSignalCatalog : VSSCandidateSignalCatalog «part» forwardCollisionRiskMitigation : CommonProductLineCapability «part» vehicleTargetAEBSSupport : CommonProductLineCapability «part» pedestrianTargetAEBSScope : DeferredProductLineScope «part» bicycleTargetAEBSScope : DeferredProductLineScope «comment» Native SysML v2 variation usages record unresolved AEBS variability topics without inventing a project-local variation-point part definition. The only variants in this framing slice are deferred choices; concrete sensor/evidence variants require later functional/evidence increments. «variation part» aebsSensorPackageSelection parts sensorPackageChoiceDeferred «variation part» aebsEvidenceLevelSelection parts evidenceLevelChoiceDeferred «part» firstSliceScope : OperationalScopeBoundary «part» vehicleTargetForwardCollisionRiskMitigationScope : InScopeItem «part» pedestrianTargetOutOfScope : OutOfScopeItem «part» bicycleTargetOutOfScope : OutOfScopeItem «part» complianceClaimOutOfScope : OutOfScopeItem «part» conceptualRealizationOutOfScope : OutOfScopeItem «part» physicalSoftwareRealizationOutOfScope : OutOfScopeItem «view» aebsIncrementFramingView viewpoints selectedIncrementFramingViewpoint : IncrementFramingViewpoint exposes IncrementFraming::* rendering viewRendering ::> asTreeDiagram «view» aebsRegulatoryScopeView viewpoints selectedRegulatoryScopeViewpoint : RegulatoryScopeViewpoint exposes IncrementFraming::* rendering viewRendering ::> asTreeDiagram

Hover a model element for details open raw SVG.

view aebsRegulatoryScopeViewsource ↓

ViewpointselectedRegulatoryScopeViewpoint (RegulatoryScopeViewpoint)
ConcernregulatoryScopeWithoutComplianceClaimConcern
RenderasTreeDiagram
ExposesIncrementFraming::*
Sourcetextual-notation-of-model/packages/features/aebs/aebs_increment_framing.sysml:130
diagram-aebsRegulatoryScopeView.svg
«view» aebsRegulatoryScopeView expose IncrementFraming::* «concern» productLineCapabilityClassificationConcern : ProductLineCapabilityClassificationConcern doc Reviewers need AEBS scope elements to distinguish common product-line capabilities from candidate features and later variability decisions. subject ref stakeholders productLineEngineer : ProductLineEngineer systemsEngineer : SystemsEngineer reviewer : OpenSourceReviewer require constraints ^doc Reviewers need model content to distinguish common product-line capabilities from features, candidate features, variability decisions, and deferred variability decisions. «concern» regulatoryScopeWithoutComplianceClaimConcern : RegulatoryScopeWithoutComplianceClaimConcern doc Reviewers need the UNECE R152 regulatory anchor and open compliance assumptions to be visible without treating this increment as evidence of compliance, certification, or type approval. subject ref stakeholders complianceEngineer : ComplianceEngineer verificationEngineer : VerificationEngineer reviewer : OpenSourceReviewer require constraints ^doc Reviewers need regulatory anchors, source assumptions, missing evidence, and scope boundaries to be visible without implying compliance, certification, or type approval. «concern» incrementBoundaryConcern : IncrementBoundaryConcern doc Reviewers need a small increment boundary that separates framing, operational context, functional modeling, conceptual realization, physical/software realization, and evidence work. subject ref stakeholders systemsEngineer : SystemsEngineer verificationEngineer : VerificationEngineer reviewer : OpenSourceReviewer require constraints ^doc Reviewers need each increment to separate framing, operational context, needs, requirements, functional modeling, logical realization, physical/software realization, and evidence work. «concern» methodStackConcern : MethodStackConcern doc Reviewers need to see how SAF viewpoint selection, SYSMOD method flow, DE4SDV ontology terms, SysML v2 model expression, and VSS signal catalog usage relate without collapsing them into one method blob. subject ref stakeholders systemsEngineer : SystemsEngineer reviewer : OpenSourceReviewer require constraints ^doc Reviewers need the relationship between viewpoint selection, method flow, ontology terms, SysML v2 expression, and external catalog use to remain explicit rather than collapsed into one method blob. «part» incAEBS001 : FeatureIncrement «part» system1SDVProductLine : System1SDVProductLine «part» system2EngineeringAndAssuranceSystem : System2EngineeringAndAssuranceSystem «part» system3OpenSourceGovernanceEcosystem : System3OpenSourceGovernanceEcosystem «part» safViewpointSelection : SAFViewpointSelection «part» sysmodMethodFlow : SYSMODMethodFlow «part» de4sdvOntologyKernel : DE4SDVOntologyKernel «part» sysmlv2ModelExpression : SysMLv2ModelExpression «part» vssCandidateSignalCatalog : VSSCandidateSignalCatalog «part» forwardCollisionRiskMitigation : CommonProductLineCapability «part» vehicleTargetAEBSSupport : CommonProductLineCapability «part» pedestrianTargetAEBSScope : DeferredProductLineScope «part» bicycleTargetAEBSScope : DeferredProductLineScope «comment» Native SysML v2 variation usages record unresolved AEBS variability topics without inventing a project-local variation-point part definition. The only variants in this framing slice are deferred choices; concrete sensor/evidence variants require later functional/evidence increments. «variation part» aebsSensorPackageSelection parts sensorPackageChoiceDeferred «variation part» aebsEvidenceLevelSelection parts evidenceLevelChoiceDeferred «part» firstSliceScope : OperationalScopeBoundary «part» vehicleTargetForwardCollisionRiskMitigationScope : InScopeItem «part» pedestrianTargetOutOfScope : OutOfScopeItem «part» bicycleTargetOutOfScope : OutOfScopeItem «part» complianceClaimOutOfScope : OutOfScopeItem «part» conceptualRealizationOutOfScope : OutOfScopeItem «part» physicalSoftwareRealizationOutOfScope : OutOfScopeItem «view» aebsIncrementFramingView viewpoints selectedIncrementFramingViewpoint : IncrementFramingViewpoint exposes IncrementFraming::* rendering viewRendering ::> asTreeDiagram «view» aebsProductLineClassificationView viewpoints selectedProductLineClassificationViewpoint : ProductLineClassificationViewpoint exposes IncrementFraming::* rendering viewRendering ::> asTreeDiagram

Hover a model element for details open raw SVG.

Source

1/*2 * DE4SDV AEBS increment framing model slice.3 *4 * This package mirrors INC-AEBS-001 from5 * methodologies/sysmod-sysmlv2/pilots/aebs-increment-framing.yaml.6 * It is a framing/model-governance slice, not an AEBS design baseline or7 * UNECE R152 compliance claim.8 *9 * Shared DE4SDV method, stakeholder, product-line, and viewpoint definitions10 * are imported from reusable method packages. This feature package keeps only11 * AEBS-specific concern usages, product-line classification usages, scope12 * usages, and concrete views.13 */1415package DE4SDV_AEBSIncrementFraming {16  package Features {17    package AEBS {18      package IncrementFraming {19        private import Views::*;20        private import DE4SDV_MethodContext::*;21        private import DE4SDV_Stakeholders::*;22        private import DE4SDV_ProductLine::*;23        private import DE4SDV_MethodViewpoints::*;24        private import SAF_Viewpoints::*;2526        concern productLineCapabilityClassificationConcern : ProductLineCapabilityClassificationConcern {27          doc /*28           * Reviewers need AEBS scope elements to distinguish common product-line29           * capabilities from candidate features and later variability decisions.30           */31          subject;32          stakeholder productLineEngineer : ProductLineEngineer;33          stakeholder systemsEngineer : SystemsEngineer;34          stakeholder reviewer : OpenSourceReviewer;35        }3637        concern regulatoryScopeWithoutComplianceClaimConcern : RegulatoryScopeWithoutComplianceClaimConcern {38          doc /*39           * Reviewers need the UNECE R152 regulatory anchor and open compliance40           * assumptions to be visible without treating this increment as evidence41           * of compliance, certification, or type approval.42           */43          subject;44          stakeholder complianceEngineer : ComplianceEngineer;45          stakeholder verificationEngineer : VerificationEngineer;46          stakeholder reviewer : OpenSourceReviewer;47        }4849        concern incrementBoundaryConcern : IncrementBoundaryConcern {50          doc /*51           * Reviewers need a small increment boundary that separates framing,52           * operational context, functional modeling, conceptual realization,53           * physical/software realization, and evidence work.54           */55          subject;56          stakeholder systemsEngineer : SystemsEngineer;57          stakeholder verificationEngineer : VerificationEngineer;58          stakeholder reviewer : OpenSourceReviewer;59        }6061        concern methodStackConcern : MethodStackConcern {62          doc /*63           * Reviewers need to see how SAF viewpoint selection, SYSMOD method flow,64           * DE4SDV ontology terms, SysML v2 model expression, and VSS signal65           * catalog usage relate without collapsing them into one method blob.66           */67          subject;68          stakeholder systemsEngineer : SystemsEngineer;69          stakeholder reviewer : OpenSourceReviewer;70        }7172        part incAEBS001 : FeatureIncrement;7374        part system1SDVProductLine : System1SDVProductLine;75        part system2EngineeringAndAssuranceSystem : System2EngineeringAndAssuranceSystem;76        part system3OpenSourceGovernanceEcosystem : System3OpenSourceGovernanceEcosystem;7778        part safViewpointSelection : SAFViewpointSelection;79        part sysmodMethodFlow : SYSMODMethodFlow;80        part de4sdvOntologyKernel : DE4SDVOntologyKernel;81        part sysmlv2ModelExpression : SysMLv2ModelExpression;82        part vssCandidateSignalCatalog : VSSCandidateSignalCatalog;8384        part forwardCollisionRiskMitigation : CommonProductLineCapability;85        part vehicleTargetAEBSSupport : CommonProductLineCapability;86        part pedestrianTargetAEBSScope : DeferredProductLineScope;87        part bicycleTargetAEBSScope : DeferredProductLineScope;8889        /*90         * Native SysML v2 variation usages record unresolved AEBS variability91         * topics without inventing a project-local variation-point part definition. The only variants92         * in this framing slice are deferred choices; concrete sensor/evidence93         * variants require later functional/evidence increments.94         */95        variation part aebsSensorPackageSelection {96          variant part sensorPackageChoiceDeferred;97        }9899        variation part aebsEvidenceLevelSelection {100          variant part evidenceLevelChoiceDeferred;101        }102103        part firstSliceScope : OperationalScopeBoundary;104        part vehicleTargetForwardCollisionRiskMitigationScope : InScopeItem;105        part pedestrianTargetOutOfScope : OutOfScopeItem;106        part bicycleTargetOutOfScope : OutOfScopeItem;107        part complianceClaimOutOfScope : OutOfScopeItem;108        part conceptualRealizationOutOfScope : OutOfScopeItem;109        part physicalSoftwareRealizationOutOfScope : OutOfScopeItem;110111        view aebsIncrementFramingView {112          viewpoint selectedIncrementFramingViewpoint : IncrementFramingViewpoint {113            frame productLineCapabilityClassificationConcern;114            frame regulatoryScopeWithoutComplianceClaimConcern;115            frame incrementBoundaryConcern;116            frame methodStackConcern;117          }118119          expose IncrementFraming::*;120          render asTreeDiagram;121        }122        view aebsProductLineClassificationView {123          viewpoint selectedProductLineClassificationViewpoint : ProductLineClassificationViewpoint {124            frame productLineCapabilityClassificationConcern;125          }126127          expose IncrementFraming::*;128          render asTreeDiagram;129        }130        view aebsRegulatoryScopeView {131          viewpoint selectedRegulatoryScopeViewpoint : RegulatoryScopeViewpoint {132            frame regulatoryScopeWithoutComplianceClaimConcern;133          }134135          expose IncrementFraming::*;136          render asTreeDiagram;137        }138      }139    }140  }141}142