9:30 - 9:45 Introduction
9:45 - 10:45 Part 1: Safety standards and debugging logic
10:45 - 11:00 Break
11:00 - 12:00 Part 2: Dynamic analysis and model-based testing
12:00 - 13:00 Lunch
13:00 - 14:00 Part 3: Test creation and testing of binary code
14:00 - 15:00 Part 4: Remote control and workflow integration
15:00 - 15:15 Break
15:15 - 16:15 Part 5: Test automation, summary, Q&A
Free 1-day Seminar and Workshop
INDES-IDS in association with iSYSTEM present:
The development ends when the testing is finished
Date: 12 October 2016
Time: 09:00 - 16:30
In this workshop, organized in cooperation with iSYSTEM AG and INDES-IDS, we will look into a process and development tools that can be used for concurrent development and testing of critical Embedded Systems.
As the test tools involved do not require any instrumentation and allow the code to run in Real-Time on the actual hardware, test development efforts are significantly reduced. This approach is also very well suited for building Hardware-In-the-Loop (HIL) system level tests.
Topics we will address
The topics below will be illustrated via an Electric Parking Brake (EPB) example application, and several live demonstrations. The EPB project artefacts are available for download from our repository.
- What do safety standards say in regard to testing (e.g. ISO 26262, IEC-61508)?
- How do auditors approach the certification of your product?
- Points to consider regarding the debug interface of your next MCU platform choice.
- Using debug tools to implement unit testing with code coverage.
- Original Binary Code (OBC) without code instrumentation for on-MCU testing.
- Model based approach to system test.
- Using your debug tools for Hardware in the Loop (HiL) testing.
- Exporting tests for continuous integration (CI) platforms, such as Jenkins.
- Multi-Core Trace and Multi-ECU trace
- Correlated tracing of CAN, CAN-FD, LIN and analog/digital I/O
Every day, embedded systems are used to improve quality of life, such as an insulin pump, or save lives, such as an air bag in a vehicle. In order to ensure users do not come to harm when using such devices, iSYSTEM provides the engineers who design and build such products with the high-quality tools they need to guarantee software and hardware safety and reliability.
Who should attend?
- R&D managers
- Engineering managers
- Embedded software engineers
- Software Quality Assurance
- Test engineers
Meet the presenters
After the presentations and during the breaks, the presenters
will be available to discuss projects in details and provide demonstrations
of their technology.
How do I register?
Register using the button at the top. You will receive a confirmation within a few days, as well as detailed guidelines a few days before the workshop.
What are the costs?
The entire event is free to attend for all registered attendees.
| 9:00 - 9:30||Registration|
| 9:30 - 9:45||Introduction and overview of INDES-IDS and iSYSTEM|
| 9:45 - 10:45||Part 1|
- Requirements for testing in accordance with, for example, ISO 26262, IEC62304...
- What does ISO 26262 or the FDA, MPG say about testing?
- The debugging interface — "The door to testing..."
- What to consider when choosing an MCU with regard to debugging.
|10:45 - 11:00||Break|
|11:00 - 12:00||Part 2|
- What do trace, profiling and code coverage actually deliver?
- Introduction to the methodology of test development
- Model-based testing, based upon an Electric Parking Brake (EPB)
|12:00 - 13:00||Lunch|
- You are cordially invited to a business lunch.
|13:00 - 14:00||Part 3|
- Strategic test case generation
- Defining test during the embedded code development phase
- Original Binary Code (OBC) testing of code without using code instrumentation, using testIDEA and BlueBox On-Chip Analyser
|14:00 - 15:00||Part 4|
- isystem.connect — Remotely controlling the BlueBox using the scripting language Python
- Continuous Integration (CI) using Jenkins
- nano-HIL concept — Hardware-In-The-Loop for continuous integration
|15:00 - 15:15||Break|
|15:15 - 16:15||Part 5|
- Integrating MBTsuite Tests, Jenkins CI and testIDEA with BlueBox
- Summary and Q&A