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

Source

1/*2 * DE4SDV AEBS needs and draft requirements model slice.3 *4 * System 1 product needs and requirements are partitioned from System 25 * engineering-assurance and evidence-governance needs and requirements.6 * Stable externally imported usage names are retained where practical.7 * No V&V verdict, realization, or UNECE R152 compliance claim is made here.8 */9package DE4SDV_AEBSNeedsRequirements {10  package Features {11    package AEBS {12      package NeedsRequirements {13        private import DE4SDV_Stakeholders::*;14        private import DE4SDV_MethodContext::*;15        private import DE4SDV_ProductLine::*;16        private import DE4SDV_MethodViewpoints::*;17        private import SAF_Viewpoints::*;18        private import SysideViews::**;19        private import Views::*;2021        part def AEBSCapability :> CommonProductLineCapability;2223        requirement def PedestrianCollisionRiskNeed :> StakeholderNeedCandidate;24        requirement def BicycleCollisionRiskNeed :> StakeholderNeedCandidate;2526        part incAEBS003 : NeedsRequirementsIncrement;2728        part aebsNeedsRequirementsSystemContext : SystemContext {29          doc /* DE4SDV method system context for INC-AEBS-003. */30          part productLine : SDVProductLine :>> systemOfInterest;31          part memberProduct : ProductLineMemberProduct;32          part aebsCapability : AEBSCapability;33          part roadUserStakeholder : RoadUser;34          part occupantStakeholder : VehicleOccupant;35          part systemsEngineerStakeholder : SystemsEngineer;36          part productLineEngineerStakeholder : ProductLineEngineer;37          part complianceEngineerStakeholder : ComplianceEngineer;38          part verificationEngineerStakeholder : VerificationEngineer;3940          requirement aebsNeedsRequirementsProblemStatement : ProblemStatement {41            doc /* How can DE4SDV define partitioned AEBS product and assurance needs and draft requirements while preserving boundaries, gaps, and controlled source constraints without making realization or compliance claims? */42            subject increment : NeedsRequirementsIncrement;43            stakeholder roadUser : RoadUser;44            stakeholder occupant : VehicleOccupant;45            stakeholder systemsEngineer : SystemsEngineer;46            stakeholder productLineEngineer : ProductLineEngineer;47            stakeholder complianceEngineer : ComplianceEngineer;48            stakeholder verificationEngineer : VerificationEngineer;49          }50        }5152        package System1Product {53          requirement needCommonAEBSCapability : ProductLineCommonCapabilityNeed {54            doc /* N-AEBS-001 draft System 1 need. */55            subject productLine : SDVProductLine;56            stakeholder roadUser : RoadUser;57            stakeholder occupant : VehicleOccupant;58            require constraint { doc /* Road users and vehicle occupants need the SDV product line to define AEBS as a common capability required across member products to reduce forward rear-end in-lane collision risk with a vehicle target under defined operating conditions. */ }59          }60          requirement needPedestrianCollisionRiskReduction : PedestrianCollisionRiskNeed {61            doc /* N-AEBS-006 draft System 1 need; source identity is controlled and applicability remains open. */62            subject productLine : SDVProductLine;63            stakeholder pedestrian : RoadUser;64            require constraint { doc /* Pedestrians need the SDV product line to provide a common AEBS capability that reduces forward collision risk with a pedestrian target under controlled applicable operating conditions. */ }65          }66          requirement needBicycleCollisionRiskReduction : BicycleCollisionRiskNeed {67            doc /* N-AEBS-007 draft System 1 need; source identity is controlled and applicability remains open. */68            subject productLine : SDVProductLine;69            stakeholder cyclist : RoadUser;70            require constraint { doc /* Cyclists need the SDV product line to provide a common AEBS capability that reduces forward collision risk with a bicycle target under controlled applicable operating conditions. */ }71          }72          requirement needBoundedDegradationAndAvailability : ProductSafetyAvailabilityNeed {73            doc /* N-AEBS-008 draft System 1 safety and availability need. */74            subject memberProduct : ProductLineMemberProduct;75            stakeholder roadUser : RoadUser;76            stakeholder occupant : VehicleOccupant;77            require constraint { doc /* Road users and vehicle occupants need each SDV product-line member product to manage AEBS degradation so that behavior remains bounded and AEBS availability is apparent when required inputs or AEBS functions are not healthy. */ }78          }7980          requirement reqDetectForwardCollisionRisk : FunctionalRequirementCandidate {81            doc /* REQ-AEBS-001 candidate. */82            subject memberProduct : ProductLineMemberProduct;83            require constraint { doc /* Each SDV product-line member product shall realize the common AEBS capability by detecting imminent forward collision risk with a vehicle target under selected operating conditions. */ }84          }85          requirement reqProvideCollisionWarning : FunctionalRequirementCandidate {86            doc /* REQ-AEBS-002 candidate. */87            subject memberProduct : ProductLineMemberProduct;88            require constraint { doc /* Each SDV product-line member product shall realize the common AEBS capability by providing a collision warning to the driver when selected warning conditions are met. */ }89          }90          requirement reqCommandEmergencyBraking : FunctionalRequirementCandidate {91            doc /* REQ-AEBS-003 candidate. */92            subject memberProduct : ProductLineMemberProduct;93            require constraint { doc /* Each SDV product-line member product shall realize the common AEBS capability by commanding emergency braking when selected activation conditions are met and no overriding condition prevents intervention. */ }94          }95          requirement reqAllowDriverOverride : FunctionalRequirementCandidate {96            doc /* REQ-AEBS-004 draft; controlled override-response mapping remains a blocker. */97            subject memberProduct : ProductLineMemberProduct;98            require constraint { doc /* When a valid, fresh, and unambiguous driver input is classified as a conscious override under controlled override criteria during AEBS intervention, each SDV product-line member product shall apply the intervention response selected by the controlled override-response mapping. */ }99          }100          requirement reqDetectAEBSFailureCondition : SafetyConstraintRequirementCandidate {101            doc /* REQ-AEBS-005 failure-detection draft derived from N-AEBS-008, not an assurance visibility need. */102            subject memberProduct : ProductLineMemberProduct;103            require constraint { doc /* Under controlled failure-detection criteria, each SDV product-line member product shall detect AEBS-related failure conditions. */ }104          }105          requirement reqResistFalseReaction : SafetyConstraintRequirementCandidate {106            doc /* REQ-AEBS-008 warning-silence draft; criteria, window, and tolerances remain gaps. */107            subject memberProduct : ProductLineMemberProduct;108            require constraint { doc /* When controlled non-activation criteria determine that imminent forward collision risk is absent under defined operating conditions, each SDV product-line member product shall not issue an AEBS collision warning. */ }109          }110          requirement reqHandleDegradedUnavailableInputs : SafetyConstraintRequirementCandidate {111            doc /* REQ-AEBS-009 state-transition draft; state mapping, ownership, and timing remain gaps. */112            subject memberProduct : ProductLineMemberProduct;113            require constraint { doc /* When a required AEBS input is stale, missing, malformed, inconsistent, or unavailable under controlled input-health criteria, each SDV product-line member product shall enter the AEBS state selected by the controlled degraded-state mapping. */ }114          }115          requirement reqPedestrianTargetResponse : FunctionalRequirementCandidate {116            doc /* REQ-AEBS-010 pedestrian detection draft; stable usage name retained for imports. */117            subject memberProduct : ProductLineMemberProduct;118            require constraint { doc /* Each SDV product-line member product shall detect imminent forward collision risk with a pedestrian target under controlled applicable pedestrian-target operating conditions. */ }119          }120          requirement reqBicycleTargetResponse : FunctionalRequirementCandidate {121            doc /* REQ-AEBS-011 bicycle detection draft; stable usage name retained for imports. */122            subject memberProduct : ProductLineMemberProduct;123            require constraint { doc /* Each SDV product-line member product shall detect imminent forward collision risk with a bicycle target under controlled applicable bicycle-target operating conditions. */ }124          }125          requirement reqResistFalseBrakingCommand : SafetyConstraintRequirementCandidate {126            doc /* REQ-AEBS-012 braking-silence draft. */127            subject memberProduct : ProductLineMemberProduct;128            require constraint { doc /* When controlled non-activation criteria determine that imminent forward collision risk is absent under defined operating conditions, each SDV product-line member product shall not command AEBS emergency braking. */ }129          }130          requirement reqIndicateDegradedUnavailableStatus : SafetyConstraintRequirementCandidate {131            doc /* REQ-AEBS-013 status-indication draft. */132            subject memberProduct : ProductLineMemberProduct;133            require constraint { doc /* When a required AEBS input is stale, missing, malformed, inconsistent, or unavailable under controlled input-health criteria, each SDV product-line member product shall provide the status indication selected by the controlled degraded-state indication mapping. */ }134          }135          requirement reqPedestrianTargetControlledResponse : FunctionalRequirementCandidate {136            doc /* REQ-AEBS-014 pedestrian response draft. */137            subject memberProduct : ProductLineMemberProduct;138            require constraint { doc /* Under controlled applicable pedestrian-target operating conditions, each SDV product-line member product shall apply the controlled AEBS response to classified pedestrian-target collision risk. */ }139          }140          requirement reqBicycleTargetControlledResponse : FunctionalRequirementCandidate {141            doc /* REQ-AEBS-015 bicycle response draft. */142            subject memberProduct : ProductLineMemberProduct;143            require constraint { doc /* Under controlled applicable bicycle-target operating conditions, each SDV product-line member product shall apply the controlled AEBS response to classified bicycle-target collision risk. */ }144          }145        }146147        package System2EngineeringAssurance {148          requirement needExplicitOperationalBoundary : EngineeringTraceabilityNeed {149            doc /* N-AEBS-002 draft System 2 need. */150            subject increment : NeedsRequirementsIncrement;151            stakeholder systemsEngineer : SystemsEngineer;152            require constraint { doc /* Systems engineers need the DE4SDV AEBS increment to keep its operational boundary, assumptions, source constraints, and out-of-scope cases explicit while draft requirements are derived. */ }153          }154          requirement needProductLineClassification : ProductLineClassificationNeed {155            doc /* N-AEBS-003 draft System 2 need. */156            subject increment : NeedsRequirementsIncrement;157            stakeholder productLineEngineer : ProductLineEngineer;158            require constraint { doc /* Product-line engineers need the DE4SDV AEBS increment to keep AEBS classified as a common capability, with native SysML v2 variation and variant choices modeled separately without weakening the System 1 capability. */ }159          }160          requirement needVisibleRegulatoryAssumptions : RegulatoryVisibilityNeed {161            doc /* N-AEBS-004 draft System 2 need. */162            subject increment : NeedsRequirementsIncrement;163            stakeholder complianceEngineer : ComplianceEngineer;164            require constraint { doc /* Compliance engineers need the DE4SDV AEBS increment to keep regulatory assumptions, controlled source references, and open applicability and interpretation gaps visible without implying compliance or type approval. */ }165          }166          requirement needRequirementVVPlanning : VerificationPlanningNeed {167            doc /* N-AEBS-005 draft System 2 need. */168            subject increment : NeedsRequirementsIncrement;169            stakeholder verificationEngineer : VerificationEngineer;170            require constraint { doc /* Verification engineers need the DE4SDV AEBS increment to maintain a separate controlled V&V planning attachment for each draft AEBS requirement without changing the product obligation. */ }171          }172          requirement reqKeepProductLineClassificationExplicit : ProductLineConstraintRequirementCandidate {173            doc /* REQ-AEBS-006 System 2 candidate. */174            subject increment : NeedsRequirementsIncrement;175            require constraint { doc /* The DE4SDV AEBS increment shall keep common-capability, feature, and native SysML v2 variation and variant classifications explicit for each AEBS behavior or scope element in its model baseline. */ }176          }177          requirement reqTraceRequirementVVAndGaps : TraceabilityConstraintRequirementCandidate {178            doc /* REQ-AEBS-007 System 2 candidate. */179            subject increment : NeedsRequirementsIncrement;180            require constraint { doc /* The DE4SDV AEBS increment shall maintain separate trace links from each draft AEBS requirement to its source, stakeholder need, unresolved gaps, validation reference, and controlled V&V planning attachment. */ }181          }182          requirement reqTraceEvidenceContractsToControlledBoundary : EvidenceContractTraceabilityRequirementCandidate {183            doc /* REQ-AEBS-S2-001 System 2 evidence-contract candidate derived only from N-AEBS-002. */184            subject increment : NeedsRequirementsIncrement;185            require constraint { doc /* The DE4SDV AEBS increment shall maintain trace links from each AEBS evidence contract to its controlled operational boundary, assumptions, source constraints, and exclusions. */ }186          }187        }188189        dependency req001DerivedFromNeed001 from reqDetectForwardCollisionRisk to needCommonAEBSCapability;190        dependency req002DerivedFromNeed001 from reqProvideCollisionWarning to needCommonAEBSCapability;191        dependency req003DerivedFromNeed001 from reqCommandEmergencyBraking to needCommonAEBSCapability;192        dependency req004DerivedFromNeed001 from reqAllowDriverOverride to needCommonAEBSCapability;193        dependency req008DerivedFromNeed001 from reqResistFalseReaction to needCommonAEBSCapability;194        dependency req012DerivedFromNeed001 from reqResistFalseBrakingCommand to needCommonAEBSCapability;195        dependency req005DerivedFromNeed008 from reqDetectAEBSFailureCondition to needBoundedDegradationAndAvailability;196        dependency req009DerivedFromNeed008 from reqHandleDegradedUnavailableInputs to needBoundedDegradationAndAvailability;197        dependency req013DerivedFromNeed008 from reqIndicateDegradedUnavailableStatus to needBoundedDegradationAndAvailability;198        dependency req010DerivedFromNeed006 from reqPedestrianTargetResponse to needPedestrianCollisionRiskReduction;199        dependency req014DerivedFromNeed006 from reqPedestrianTargetControlledResponse to needPedestrianCollisionRiskReduction;200        dependency req011DerivedFromNeed007 from reqBicycleTargetResponse to needBicycleCollisionRiskReduction;201        dependency req015DerivedFromNeed007 from reqBicycleTargetControlledResponse to needBicycleCollisionRiskReduction;202        dependency req006DerivedFromNeed003 from reqKeepProductLineClassificationExplicit to needProductLineClassification;203        dependency req007DerivedFromNeed004 from reqTraceRequirementVVAndGaps to needVisibleRegulatoryAssumptions;204        dependency req007DerivedFromNeed005 from reqTraceRequirementVVAndGaps to needRequirementVVPlanning;205        dependency reqS2001DerivedFromNeed002 from reqTraceEvidenceContractsToControlledBoundary to needExplicitOperationalBoundary;206207        public import System1Product::*;208        public import System2EngineeringAssurance::*;209210        /*211         * Gaps — deferred scope items per the DE4SDV method.212         * These are the most important gap categories; individual213         * requirement-level gaps are referenced in the YAML V&V planning.214         */215        part operatingConditionsGap : DeferredProductLineScope {216          doc /* GAP-AEBS-REQ-001: Selected operating conditions remain undefined. */217        }218        part detectionCriteriaGap : DeferredProductLineScope {219          doc /* GAP-AEBS-REQ-002: Vehicle-target detection criteria remain undefined. */220        }221        part warningCriteriaGap : DeferredProductLineScope {222          doc /* GAP-AEBS-REQ-003: Collision-warning timing, modality, and observability criteria remain undefined. */223        }224        part brakingActivationGap : DeferredProductLineScope {225          doc /* GAP-AEBS-REQ-004: Emergency-braking activation conditions and braking demand profile remain undefined. */226        }227        part nonActivationGap : DeferredProductLineScope {228          doc /* GAP-AEBS-REQ-005: Non-activation and false-reaction constraints remain undefined. */229        }230        part overrideCriteriaGap : DeferredProductLineScope {231          doc /* GAP-AEBS-REQ-006: Conscious driver override inputs and resulting behavior remain undefined. */232        }233        part failureDetectionGap : DeferredProductLineScope {234          doc /* GAP-AEBS-REQ-007: AEBS failure detection, indication, and safe-operation criteria remain undefined. */235        }236        part variationModelingGap : DeferredProductLineScope {237          doc /* GAP-AEBS-REQ-008: Native SysML v2 variation and variant choices are not yet modeled. */238        }239        part vssSignalGap : DeferredProductLineScope {240          doc /* GAP-AEBS-REQ-009: VSS signal candidates are intentionally deferred until the functional-interface increment. */241        }242        part satisfactionGap : DeferredProductLineScope {243          doc /* GAP-AEBS-REQ-010: Requirement satisfaction assertions are deferred until functional/conceptual realization exists. */244        }245        part regulatoryApplicabilityGap : DeferredProductLineScope {246          doc /* GAP-AEBS-REQ-013: Source identity is controlled, but amendment-selection rationale, vehicle-category applicability, and authority interpretation remain unresolved. */247        }248        part quantifiedThresholdGap : DeferredProductLineScope {249          doc /* GAP-AEBS-REQ-014: Promotion of quantified thresholds into System 1 obligations remains deferred. */250        }251        part pedestrianTargetGap : DeferredProductLineScope {252          doc /* GAP-AEBS-REQ-015: Pedestrian target definition, operating conditions, response criteria, and applicability remain unresolved. */253        }254        part bicycleTargetGap : DeferredProductLineScope {255          doc /* GAP-AEBS-REQ-016: Bicycle target definition, operating conditions, response criteria, and applicability remain unresolved. */256        }257258        concern stakeholderNeedsConcern : StakeholderNeedsConcern {259          subject;260          stakeholder systemsEngineer : SystemsEngineer;261          stakeholder reviewer : OpenSourceReviewer;262        }263        concern requirementTraceConcern : RequirementTraceConcern {264          subject;265          stakeholder verificationEngineer : VerificationEngineer;266          stakeholder reviewer : OpenSourceReviewer;267        }268        view aebsStakeholderNeedsView : TVD::TableView {269          viewpoint selectedStakeholderNeedsViewpoint : StakeholderRequirementDefinitionViewpoint { frame stakeholderNeedsConcern; }270          expose System1Product::*;271          expose System2EngineeringAssurance::*;272          filter @ SysML::RequirementUsage;273          attribute :>> includeReferenceElements = true;274          attribute :>> maxRowHeight = 300;275          view ID :> columnViews {276            attribute :>> featureToRender = CT::declaredName;277          }278          view Name :> columnViews {279            attribute :>> featureToRender = CT::heritage;280          }281          view Statement :> columnViews {282            attribute :>> featureToRender = CT::documentation;283            attribute :>> columnWidth = 360;284          }285        }286        view aebsRequirementTraceView {287          viewpoint selectedRequirementTraceViewpoint : SystemRequirementTraceabilityViewpoint { frame requirementTraceConcern; }288          expose System1Product::*;289          expose System2EngineeringAssurance::*;290          render asTreeDiagram;291        }292      }293    }294  }295}296