This webinar is in CEST.
When developing safety critical systems according to standards such as ISO 26262, Automotive SPICE, DO-178, IEC 61508, IEC 62304 and EN 50128, it is necessary to capture the Requirements Traceability. The goal is to prove that critical requirements have been implemented and validated. A continuous Traceability optimizes development activities and minimizes the chance of programming errors. In modern development projects, however, capturing Traceability information leads to high collection costs, due to the sheer amount of design artefacts, source code, and test cases. In most cases, utilizing individual programs for the creation and management of requirements, for software design, source code, or software testing does not allow for the capture of Traceability across tools. Usually, elaborate analysis is necessary, since artifacts are not directly linked, but indirectly over other artifacts.
In this Webinar, we will be providing approaches to solve these problems, and we will display a consistent Traceability implementation from the requirements, over model and source code, to the testing of individual modules.
- Safety critical systems and traceability
- Continuous traceability to the test
- Embedded Unit Test and Code Coverage
- Linking Unit Tests with Requirements
- Live Demo - "Traceability Cockpit with evaluation of test results"
Boris Holzer is a certified requirements engineer and software architect. He has worked as a (technical) project manager in various specialist domains. Since 2014, he brings his enthusiasm for tools that enhance the development process and development quality into Yakindu Traceability's product development.
Ingo Nickles is a Senior Field Application Engineer at Vector and responsible for customer and project support for training and lectures on software development, system design, software testing and agile development methods.