Synopsys, Inc. · NASDAQ:SNPS

Synopsys — Embedded World 2018 Exhibition & Conference

13 slides from Synopsys's conference presentation, Mar 1, 2018

  1. Slide 1: Continuous Integration and Test from Module Level to Virtual System Level

    Continuous Integration and Test from Module Level to Virtual System Level 1/3/2018 FOUFAS, ANDREASSON, HARTMANN, JUNGHANNS - PRESENTED AT THE EMBEDDED WORLD 2018 EXHIBITION & CONFERENCE 1

  2. Slide 2: A way of working

    A way of working • At Volvo Car Corporation, Propulsion division, we develop our own algorithms • These algorithms control the engine and the gearbox • Equations of physical systems are expressed in Python • These equations or functions are connected into a network • A python package is used to opti

  3. Slide 3: The bigger picture

    The bigger picture SIL removes bottlenecks Physical Testing Virtual Testing Number of tests • Physical test cells are limited in numbers due to HW and Facilities EP CD FPD HIL SIL • Virtual test cells are limited by number of SW licenses, only • SIL offers a vehicle like integration environment • SI

  4. Slide 4: History

    History • Prior to the current engine generation, all tests done in car • During the development of the current engine generation, automatic unit and system tests were introduced. • Aftertreatment SW solely developed in Sil platform. • One senior SW developer said: now I know it will work when we te

  5. Slide 5: Unit testing an engine control Module

    Unit testing an engine control Module • The Software in current generation ECMs is structured into around 250 modules • Unit tests are required to ensure software quality and compliance with industry norms (e.g. ISO 26262) 1/3/2018 FOUFAS, ANDREASSON, HARTMANN, JUNGHANNS - PRESENTED AT THE EMBEDDED

  6. Slide 6: Code instrumentation: Motivation

    code instrumentation: Motivation • Functions in the ECU are made • Unit tests need to be up of smaller units during applicable to subfunctions the design phase • Values need to be injected • These Subfunctions are not into the input vector of each represented in generated code subfunction 1/3/2018 F

  7. Slide 7: Code instrumentation: Signal Aliases

    code instrumentation: Signal Aliases • Code generators tend to use temporary, local variables • Analysis is needed to determine cases where such a temporary variable is always equal to a measurable signal • Value injecting needs to take into account all aliases of a given input 1/3/2018 FOUFAS, ANDR

  8. Slide 8: Requirement based Test (Motivation)

    Requirement based Test (Motivation) • Traditional Unit Tests rely on a small amount of scripted scenarios • Every requirement is associated with a fixed set of stimuli that should result in the wanted behavior • In large systems in a continuous environment it is hard to achieve a sufficient test cov

  9. Slide 9: Requirement based Test (WATCHERS)

    Requirement based Test (WATCHERS) • Requirement watchers are defined through preconditions and expected behavior WHENEVER Pressure Cntrl is Active EXPECT Desired Pressure WITHIN 10s • All requirements can be monitored at all times • Watchers are independent of the scope of the test large number of s

  10. Slide 10: SiL Software process

    SiL Software process • A DLL of our SW components is created • A text file specifies the System Under Test, can be the whole SW, a set of function, one function or a subsystem of a model • Test cases are extracted from the developers Silver database 1/3/2018 FOUFAS, ANDREASSON, HARTMANN, JUNGHANNS -

  11. Slide 11: SiL Software process

    SiL Software process • Test cases are expressed in Python • Run TestWeaver Light on a Jenkins test server as a nightly build • Code coverage is measured by using CTC++ from Verifysoft and reported as HTML 1/3/2018 FOUFAS, ANDREASSON, HARTMANN, JUNGHANNS - PRESENTED AT THE EMBEDDED WORLD 2018 EXHIBIT

  12. Slide 12: Conclusions

    Conclusions • The presented method of code instrumentation provides a way to design tests and requirements for arbitrarily small units inside a large system • By ensuring reusability and independence of requirement definitions - watchers, they can be applied to many test – stimuli • The cross produc

  13. Slide 13: Way forward

    Way forward • We are currently expanding our Engine, ECU C code range of plant models, so that Sensor and the developers can use closed Emission loop simulations. Models Silver • We have started with Explorative Tests, where the stimuli is Gear Box automatically generated. • We are adding more Addit

Synopsys — Embedded World 2018 Exhibition & Conference on 6ix