DE4SDV Model Viewer Revision
Model / textual-notation-of-model / packages / features / middleware / middleware_requirements.sysml

textual-notation-of-model/packages/features/middleware/middleware_requirements.sysml

2 view(s) · 78 declared member(s) Jump to source ↓

view middlewareSystemRequirementsViewsource ↓

ViewpointselectedSystemRequirementsViewpoint (SystemRequirementDefinitionViewpoint)
View typeTVD::TableView
ConcernrequirementTraceConcern
ExposesSystem1Product::*
System2EngineeringAssurance::*
Sourcetextual-notation-of-model/packages/features/middleware/middleware_requirements.sysml:227
diagram-table-middlewareSystemRequirementsView.svg
Middleware system requirements Lists system requirements with their authoritative natural-language statements. Middleware system requirements ID Name Statement reqProvideMiddlewareSignalAccess MiddlewareSignalAccessRequirement, FunctionalRequirementCandidate, RequirementCandidate, SYSMODRequirementBase, RequirementsManagementAttributeBase Each SDV product-line member product shall provide the ADAS application access to the vehicle signals required by its selected operational use cases through the selected middleware integration boundary. reqProvideMiddlewareDiagnosticAccess MiddlewareDiagnosticAccessRequirement, FunctionalRequirementCandidate, RequirementCandidate, SYSMODRequirementBase, RequirementsManagementAttributeBase Each SDV product-line member product shall provide the ADAS application access to middleware and vehicle diagnostic status from which the health of the selected integration boundary can be determined. reqCoordinateMiddlewareLifecycle MiddlewareLifecycleCoordinationRequirement, FunctionalRequirementCandidate, RequirementCandidate, SYSMODRequirementBase, RequirementsManagementAttributeBase Each SDV product-line member product shall coordinate middleware integration lifecycle state with the ADAS application so that startup, readiness, degraded operation, and shutdown transitions are observable at the integration boundary. reqMonitorMiddlewareHealth MiddlewareHealthMonitoringRequirement, FunctionalRequirementCandidate, RequirementCandidate, SYSMODRequirementBase, RequirementsManagementAttributeBase Each SDV product-line member product shall monitor the health of the selected middleware integration boundary and provide an observable indication when a required integration service is stale, missing, inconsistent, or unavailable. reqCoordinateMiddlewareUpdates MiddlewareUpdateCoordinationRequirement, FunctionalRequirementCandidate, RequirementCandidate, SYSMODRequirementBase, RequirementsManagementAttributeBase Each SDV product-line member product shall coordinate middleware integration updates with the ADAS application lifecycle so that an update does not silently invalidate required signal, diagnostic, lifecycle, or health interfaces. reqIsolateSafetyPath MiddlewareSafetyPathIsolationRequirement, SafetyConstraintRequirementCandidate, RequirementCandidate, SYSMODRequirementBase, RequirementsManagementAttributeBase Each SDV product-line member product shall prevent a failure of the non-safety middleware integration path from causing an uncontrolled emergency intervention command, whether the selected realization uses a safety-certified middleware partition or a direct vehicle-command path. reqProvideServiceDiscovery MiddlewareServiceDiscoveryRequirement, FunctionalRequirementCandidate, RequirementCandidate, SYSMODRequirementBase, RequirementsManagementAttributeBase Each SDV product-line member product shall discover and bind the middleware services required by the selected ADAS application integration configuration before those services are used. reqAuthenticateServiceBinding MiddlewareServiceAuthenticationRequirement, SecurityConstraintRequirementCandidate, RequirementCandidate, SYSMODRequirementBase, RequirementsManagementAttributeBase Each SDV product-line member product shall authenticate a middleware service binding before accepting service data or commands across a trust boundary defined for the selected integration configuration. reqMaintainMiddlewareBoundaryTraceability MiddlewareBoundaryTraceabilityRequirement, TraceabilityConstraintRequirementCandidate, RequirementCandidate, SYSMODRequirementBase, RequirementsManagementAttributeBase The DE4SDV middleware increment shall maintain trace links from each middleware requirement to its stakeholder need, operational-context source, feature/common-capability classification, unresolved gap, and planned verification record.

Hover a model element for details open raw SVG.

