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

Source

1/*2 * DE4SDV middleware stakeholder needs model slice.3 *4 * INC-MW-004 defines stakeholder needs for middleware integration. Needs are5 * separated from requirements (INC-MW-005). System 1 needs are product-level6 * needs from operational stakeholders. System 2 needs are engineering-7 * assurance needs from the DE4SDV engineering team.8 *9 * This increment does NOT define requirements, functional architecture,10 * system architecture, or physical/software realization.11 */1213package DE4SDV_MWStakeholderNeeds {14  package Features {15    package Middleware {16      package StakeholderNeeds {17        private import Views::*;18        private import DE4SDV_Stakeholders::*;19        private import DE4SDV_MethodContext::*;20        private import DE4SDV_ProductLine::*;21        private import DE4SDV_MethodViewpoints::*;22        private import SAF_Viewpoints::*;23        private import SysideViews::**;2425        requirement def MiddlewareIntegrationNeed :> StakeholderNeedCandidate;26        requirement def PlatformDecouplingNeed :> StakeholderNeedCandidate;27        requirement def SafetyPathIsolationNeed :> StakeholderNeedCandidate;28        requirement def UpstreamEngagementNeed :> StakeholderNeedCandidate;2930        part incMW004 : NeedsRequirementsIncrement {31          doc /* INC-MW-004: middleware integration stakeholder needs. */32        }3334        package System1Product {35          requirement needMiddlewareIntegration : MiddlewareIntegrationNeed {36            doc /* N-MW-001 draft System 1 need. */37            subject productLine : SDVProductLine;38            stakeholder platformEngineer : SystemsEngineer;39            require constraint statement { language "English" /* Platform engineers need the SDV product line to provide middleware integration that enables signal access, diagnostic access, lifecycle coordination, health monitoring, and update coordination between an ADAS application and a vehicle-level platform middleware. */ }40          }4142          requirement needPlatformDecoupling : PlatformDecouplingNeed {43            doc /* N-MW-002 draft System 1 need. */44            subject productLine : SDVProductLine;45            stakeholder platformEngineer : SystemsEngineer;46            require constraint statement { language "English" /* Platform engineers need the SDV product line to ensure the ADAS application is not coupled to a specific middleware implementation so that middleware selection remains a product-line feature choice. */ }47          }4849          requirement needMiddlewareAsFeature : ProductLineClassificationNeed {50            doc /* N-MW-003 draft System 1 need. */51            subject productLine : SDVProductLine;52            stakeholder productLineEngineer : ProductLineEngineer;53            require constraint statement { language "English" /* Product-line engineers need the SDV product line to treat middleware platform selection as a feature that distinguishes member products, with the adapter layer as a common capability derived from the application-middleware feature pair. */ }54          }5556          requirement needSafetyPathIsolation : SafetyPathIsolationNeed {57            doc /* N-MW-004 draft System 1 need. */58            subject memberProduct : ProductLineMemberProduct;59            stakeholder safetyExpert : SafetyExpert;60            require constraint statement { language "English" /* Safety experts need each SDV product-line member product to ensure that the emergency intervention path is isolated from middleware failures, whether routed through a safety-certified middleware partition or via a direct vehicle-command path. */ }61          }6263          requirement needUpstreamEngagement : UpstreamEngagementNeed {64            doc /* N-MW-005 draft System 1 need. */65            subject productLine : SDVProductLine;66            stakeholder maintainer : Maintainer;67            require constraint statement { language "English" /* Maintainers need the SDV product line to engage upstream middleware maintainers before deeper integration, vendoring, or presenting borrowed methods as settled DE4SDV practice. */ }68          }69        }7071        package System2EngineeringAssurance {72          requirement needTraceabilityToOperationalContext : EngineeringTraceabilityNeed {73            doc /* N-MW-006 draft System 2 need. */74            subject increment : NeedsRequirementsIncrement;75            stakeholder systemsEngineer : SystemsEngineer;76            require constraint statement { language "English" /* Systems engineers need the DE4SDV middleware increment to maintain trace links from stakeholder needs to the operational context scenarios defined in INC-MW-002 and the feature classifications defined in INC-MW-003. */ }77          }7879          requirement needExplicitEngineeringBoundary : EngineeringTraceabilityNeed {80            doc /* N-MW-007 draft System 2 need. */81            subject increment : NeedsRequirementsIncrement;82            stakeholder systemsEngineer : SystemsEngineer;83            require constraint statement { language "English" /* Systems engineers need the DE4SDV middleware increment to keep its engineering boundary, assumptions, source constraints, and out-of-scope cases explicit while needs are derived. */ }84          }8586          requirement needVVPlanningAttachment : VerificationPlanningNeed {87            doc /* N-MW-008 draft System 2 need. */88            subject increment : NeedsRequirementsIncrement;89            stakeholder reviewer : OpenSourceReviewer;90            require constraint statement { language "English" /* Reviewers need the DE4SDV middleware increment to maintain a separate controlled V&V planning attachment for each stakeholder need without changing the product obligation. */ }91          }92        }9394        /*95         * Gaps — deferred scope items, same pattern as INC-MW-003.96         */97        part vehicleSignalEnumerationGap : DeferredProductLineScope {98          doc /*99           * GAP-MW-011: The specific vehicle signals needed by the ADAS100           * application are not enumerated at the needs level. Deferred101           * to INC-MW-005 (requirements).102           */103        }104105        part securityTrustBoundaryGap : DeferredProductLineScope {106          doc /*107           * GAP-MW-012: The security and trust boundary needs are not yet108           * derived. Deferred to a security-focused increment or109           * INC-MW-005.110           */111        }112113        /*114         * Trace links from needs to prior increments.115         */116        dependency need001FromOperationalContext117          from needMiddlewareIntegration118          to DE4SDV_MWOperationalContext::Features::Middleware::OperationalContext::operationalCapabilityConcern;119120        dependency need002FromClassification121          from needPlatformDecoupling122          to DE4SDV_MWFeatureClassification::Features::Middleware::FeatureClassification::productLineCapabilityClassificationConcern;123124        dependency need003FromClassification125          from needMiddlewareAsFeature126          to DE4SDV_MWFeatureClassification::Features::Middleware::FeatureClassification::productLineCapabilityClassificationConcern;127128        dependency need004FromOperationalContext129          from needSafetyPathIsolation130          to DE4SDV_MWOperationalContext::Features::Middleware::OperationalContext::operationalCapabilityConcern;131132        public import System1Product::*;133        public import System2EngineeringAssurance::*;134135        concern stakeholderNeedsConcern : StakeholderNeedsConcern {136          doc /*137           * Reviewers need stakeholder needs for middleware integration138           * separated from requirements, with traceability to the139           * operational context and feature classification.140           */141          subject;142          stakeholder systemsEngineer : SystemsEngineer;143          stakeholder productLineEngineer : ProductLineEngineer;144          stakeholder reviewer : OpenSourceReviewer;145        }146147        view mwStakeholderNeedsView : TVD::TableView {148          viewpoint selectedStakeholderNeedsViewpoint : StakeholderRequirementDefinitionViewpoint {149            frame stakeholderNeedsConcern;150          }151152          expose System1Product::*;153          expose System2EngineeringAssurance::*;154          filter @ SysML::RequirementUsage;155          attribute :>> includeReferenceElements = true;156          attribute :>> maxRowHeight = 300;157          view ID :> columnViews {158            attribute :>> featureToRender = CT::declaredName;159          }160          view Name :> columnViews {161            attribute :>> featureToRender = CT::heritage;162          }163          view Statement :> columnViews {164            attribute :>> featureToRender = CT::constraintLanguage {165              attribute constraintName = "statement";166              attribute constraintType = CL::ConT::required;167              attribute constraintLanguage = "English";168            }169            attribute :>> columnWidth = 360;170          }171        }172      }173    }174  }175}176