The missing link in requirements engineering
ACM SIGSOFT Software Engineering Notes
Why and How of Requirements Tracing
IEEE Software
Recovering Traceability Links between Code and Documentation
IEEE Transactions on Software Engineering
A Scenario-Driven Approach to Trace Dependency Analysis
IEEE Transactions on Software Engineering
Automating Requirements Traceability: Beyond the Record & Replay Paradigm
Proceedings of the 17th IEEE international conference on Automated software engineering
Understanding and Measuring the Sources of Variation in the Prioritization of Regression Test Suites
METRICS '01 Proceedings of the 7th International Symposium on Software Metrics
Balancing Agility and Discipline: A Guide for the Perplexed
Balancing Agility and Discipline: A Guide for the Perplexed
An Empirical Comparison of Two Safe Regression Test Selection Techniques
ISESE '03 Proceedings of the 2003 International Symposium on Empirical Software Engineering
Reviewing 25 Years of Testing Technique Experiments
Empirical Software Engineering
A Heterogeneous Solution for Improving the Return on Investment of Requirements Traceability
RE '04 Proceedings of the Requirements Engineering Conference, 12th IEEE International
A case study on value-based requirements tracing
Proceedings of the 10th European software engineering conference held jointly with 13th ACM SIGSOFT international symposium on Foundations of software engineering
Determining the cost-quality trade-off for automated software traceability
Proceedings of the 20th IEEE/ACM international Conference on Automated software engineering
TEFSE '05 Proceedings of the 3rd international workshop on Traceability in emerging forms of software engineering
Advancing Candidate Link Generation for Requirements Tracing: The Study of Methods
IEEE Transactions on Software Engineering
Automating Software Traceability in Very Small Companies: A Case Study and Lessons Learne
ASE '06 Proceedings of the 21st IEEE/ACM International Conference on Automated Software Engineering
A survey of traceability in requirements engineering and model-driven development
Software and Systems Modeling (SoSyM)
| Hi-index | 0.00 |
Software customers want both sufficient product quality and agile response to requirements changes. Formal software requirements tracing helps to systematically determine the impact of changes and to keep track of development artifacts that need to be re-tested when requirements change. However, full tracing of all requirements on the most detailed level can be very expensive and time consuming. In the paper an initial "tracing activity model" is introduced along with a framework that allows measuring the expected cost and benefit of tracing approaches. In a feasibility study a subset of the activities belonging to the model has been applied to compare three tracing strategies: agile, "just in time" tracing, and fully formal tracing. The study focused on re-testing and it has been performed in the context of an industry project where the customer was a large financial service provider.In the study a) the model was found useful to capture costs and benefits of the tracing activities and to compare different strategies; b) a combination of tracing approaches proved helpful in balancing agility and formalism.