Supporting software understanding with automated requirements traceability

International Journal of Software Engineering and Knowledge Engineering

Volumn 15, Issue 5, 2005, Pages 783-810

  Egyed, Alexander ^a   Grünbacher, Paul ^b  

^a Teknowledge Corporation   (United States)

^b JOHANNES KEPLER UNIVERSITY LINZ   (Austria)

Author keywords

Automation; Software traceability; Software understanding

Indexed keywords

AUTOMATION; COMPUTATIONAL COMPLEXITY; COMPUTER SOFTWARE; DATA ACQUISITION; LARGE SCALE SYSTEMS; LIFE CYCLE; REQUIREMENTS ENGINEERING; VIDEO ON DEMAND;

REQUIREMENTS TRACEABILITY (RT); SOFTWARE APPLICATIONS; SOFTWARE TRACEABILITY; SOFTWARE UNDERSTANDING;

SOFTWARE ENGINEERING;

EID: 27744609126     PISSN: 02181940     EISSN: None     Source Type: Journal    
DOI: 10.1142/S0218194005002464     Document Type: Article

References (26)

1. O. C. Z. Gotel and A. C. W. Finkelstein, An analysis of the requirements traceability problem, in 1st Int. Conf. on Requirements Engineering, 1994, pp. 94-101.
2. B. Ramesh and M. Jarke, Toward reference models for requirements traceability, IEEE Trans. on Software Engineering 27(4) (2001) 58-93.
3. N. Medvidovic, P. Grünbacher, A. Egyed, and B. W. Boehm, Bridging models across the software lifecycle, Journal of Systems and Software 68(3) (2003) 199-215.
4. B. W. Boehm, Software risk management: Principles and practices, IEEE Software 8(1) (1991) 32-41.
5. ISO/IEC-9126, Information technology - software product evaluation - quality characteristics and guidelines for their use, Technical report, 1991.
6. P. Grünbacher, N. Medvicovic, and A. Egyed, Reconciling software requirements and architectures with intermediate models, Journal on Software and System Modeling, 2003.
7. K. Pohl, M. Brandenburg, and A. Glich, Integrating requirement and architecture information: A scenario and metarmodel based approach, in REFSQ Workshop, 2001.
8. INCOSE, Requirements management tool survey, online at http://www.incose.org. Technical report, INCOSE.
9. B. Ramesh, C. Stubbs, and M. Edwards, Lessons learned from implementing requirements traceability, Crosstalk - Journal of Defense Software Engineering 8(4) (1995) 11-15.
10. T. R,. Gruber and D. M. Russell, Generative Design Rationale, Lawrence Erlbaum Associates, 1994.
11. A. Egyed, Resolving uncertainties during trace analysis, in Proc. 12th ACM SIGSOFT Symposium on Foundations of Software Engineering (FSE), Irvine, CA, November 2004, pp. 3-12.
12. A. Egyed, A scenario-driven approach to trace dependency analysis, IEEE Trans. on Software Engineering 29(2) (2003) 116-132.
13. A. Egyed and P. Grünbacher, Identifying requirements conflicts and cooperation: How quality attributes and automated traceability can help, IEEE Software 21(6) (2004).
14. A. Egyed and P. Grünbacher, Automating requirements traceability: Beyond the record and replay paradigm, in Proc. 17th IEEE Int. Conf. on Automated Software Engineering (ASE02), Edinburgh, 2002, IEEE CS, pp. 163-171.
15. A. Egyed and P. Grünbacher, Towards understanding implications of trace dependencies among quality requirements, in 2nd Int. Workshop on Traceability in Emerging Forms of Software Engineering, eds. G. Spanoudakis and A. Zisman, Montreal, 2003.
16. S. Robertson and J. Robertson, Mastering the Requirements Process, Addison-Wesley, 1999.
17. B. W. Boehm, P. Grünbacher, and R. O. Briggs, Developing groupware for requirements negotiation: Lessons learned, IEEE Software 18(3) (2001) 46-55.
18. B. W. Boehm, A. Egyed, J. Kwan, D. Port, A. Shah, and R. Madachy, Using the winwin spiral model: A case study, IEEE Computer (7) (1998) 33-44.
19. G. Antoniol, B. Caprile, A. Potrich, and P. Tonella, Design-code traceability recovery: Selecting the basic linkage properties, Science of Computer Programming 40(2-3) (2001) 213-234.
20. G. C. Murphy, D. Notkin, and K. Sullivan, Software reflexion models: Bridging the gap between source and high-level models, in Proc. Third ACM SIGSOFT Symposium on the Foundations of Software Engineering, ACM, New York, 1995, pp. 18-28.
21. G. Antoniol, G. Canfora, A. De Lucia, and G. Casazza, Information retrieval models for recovering traceability links between code and documentation, in Proceedings of the International Conference on Software Maintenance, 2000, p. 40.
22. J. Arlow, W. Emmerich, and J. Quinn, Literate modelling - capturing business knowledge with the UML, in UML '98: Beyond the Notation, 1998.
23. O. Gotel and A. Finkelstein, Extended requirements traceability: Results of an industrial case study, in Proc. 3rd Int. Symposium on Requirements Engineering RE97, IEEE CS Press, 1997, pp. 169-178.
24. G. Spanoudakis, A. Zisman, E. Pérez-Minana, and P. Krause, Rule-based generation of requirements traceability relations, J. Systems and Software 72(2) (2004) 105-127.
25. F. G. Cysneiros, A. Zisman, and G. A. Spanoudakis, Traceability approach for i* and UML models, in Workshop Report (SELMAS 03): Software Eng. for Large-Scale Multi-Agent Systems, 2003.
26. J. Richardson and J. Green, Automating traceability for generated software artifacts, in ASE 2004, pp. 24-33.