Why software requirements traceability remains a challenge

CrossTalk

Volumn 22, Issue 7-8, 2009, Pages 14-19

  Kannenberg, Andrew ^a   Saiedian, Hossein ^b  

^a Garmin International Inc   (United States)

^b UNIVERSITY OF KANSAS   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

OPEN PROBLEMS; ORGANIZATIONAL POLICIES; QUALITY REQUIREMENTS; SOFTWARE REQUIREMENTS; TOOL SUPPORT; TRACEABILITY METHODS;

REQUIREMENTS ENGINEERING;

COMPUTER SOFTWARE;

EID: 68349083564     PISSN: None     EISSN: None     Source Type: Journal    
DOI: None     Document Type: Article

References (20)

1. The Standish Group. The Chaos Report. 1994 .
2. Gotel Orlena, and Anthony Finkelstein. An Analysis of the Requirements Traceability Problem. Proc. of the First International Conference on Requirements Engineering. Colorado Springs, 1994:94-101.
3. Domges Ralf, and Klaus Pohl. "Adapting Traceability Environments to Project Specific Needs." Communications of the ACM 41.12 (2008): 55-62.
4. The Standish Group. The Chaos Report. 2006.
5. Ramesh Balasubramaniam, and Matthias Jarke. "Toward Reference Models for Requirements Traceability." IEEE Transactions on Software Engineering 27.1 (2001): 58-93.
6. Palmer, J. D. "Traceability." Software Requirements Engineering. Richard H. Thayer and Merlin Dorfman, eds. New York: IEEE Computer Society Press, 1997.
7. Heindl Matthias, and Stefan Biffl. A Case Study on. Value-Based Requirements Tracing. Proc. of the 10th European Software Engineering Conference. Lisbon, Portugal, 2005: 60-69.
8. Wiegers Karl. Software Requirements. 2nd ed. Redmond, WA: Microsoft Press, 2003.
9. Boehm, Barry "Value Based Software Engineering." ACM SIGSOFT Software Engineering Notes 28.2 (2003).
10. Clarke Siobhán, et al. SubjectOriented Design.: Towards Improved Alignment of Requirements. Design. and Code. Proc. of the 1999 ACM SIGPLAN Conference on ObjectOriented Programming, Systems, Languages, and Applications. Dallas, : 325-329.
11. Cleland-Huang Jane, Carl Ê Chang, and Yujia G C. Supporting Event Based Traceability Through Higb-Level Recognition of Change Events. Proc. of the 26th Annual International Computer Software and Applications Conference on Prolonging Software Life: Development and Redevelopment. Oxford, England, 2002: 595-602.
12. Ramesh Balasubramaniam. "Factors Influencing Requirements Traceability Practice." Communications of the ACM 41.12 (1998): 37-44.
13. Jarke Matthias. "Requirements Tracing." Communications of the ACM 41.12 (1998): 32-36.
14. INCOSE. "INCOSE Requirements Management Tools Survey." 2008 .
15. Gills Martins. "Software Testing and Traceability." University of Latvia. 2005 .
16. Lempia, David L., and Steven P. Miller. Requirements Engineering Management. Proc. of the National Software and Complex Electronic Hardware Standardization Conference. Atlanta, 2006.
17. Cleland-Huang Jane, Carl K. Chang, and Mark J. Christensen. "EventBased Traceability for Managing Evolutionary Change." IEEE Transactions on Software Engineering 29.9 (2003): 796-810.
18. Young, Ralph R. "Twelve Requirement Basics for Project Success." CrossTalk Dec. 2006.
19. Spanoudakis George, et al. "RuleBased Generation of Requirements Traceability Relations." Journal of Systems and Software 72.2 (2004): 105-127.
20. Naslavsky Leila, et al. Using Scenarios to Support Traceability. Proc. of the Third International Workshop on Traceability in Emerging Forms of Software Engineering. Long Beach, CA, 2005: 25-30.