WIXLIB

Improving Systems Engineering capabilities with Automotive SPICEand PREEvsisionDr.-Ing. Oliver Plan, Vector Consulting ServicesPREEvision User Day, Stuttgart, 20.03.2019V1.0 2019-03-16

Motivation“Improving Systems Engineering capabilities with Automotive SPICEand PREEvsision”Automotive SPICE (ASPICE)Systems Engineering (SE) Process capabilities correlate with productmaturity High complexity and distributed functionsin today’s automotive customer features ASPICE Level 3 is de-facto standard inAutomotive Engineering SE provides methods and systematicapproach to design complex features OEMS and Tier-1 require ASPICE by theirsupplier Trend: Document driven - Model BasedSystems Engineering (MBSE) ASPICE practices can be used for processimprovement Trend: Plan driven - AGILE MethodsHow can the use of PREEvision the implementation of Automotive SPICE and Systems Engineering?2/21 2018. Vector Consulting Services GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V1.0 2019-03-16

What is SPICE?SPICE: Software Process Improvement and Capability dEtermination Maturity model for system and software development Includes industrial “best practices” for ensuring a mature, systematicand well-documented system and software development SPICE is typically applied in two scenarios:Review of process maturity withinthe company and at suppliersGuideline for in-house em,ProcessSWimprovementdevelopment 2018. Vector Consulting Services GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V1.0 2019-03-16

Use Automotive SPICE for Process ImprovementExample: SYS.3 System architectural design (Level 1 only)BP 1: Develop system architectural designBP 2: Allocate System RequirementsBP 3: Define interfaces of system elementsBP 4: Describe dynamic behaviorImplement thebase practicesBP 5: Evaluate alternative systemarchitecturesBP 6: Establish bidirectional traceabilityBP 7: Ensure consistencyBP 8: Communicate agreed systemarchitectural design [ ] to all relevant e requiredwork products4/21Systemarch.design 2018. Vector Consulting Services GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V1.0 2019-03-16Traceabilityrecord( )

Use Automotive SPICE for Capability DeterminationLevel 3 Established PA.3.1 Process DefinitionPA.3.2 Process DeploymentA set of standard processes exists for theorganization The standard processes are applied inthe projects Feedback to improve standard processesis collected Processes are planned and tracked,responsibilities are defined, resources areprovided Results are identified, reviewed (QA) andunder configuration management Implement base practices, create workproducts Process outcomes are achieved andresults are created (somehow) Process outcomes are not or onlypartially achievedCapabilitydeterminationLevel 2 ManagedSystem,SW developmentPA.2.1 Performance ManagementPA.2.2 Work Product ManagementLevel 1 PerformedPA.1.1 Process PerformanceLevel 0 Incomplete5/21 2018. Vector Consulting Services GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V1.0 2019-03-16

Automotive SPICE Processes (VDA/HIS scope)Idea ?Systemreqts. analysisSystems EngineeringSystem arch.designSoftware EngineeringSW reqts.analysisManagement activityEngineering activityQualityassurance6/21SystemQualification testSystemintegration andint. testSW qualificationtestSW arch. designSW integrationand int. testSW det. designand unit constr.SW gementSuppliermonitoring 2018. Vector Consulting Services GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V1.0 ent

Automotive SPICE and Systems Engineering use similar Methods and ConceptsRequirement“What”Design and Test“How”“o.k.?”“Why”Example: Methods of abstraction, e.g. system levels, modularity, Requirements and allocated architecture on each level “Every requirement is a part of someone’s design” (S. Halligan) Supported by Model Driven Systems Engineering (i.e. Functional analysis using SysML)How can we implement those concepts in projects using PREEvision?7/21 2018. Vector Consulting Services GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V1.0 2019-03-16

System Requirements EngineeringSYS.2 System reqts analysis (Level 1)BP 1: Specify system requirementsBP 2: Structure system requirementsBP 3: Analyze system requirementsBP 4: Analyze the impact on the operatingenvironmentBP 5: Develop verification criteriaBP 6: Establish bidirectional traceabilityBP 7: Ensure consistencyBP 8: Communicate agreed record( )Benefits Definition, analysis and alignment is supported byattributes, mappings to other model artefacts in the EEbackbone Process is supported by metrics and workflows All needed information can be stored in the modelwithout tool-barriers 2018. Vector Consulting Services GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V1.0 2019-03-16

System ArchitectureSYS.3 System architect. design (Level 1)BP 1: Develop system architectural designBP 2: Allocate System RequirementsBP 3: Define interfaces of system elementsBP 4: Describe dynamic behaviorBP 5: Evaluate alternative systemarchitecturesBP 6: Establish bidirectional traceabilityBP 7: Ensure consistencyBP 8: Communicate agreed systemarchitectural design [ ] to all relevant partiesSystemarch.design9/21Traceabilityrecord( )Benefits Consistency of requirements and architecture can beeasily applied and managed using mappings Requirements, architecture and interfaces can beconsistently reused and updated as needed 2018. Vector Consulting Services GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V1.0 2019-03-16

