QuaTrace: A Tool Environment for (Semi-) Automatic Impact Analysis Based on Traces

IEEE International Conference on Software Maintenance, ICSM

Volumn , Issue , 2003, Pages 246-255

  Von Knethen, Antje ^a   Grund, Mathias ^b  

^a FRAUNHOFER IESE   (Germany)

^b University of Koblenz Landau   (Germany)

Author keywords

[No Author keywords available]

Indexed keywords

MANAGEMENT INFORMATION SYSTEMS; PROFESSIONAL ASPECTS; PROJECT MANAGEMENT;

MANAGEMENT TOOLS;

COMPUTER SOFTWARE;

EID: 57649154250     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/ICSM.2003.1235427     Document Type: Conference Paper

References (31)

1. S. A. Bohner and R. S. Arnold, "Software Change Impact Analysis", IEEE Computer Society Press, Los Alamitos, California, 1996.
2. M. Lindvall and K. Sandahl, "How well do experienced software developers predict software change", The Journal of Systems and Software, Vol. 43, 1998, pp. 19-27.
3. http://www.rational.com/products/reqpro/index.jsp
4. http://www.ilogix.com/products/rhapsody/index.cfm
5. B. Ramesh and M. Jarke, "Towards Reference Models for Requirements Traceability", IEEE Transactions on Software Engineering, Vol. 27, No. 1, 2001.
6. A. von Knethen, "A Trace Model for System Requirements Changes on Embedded Systems", International Workshop on Principles of Software Evolution (IWPSE' 01), 2001.
7. A. von Knethen, et al., "Systematic Requirements Recycling through Abstraction and Reuse". RE 2002, 2002.
8. M. Lindvall, "A Study of Traceability in Object-Oriented Systems Development", Licentiate thesis Linköping Studies in Science and Technology, No 462, Linköping University, Institute of Technology, Sweden, 1994.
9. D. Leffingwell and D. Widrig, "Managing Software Requirements. A Unified Approach", Addison-Wesley, 2000.
10. A. von Knethen, "Change-Oriented Requirements Traceability. Support for Evolution of Embedded Systems", PhD Thesis, University of Kaiserslautern, Germany, 2001.
11. http://www.telelogic.com/products/doorsers/index.cfm
12. M. Grund, "Verfolgung funktionaler Anforderungen mit Hilfe existierender Werkzeuge", Master Thesis, University of Kaiserslautern, Germany, 2003.
13. B. Paech, et al., "Integrated Quality Assurance and Requirements Analysis for the Software Development in Automotive Systems", http://www.first.gmd.de/svt/quasar/english, 2002.
14. B. Smith, "The Application of a Tool Like RDD-100 to Accommodate Traceability from Requirements to Test Results", http://www.alc.com/archive.shtml, 1999.
15. th International Computer Software & Application Conference, 1992, pp. 362-368.
16. A.C.W. Finkelstein et al., "Inconsistency handling in multi-perspective specifications", IEEE Transactions on Software Engineering, Vol. 20, No. 8, 1994, pp. 569-578.
17. K. Pohl, "PRO-ART: A Process Centered Requirements Engineering Environment", In: M. Jarke, C. Rolland, A. Sutclifffe and R. Dömges (Publisher), The NATURE of Requirements Engineering, Shaker Verlag, 1999, pp. 255-278.
18. A. van Lamsweerde et al., "Managing Conflicts in Goal-Driven Requirements Engineering", IEEE Transactions on Software Engineering, Vol. 24, No. 11, 1998, pp. 908-926.
19. K.B. Gallagher and J.R. Lyle, "Using Program Slicing in Software Maintenance", IEEE Transactions on Software Engineering, Vol. 17, No. 8, 1991, pp. 751-761.
20. nd Edition, 1996.
21. D. Parnas and J. Madey, "Functional Documentation for Computer Systems Engineering", CRL Report 237, McMaster University, Hamilton, Ontario, Canada, 1991.
22. R. Janicki et al., "Tabular Representations in Relational Documents", Technical Report CRL 313, Telecommunication Research Institute of Ontario (TRIO), Nov. 1995.
23. D.P. Kirkman, "Requirements Decomposition and Traceability", Journal Requirements Engineering, Vol. 3, No. 2, 1998, pp. 107-114.
24. C.V. Ramamoorthy et al., "The evolution support environment system", IEEE Transactions on Software Engineering, Vol. 16, No. 11, 1990, pp. 1225-1234.
25. B. Ramesh and V. Dhar, "Supporting Systems Development by Capturing Deliberations During Requirements Engineering", IEEE Transactions on Software Engineering, Vol. 18, No. 6, 1992, pp. 498-510.
26. INCOSE Requirements working group, "Requirements Management, Requirements Analysis, and Requirements Engineering methodology", http://www.incose.org/tools/.
27. X. Song et al., "Lessons Learned From Building A Web-Based Requirements Tracing System", Proc. of International Conference on Requirements Eingieering, 1998, pp. 41-50.
28. F.A.C. Pinheiro and J.A. Goguen, "An Object-Oriented Tool for Tracing Requirements", IEEE Software, Vol. 13, No. 2, 1996, pp. 52-64.
29. O.C.Z. Gotel and A. Finkelstein, "An Analysis of the Requirements Traceability Problem", Proc. Internatioal Conference on Requirements Engineering (ICRE), IEEE CS Press, 1994, pp. 94-101.
30. IEEE Std. 610.12-1990, "Standard Glossary of Software Engineering Terminology", 1990.
31. R.J Turver and M. Munro, "An early impact analysis technique for software maintenance", Journal of Software Maintenance - Research and Practice, Vol. 6, 1994, pp. 35-52. Also published in [1].