End to end requirement traceability through contribution structures
End-to-End Requirement Traceability through Contribution Structures and Requirements Traceability Matrices
Aamrah Naqvi aamra_naqvi@yahoo.com College of Computer Science
PAF - Karachi Institute of Economics and Technology, Pakistan
Syed Irfan Hyder hyder@pafkiet.edu.pk College of Compter Science
PAF - Karachi Institute of Economics and Technology, Pakistan.
Abstract
Requirements traceability is the ability to follow the life of a requirement, in both forward and backward direction, i.e. from its origin, to its refinement and inclusion in the requirement specification document, and from there to its subsequent deployment in coding, testing and validation [1]. Requirement traceability is often divided into Pre-Requirement Traceability and Post-Requirement Traceability. Pre-Requirement Traceability is concerned with requirement’s life before its inclusion in the requirement specification, while Post-Requirement Traceability is concerned with the requirement’s life after its inclusion in the requirement specification.
Traceability tools and techniques often use frameworks that are stronger in the Post-Requirement Traceability area [14, 15, 19]. Pre-Requirement Traceability is typically not covered because it is difficult to trace the origin of requirements to the individuals who initiate, authenticate and document the user requirements. This research indicates that the performance of these tools can be significantly improved by including Pre-Requirement Traceability in their traceability frameworks. This inclusion would solve many of the problems associated with these tools and techniques such as difficulty to trace the information necessary for requirements management and requirements change management.
Contribution structures specify relationships between the user requirements and their initiators [1,4]. Traceability matrix is a structure often used by tools and techniques covering post-requirement traceability [4]. Thesis of this research is
Aamrah Naqvi aamra_naqvi@yahoo.com College of Computer Science
PAF - Karachi Institute of Economics and Technology, Pakistan
Syed Irfan Hyder hyder@pafkiet.edu.pk College of Compter Science
PAF - Karachi Institute of Economics and Technology, Pakistan.
Abstract
Requirements traceability is the ability to follow the life of a requirement, in both forward and backward direction, i.e. from its origin, to its refinement and inclusion in the requirement specification document, and from there to its subsequent deployment in coding, testing and validation [1]. Requirement traceability is often divided into Pre-Requirement Traceability and Post-Requirement Traceability. Pre-Requirement Traceability is concerned with requirement’s life before its inclusion in the requirement specification, while Post-Requirement Traceability is concerned with the requirement’s life after its inclusion in the requirement specification.
Traceability tools and techniques often use frameworks that are stronger in the Post-Requirement Traceability area [14, 15, 19]. Pre-Requirement Traceability is typically not covered because it is difficult to trace the origin of requirements to the individuals who initiate, authenticate and document the user requirements. This research indicates that the performance of these tools can be significantly improved by including Pre-Requirement Traceability in their traceability frameworks. This inclusion would solve many of the problems associated with these tools and techniques such as difficulty to trace the information necessary for requirements management and requirements change management.
Contribution structures specify relationships between the user requirements and their initiators [1,4]. Traceability matrix is a structure often used by tools and techniques covering post-requirement traceability [4]. Thesis of this research is