7.6.3 Requirements Driven Quality Assurance

Abstract

System development in practice is accompanied by two quality assurance measures for controlling and assessing development results: the review and the test. The form, frequency and scope of these measures must meet the quality and safety demands of the system, and take into account the working methods of the developers, the time available and budget of the project. High‐quality quality assurance has to be closely linked to the actual system development. Up to now this link has only been defined on the level of processes. This article describes a stronger content‐oriented and methodological integration of construction and quality assurance methods. On the basis of the central system development process Requirements Management, well‐known quality assurance processes have been embedded into comprehensive quality management. The result is a method for the generation and execution of an integrated quality assurance plan that runs parallel to and extensively supports the development of safety‐critical systems. The method is strongly focused on the requirements of a system and the ensurance of their implementation. The integrated method has already been successfully applied to real system development projects. The consistent application of quality assurance clearly improves the consistency and completeness of development items and their interfaces and ensures a complete realization of the requirements made of the system.

8.3.1 Towards an Integrated Methodology for the Model‐based Development of Embedded Automotive Control Software

“…As can be seen, the information model provides the Constraint class and four derived requirements classes. The fact that no abstraction levels [BD03] are provided for the requirements reflects the model's generic approach, since the number of levels of abstraction depend on system characteristics. Thus, abstraction levels for the requirements are not always useful.…”

4.4.1 Fine‐grained Method and Tool Integration for better Automotive Software

“…A development process thus acts as a framework, coordinating and controlling the use of the development methods it contains. Typical examples of development methods used in the automotive field are feature-based specification development [5], miscellaneous test methods and quality assurance procedures [6], but also a large number of knowledge fragments [7] -incomplete methods that are local to development teams, like best practices, etc. Our decision to focus on development methods is due to an important constraint in the auto-motive field: our work must fit into the current working environment of the development engineers.…”