An analysis of the requirements traceability problem

@article{Gotel1994AnAO,
  title={An analysis of the requirements traceability problem},
  author={Olly Gotel and A. C. W. Finkelstein},
  journal={Proceedings of IEEE International Conference on Requirements Engineering},
  year={1994},
  pages={94-101}
}
  • O. Gotel, A. Finkelstein
  • Published 18 April 1994
  • Computer Science
  • Proceedings of IEEE International Conference on Requirements Engineering
Investigates and discusses the underlying nature of the requirements traceability problem. Our work is based on empirical studies, involving over 100 practitioners, and an evaluation of current support. We introduce the distinction between pre-requirements specification (pre-RS) traceability and post-requirements specification (post-RS) traceability to demonstrate why an all-encompassing solution to the problem is unlikely, and to provide a framework through which to understand its multifaceted… 
View on IEEE
discovery.ucl.ac.uk
1,416 Citations
Highly Influential Citations
108
Background Citations
690
Methods Citations
116
Results Citations
10

Figures and Tables from this paper

1,416 Citations

Citation Type

Citation Type

Contribution structures for requirements traceability
Our research is concerned with the problem of requirements traceability (RT). In the context of systems and software engineering, RT refers to the ability to describe and follow the life of a…
Today ' s practice of establishing traceability via < < Satisfy > >-links
TLDR
This analysis mainly serves the derivation of a concept for the integrated extension of today's traceability models with the aspect of documented design decisions as sustainable solution that supports,, heavyweight" prescriptive approaches as well as, lightweight" pragmatic approaches and moreover shows interdependencies between both kinds.
The Code System of a Systematic Literature Review on Pre-Requirements Specification Traceability
TLDR
A systematic literature review of the so-called pre-requirements specification (pre-RS) traceability was conducted, which identified 67 relevant papers and the whole resulting code system of the QDA was presented, to describe the relationships between the identified themes.
The Barriers to Traceability and their Potential Solutions: Towards a Reference Framework
TLDR
The barriers faced by organizations while implementing traceability are synthesized, along with proposed solutions to the barriers, given the importance of traceability in the regulated domain of safety critical software.
Analyzing and Systematizing Current Traceability Schemas
TLDR
An approach for a "traceability schema specification" and a first implementation on a software/system engineering environment are provided, which attempts to systematize the definition, deployment and maintenance of a traceability implementation.
The quest for Ubiquity: A roadmap for software and systems traceability research
TLDR
A brief view of the state of the art in traceability, the grand challenge for traceability and future directions for the field are presented.
A survey of traceability in requirements engineering and model-driven development
TLDR
An overview of the current state of traceability research and practice in requirements engineering and model-driven developers is provided, identifying commonalities and differences in these areas and uncover several unresolved challenges which affect both domains.
The Need for a Unifying Traceability Scheme
TLDR
This paper analyzes several current traceability schemes, in order to obtain relevant features and identify overlaps and inconsistencies among the approaches, and provides an initial approach for a Traceability Specification Scheme.
3 Why Post-RS Traceability Only Supports Limited Improvements
TLDR
This paper proposes an approach to support such modelling, outline preliminary details, and discusses how it provides the foundations for developing quality software.
Traceability-Why Do It?
TLDR
The paper compares the motivations and benefits for organizations operating inside and outside of the regulated domain of safety critical software, and re-assesses the value of traceability motivators for more widespread adoption by firmsoutside of the safety critical sector.
...
1
2
3
4
5
...

References

SHOWING 1-10 OF 159 REFERENCES
Issues of traceability in integrating tools
TLDR
Why the ability to discover the history of every feature of a system and being able to find out what resulted from a change request are needed are discussed.
Issues in the development of a requirements traceability model
  • B. Ramesh, M. Edwards
  • Computer Science
    [1993] Proceedings of the IEEE International Symposium on Requirements Engineering
  • 1993
TLDR
Based on an empirical study in a simulated systems development environment, several major issues that need to be considered in the development of a model of requirements traceability are addressed.
Tracing back from requirements
TLDR
The author compares and contrasts the problem of achieving traceability from a design, and its associated documentation, back to a requirements specification into the domain which gave rise to those requirements.
PDM: A Requirements Methodology for Software System Enhancements
TLDR
PDM is described, a requirements planning process that supports the collection, analysis, documentation, and tracking of software requirements and has been applied in three development areas with positive results.
A keyphrase based traceability scheme
TLDR
The paper discusses the purpose of a requirements traceability system, embedded machine readable traceability keyphrases, keyphrase syntax, the Dowty-SEMA traceability scheme, and the RRDS traceability schemes.
A taxonomy of current issues in requirements engineering
TLDR
A discussion of various classification criteria for existing requirements specification techniques follows a brief review of requirements specification contents and concerns.
Arts - an automated requirements traceability system
Integrating domain knowledge, requirements, and specifications
TLDR
A transformation-based software environment that supports the acquisition and validation of software requirements specifications and assists in the validation of formalized requirements by translating them into natural language and graphical diagrams and testing them against a running simulation of the system to be built.
The object-oriented systems life cycle
In software engineering, the traditional description of the software life cycle is based on an underlying model, commonly referred to as the “waterfall” model (e.g., [4]). This model initially…
Environment Evolution: The Prism Model of Changes
TLDR
The authors have designed in the Prism project a model of changes and two supporting change-related environment infrastructures with the following key features: separation of changes to the described items from theChanges to the environmental facilities encapsulating these items; a facility for describing various items and their interdependencies; and a built-in mechanism for providing feedback.
...
1
2
3
4
5
...