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

Source

1/*2 * DE4SDV middleware feature/common-capability classification model slice.3 *4 * INC-MW-003 classifies each middleware integration element as a feature,5 * common capability, constraint, or evidence capability per the DE4SDV6 * feature/common-capability rule (ISO/IEC 26580-aligned). It confirms the7 * classification hypothesis from INC-MW-002.8 *9 * Features (middleware selection, application selection) are already modeled10 * as native SysML v2 variation/variant in the SDV platform stack11 * (DE4SDV_SDVPlatformStack). This file does NOT duplicate them. It records12 * only the common capabilities that are not variation points and the13 * classification concern for review.14 *15 * This increment does NOT define requirements, functional behavior, logical16 * architecture, or physical/software realization.17 */1819package DE4SDV_MWFeatureClassification {20  package Features {21    package Middleware {22      package FeatureClassification {23        private import Views::*;24        private import DE4SDV_Stakeholders::*;25        private import DE4SDV_ProductLine::*;26        private import DE4SDV_MethodViewpoints::*;27        private import SAF_Viewpoints::*;28        private import DE4SDV_SDVPlatformStack::*;29        private import SysideViews::**;3031        /*32         * Classification concern: reviewers need to see common capabilities33         * separated from features and variation points.34         */35        concern productLineCapabilityClassificationConcern : ProductLineCapabilityClassificationConcern {36          doc /*37           * Reviewers need middleware scope elements to distinguish common38           * product-line capabilities from features and variation points39           * before downstream functional modeling starts. Features are the40           * variation points already in the SDV platform stack; common41           * capabilities are the parts listed here that are required for42           * any app+middleware combination.43           */44          subject;45          stakeholder productLineEngineer : ProductLineEngineer;46          stakeholder systemsEngineer : SystemsEngineer;47          stakeholder reviewer : OpenSourceReviewer;48        }4950        /*51         * Common capabilities — required for any app+middleware combination.52         * Not features: they do not distinguish member products.53         * These are NOT variation points in the SDV platform stack.54         */55        part adapterLayer : CommonProductLineCapability {56          doc /*57           * The application-middleware adapter layer is a common capability.58           * Every (application, middleware) pair requires an adapter to59           * translate between incompatible communication paradigms60           * (ROS 2/DDS vs VSIDL/LoLa/SOME/IP). The adapter does not61           * distinguish member products — it is present whenever middleware62           * is not "none" and absent when it is. The specific adapter63           * variant follows from the (application, middleware) feature64           * pair — see the adapter variation in DE4SDV_SDVPlatformStack.65           */66        }6768        part signalAccessCapability : CommonProductLineCapability {69          doc /*70           * The capability to exchange vehicle signals through the71           * middleware is a common capability. It is required whenever72           * an ADAS application and a vehicle-level middleware are both73           * selected. Does not distinguish member products.74           */75        }7677        part lifecycleCoordinationCapability : CommonProductLineCapability {78          doc /*79           * Lifecycle coordination (startup, shutdown, suspend, resume)80           * through the middleware is a common capability. Required for81           * all middleware-integrated products. Does not distinguish82           * member products.83           */84        }8586        part healthMonitoringCapability : CommonProductLineCapability {87          doc /*88           * Health monitoring and fault detection through the middleware89           * is a common capability. Required for all middleware-integrated90           * products.91           */92        }9394        part diagnosticAccessCapability : CommonProductLineCapability {95          doc /*96           * Authenticated diagnostic access through the middleware is a97           * common capability. Does not distinguish member products.98           */99        }100101        part updateCoordinationCapability : CommonProductLineCapability {102          doc /*103           * OTA software update coordination through the middleware is a104           * common capability. Does not distinguish member products.105           */106        }107108        /*109         * Deferred scope — not classified in this increment.110         */111        part safetyPathDecision : DeferredProductLineScope {112          doc /*113           * The decision about which emergency intervention path to114           * realize (through safety-certified middleware partition vs115           * direct vehicle-command gate) is deferred to INC-MW-004116           * (needs) and INC-MW-005 (requirements).117           */118        }119120        part securityTrustBoundary : DeferredProductLineScope {121          doc /*122           * The security and trust boundary for middleware communication123           * (DICE identity, attestation, VLAN segmentation) is not yet124           * classified. Deferred to a security-focused increment or125           * INC-MW-005.126           */127        }128129        /*130         * View131         */132        view mwProductLineClassificationView : TVD::TableView {133          viewpoint selectedProductLineClassificationViewpoint : ProductLineClassificationViewpoint {134            frame productLineCapabilityClassificationConcern;135          }136137          expose FeatureClassification::adapterLayer;138          expose FeatureClassification::signalAccessCapability;139          expose FeatureClassification::lifecycleCoordinationCapability;140          expose FeatureClassification::healthMonitoringCapability;141          expose FeatureClassification::diagnosticAccessCapability;142          expose FeatureClassification::updateCoordinationCapability;143          expose FeatureClassification::safetyPathDecision;144          expose FeatureClassification::securityTrustBoundary;145          filter @ SysML::PartUsage;146          attribute :>> includeReferenceElements = true;147          attribute :>> maxRowHeight = 300;148          view ID :> columnViews {149            attribute :>> featureToRender = CT::declaredName;150          }151          view Classification :> columnViews {152            attribute :>> featureToRender = CT::heritage;153          }154          view Rationale :> columnViews {155            attribute :>> featureToRender = CT::documentation;156            attribute :>> columnWidth = 360;157          }158        }159      }160    }161  }162}163