Compositional Variability Management - - Key Success Factor for Systems Engineering

Transcription

1 Compositional Variability Management - - Key Success Factor for Systems Engineering SECESA th October 2012 Lisbon, Portugal Achim Seibertz Dr. Markus Brandstätter Dr. Karsten Theis PROSTEP AG 2012

2 Product Variants Explosion Automotive Example (Audi A6) Door panel front left Door panel rear Door panel front right Glove box Storage box front left Fuel tank Door handle cover Seat Exterior mirror mount A6 old A6 new Source: Audi, PROSTEP AG 2012

3 The Variant Dilemma Situation Customer requests individual product and new technologies Systematic reuse to reduce the number of components Domain specific approaches for managing variability Level Product Web-Configurator & ERP System & Component PDM/ALM & BOM-System Engineering & Documentation Artifacts Requirements Models SW-Impl. Tests Objects Product options, option sets and their relations Which options can be combined? Variant components and their relations Which components have to be in the same configuration and which not? Engineering documentation artifacts and their relations Which artifacts belong to a certain product configuration? Product variants are not only represented in their systems & components but also in the corresponding engineering & documentation artifacts 3

4 Versions, Variants & Relations 4

5 Versions, Variants & Relations 5

6 Versions, Variants & Relations 6

7 Versions, Variants & Relations Vertical & horizontal information flow Variant Management Challenges All information can be variant Different engineering tools use different variant management concepts and data models The limited cross-domain variant management leads to high maintenance & configuration effort Traceability Challenges Traceability of versions and variants cross domains Information encapsulation by file based data storage Non-integrated tool chains (horizontal & vertical) PROSTEP AG

8 Domain specific approaches to manage variability Variant management via attributes and filter, e.g. in DOORS Variant management by specific modeling means, e.g. enabled subsystems in Simulink Variant management via #ifdef, C++-Templates, Make, CVS Hard to read, comprehend and maintain Few/no data transfer between the systems / tools Variant management via code rules, No e.g. in Teamcenter cross checking for consistency Variant management via spreadsheets, e.g. in Excel 8

9 Variant management using Feature-Models Car mandatory optional Chassis Transmission Engine Cruise Control Alternative (XOR) OR Off-Road Sport Automatic Manual Electric Gasoline Diesel Standard ACC needs excludes V1 V2 # 112 variants w/o constraints Semantics given by propositional logic Supports use of formal solvers (SAT Solvers) # 15 variants left with constraints Arbitrary constraints possible 10/31/2012 PROSTEP AG

10 Raumkonzept Raumangebot vorne inkl. Ein- / Ausstieg Raumangebot hinten inkl. Ein- / Ausstieg Ablagekonzept Kofferraum / Zuladung VDA Volumen min/max in l, Länge, Breite und Tiefe des Kofferraums in mm Gesamtfahrzeug Zugänglichkeit Kofferraum Gesamtfahrzeug Höhe der Ladekante in mm, Höhe der Ladeöffnung und Breite der Ladeöffnung in mm Heckscheibenneigung in Grad Anzahl und Lage Golfbags J,.D. Power Maßgrößen Gesamtfahrzeug Gesamtfahrzeug MB-Warenkorb Gesamtfahrzeug besondere einzuhaltende Vorgaben, z.b. Anzahl der Sprudelkisten/Samsonitekoffer Compositional Variant Management Product-Variants Requirements Sign-Off Test Functional Spec. System-Test System Design Integration-Test Software-Arch. Unit-Test Implementation Variant information and structures along the life cycle Transformation into a generic variance representation Unified represention of different variance information Composition of the different variance models 10/31/2012 PROSTEP AG

11 Compositional Variant Management Methodology Domain (Variability Specification of Product Features & associated Technical Architecture) Product Feature Model (150% Structure) Vehicle Application (Application of the specified variability information for Product & Technical Configuration) Vehicle Product Configuration (100% Structure) Powertrain Chassis Powertrain Chassis Feature 3 Feature 4 Feature 1 Feature 2 Feature 3 Feature 1 Mapg Requirements Structure Vehicle Customer Req. Spec. CRS Req. 1 CRS Req. 2. System Req. Spec. SRS Req. 1 Requirements Structure Vehicle Customer Req. Spec. CRS Req. 1 CRS Req. 2 Function B SRS Req. 2 Technical Architecture (150% Structure).. SRS Req. 2. Technical Configuration (100% Structure) 11

