textual-notation-of-model/packages/features/middleware/middleware_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_MiddlewareFeatureClassification {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 DE4SDV_MiddlewareOperationalContext::Features::Middleware::OperationalContext::*;30        private import SysideViews::**;3132        /*33         * Classification concern: reviewers need to see common capabilities34         * separated from features and variation points.35         */36        concern productLineCapabilityClassificationConcern : ProductLineCapabilityClassificationConcern {37          doc /*38           * Reviewers need middleware scope elements to distinguish common39           * product-line capabilities from features and variation points40           * before downstream functional modeling starts. Features are the41           * variation points already in the SDV platform stack; common42           * capabilities are the parts listed here that are required for43           * any app+middleware combination.44           */45          subject;46          stakeholder productLineEngineer : ProductLineEngineer;47          stakeholder systemsEngineer : SystemsEngineer;48          stakeholder reviewer : OpenSourceReviewer;49        }5051        /*52         * Common capabilities — required for any app+middleware combination.53         * Not features: they do not distinguish member products.54         * These are NOT variation points in the SDV platform stack.55         */56        part adapterLayer : CommonProductLineCapability {57          doc /*58           * The application-middleware adapter layer is a common capability.59           * Every (application, middleware) pair requires an adapter to60           * translate between incompatible communication paradigms61           * (ROS 2/DDS vs VSIDL/LoLa/SOME/IP). The adapter does not62           * distinguish member products — it is present whenever middleware63           * is not "none" and absent when it is. The specific adapter64           * variant follows from the (application, middleware) feature65           * pair — see the adapter variation in DE4SDV_SDVPlatformStack.66           */67        }6869        part signalAccessCapability : CommonProductLineCapability {70          doc /*71           * The capability to exchange vehicle signals through the72           * middleware is a common capability. It is required whenever73           * an ADAS application and a vehicle-level middleware are both74           * selected. Does not distinguish member products.75           */76        }7778        part lifecycleCoordinationCapability : CommonProductLineCapability {79          doc /*80           * Lifecycle coordination (startup, shutdown, suspend, resume)81           * through the middleware is a common capability. Required for82           * all middleware-integrated products. Does not distinguish83           * member products.84           */85        }8687        part healthMonitoringCapability : CommonProductLineCapability {88          doc /*89           * Health monitoring and fault detection through the middleware90           * is a common capability. Required for all middleware-integrated91           * products.92           */93        }9495        part diagnosticAccessCapability : CommonProductLineCapability {96          doc /*97           * Authenticated diagnostic access through the middleware is a98           * common capability. Does not distinguish member products.99           */100        }101102        part updateCoordinationCapability : CommonProductLineCapability {103          doc /*104           * OTA software update coordination through the middleware is a105           * common capability. Does not distinguish member products.106           */107        }108109        /*110         * Deferred scope — not classified in this increment.111         */112        part safetyPathDecision : DeferredProductLineScope {113          doc /*114           * The decision about which emergency intervention path to115           * realize (through safety-certified middleware partition vs116           * direct vehicle-command gate) is deferred to INC-MW-004117           * (needs) and INC-MW-005 (requirements).118           */119        }120121        part securityTrustBoundary : DeferredProductLineScope {122          doc /*123           * The security and trust boundary for middleware communication124           * (DICE identity, attestation, VLAN segmentation) is not yet125           * classified. Deferred to a security-focused increment or126           * INC-MW-005.127           */128        }129130        /*131         * View132         */133        part def ISOIEC26580ClassificationSource {134          doc /*135           * External reference: ISO/IEC 26580 product-line engineering136           * feature-classification rule — a feature distinguishes member137           * products; a common capability does not.138           */139        }140        part isoIEC26580ClassificationSource : ISOIEC26580ClassificationSource;141142        dependency classificationOperationalContextTrace143          from adapterLayer144          to DE4SDV_MiddlewareOperationalContext::Features::Middleware::OperationalContext::'integrate ADAS with vehicle platform';145        dependency classificationPlatformStackTrace146          from adapterLayer147          to DE4SDV_SDVPlatformStack::SDVPlatformStack::middleware;148        dependency classificationRuleSourceTrace149          from adapterLayer150          to isoIEC26580ClassificationSource;151152        view middlewareProductLineClassificationView : TVD::TableView {153          viewpoint selectedProductLineClassificationViewpoint : ProductLineClassificationViewpoint {154            frame productLineCapabilityClassificationConcern;155          }156157          expose FeatureClassification::adapterLayer;158          expose FeatureClassification::signalAccessCapability;159          expose FeatureClassification::lifecycleCoordinationCapability;160          expose FeatureClassification::healthMonitoringCapability;161          expose FeatureClassification::diagnosticAccessCapability;162          expose FeatureClassification::updateCoordinationCapability;163          expose FeatureClassification::safetyPathDecision;164          expose FeatureClassification::securityTrustBoundary;165          filter @ SysML::PartUsage;166          attribute :>> includeReferenceElements = true;167          attribute :>> maxRowHeight = 300;168          view ID :> columnViews {169            attribute :>> featureToRender = CT::declaredName;170          }171          view Classification :> columnViews {172            attribute :>> featureToRender = CT::heritage;173          }174          view Rationale :> columnViews {175            attribute :>> featureToRender = CT::documentation;176            attribute :>> columnWidth = 360;177          }178        }179      }180    }181  }182}183