Writing proper requirements is no easy task, especially in the domain of safety-critical systems. Standards (such as #ISO26262 or #ASpice) require semi-formal notations and proof of completeness, correctness, and consistency across various levels of abstraction.
Watch our online talk on lightweight semi-formal requirements with #hashtags with Boris Holzer from itemis AG and J. Fox from ZF Group Koblenz.
In the design and implementation of modern autonomous systems, machine learning and "classical" control systems are often combined to achieve the required functionality.
This poses new challenges to validation and verification. Traceability must be supported for the ML aspects as well as it is supported for classical software engineering. Creating a modular combination supports the testing of the functions with well establish methods and tools.
In this talk, Andreas Graf and Boris Holzer from itemis AG together with Ingo Nickles and Winfried Schröder from Vector Software adress those topics and discuss challenges and solutions.
Especially in the development of safety-critical systems where standards and guidelines such as ISO 26262, Automotive SPICE, DO-178, IEC61508, IEC 62304 and EN 50128 require the collection of requirements traceability in order to demonstrate that critical requirements have been adequately implemented and validated, are making traceability highly relevant. Consistent traceability speeds up and improves development activities and helps to avoid programming errors. However, in today's development projects, capturing traceability information leads to high acquisition costs due to the sheer volume of requirements and the resulting design artifacts, source code, and test cases. The use of custom tools to create and manage requirements, software design, source code, or software testing often does not allow for cross-tool traceability. Not infrequently, complex analyzes are necessary because artefacts are not linked directly but indirectly via other artifacts.
In this talk, Boris Holzer from itemis AG and Ingo Nickles from Vector Software tackle the biggest challenges with solutions and show a consistent traceability-implementation from requirement to model and source code to testing of individual modules.
Requirements Traceability is mandatory in many standards such as ISO26262 or Automotive Spice. Why actually?
In this online talk, we look at requirements traceability from the perspective of the manufacturer of a traceability tool. The talk is tool-agnostic! Instead, we discuss prerequisites for using traceability in the most beneficial way. Therefore, we also share impressions and ideas from various usage scenarios. This online talk is also suitable for beginners.