12 v.control Unique Technology Demonstrator Example: Simultaneous Configuration 12

13 Selected References Development of a seamless variant management concept for model based function development Our Job Specification of a Feature-Model based concept Requirements Engineering & Management Architectur-Design Modeling & Code-Generation Validation & Verification Calibration Bridge between engineering department and system vendor Proof of Concept with v.control Systems Vector-Informatik easee The Mathworks - MATLAB/Simulink dspace TargetLink/RCP/CalDesk Time Frame: 18 Month Development and implementation of a variant based requirements management for the engine development department Our Job Definition of the Master-Specification Concept Coordination of the involved departments Creation of training material & demos Implementation in the existing IT-System Roll-Out support Systems IBM Rational DOORS Time Frame: 36 Month 13

14 Questions & Discussion Achim Seibertz Senior Manager Advanced Methods & Technology Dr. Markus Brandstätter Senior Consultant Advanced Methods & Technology Dr. Karsten Theis Head of Business Unit Systems Engineering 14

15 Backup 15

16 v.control Key Features Graphical feature model based variability specification Logic based constraint formulation Consistency checks based on formal analysis proving Rule based configuration with impact propagation Compositional approach to specify dependencies with work products (e.g. BOM entries) Simultaneous Configuration Optimization 16

17 Domain specific approaches to manage variability Examples 1/2 Variant management in PDM systems Specification of Variant Positions Specification of the corresponding Conditions Set of rules grow rapidly by adding new configuration conditions and variants due to clone and own approach of the engineers Example: (( IF2 + IC4 + IV0 + IA0 + ID2 + IQ1 ))/(( IF2 + IC4 + IV0 + IA0 + ID4 + IQ1 ))/(( IF2 + IC4 + IV0 + IA0 + ID5 + IQ1 )) identical with ( ID5/ID2/ID4 ) + IF2 + IQ1 + IA0 + IV0 + IC4 Variability is often only represented in leaf nodes of the product structure Hard to read, comprehend and maintain 17

18 poutservpf poutservsp poutservmo poutservsp poutservmo DoService DoService pout Availability poutdisplay Basic pout Availability poutdisplay Basic pout Availability Domain specific approaches to manage variability Examples II Variant management in function nets 150% Function net 100% Function net Car Mileage Km Cbs Car Mileage Km Cbs CarTime Sensors MotorOil Date Sensors Mo Km Date SensorsMo DoService CbsWd MotorOil Adaptive CbsWdSparkPlugs pout Availability Cbs ComputeServiceDate AvailabilityMo AvailabilitySp AvailabilityPf CarTime Sensors MotorOil Configuration Date Sensors Mo Km Date SensorsMo DoService CbsWd MotorOil Adaptive pout Availability Cbs ComputeServiceDate AvailabilityMo AvailabilitySp Sensors SparkPlugs Sensors Sp Km Date DoService SensorsSp CbsWd SparkPlugs Linear CbsWd SparkPlugs Adaptive pout Reset pout ServiceDate ServiceDate Cbs Display Car Display Sensors SparkPlugs Sensors Sp Km Date DoService SensorsSp CbsWd SparkPlugs Adaptive pout Reset pout ServiceDate ServiceDate Cbs Display Car Display Sensors Particle Filter Sensors Pf Km Date SensorsPf DoService CbsWd ParticleFilter Adaptive Reset CbsReset Car Service Reset CbsReset Car Service 18

19 Common Variability Language (CVL) Was ist die CVL? Domänenübergreifende Sprache zur Spezifikation und Berechnung von Varianten in Produktmodellen Basiert auf dem OMG Metamodell und ist somit z.b. in UML und SysML gleichermaßen einsetzbar Ist ein Subset der Object Constraint Language (OCL) Beinhaltet: Definition der wichtigsten Begriffe Beschreibung aller gängigen Beschreibungsmethoden für Varianten Status der CVL? Request for Proposal (RFP) Anmerkung: Feature-Modelle lassen sich in CVL-Notation überführen 19

20 Common Variability Language (CVL) Scope? Domain-independent language for the specification and resolving variability in product line models Based on OMG Metamodell and ready for use e.g. in UML und SysML Subset of Object Constraint Language (OCL) Including: Definition of key terms and concepts Status? Request for Proposal (RFP) Note: Feature-models can be converted into CVL notation 20

21 Common Variability Language (CVL) Overview interaction between CVL and MOF-based models Quelle: 21