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

1 view(s) · 62 declared member(s) Jump to source ↓

view middlewareStakeholderNeedsViewsource ↓

ViewpointselectedStakeholderNeedsViewpoint (StakeholderRequirementDefinitionViewpoint)
View typeTVD::TableView
ConcernstakeholderNeedsConcern
ExposesSystem1Product::*
System2EngineeringAssurance::*
Sourcetextual-notation-of-model/packages/features/middleware/middleware_stakeholder_needs.sysml:203
diagram-table-middlewareStakeholderNeedsView.svg
Middleware stakeholder needs Lists stakeholder needs with their authoritative natural-language statements. Middleware stakeholder needs ID Name Statement needMiddlewareIntegration MiddlewareIntegrationNeed, StakeholderNeedCandidate, RequirementsManagementAttributeBase Platform engineers need the SDV product line to provide middleware integration connecting the ADAS application with a vehicle-level platform middleware for signal access, diagnostic access, lifecycle coordination, health monitoring, and update coordination. needPlatformDecoupling PlatformDecouplingNeed, StakeholderNeedCandidate, RequirementsManagementAttributeBase 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. needMiddlewareAsFeature ProductLineClassificationNeed, StakeholderNeedCandidate, RequirementsManagementAttributeBase 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. needSafetyPathIsolation SafetyPathIsolationNeed, StakeholderNeedCandidate, RequirementsManagementAttributeBase 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. needUpstreamEngagement UpstreamEngagementNeed, StakeholderNeedCandidate, RequirementsManagementAttributeBase Maintainers need the DE4SDV middleware increment to engage upstream middleware maintainers before deeper integration, vendoring, or presenting borrowed methods as settled DE4SDV practice. needSecurityTrustBoundary SecurityTrustBoundaryNeed, StakeholderNeedCandidate, RequirementsManagementAttributeBase Security experts need the DE4SDV middleware increment to define the trust boundary that middleware service bindings must authenticate across before the ADAS application accepts service data or commands. needTraceabilityToOperationalContext EngineeringTraceabilityNeed, StakeholderNeedCandidate, RequirementsManagementAttributeBase 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. needExplicitEngineeringBoundary EngineeringTraceabilityNeed, StakeholderNeedCandidate, RequirementsManagementAttributeBase 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. needVVPlanningAttachment VerificationPlanningNeed, StakeholderNeedCandidate, RequirementsManagementAttributeBase Reviewers need the DE4SDV middleware increment to maintain a separate controlled V&V planning attachment for each stakeholder need without changing the product obligation.

