Requirements Traceability Task
Jump to navigation
Jump to search
A Requirements Traceability Task is a Software Development Task that requires the tracing of a Software Item to the one or more supporting Software Requirements.
- Context:
- It can be used to discover dependencies that exist among software artifacts.
- It can be used to assess completeness of software artifacts.
- It can be used to test coverage.
- It can be used to support a change impact assessment.
- See: Requirements Management, Requirements Lifecycle.
References
2011
- (Wikipedia, 2011) ⇒ http://en.wikipedia.org/wiki/Requirements_traceability
- Requirements traceability is a sub-discipline of requirements management within software development and systems engineering. Requirements traceability is concerned with documenting the life of a requirement and to provide bi-directional traceability between various associated requirements. It enables users to find the origin of each requirement and track every change which was made to this requirement. For this purpose, it may be necessary to document every change made to the requirement.
It has been argued that even the use of the requirement after the implemented features have been deployed and used should be traceable[1].
- Requirements traceability is a sub-discipline of requirements management within software development and systems engineering. Requirements traceability is concerned with documenting the life of a requirement and to provide bi-directional traceability between various associated requirements. It enables users to find the origin of each requirement and track every change which was made to this requirement. For this purpose, it may be necessary to document every change made to the requirement.
- ↑ Gotel, O., Finkelstein, A. An Analysis of the Requirements Traceability Problem Proceedings of First International Conference on Requirements Engineering, 1994, pages 94-101
- (Kerton, 2011) ⇒ Brenda Kerton. (2011). “Requirements Traceability: Why Bother." Software Quality Connection.
- … There are three key reasons to add a requirements traceability practice:
- 1. Improve scope management. ...
- 2. Improve test coverage and test cost.
- 3. Improve change impact assessment.
- … There are three key reasons to add a requirements traceability practice:
2005
- G. Spanoudakis, and A. Zisman. (2005). “Software Traceability: A Roadmap.” In: Handbook of Software Engineering and Knowledge Engineering. World Scientific Publishing.
1998
- (Ramesh, 1998) ⇒ Balasubramaniam Ramesh. (1998). “Factors influencing requirements traceability practice.” In: Commun. ACM, 41(12). doi:10.1145/290133.290147
1993
- O. C. Z. Gotel, and C. W. Finkelstein. (1993). “An Analysis of the Requirements Traceability Problem.” In: Proceedings of the First International Conference on Requirements Engineering. doi:10.1109/ICRE.1994.292398
- ABSTRACT: 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 nature. We report how the majority of the problems attributed to poor requirements traceability are due to inadequate pre-RS traceability and show the fundamental need for improvements. We present an analysis of the main barriers confronting such improvements in practice, identify relevant areas in which advances have been (or can be) made, and make recommendations for research