Tool-Based Requirement Traceability between Requirement and Design Artifacts, 1st Edition

  • Published By:
  • ISBN-10: 3834824747
  • ISBN-13: 9783834824745
  • DDC: 005.1
  • Grade Level Range: College Freshman - College Senior
  • 439 Pages | eBook
  • Original Copyright 2013 | Published/Released April 2014
  • This publication's content originally published in print form: 2013

  • Price:  Sign in for price



Processes for developing safety-critical systems impose special demands on ensuring requirements traceability. Achieving valuable traceability information, however, is especially difficult concerning the transition from requirements to design. Bernhard Turban analyzes systems and software engineering theories cross-cutting the issue (embedded systems development, systems engineering, software engineering, requirements engineering and management, design theory and processes for safety-critical systems). As a solution, the author proposes a new tool approach to support designers in their thinking in order to achieve traceability as a by-product to normal design activities and to extend traceability information with information about design decision rationale.

Table of Contents

Front Cover.
Half Title Page.
Title Page.
Copyright Page.
Other Frontmatter.
1: List of Figures.
2: List of Tables.
3: Abbreviations.
4: Introduction.
5: Introduction to the Topic.
6: Context of this Thesis Project.
7: General Remarks on this Thesis.
8: General Structure of this Thesis.
9: General Context and Theories.
10: The Model Concept.
11: Embedded Systems Development.
12: Software Engineering (SE).
13: Systems Engineering (SysEng).
14: Requirements Engineering and Management.
15: Design in Systems and Software Development.
16: Quality Standards for Safety-Critical Development Processes.
17: Feedback from Embedded Practice.
18: Rationale Management and Traceability in Detailed Discussion.
19: Rationale Management in Systems and Software Engineering.
20: Requirements Traceability.
21: PROVEtech:R2A – A Tool for Dedicated Requirements Traceability.
22: Research Goals.
23: Accompanying Case Study.
24: Closing the Tool Gap.
25: Closing the Gap Between Requirements and Design.
26: Abstraction Layers and Abstraction Nodes.
27: Models Crossing Tool-Barriers.
28: Basic Support Features of R2A.
29: Requirements and Requirements Traceability.
30: Taxonomy of Requiremental Items231.
31: Support for Capturing Decisions236.
32: Resource Allocation as a Special Decision Making Case253.
33: Managing Changes and Consistency.
34: Aspects of Embedding R2A in a Process Environment.
35: Overall Architecture of R2A.
36: Synopsis.
37: Summary of the Achieved Research Results.
38: Perspectives for Further Research.
39: Conclusions.