SW Engineering and Detailed DesignSWE.1 SW reqts analysis (Level 1Same methodology as on System levelSWE.2 SW architectural design (Level 1Base practices mostly identicalSWE.3 SW detailed design and unitconstruction (Level 1)BP 1: Develop software detailed designBP 2: Define interfaces of software unitsBP 3: Describe dynamic behaviorBP 4: Evaluate software detailed designBP 5: Establish bidirectional traceabilityBP 6: Ensure consistencyBP 7: Communicate agreed SW det. design [ BP 8: Develop software unitsCoding acc. to Coding guidelinesInterfaces to MATLAB/SIMULINKSWE.4 SW unit verificationDynamic and static verification of SW units10/21Unit Test, e.g. VectorCASTBenefits Consistent and reusable definition of interfaces andarchitecture elements Closecouplingof System and SW engineering 2018. Vector Consulting Services GmbH. All rights reserved. Any distribution or copying is subject to prior writtenapproval by Vector.V1.0 2019-03-16

Integration and TestSWE.4 SW unit verificationSWE.5 SW integration and int. testSWE.6 SW qualification testSYS.4 System integration and int. testBP 1: Develop system integration strategyBP 2: Develop system integration test strategyincl. regression test strategyBP 3: Develop specification for systemintegration testBP 4: Integrate system itemsBP 5: Select test casesBP 6: Perform system integration testBP 7: Establish bidirectional traceabilityBP 8: Ensure consistencyBP 9: Summarize and communicate resultsdefine& alignTest strategy withtest levelsAligned definition of:-implement inTest objectsTest goalsTest methodsTest environmentTest end criteriaIntegration strategy execute & reportSYS.5 System qualification testBenefits Requirements, architecture and their model attributescan easily and consistently reused during testing11/21 2018. Vector Consulting Services GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V1.0 2019-03-16

Traceability is one of the biggest challenges in ASPICE projectsSource: Automotive SPICE 3.0 Process Assessment model12/21In many projects, traceability isapplied manually and costly afterengineering is finished.This brings no value to the project! 2018. Vector Consulting Services GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V1.0 2019-03-16

Applying consistency and traceabilityusing mappingsBenefits Traceability benefits most of integrated E/E backbone Integrated requirements architecture with abstractionis biggest advantage compared to heterogeneoustool-chains13/21 2018. Vector Consulting Services GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V1.0 2019-03-16

Project ManagementMAN.3 Project managementBP 1: Define the scope of workBP 2: Define project life cycleBP 3: Evaluate feasibility of the projectBP 4: Define, monitor and adjust projectactivitiesBP 5: Define, monitor and adjust projectestimates and resourcesBP 6: Ensure required skills, knowledge, andexperienceBP 7: Identify, monitor and adjust projectinterfaces and agreed commitmentsBP 8: Define, monitor and adjust projectscheduleBP 9: Ensure consistencyBP 10: Review and report progress of theprojectASPICE does not explicitly require V-Model, Waterfall etc.;AGILE methods are allowed, too!“Model-driven Systems Engineeringusing AGILE methods” Source: F. Kirschke-Biller (Ford): “Agile meetsAutomotive Systems Engineering”, Vector Forum, 201814/21 The model is the Systems Engineer’s “code”.The model is the integrated work product ofall processesDocumentation shall be derived from it asmuch as possibleThe model can be automatically verified forconsistency and traceability and enables highre-use and qualitystrongly supported by tools 2018. Vector Consulting Services GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V1.0 2019-03-16

The Future of the Management and Supporting ProcessesMAN.3 Projectmanagement“Model-driven Systems Engineering using AGILE methods”SUP.1 QualityassuranceSUP.8 ConfigurationManagementSUP.9 ProblemresolutionmanagementSUP.10 Change requestmanagementEach of those Management and Supporting Processes benefit from a systematic task-basedplanning, i.e. using PREEvision’s ticket functionality15/21 2018. Vector Consulting Services GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V1.0 2019-03-16

Quality AssuranceSUP.1 Quality assuranceBP 1: Develop a project quality assurancestrategyBP 2: Assure quality of work productsBP 3: Assure quality of process activitiesBP 4: Summarize and communicate QAactivities and resultsBP 5: Ensure resolution of non-conformancesBP 6: Implement an escalation mechanismBenefits QA activities are supported by workflow managementand review functionalities which can be applied on anyartefact (work products) QA team is supported also by reporting functionalities16/21 2018. Vector Consulting Services GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V1.0 2019-03-16

Configuration ManagementSUP.8 Configuration ManagementBP 1: Develop a configuration managementstrategyBP 2: Identify configuration itemsBP 3: Establish a configuration managementsystemBP 4: Establish branch managementBP 5: Control modifications and releasesBP 6: Establish baselinesBP 7: Report configuration statusBP 8: Verify the information about configureditemsBP 9: Manage the storage of configurationitems and baselinesBenefits Configuration Management more focusedon model configurations and baselines ofartefacts instead of storing files Plan and generate required reports forstakeholders as needed.17/21 2018. Vector Consulting Services GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V1.0 2019-03-16