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

2 view(s) · 74 declared member(s) view source on GitHub

view mwSystemRequirementsView

ViewpointselectedSystemRequirementsViewpoint (SystemRequirementDefinitionViewpoint)
View typeTVD::TableView
ConcernrequirementTraceConcern
ExposesSystem1Product::*
System2EngineeringAssurance::*
Sourcetextual-notation-of-model/packages/features/middleware/mw_requirements.sysml:188
diagram-table-mwSystemRequirementsView.svg
Middleware system requirements Lists system requirements with their authoritative natural-language statements. Middleware system requirements ID Name Statement reqProvideMiddlewareSignalAccess MiddlewareSignalAccessRequirement, FunctionalRequirementCandidate, RequirementCandidate 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 Each SDV product-line member product shall provide the ADAS application access to middleware and vehicle diagnostic status needed to determine the health of the selected integration boundary. reqCoordinateMiddlewareLifecycle MiddlewareLifecycleCoordinationRequirement, FunctionalRequirementCandidate, RequirementCandidate 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 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 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 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 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, SafetyConstraintRequirementCandidate, RequirementCandidate 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 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 mwRequirementTraceView

ViewpointselectedRequirementTraceViewpoint (SystemRequirementTraceabilityViewpoint)
View typeGeneralView
ConcernrequirementTraceConcern
Depth1
ExposesSystem1Product::*
System2EngineeringAssurance::*
DE4SDV_MWOperationalContext::Features::Middleware::OperationalContext::'exchange vehicle signals'
DE4SDV_MWOperationalContext::Features::Middleware::OperationalContext::'access diagnostics'
DE4SDV_MWOperationalContext::Features::Middleware::OperationalContext::'coordinate lifecycle'
DE4SDV_MWOperationalContext::Features::Middleware::OperationalContext::'monitor service health'
DE4SDV_MWOperationalContext::Features::Middleware::OperationalContext::'coordinate software update'
DE4SDV_MWOperationalContext::Features::Middleware::OperationalContext::'emergency intervention via safety path'
DE4SDV_MWFunctionalArchitecture::Features::Middleware::FunctionalArchitecture::middlewareIntegrationFunctionalFlow
Sourcetextual-notation-of-model/packages/features/middleware/mw_requirements.sysml:212
diagram-mwRequirementTraceView.svg
«view» mwRequirementTraceView : GeneralView expose System1Product::* expose System2EngineeringAssurance::* expose DE4SDV_MWOperationalContext::Features::Middleware::OperationalContext::'exchange vehicle signals' expose DE4SDV_MWOperationalContext::Features::Middleware::OperationalContext::'access diagnostics' expose DE4SDV_MWOperationalContext::Features::Middleware::OperationalContext::'coordinate lifecycle' expose DE4SDV_MWOperationalContext::Features::Middleware::OperationalContext::'monitor service health' expose DE4SDV_MWOperationalContext::Features::Middleware::OperationalContext::'coordinate software update' expose DE4SDV_MWOperationalContext::Features::Middleware::OperationalContext::'emergency intervention via safety path' expose DE4SDV_MWFunctionalArchitecture::Features::Middleware::FunctionalArchitecture ::middlewareIntegrationFunctionalFlow «requirement» reqProvideMiddlewareSignalAccess : MiddlewareSignalAccessRequirement doc REQ-MW-001 draft design-input requirement. 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. subject memberProduct : ProductLineMemberProduct require constraints doc Each SDV product-line member product shall provide the ADAS application access to middleware and vehicle diagnostic status needed to determine the health of the selected integration boundary. statement { language "English" } «requirement» reqCoordinateMiddlewareLifecycle : MiddlewareLifecycleCoordinationRequirement doc REQ-MW-003 draft design-input requirement. 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. 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. 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 remains open. 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. 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 safety/security constraint; trust-boundary details remain deferred. 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. 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_MWRequirements {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_MWOperationalContext::Features::Middleware::OperationalContext::*;23        private import DE4SDV_MWFunctionalArchitecture::Features::Middleware::FunctionalArchitecture::*;2425        requirement def MiddlewareSignalAccessRequirement :> FunctionalRequirementCandidate;26        requirement def MiddlewareDiagnosticAccessRequirement :> FunctionalRequirementCandidate;27        requirement def MiddlewareLifecycleCoordinationRequirement :> FunctionalRequirementCandidate;28        requirement def MiddlewareHealthMonitoringRequirement :> FunctionalRequirementCandidate;29        requirement def MiddlewareUpdateCoordinationRequirement :> FunctionalRequirementCandidate;30        requirement def MiddlewareSafetyPathIsolationRequirement :> SafetyConstraintRequirementCandidate;31        requirement def MiddlewareServiceDiscoveryRequirement :> FunctionalRequirementCandidate;32        requirement def MiddlewareServiceAuthenticationRequirement :> SafetyConstraintRequirementCandidate;33        requirement def MiddlewareBoundaryTraceabilityRequirement :> TraceabilityConstraintRequirementCandidate;3435        part incMW005 : NeedsRequirementsIncrement {36          doc /* INC-MW-005: middleware integration design-input requirements. */37        }3839        package System1Product {40          requirement reqProvideMiddlewareSignalAccess : MiddlewareSignalAccessRequirement {41            doc /* REQ-MW-001 draft design-input requirement. */42            subject memberProduct : ProductLineMemberProduct;43            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. */ }44          }4546          requirement reqProvideMiddlewareDiagnosticAccess : MiddlewareDiagnosticAccessRequirement {47            doc /* REQ-MW-002 draft design-input requirement. */48            subject memberProduct : ProductLineMemberProduct;49            require constraint statement { language "English" /* Each SDV product-line member product shall provide the ADAS application access to middleware and vehicle diagnostic status needed to determine the health of the selected integration boundary. */ }50          }5152          requirement reqCoordinateMiddlewareLifecycle : MiddlewareLifecycleCoordinationRequirement {53            doc /* REQ-MW-003 draft design-input requirement. */54            subject memberProduct : ProductLineMemberProduct;55            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. */ }56          }5758          requirement reqMonitorMiddlewareHealth : MiddlewareHealthMonitoringRequirement {59            doc /* REQ-MW-004 draft design-input requirement. */60            subject memberProduct : ProductLineMemberProduct;61            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. */ }62          }6364          requirement reqCoordinateMiddlewareUpdates : MiddlewareUpdateCoordinationRequirement {65            doc /* REQ-MW-005 draft design-input requirement. */66            subject memberProduct : ProductLineMemberProduct;67            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. */ }68          }6970          requirement reqIsolateSafetyPath : MiddlewareSafetyPathIsolationRequirement {71            doc /* REQ-MW-006 draft safety-constraint requirement; architecture choice remains open. */72            subject memberProduct : ProductLineMemberProduct;73            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. */ }74          }7576          requirement reqProvideServiceDiscovery : MiddlewareServiceDiscoveryRequirement {77            doc /* REQ-MW-007 draft design-input requirement. */78            subject memberProduct : ProductLineMemberProduct;79            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. */ }80          }8182          requirement reqAuthenticateServiceBinding : MiddlewareServiceAuthenticationRequirement {83            doc /* REQ-MW-008 draft safety/security constraint; trust-boundary details remain deferred. */84            subject memberProduct : ProductLineMemberProduct;85            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. */ }86          }87        }8889        package System2EngineeringAssurance {90          requirement reqMaintainMiddlewareBoundaryTraceability : MiddlewareBoundaryTraceabilityRequirement {91            doc /* REQ-MW-009 System 2 traceability requirement. */92            subject increment : NeedsRequirementsIncrement;93            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. */ }94          }95        }9697        dependency req001DerivedFromNeed00198          from reqProvideMiddlewareSignalAccess99          to DE4SDV_MWStakeholderNeeds::Features::Middleware::StakeholderNeeds::needMiddlewareIntegration;100        dependency req002DerivedFromNeed001101          from reqProvideMiddlewareDiagnosticAccess102          to DE4SDV_MWStakeholderNeeds::Features::Middleware::StakeholderNeeds::needMiddlewareIntegration;103        dependency req003DerivedFromNeed001104          from reqCoordinateMiddlewareLifecycle105          to DE4SDV_MWStakeholderNeeds::Features::Middleware::StakeholderNeeds::needMiddlewareIntegration;106        dependency req004DerivedFromNeed001107          from reqMonitorMiddlewareHealth108          to DE4SDV_MWStakeholderNeeds::Features::Middleware::StakeholderNeeds::needMiddlewareIntegration;109        dependency req005DerivedFromNeed001110          from reqCoordinateMiddlewareUpdates111          to DE4SDV_MWStakeholderNeeds::Features::Middleware::StakeholderNeeds::needMiddlewareIntegration;112        dependency req006DerivedFromNeed004113          from reqIsolateSafetyPath114          to DE4SDV_MWStakeholderNeeds::Features::Middleware::StakeholderNeeds::needSafetyPathIsolation;115        dependency req007DerivedFromNeed002116          from reqProvideServiceDiscovery117          to DE4SDV_MWStakeholderNeeds::Features::Middleware::StakeholderNeeds::needPlatformDecoupling;118        dependency req008DerivedFromNeed012119          from reqAuthenticateServiceBinding120          to DE4SDV_MWStakeholderNeeds::Features::Middleware::StakeholderNeeds::securityTrustBoundaryGap;121        dependency req009DerivedFromNeed006122          from reqMaintainMiddlewareBoundaryTraceability123          to DE4SDV_MWStakeholderNeeds::Features::Middleware::StakeholderNeeds::needTraceabilityToOperationalContext;124125        /* Requirement traceability to the operational use cases that justify126         * each requirement (SystemRequirementTraceabilityViewpoint targets:127         * use case, process, context). Each requirement is justified by the128         * operational scenario it enables. */129        dependency req001TracedToExchangeVehicleSignals130          from reqProvideMiddlewareSignalAccess131          to 'exchange vehicle signals';132        dependency req001TracedToTranslateSignalAction133          from reqProvideMiddlewareSignalAccess134          to middlewareIntegrationFunctionalFlow::translateSignal;135        dependency req002TracedToAccessDiagnostics136          from reqProvideMiddlewareDiagnosticAccess137          to 'access diagnostics';138        dependency req002TracedToProxyDiagnosticsAction139          from reqProvideMiddlewareDiagnosticAccess140          to middlewareIntegrationFunctionalFlow::proxyDiagnostics;141        dependency req003TracedToCoordinateLifecycle142          from reqCoordinateMiddlewareLifecycle143          to 'coordinate lifecycle';144        dependency req003TracedToCoordinateLifecycleAction145          from reqCoordinateMiddlewareLifecycle146          to middlewareIntegrationFunctionalFlow::coordinateLifecycle;147        dependency req004TracedToMonitorServiceHealth148          from reqMonitorMiddlewareHealth149          to 'monitor service health';150        dependency req004TracedToForwardHealthAction151          from reqMonitorMiddlewareHealth152          to middlewareIntegrationFunctionalFlow::forwardHealth;153        dependency req005TracedToCoordinateUpdate154          from reqCoordinateMiddlewareUpdates155          to 'coordinate software update';156        dependency req005TracedToCoordinateUpdateAction157          from reqCoordinateMiddlewareUpdates158          to middlewareIntegrationFunctionalFlow::coordinateUpdate;159        dependency req006TracedToEmergencySafetyPath160          from reqIsolateSafetyPath161          to 'emergency intervention via safety path';162        dependency req006TracedToProtectSafetyPathAction163          from reqIsolateSafetyPath164          to middlewareIntegrationFunctionalFlow::protectSafetyPath;165        dependency req007TracedToExchangeVehicleSignals166          from reqProvideServiceDiscovery167          to 'exchange vehicle signals';168        dependency req007TracedToBindServiceAction169          from reqProvideServiceDiscovery170          to middlewareIntegrationFunctionalFlow::bindService;171        dependency req008TracedToExchangeVehicleSignals172          from reqAuthenticateServiceBinding173          to 'exchange vehicle signals';174        dependency req008TracedToBindServiceAction175          from reqAuthenticateServiceBinding176          to middlewareIntegrationFunctionalFlow::bindService;177178        public import System1Product::*;179        public import System2EngineeringAssurance::*;180181        concern requirementTraceConcern : RequirementTraceConcern {182          subject;183          stakeholder systemsEngineer : SystemsEngineer;184          stakeholder verificationEngineer : VerificationEngineer;185          stakeholder reviewer : OpenSourceReviewer;186        }187188        view mwSystemRequirementsView : TVD::TableView {189          viewpoint selectedSystemRequirementsViewpoint : SystemRequirementDefinitionViewpoint {190            frame requirementTraceConcern;191          }192          expose System1Product::*;193          expose System2EngineeringAssurance::*;194          filter @ SysML::RequirementUsage;195          attribute :>> includeReferenceElements = true;196          attribute :>> maxRowHeight = 300;197          view ID :> columnViews {198            attribute :>> featureToRender = CT::declaredName;199          }200          view Name :> columnViews {201            attribute :>> featureToRender = CT::heritage;202          }203          view Statement :> columnViews {204            attribute :>> featureToRender = CT::constraintLanguage {205              attribute constraintName = "statement";206              attribute constraintType = CL::ConT::required;207              attribute constraintLanguage = "English";208            }209            attribute :>> columnWidth = 360;210          }211        }212        view mwRequirementTraceView : GeneralView {213          viewpoint selectedRequirementTraceViewpoint : SystemRequirementTraceabilityViewpoint {214            frame requirementTraceConcern;215          }216          expose System1Product::*;217          expose System2EngineeringAssurance::*;218          expose DE4SDV_MWOperationalContext::Features::Middleware::OperationalContext::'exchange vehicle signals';219          expose DE4SDV_MWOperationalContext::Features::Middleware::OperationalContext::'access diagnostics';220          expose DE4SDV_MWOperationalContext::Features::Middleware::OperationalContext::'coordinate lifecycle';221          expose DE4SDV_MWOperationalContext::Features::Middleware::OperationalContext::'monitor service health';222          expose DE4SDV_MWOperationalContext::Features::Middleware::OperationalContext::'coordinate software update';223          expose DE4SDV_MWOperationalContext::Features::Middleware::OperationalContext::'emergency intervention via safety path';224          expose DE4SDV_MWFunctionalArchitecture::Features::Middleware::FunctionalArchitecture::middlewareIntegrationFunctionalFlow;225          attribute depth = 1;226        }227      }228    }229  }230}231