SARE-väst. Challenges with traditional requirement handling from a Tier-1 perspective. Magnus Skoog Driven for Life

Autoliv - Safety Systems Active Safety Autoliv Every year, Autoliv s products save over 25,000 lives Passive The Worldwide Leader in Automotive Safety Systems Safety Magnus Skoog - 2 - Copyright Autoliv Inc All Rights Reserved

Vision Systems Example of functions Lane Detection Forward Collision Warning (Vehicle Detection) Traffic Sign Recognition Pedestrian Detection Light Source Recognition a Magnus Skoog - 4 - Copyright Autoliv Inc All Rights Reserved

System Break Down Traditionally Requirements View Function Design View Architecture View System level (Vehicle) Needs, requirements, constraints System Functions System Architecture OEM perspective Requirement Flow Sub-sys level Needs, requirements, constraints Sub-Sys Functions Requirement Flow Sub-Sys Architecture Tier 1 perspective HW/SW level Needs, requirements, constraints SW / HW Functions SW / HW Architecture Requirement Adaptation Vendors HW Components SW Components SW Tools Tier 2 perspective Magnus Skoog - 5 - Copyright Autoliv Inc All Rights Reserved

Customer requirements are on many levels The pedestrian detection must function within the speed range of greater than 0 km/h to X km/h of the system vehicle. For each pedestrian object, a warning trigger is defined based on the pedestrian's movement and position. The warning time is defined by OEM and is between X and Y seconds. The pedestrian detection must function in all weather conditions. The pedestrian detection must function worldwide. The development process at the supplier's company must fulfill all requirements in order to ensure a development process that is classified according to ASIL-X. ECU shall set DTC X in case failure of internal voltage Magnus Skoog - 7 - Copyright Autoliv Inc All Rights Reserved

System Complexity Increase Automotive electronics: Trends versus demands Expansion Low cost Complexity Quality and lead-time Integration Functional safety (ISO 26262) Necessary Actions System Design Collaboration Visibility of requirements Decision Support Tools and methodology Reuse aspects Data exchange 1000000 10000 100 1 2005 2010 2015 2020 Functions Lines of Code Requirements Magnus Skoog - 8 - Copyright Autoliv Inc All Rights Reserved

Architectural Priorities No FuSa, no feedback 1. Availability 2. Functionalities 3. Performance 4. Reuse FuSa system 1. Functional Safety 2. Availability 3. Performance 4. Reuse 5. Functionalities Magnus Skoog - 9 - Copyright Autoliv Inc All Rights Reserved

Tool Chains Complicated to exchange information between different tools Different roles have different views of the system System Model Sys Eng Requirements Management SW Eng Design QA SW Eng Code CM Magnus Skoog - 11 - Copyright Autoliv Inc All Rights Reserved

The planning tools need to be developed Different generations of planning tools: 1. Checklists: 70s 2. Planning Calendars: Time + Activities: 80s 3. Planning tools (e.g. Microsoft Project): 90s Time + Activities + Deadlines + Priority + Resources Planning Next Generation: 4. High level of planning? Ratio and results centered Taking into account the architecture Is visual Taking into account the integration Systems of systems Contributes to detailed planning Magnus Skoog - 12 - Copyright Autoliv Inc All Rights Reserved

Planning Next Generation Purpose Views that support different roles Efficiency ratios Integrating design and planning Support the integration work Potential Overview of planning and project monitoring Increased Productivity Magnus Skoog - 13 - Copyright Autoliv Inc All Rights Reserved

MBSE = Model Based System Engineering Dimensioning Analysis Analysis and technical decisions / selection of algorithms are done aided by models It is efficient and economic to do design once and not to have redundant information The model is the information container. Code and documents are generated Documentation Code Magnus Skoog - 15 - Copyright Autoliv Inc All Rights Reserved

Model Based Design on system level We need alternative notation for requirements. This would mean that OEM/Tier1/Tier2.. Could exchange models and not just requirements Magnus Skoog - 16 - Copyright Autoliv Inc All Rights Reserved