view middlewareRequirementTraceViewsource ↓

ViewpointselectedRequirementTraceViewpoint (SystemRequirementTraceabilityViewpoint)
View typeGeneralView
ConcernrequirementTraceConcern
Depth1
ExposesSystem1Product::*
System2EngineeringAssurance::*
DE4SDV_MiddlewareOperationalContext::Features::Middleware::OperationalContext::'exchange vehicle signals'
DE4SDV_MiddlewareOperationalContext::Features::Middleware::OperationalContext::'access diagnostics'
DE4SDV_MiddlewareOperationalContext::Features::Middleware::OperationalContext::'coordinate lifecycle'
DE4SDV_MiddlewareOperationalContext::Features::Middleware::OperationalContext::'monitor service health'
DE4SDV_MiddlewareOperationalContext::Features::Middleware::OperationalContext::'coordinate software update'
DE4SDV_MiddlewareOperationalContext::Features::Middleware::OperationalContext::'emergency intervention via safety path'
DE4SDV_MiddlewareFunctionalArchitecture::Features::Middleware::FunctionalArchitecture::middlewareIntegrationFunctionalFlow
Sourcetextual-notation-of-model/packages/features/middleware/middleware_requirements.sysml:251
diagram-middlewareRequirementTraceView.svg
«view» middlewareRequirementTraceView : GeneralView expose System1Product::* expose System2EngineeringAssurance::* expose DE4SDV_MiddlewareOperationalContext::Features::Middleware::OperationalContext::'exchange vehicle signals' expose DE4SDV_MiddlewareOperationalContext::Features::Middleware::OperationalContext::'access diagnostics' expose DE4SDV_MiddlewareOperationalContext::Features::Middleware::OperationalContext::'coordinate lifecycle' expose DE4SDV_MiddlewareOperationalContext::Features::Middleware::OperationalContext::'monitor service health' expose DE4SDV_MiddlewareOperationalContext::Features::Middleware::OperationalContext::'coordinate software update' expose DE4SDV_MiddlewareOperationalContext::Features::Middleware::OperationalContext ::'emergency intervention via safety path' expose DE4SDV_MiddlewareFunctionalArchitecture::Features::Middleware::FunctionalArchitecture ::middlewareIntegrationFunctionalFlow «requirement» reqProvideMiddlewareSignalAccess : MiddlewareSignalAccessRequirement doc REQ-MW-001 draft design-input requirement. attributes status :>> status = ReqStatus::ReadyForReview source :>> source = "Derived from N-MW-001" rationale :>> rationale = "Signal access is the core middleware integration service for the ADAS application." ^status ^source ^rationale subject memberProduct : ProductLineMemberProduct require constraints doc Each SDV product-line member product shall provide the ADAS application access to the vehicle signals required by its selected operational use cases through the selected middleware integration boundary. statement { language "English" } «requirement» reqProvideMiddlewareDiagnosticAccess : MiddlewareDiagnosticAccessRequirement doc REQ-MW-002 draft design-input requirement. attributes status :>> status = ReqStatus::ReadyForReview source :>> source = "Derived from N-MW-001" rationale :>> rationale = "Boundary health determinations require diagnostic visibility." subject memberProduct : ProductLineMemberProduct require constraints doc Each SDV product-line member product shall provide the ADAS application access to middleware and vehicle diagnostic status from which the health of the selected integration boundary can be determined. statement { language "English" } «requirement» reqCoordinateMiddlewareLifecycle : MiddlewareLifecycleCoordinationRequirement doc REQ-MW-003 draft design-input requirement. attributes status :>> status = ReqStatus::ReadyForReview source :>> source = "Derived from N-MW-001" rationale :>> rationale = "Lifecycle transitions must be observable at the integration boundary." subject memberProduct : ProductLineMemberProduct require constraints doc Each SDV product-line member product shall coordinate middleware integration lifecycle state with the ADAS application so that startup, readiness, degraded operation, and shutdown transitions are observable at the integration boundary. statement { language "English" } «requirement» reqMonitorMiddlewareHealth : MiddlewareHealthMonitoringRequirement doc REQ-MW-004 draft design-input requirement. attributes status :>> status = ReqStatus::ReadyForReview source :>> source = "Derived from N-MW-001" rationale :>> rationale = "Degraded integration services must be detected and indicated." subject memberProduct : ProductLineMemberProduct require constraints doc Each SDV product-line member product shall monitor the health of the selected middleware integration boundary and provide an observable indication when a required integration service is stale, missing, inconsistent, or unavailable. statement { language "English" } «requirement» reqCoordinateMiddlewareUpdates : MiddlewareUpdateCoordinationRequirement doc REQ-MW-005 draft design-input requirement. attributes status :>> status = ReqStatus::ReadyForReview source :>> source = "Derived from N-MW-001" rationale :>> rationale = "Updates must not silently invalidate required interfaces." subject memberProduct : ProductLineMemberProduct require constraints doc Each SDV product-line member product shall coordinate middleware integration updates with the ADAS application lifecycle so that an update does not silently invalidate required signal, diagnostic, lifecycle, or health interfaces. statement { language "English" } «requirement» reqIsolateSafetyPath : MiddlewareSafetyPathIsolationRequirement doc REQ-MW-006 draft safety-constraint requirement; architecture choice and containment criteria remain open per GAP-MW-029. attributes status :>> status = ReqStatus::InDevelopment source :>> source = "Derived from N-MW-004" rationale :>> rationale = "Middleware failure must not cause uncontrolled emergency intervention; containment criteria open per GAP-MW-029." subject memberProduct : ProductLineMemberProduct require constraints doc Each SDV product-line member product shall prevent a failure of the non-safety middleware integration path from causing an uncontrolled emergency intervention command, whether the selected realization uses a safety-certified middleware partition or a direct vehicle-command path. statement { language "English" } «requirement» reqProvideServiceDiscovery : MiddlewareServiceDiscoveryRequirement doc REQ-MW-007 draft design-input requirement. attributes status :>> status = ReqStatus::ReadyForReview source :>> source = "Derived from N-MW-002" rationale :>> rationale = "Services must be bound before use for decoupled integration." subject memberProduct : ProductLineMemberProduct require constraints doc Each SDV product-line member product shall discover and bind the middleware services required by the selected ADAS application integration configuration before those services are used. statement { language "English" } «requirement» reqAuthenticateServiceBinding : MiddlewareServiceAuthenticationRequirement doc REQ-MW-008 draft security constraint derived from N-MW-009; trust-boundary details remain deferred per GAP-MW-012. attributes status :>> status = ReqStatus::InDevelopment source :>> source = "Derived from N-MW-009" rationale :>> rationale = "Service data and commands across a trust boundary must be authenticated; boundary details deferred per GAP-MW-012." subject memberProduct : ProductLineMemberProduct require constraints doc Each SDV product-line member product shall authenticate a middleware service binding before accepting service data or commands across a trust boundary defined for the selected integration configuration. statement { language "English" } «requirement» reqMaintainMiddlewareBoundaryTraceability : MiddlewareBoundaryTraceabilityRequirement doc REQ-MW-009 System 2 traceability requirement. attributes status :>> status = ReqStatus::ReadyForReview source :>> source = "Derived from N-MW-006" rationale :>> rationale = "Trace links are the increment's assurance backbone." subject increment : NeedsRequirementsIncrement require constraints doc The DE4SDV middleware increment shall maintain trace links from each middleware requirement to its stakeholder need, operational-context source, feature/common-capability classification, unresolved gap, and planned verification record. statement { language "English" } «use case» exchange vehicle signals subject middlewareOperationalContext : MiddlewareOperationalContext objective doc Exchange normal-driving vehicle signals through VSS-backed interfaces so the ADAS application can consume vehicle speed, yaw rate, longitudinal acceleration, and steering wheel angle. VSS signal references: Vehicle_Speed, Vehicle_AngularVelocity_Yaw, Vehicle_Acceleration_Longitudinal, Vehicle_Chassis_SteeringWheel_Angle. actors adasApplication : ADASApplicationStack vehicleMiddleware : VehiclePlatformMiddleware adapter : ApplicationMiddlewareAdapter «use case» access diagnostics subject middlewareOperationalContext : MiddlewareOperationalContext objective doc Provide authenticated diagnostic access during service so a technician can inspect vehicle and ADAS diagnostic state through middleware-mediated diagnostic services. VSS signal references: Vehicle_ADAS_AEBS_IsError and related diagnostic-state indicators exposed through the platform. actors diagnosticTechnician : DiagnosticTechnician vehicleMiddleware : VehiclePlatformMiddleware adapter : ApplicationMiddlewareAdapter «use case» coordinate lifecycle subject middlewareOperationalContext : MiddlewareOperationalContext objective doc Coordinate vehicle startup and shutdown lifecycle transitions via middleware-managed lifecycle commands. VSS-related lifecycle state and mode transitions are represented through the operational handoff between the ADAS application and the vehicle platform, including init, running, suspend, resume, and shutdown coordination. actors adasApplication : ADASApplicationStack vehicleMiddleware : VehiclePlatformMiddleware adapter : ApplicationMiddlewareAdapter «use case» monitor service health subject middlewareOperationalContext : MiddlewareOperationalContext objective doc Monitor service health and fault conditions so the ADAS application can detect degraded or unavailable middleware services and respond to health status updates. VSS signal references: Vehicle_ADAS_AEBS_IsError, Vehicle_ADAS_AEBS_FailureIndication_IsActive. actors adasApplication : ADASApplicationStack vehicleMiddleware : VehiclePlatformMiddleware adapter : ApplicationMiddlewareAdapter «use case» coordinate software update subject middlewareOperationalContext : MiddlewareOperationalContext objective doc Coordinate over-the-air software updates so the middleware can manage service dependencies, safe vehicle states, partition-aware update sequencing, and rollback consistency. actors otaCoordinator : OTAUpdateCoordinator vehicleMiddleware : VehiclePlatformMiddleware adapter : ApplicationMiddlewareAdapter «use case» emergency intervention via safety path subject middlewareOperationalContext : MiddlewareOperationalContext objective doc Route emergency braking through a safety-certified middleware partition to maintain unified lifecycle and health monitoring while ensuring safety integrity. This option assumes the middleware path is qualified to the required ASIL level and preserves a single managed operational chain for monitoring and update control. actors aebNode : AEBNode vehicleMiddleware : SafetyCertifiedMiddlewarePartition vehicleCommandGate : VehicleCommandGate «action» middlewareIntegrationFunctionalFlow : MiddlewareIntegrationFunctionalFlow items ^signalRequest : VehicleSignalAccessRequest ^diagnosticRequest : DiagnosticAccessRequest ^lifecycleRequest : LifecycleCoordinationRequest ^healthStatus : HealthStatus ^updateNotification : UpdateNotification ^bindingRequest : ServiceBindingRequest ^signalResponse : VehicleSignalAccessResponse ^diagnosticResponse : DiagnosticAccessResponse ^lifecycleStatus : LifecycleCoordinationStatus ^forwardedHealth : HealthForwardingStatus ^updateStatus : UpdateCoordinationStatus ^bindingStatus : ServiceBindingStatus ^safetyPathStatus : SafetyPathProtectionStatus actions ^translateSignal : TranslateVehicleSignal ^proxyDiagnostics : ProxyDiagnosticAccess ^coordinateLifecycle : CoordinateLifecycle ^forwardHealth : ForwardServiceHealth ^coordinateUpdate : CoordinateIntegrationUpdate ^bindService : DiscoverAndBindService ^protectSafetyPath : ProtectEmergencyInterventionPath

