/CFB04/
Mirko Conrad, Ines Fey, Kerstin Buhr:
Integration of Requirements into Model-based Development

Proc. International Workshop W-7 on Automotive Requirements Engineering (AuRE 2004), pp. 23-31, Nagoya, Japan, Sept. 2004

+ Download

Abstract:
Executable models are the central artifact in modelbased software development; they represent operational descriptions of system behavior and can describe aspects of specification and design as well as of implementation. However, certain types of relevant information, such as abstract top-level and non-functional requirements, are not easily covered within these models and therefore have to be described additionally by textual requirements. Besides these technical reasons, development standards and guidelines also enforce a separate capture of all requirements. Furthermore, an effective model-based development process requires a systematic tool-supported linking and tracing between textual requirements and individual model parts. In this paper we present our experiences gained at DaimlerChrysler Research in using such a dual modeling approach and respective tools. A UML information model describes the integration of the different engineering disciplines in model-based development, focusing on the requirement specification and modeling parts. This representation of all the essential information items which occur during modelbased development together with their relations was used to identify and select (according to project needs) those links which are useful in this specific development procedure. It was also possible to evaluate the tool support available on the basis of this information model.