Hover a model element for details open raw SVG.

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 * logical architecture, or physical/software realization.11 */1213package DE4SDV_MiddlewareStakeholderNeeds {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_MiddlewareOperationalContext::Features::Middleware::OperationalContext::*;22        private import DE4SDV_MiddlewareFeatureClassification::Features::Middleware::FeatureClassification::*;23        private import DE4SDV_MiddlewareIncrementFraming::Features::Middleware::IncrementFraming::*;24        private import DE4SDV_MethodViewpoints::*;25        private import SAF_Viewpoints::*;26        private import SysideViews::**;2728        requirement def MiddlewareIntegrationNeed :> StakeholderNeedCandidate;29        requirement def PlatformDecouplingNeed :> StakeholderNeedCandidate;30        requirement def SafetyPathIsolationNeed :> StakeholderNeedCandidate;31        requirement def UpstreamEngagementNeed :> StakeholderNeedCandidate;32        requirement def SecurityTrustBoundaryNeed :> StakeholderNeedCandidate;3334        part incMW004 : NeedsRequirementsIncrement {35          doc /* INC-MW-004: middleware integration stakeholder needs. */36        }3738        package System1Product {39          requirement needMiddlewareIntegration : MiddlewareIntegrationNeed {40            doc /* N-MW-001 draft System 1 need. */41            subject productLine : SDVProductLine;42            stakeholder platformEngineer : SystemsEngineer;43            require constraint statement { language "English" /* Platform engineers need the SDV product line to provide middleware integration connecting the ADAS application with a vehicle-level platform middleware for signal access, diagnostic access, lifecycle coordination, health monitoring, and update coordination. */ }44            attribute :>> status = ReqStatus::InDevelopment;45            attribute :>> source = "INC-MW-002 operational context and INC-MW-003 feature classification";46            attribute :>> rationale = "ADAS application capability depends on signal, diagnostic, lifecycle, health, and update access through platform middleware.";47          }4849          requirement needPlatformDecoupling : PlatformDecouplingNeed {50            doc /* N-MW-002 draft System 1 need. */51            subject productLine : SDVProductLine;52            stakeholder platformEngineer : SystemsEngineer;53            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. */ }54            attribute :>> status = ReqStatus::InDevelopment;55            attribute :>> source = "INC-MW-003 feature classification";56            attribute :>> rationale = "Middleware selection must remain a product-line feature choice, not an application property.";57          }5859          requirement needMiddlewareAsFeature : ProductLineClassificationNeed {60            doc /* N-MW-003 draft System 1 need; derived requirements are owned by the PLE configuration increment INC-MW-009 rather than INC-MW-005. */61            subject productLine : SDVProductLine;62            stakeholder productLineEngineer : ProductLineEngineer;63            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. */ }64            attribute :>> status = ReqStatus::InDevelopment;65            attribute :>> source = "INC-MW-003 feature classification";66            attribute :>> rationale = "Adapter-layer commonality derives from the application-middleware feature pair.";67          }6869          requirement needSafetyPathIsolation : SafetyPathIsolationNeed {70            doc /* N-MW-004 draft System 1 need; isolation and containment criteria remain open per GAP-MW-029. */71            subject memberProduct : ProductLineMemberProduct;72            stakeholder safetyExpert : SafetyExpert;73            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. */ }74            attribute :>> status = ReqStatus::InDevelopment;75            attribute :>> source = "INC-MW-002 operational context emergency-intervention scenario";76            attribute :>> rationale = "Emergency intervention must survive middleware failure regardless of selected architecture; criteria open per GAP-MW-029.";77          }78        }7980        package System2EngineeringAssurance {81          requirement needUpstreamEngagement : UpstreamEngagementNeed {82            doc /* N-MW-005 draft System 2 need; moved from System 1 because upstream engagement is a DE4SDV project obligation, not a product-line capability. */83            subject increment : NeedsRequirementsIncrement;84            stakeholder maintainer : Maintainer;85            require constraint statement { language "English" /* Maintainers need the DE4SDV middleware increment to engage upstream middleware maintainers before deeper integration, vendoring, or presenting borrowed methods as settled DE4SDV practice. */ }86            attribute :>> status = ReqStatus::InDevelopment;87            attribute :>> source = "DE4SDV governance policy on external methodology adoption";88            attribute :>> rationale = "Upstream maintainers must be involved before deeper integration or vendoring.";89          }9091          requirement needSecurityTrustBoundary : SecurityTrustBoundaryNeed {92            doc /* N-MW-009 draft System 2 need; parents REQ-MW-008, trust-boundary details remain deferred per GAP-MW-012. */93            subject increment : NeedsRequirementsIncrement;94            stakeholder securityExpert : SecurityExpert;95            require constraint statement { language "English" /* Security experts need the DE4SDV middleware increment to define the trust boundary that middleware service bindings must authenticate across before the ADAS application accepts service data or commands. */ }96            attribute :>> status = ReqStatus::InDevelopment;97            attribute :>> source = "Requirements QA gate review of the INC-MW-005 baseline";98            attribute :>> rationale = "Service-binding authentication needs a defined trust boundary to authenticate across; details deferred per GAP-MW-012.";99          }100          requirement needTraceabilityToOperationalContext : EngineeringTraceabilityNeed {101            doc /* N-MW-006 draft System 2 need. */102            subject increment : NeedsRequirementsIncrement;103            stakeholder systemsEngineer : SystemsEngineer;104            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. */ }105            attribute :>> status = ReqStatus::InDevelopment;106            attribute :>> source = "DE4SDV method increment workflow";107            attribute :>> rationale = "Needs must trace to the operational scenarios that justify them.";108          }109110          requirement needExplicitEngineeringBoundary : EngineeringTraceabilityNeed {111            doc /* N-MW-007 draft System 2 need; satisfied by the increment framing and gap records rather than a derived requirement. */112            subject increment : NeedsRequirementsIncrement;113            stakeholder systemsEngineer : SystemsEngineer;114            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. */ }115            attribute :>> status = ReqStatus::InDevelopment;116            attribute :>> source = "DE4SDV method increment workflow";117            attribute :>> rationale = "Boundary, assumptions, and out-of-scope cases stay explicit while needs are derived.";118          }119120          requirement needVVPlanningAttachment : VerificationPlanningNeed {121            doc /* N-MW-008 draft System 2 need; satisfied by the separate verification_planning attachment in the INC-MW-004 and INC-MW-005 artifacts rather than a derived requirement. */122            subject increment : NeedsRequirementsIncrement;123            stakeholder reviewer : OpenSourceReviewer;124            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. */ }125            attribute :>> status = ReqStatus::InDevelopment;126            attribute :>> source = "DE4SDV verification and assurance workflow";127            attribute :>> rationale = "Per-need V&V planning attachments stay separate from product obligations.";128          }129        }130131        /*132         * Gaps — deferred scope items, same pattern as INC-MW-003.133         */134        part vehicleSignalEnumerationGap : DeferredProductLineScope {135          doc /*136           * GAP-MW-011: The specific vehicle signals needed by the ADAS137           * application are not enumerated at the needs level. Deferred138           * to INC-MW-005 (requirements).139           */140        }141142        part securityTrustBoundaryGap : DeferredProductLineScope {143          doc /*144           * GAP-MW-012: The security and trust boundary needs are not yet145           * derived. Deferred to a security-focused increment or146           * INC-MW-005.147           */148        }149150        part safetyPathIsolationCriteriaGap : DeferredProductLineScope {151          doc /*152           * GAP-MW-029: The isolation criteria and failure-containment153           * expectations for the emergency intervention path remain154           * undefined; the selected safety-path architecture is deferred155           * to INC-MW-005.156           */157        }158159        /*160         * Trace links from needs to prior increments.161         */162        dependency needMiddlewareIntegrationFromOperationalContext163          from needMiddlewareIntegration164          to DE4SDV_MiddlewareOperationalContext::Features::Middleware::OperationalContext::operationalCapabilityConcern;165166        dependency needPlatformDecouplingFromClassification167          from needPlatformDecoupling168          to DE4SDV_MiddlewareFeatureClassification::Features::Middleware::FeatureClassification::productLineCapabilityClassificationConcern;169170        dependency needMiddlewareAsFeatureFromClassification171          from needMiddlewareAsFeature172          to DE4SDV_MiddlewareFeatureClassification::Features::Middleware::FeatureClassification::productLineCapabilityClassificationConcern;173174        dependency needSafetyPathIsolationFromOperationalContext175          from needSafetyPathIsolation176          to DE4SDV_MiddlewareOperationalContext::Features::Middleware::OperationalContext::operationalCapabilityConcern;177178        public import System1Product::*;179        public import System2EngineeringAssurance::*;180181        dependency needOperationalContextTrace182          from DE4SDV_MiddlewareStakeholderNeeds::Features::Middleware::StakeholderNeeds::System1Product::needMiddlewareIntegration183          to DE4SDV_MiddlewareOperationalContext::Features::Middleware::OperationalContext::'integrate ADAS with vehicle platform';184        dependency needClassificationTrace185          from DE4SDV_MiddlewareStakeholderNeeds::Features::Middleware::StakeholderNeeds::System1Product::needMiddlewareIntegration186          to DE4SDV_MiddlewareFeatureClassification::Features::Middleware::FeatureClassification::adapterLayer;187        dependency needFramingTrace188          from DE4SDV_MiddlewareStakeholderNeeds::Features::Middleware::StakeholderNeeds::System1Product::needMiddlewareIntegration189          to DE4SDV_MiddlewareIncrementFraming::Features::Middleware::IncrementFraming::middlewareIntegrationProblemStatement;190191        concern stakeholderNeedsConcern : StakeholderNeedsConcern {192          doc /*193           * Reviewers need stakeholder needs for middleware integration194           * separated from requirements, with traceability to the195           * operational context and feature classification.196           */197          subject;198          stakeholder systemsEngineer : SystemsEngineer;199          stakeholder productLineEngineer : ProductLineEngineer;200          stakeholder reviewer : OpenSourceReviewer;201        }202203        view middlewareStakeholderNeedsView : TVD::TableView {204          viewpoint selectedStakeholderNeedsViewpoint : StakeholderRequirementDefinitionViewpoint {205            frame stakeholderNeedsConcern;206          }207208          expose System1Product::*;209          expose System2EngineeringAssurance::*;210          filter @ SysML::RequirementUsage;211          attribute :>> includeReferenceElements = true;212          attribute :>> maxRowHeight = 300;213          view ID :> columnViews {214            attribute :>> featureToRender = CT::declaredName;215          }216          view Name :> columnViews {217            attribute :>> featureToRender = CT::heritage;218          }219          view Statement :> columnViews {220            attribute :>> featureToRender = CT::constraintLanguage {221              attribute constraintName = "statement";222              attribute constraintType = CL::ConT::required;223              attribute constraintLanguage = "English";224            }225            attribute :>> columnWidth = 360;226          }227        }228      }229    }230  }231}232