Using a Common Information Model as a Methodological Basis for a Tool‐supported Requirements Management Process

John, Gisela; Hoffmann, Matthias; Weber, M.; Nagel, M.; Thomas, Carsten

doi:10.1002/j.2334-5837.1999.tb00327.x

Cited by 9 publications

(8 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The information model. In the past, information models were mainly examined in the context of managing requirements [JHN+99,WW03] and, limited to this application context, were introduced into industrial practice selectively. Information models were also used to simplify the exchange of model information between different modelling and simulation tools [SM01].…”

Section: Structure and Content Of An Integrated Methodologymentioning

confidence: 99%

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

Buhr

Conrad

Dörr

et al. 2005

INCOSE International Symp

View full text Add to dashboard Cite

The complexity of developing automotive control unit software can generally not be mastered without an efficient development methodology. The development discipline activities requirements, modelling / implementation and quality assurance are, for this reason, supported by individual methods. In order to optimally coordinate the methods with one another during their deployment, a structured integration of these individual specialised methods is, however, essential. The following paper, using the model‐based development approach as an example, outlines the content and structure of an integrated methodology that provides such integration. Its use shortens development time and increases product quality by coordinating the deployment of individual methods over the course of the entire developmental process. The main components of this kind of integrated methodology are an interdisciplinary information model, process models with integrated procedures for the realisation of single development activities as well as guidance such as checklists, templates, and examples, among other things. In this paper, we present the experiences that we have gained at DaimlerChrylser Research in developing and applying such an integrated methodology1.

show abstract

Section: Structure and Content Of An Integrated Methodologymentioning

confidence: 99%

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

Buhr

Conrad

Dörr

et al. 2005

INCOSE International Symp

View full text Add to dashboard Cite

show abstract

“…At DaimlerChrysler we have introduced the acronym RMI (Requirements Management Information model) for these models. The development of a RMI together with engineers has become the central means for a successful introduction of requirements management into a project [7]. For obvious reasons of consistency and reusability we have introduced a company-wide modular RMI, so that new projects can start requirements management activities by adapting and tailoring this model.…”

Section: General Issuesmentioning

confidence: 99%

Requirements engineering in automotive development-experiences and challenges

Weber

Weisbrod

Proceedings IEEE Joint International Conference on Requirements Engineering

View full text Add to dashboard Cite

“…If used, object models can be found in the area of requirements engineering and management, because of the key role of the specification as the starting point of a development process' artifact chain. A lot of research work has been taken place there ( [24], [25], [26]).…”

Section: Figure 2 Artifact Model For Test Case Reviewmentioning

confidence: 99%

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

Altheide

Buhr

Doerr

2006

INCOSE International Symp

View full text Add to dashboard Cite

In the automotive field, software development methods and tools are used to cope with the high complexity of automotive software development. However, problems occur with the tracing of information, the assessment and monitoring of the development status, late and thus expensive changes, etc, which lead to increasing development costs and time as well as quality deficits. Our experience with recent projects have shown that the key to solving these problems lies in providing proper answers to the following questions: (1) How can development methods be assembled? (2) How can the use of a variety of development methods be supported by an appropriate tool? To answer these questions, we introduce a tool integration approach that is strongly based on the integration of development methods. The contribution of this paper is (a) a method integration approach that considers finegrained method objects and their specific structure in addition to the usually considered artifacts, (b) an approach to tool integration that overcomes the deficits of heterogeneous tool environments and utilizes the results of the methodical understanding.

show abstract

Using a Common Information Model as a Methodological Basis for a Tool‐supported Requirements Management Process

Cited by 9 publications

References 0 publications

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

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

Requirements engineering in automotive development-experiences and challenges

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

Contact Info

Product

Resources

About