Hover a model element for details open raw SVG.

Source

1/*2 * DE4SDV middleware design-input requirement model slice.3 *4 * INC-MW-005 derives draft, verifiable requirement candidates from the5 * stakeholder needs in INC-MW-004. This slice does not define functional,6 * logical, or physical architecture; those follow in INC-MW-006 through7 * INC-MW-008.8 */910package DE4SDV_MiddlewareRequirements {11  package Features {12    package Middleware {13      package Requirements {14        private import Views::*;15        private import StandardViewDefinitions::*;16        private import DE4SDV_Stakeholders::*;17        private import DE4SDV_MethodContext::*;18        private import DE4SDV_ProductLine::*;19        private import DE4SDV_MethodViewpoints::*;20        private import SAF_Viewpoints::*;21        private import SysideViews::**;22        private import DE4SDV_MiddlewareOperationalContext::Features::Middleware::OperationalContext::*;23        private import DE4SDV_MiddlewareFunctionalArchitecture::Features::Middleware::FunctionalArchitecture::*;24        private import DE4SDV_MiddlewareStakeholderNeeds::Features::Middleware::StakeholderNeeds::System1Product::*;25        private import DE4SDV_MiddlewareIncrementFraming::Features::Middleware::IncrementFraming::*;2627        requirement def MiddlewareSignalAccessRequirement :> FunctionalRequirementCandidate;28        requirement def MiddlewareDiagnosticAccessRequirement :> FunctionalRequirementCandidate;29        requirement def MiddlewareLifecycleCoordinationRequirement :> FunctionalRequirementCandidate;30        requirement def MiddlewareHealthMonitoringRequirement :> FunctionalRequirementCandidate;31        requirement def MiddlewareUpdateCoordinationRequirement :> FunctionalRequirementCandidate;32        requirement def MiddlewareSafetyPathIsolationRequirement :> SafetyConstraintRequirementCandidate;33        requirement def MiddlewareServiceDiscoveryRequirement :> FunctionalRequirementCandidate;34        requirement def MiddlewareBoundaryTraceabilityRequirement :> TraceabilityConstraintRequirementCandidate;35        requirement def MiddlewareServiceAuthenticationRequirement :> SecurityConstraintRequirementCandidate;3637        part incMW005 : NeedsRequirementsIncrement {38          doc /* INC-MW-005: middleware integration design-input requirements. */39        }4041        package System1Product {42          requirement reqProvideMiddlewareSignalAccess : MiddlewareSignalAccessRequirement {43            doc /* REQ-MW-001 draft design-input requirement. */44            subject memberProduct : ProductLineMemberProduct;45            require constraint statement { language "English" /* Each SDV product-line member product shall provide the ADAS application access to the vehicle signals required by its selected operational use cases through the selected middleware integration boundary. */ }46            attribute :>> status = ReqStatus::ReadyForReview;47            attribute :>> source = "Derived from N-MW-001";48            attribute :>> rationale = "Signal access is the core middleware integration service for the ADAS application.";49          }5051          requirement reqProvideMiddlewareDiagnosticAccess : MiddlewareDiagnosticAccessRequirement {52            doc /* REQ-MW-002 draft design-input requirement. */53            subject memberProduct : ProductLineMemberProduct;54            require constraint statement { language "English" /* Each SDV product-line member product shall provide the ADAS application access to middleware and vehicle diagnostic status from which the health of the selected integration boundary can be determined. */ }55            attribute :>> status = ReqStatus::ReadyForReview;56            attribute :>> source = "Derived from N-MW-001";57            attribute :>> rationale = "Boundary health determinations require diagnostic visibility.";58          }5960          requirement reqCoordinateMiddlewareLifecycle : MiddlewareLifecycleCoordinationRequirement {61            doc /* REQ-MW-003 draft design-input requirement. */62            subject memberProduct : ProductLineMemberProduct;63            require constraint statement { language "English" /* Each SDV product-line member product shall coordinate middleware integration lifecycle state with the ADAS application so that startup, readiness, degraded operation, and shutdown transitions are observable at the integration boundary. */ }64            attribute :>> status = ReqStatus::ReadyForReview;65            attribute :>> source = "Derived from N-MW-001";66            attribute :>> rationale = "Lifecycle transitions must be observable at the integration boundary.";67          }6869          requirement reqMonitorMiddlewareHealth : MiddlewareHealthMonitoringRequirement {70            doc /* REQ-MW-004 draft design-input requirement. */71            subject memberProduct : ProductLineMemberProduct;72            require constraint statement { language "English" /* Each SDV product-line member product shall monitor the health of the selected middleware integration boundary and provide an observable indication when a required integration service is stale, missing, inconsistent, or unavailable. */ }73            attribute :>> status = ReqStatus::ReadyForReview;74            attribute :>> source = "Derived from N-MW-001";75            attribute :>> rationale = "Degraded integration services must be detected and indicated.";76          }7778          requirement reqCoordinateMiddlewareUpdates : MiddlewareUpdateCoordinationRequirement {79            doc /* REQ-MW-005 draft design-input requirement. */80            subject memberProduct : ProductLineMemberProduct;81            require constraint statement { language "English" /* Each SDV product-line member product shall coordinate middleware integration updates with the ADAS application lifecycle so that an update does not silently invalidate required signal, diagnostic, lifecycle, or health interfaces. */ }82            attribute :>> status = ReqStatus::ReadyForReview;83            attribute :>> source = "Derived from N-MW-001";84            attribute :>> rationale = "Updates must not silently invalidate required interfaces.";85          }8687          requirement reqIsolateSafetyPath : MiddlewareSafetyPathIsolationRequirement {88            doc /* REQ-MW-006 draft safety-constraint requirement; architecture choice and containment criteria remain open per GAP-MW-029. */89            subject memberProduct : ProductLineMemberProduct;90            require constraint statement { language "English" /* Each SDV product-line member product shall prevent a failure of the non-safety middleware integration path from causing an uncontrolled emergency intervention command, whether the selected realization uses a safety-certified middleware partition or a direct vehicle-command path. */ }91            attribute :>> status = ReqStatus::InDevelopment;92            attribute :>> source = "Derived from N-MW-004";93            attribute :>> rationale = "Middleware failure must not cause uncontrolled emergency intervention; containment criteria open per GAP-MW-029.";94          }9596          requirement reqProvideServiceDiscovery : MiddlewareServiceDiscoveryRequirement {97            doc /* REQ-MW-007 draft design-input requirement. */98            subject memberProduct : ProductLineMemberProduct;99            require constraint statement { language "English" /* Each SDV product-line member product shall discover and bind the middleware services required by the selected ADAS application integration configuration before those services are used. */ }100            attribute :>> status = ReqStatus::ReadyForReview;101            attribute :>> source = "Derived from N-MW-002";102            attribute :>> rationale = "Services must be bound before use for decoupled integration.";103          }104105          requirement reqAuthenticateServiceBinding : MiddlewareServiceAuthenticationRequirement {106            doc /* REQ-MW-008 draft security constraint derived from N-MW-009; trust-boundary details remain deferred per GAP-MW-012. */107            subject memberProduct : ProductLineMemberProduct;108            require constraint statement { language "English" /* Each SDV product-line member product shall authenticate a middleware service binding before accepting service data or commands across a trust boundary defined for the selected integration configuration. */ }109            attribute :>> status = ReqStatus::InDevelopment;110            attribute :>> source = "Derived from N-MW-009";111            attribute :>> rationale = "Service data and commands across a trust boundary must be authenticated; boundary details deferred per GAP-MW-012.";112          }113        }114115        package System2EngineeringAssurance {116          requirement reqMaintainMiddlewareBoundaryTraceability : MiddlewareBoundaryTraceabilityRequirement {117            doc /* REQ-MW-009 System 2 traceability requirement. */118            subject increment : NeedsRequirementsIncrement;119            require constraint statement { language "English" /* The DE4SDV middleware increment shall maintain trace links from each middleware requirement to its stakeholder need, operational-context source, feature/common-capability classification, unresolved gap, and planned verification record. */ }120            attribute :>> status = ReqStatus::ReadyForReview;121            attribute :>> source = "Derived from N-MW-006";122            attribute :>> rationale = "Trace links are the increment's assurance backbone.";123          }124        }125126        dependency reqProvideMiddlewareSignalAccessDerivedFromMiddlewareIntegration127          from reqProvideMiddlewareSignalAccess128          to DE4SDV_MiddlewareStakeholderNeeds::Features::Middleware::StakeholderNeeds::needMiddlewareIntegration;129        dependency reqProvideMiddlewareDiagnosticAccessDerivedFromMiddlewareIntegration130          from reqProvideMiddlewareDiagnosticAccess131          to DE4SDV_MiddlewareStakeholderNeeds::Features::Middleware::StakeholderNeeds::needMiddlewareIntegration;132        dependency reqCoordinateMiddlewareLifecycleDerivedFromMiddlewareIntegration133          from reqCoordinateMiddlewareLifecycle134          to DE4SDV_MiddlewareStakeholderNeeds::Features::Middleware::StakeholderNeeds::needMiddlewareIntegration;135        dependency reqMonitorMiddlewareHealthDerivedFromMiddlewareIntegration136          from reqMonitorMiddlewareHealth137          to DE4SDV_MiddlewareStakeholderNeeds::Features::Middleware::StakeholderNeeds::needMiddlewareIntegration;138        dependency reqCoordinateMiddlewareUpdatesDerivedFromMiddlewareIntegration139          from reqCoordinateMiddlewareUpdates140          to DE4SDV_MiddlewareStakeholderNeeds::Features::Middleware::StakeholderNeeds::needMiddlewareIntegration;141        dependency reqIsolateSafetyPathDerivedFromSafetyPathIsolation142          from reqIsolateSafetyPath143          to DE4SDV_MiddlewareStakeholderNeeds::Features::Middleware::StakeholderNeeds::needSafetyPathIsolation;144        dependency reqProvideServiceDiscoveryDerivedFromPlatformDecoupling145          from reqProvideServiceDiscovery146          to DE4SDV_MiddlewareStakeholderNeeds::Features::Middleware::StakeholderNeeds::needPlatformDecoupling;147        dependency reqAuthenticateServiceBindingDerivedFromSecurityTrustBoundary148          from reqAuthenticateServiceBinding149          to DE4SDV_MiddlewareStakeholderNeeds::Features::Middleware::StakeholderNeeds::System2EngineeringAssurance::needSecurityTrustBoundary;150        dependency reqMaintainMiddlewareBoundaryTraceabilityDerivedFromTraceabilityToOperationalContext151          from reqMaintainMiddlewareBoundaryTraceability152          to DE4SDV_MiddlewareStakeholderNeeds::Features::Middleware::StakeholderNeeds::needTraceabilityToOperationalContext;153154        /* Requirement traceability to the operational use cases that justify155         * each requirement (SystemRequirementTraceabilityViewpoint targets:156         * use case, process, context). Each requirement is justified by the157         * operational scenario it enables. */158        dependency reqProvideMiddlewareSignalAccessTracedToExchangeVehicleSignals159          from reqProvideMiddlewareSignalAccess160          to 'exchange vehicle signals';161        dependency reqProvideMiddlewareSignalAccessTracedToTranslateSignalAction162          from reqProvideMiddlewareSignalAccess163          to middlewareIntegrationFunctionalFlow::translateSignal;164        dependency reqProvideMiddlewareDiagnosticAccessTracedToAccessDiagnostics165          from reqProvideMiddlewareDiagnosticAccess166          to 'access diagnostics';167        dependency reqProvideMiddlewareDiagnosticAccessTracedToProxyDiagnosticsAction168          from reqProvideMiddlewareDiagnosticAccess169          to middlewareIntegrationFunctionalFlow::proxyDiagnostics;170        dependency reqCoordinateMiddlewareLifecycleTracedToCoordinateLifecycle171          from reqCoordinateMiddlewareLifecycle172          to 'coordinate lifecycle';173        dependency reqCoordinateMiddlewareLifecycleTracedToCoordinateLifecycleAction174          from reqCoordinateMiddlewareLifecycle175          to middlewareIntegrationFunctionalFlow::coordinateLifecycle;176        dependency reqMonitorMiddlewareHealthTracedToMonitorServiceHealth177          from reqMonitorMiddlewareHealth178          to 'monitor service health';179        dependency reqMonitorMiddlewareHealthTracedToForwardHealthAction180          from reqMonitorMiddlewareHealth181          to middlewareIntegrationFunctionalFlow::forwardHealth;182        dependency reqCoordinateMiddlewareUpdatesTracedToCoordinateUpdate183          from reqCoordinateMiddlewareUpdates184          to 'coordinate software update';185        dependency reqCoordinateMiddlewareUpdatesTracedToCoordinateUpdateAction186          from reqCoordinateMiddlewareUpdates187          to middlewareIntegrationFunctionalFlow::coordinateUpdate;188        dependency reqIsolateSafetyPathTracedToEmergencySafetyPath189          from reqIsolateSafetyPath190          to 'emergency intervention via safety path';191        dependency reqIsolateSafetyPathTracedToProtectSafetyPathAction192          from reqIsolateSafetyPath193          to middlewareIntegrationFunctionalFlow::protectSafetyPath;194        dependency reqProvideServiceDiscoveryTracedToExchangeVehicleSignals195          from reqProvideServiceDiscovery196          to 'exchange vehicle signals';197        dependency reqProvideServiceDiscoveryTracedToBindServiceAction198          from reqProvideServiceDiscovery199          to middlewareIntegrationFunctionalFlow::bindService;200        dependency reqAuthenticateServiceBindingTracedToExchangeVehicleSignals201          from reqAuthenticateServiceBinding202          to 'exchange vehicle signals';203        dependency reqAuthenticateServiceBindingTracedToBindServiceAction204          from reqAuthenticateServiceBinding205          to middlewareIntegrationFunctionalFlow::bindService;206207        public import System1Product::*;208        public import System2EngineeringAssurance::*;209210        dependency requirementNeedsTrace211          from DE4SDV_MiddlewareRequirements::Features::Middleware::Requirements::System1Product::reqProvideMiddlewareSignalAccess212          to DE4SDV_MiddlewareStakeholderNeeds::Features::Middleware::StakeholderNeeds::System1Product::needMiddlewareIntegration;213        dependency requirementOperationalContextTrace214          from DE4SDV_MiddlewareRequirements::Features::Middleware::Requirements::System1Product::reqProvideMiddlewareSignalAccess215          to DE4SDV_MiddlewareOperationalContext::Features::Middleware::OperationalContext::'integrate ADAS with vehicle platform';216        dependency requirementFramingTrace217          from DE4SDV_MiddlewareRequirements::Features::Middleware::Requirements::System1Product::reqProvideMiddlewareSignalAccess218          to DE4SDV_MiddlewareIncrementFraming::Features::Middleware::IncrementFraming::middlewareIntegrationProblemStatement;219220        concern requirementTraceConcern : RequirementTraceConcern {221          subject;222          stakeholder systemsEngineer : SystemsEngineer;223          stakeholder verificationEngineer : VerificationEngineer;224          stakeholder reviewer : OpenSourceReviewer;225        }226227        view middlewareSystemRequirementsView : TVD::TableView {228          viewpoint selectedSystemRequirementsViewpoint : SystemRequirementDefinitionViewpoint {229            frame requirementTraceConcern;230          }231          expose System1Product::*;232          expose System2EngineeringAssurance::*;233          filter @ SysML::RequirementUsage;234          attribute :>> includeReferenceElements = true;235          attribute :>> maxRowHeight = 300;236          view ID :> columnViews {237            attribute :>> featureToRender = CT::declaredName;238          }239          view Name :> columnViews {240            attribute :>> featureToRender = CT::heritage;241          }242          view Statement :> columnViews {243            attribute :>> featureToRender = CT::constraintLanguage {244              attribute constraintName = "statement";245              attribute constraintType = CL::ConT::required;246              attribute constraintLanguage = "English";247            }248            attribute :>> columnWidth = 360;249          }250        }251        view middlewareRequirementTraceView : GeneralView {252          viewpoint selectedRequirementTraceViewpoint : SystemRequirementTraceabilityViewpoint {253            frame requirementTraceConcern;254          }255          expose System1Product::*;256          expose System2EngineeringAssurance::*;257          expose DE4SDV_MiddlewareOperationalContext::Features::Middleware::OperationalContext::'exchange vehicle signals';258          expose DE4SDV_MiddlewareOperationalContext::Features::Middleware::OperationalContext::'access diagnostics';259          expose DE4SDV_MiddlewareOperationalContext::Features::Middleware::OperationalContext::'coordinate lifecycle';260          expose DE4SDV_MiddlewareOperationalContext::Features::Middleware::OperationalContext::'monitor service health';261          expose DE4SDV_MiddlewareOperationalContext::Features::Middleware::OperationalContext::'coordinate software update';262          expose DE4SDV_MiddlewareOperationalContext::Features::Middleware::OperationalContext::'emergency intervention via safety path';263          expose DE4SDV_MiddlewareFunctionalArchitecture::Features::Middleware::FunctionalArchitecture::middlewareIntegrationFunctionalFlow;264          attribute depth = 1;265        }266      }267    }268  }269}270