An Evaluation of Requirements Management and Traceability Tools

Requirements management is critical to software delivery success and project lifecycle. Requirements management and their traceability provide assistance for many software engineering activities like impact analysis, coverage analysis, requirements validation and regression testing. In addition requirements traceability is the recognized component of many software process improvement initiatives. Requirements traceability also helps to control and manage evolution of a software system. This paper aims to provide an evaluation of current requirements management and traceability tools. Management and test managers require an appropriate tool for the software under test. We hope, evaluation identified here will help to select the efficient and effective tool.




References:
[1] I. Sommerville, P. Sawyer, Requirement Engineering: A Good Practice
Guide, John Wiley & Sons, 1997.
[2] G. Kotonya, I. Sommerville, Requirements Engineering, John Wiley &
Sons, New York, 1998.
[3] T. Gorschek, Requirements Engineering Supporting Technical Product
Management, PhD Thesis no. 2006:01, ISBN 91-7295-081-1, Blekinge
Institute of Technology, Ronneby, Sweden.
[4] DOORS, http://www-01.ibm.com/software/awdtools/doors/
[5] Rational RequisitePro, http://www-
01.ibm.com/software/awdtools/reqpro/
[6] J.H. Hayes, A. Dekhtyar, S.K. Sundaram, E.A. Holbrook, S. Vadlamudi,
and A. April, "REquirements TRacing On target (RETRO): improving
software maintenance through traceability recovery", Innovations in
Systems and Software Engineering, vol. 3, no. 3, Springer, 2007, pp.193-
202
[7] J. Han, "TRAM: A Tool for Requirements and Architecture
Management", Proceedings of 24th Australasian Computer Science
Conference, IEEE, 2001, pp. 60-68
[8] I Ozkaya, Ö Akin, "Tool support for computer-aided requirement
traceability in architectural design: The case of DesignTrack",
Automation in Construction, vol. 16, ELSEVIER, 2007, pp. 674-684
[9] Cradle, http://www.threesl.com/
[10] XTie-RT, http://www.tbe.com/index.php/defense/ps/sp/xtie/
[11] DevComplete, http://www2.smartbear.com/devc-aw-intrequirementstracking.
html?gclid=CN650pCPu6YCFYQa6wodiytkGw
[12] SLATE,
http://www.mathworks.com/products/connections/product_detail/produc
t_35447.htm
[13] J.E. Shin, A.G. Sutcliffe, and A. Gregoriades, "Scenario advisor tool for
requirements engineering", Journal of Requirements Engineering, vol.
10, no. 2, Springer, 2005, pp. 132-145.
[14] B. Nuseibeh, S. Easterbrook, "Requirements engineering: a roadmap",
Proceedings of Conference on the Future of Software Engineering,
ACM, 2000, pp. 35-46.
[15] http://en.wikipedia.org/wiki/Requirements_traceability
[16] O. Gotel, A. Finkelstein, "Extended Requirements Traceability: Results
of an Industrial Case Study", Proceedings of the Third IEEE
International Symposium on Requirements Engineering, IEEE, 1997,
pp.169-178.
[17] SWEBOK http://www.swebok.org
[18] Zave, P. (1997). Classification of Research Efforts in Requirements
Engineering. ACM Computing Surveys, 29(4): 315-321.
[19] Hoffmann, M., Kuhn, N., Weber, M. and Bittner, M. Requirements for
requirements management tools, Requirements Engineering Conference,
2004. Proceedings. 12th IEEE International. 301-308.
[20] CaliberRM,
http://www.ktgcorp.com/borland/products/caliber/index.html
[21] TopTeamAnalyst,
http://www.technosolutions.com/topteam_requirements_management.ht
ml
[22] ReMa, http://rema-soft.com/