Automating software traceability in very small companies: A case study and lessons learned

Proceedings - 21st IEEE/ACM International Conference on Automated Software Engineering, ASE 2006

Volumn , Issue , 2006, Pages 145-153

  Neumüller, Christian ^a   Grünbacher, Paul ^a  

^a JOHANNES KEPLER UNIVERSITY LINZ   (Austria)

Author keywords

[No Author keywords available]

Indexed keywords

AUTOMATION; CODES (SYMBOLS); LEARNING SYSTEMS; PROJECT MANAGEMENT;

AUTOMATION TECHNIQUES; SOFTWARE TRACEABILITY;

SOFTWARE ENGINEERING;

EID: 34547476486     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/ASE.2006.25     Document Type: Conference Paper

References (23)

1. F. Abbattista, F. Lanubile, G. Mastelloni, and G. Visaggio. An experiment on the effect of design recording on impact analysis. In ICSM, pages 253-259, 1994.
2. G. Antoniol, G. Canfora, G. Casazza, A. De Lucia, and E. Merlo. Recovering traceability links between code and documentation. IEEE Transactions on Software Engineering, 28(10):970-983, 2002.
3. S. Biffl, A. Aurum, B. Boehm, H. Erdogmus, and P. Grünbacher, editors. Value-based Software Engineering. Springer-Verlag, 2006.
4. J. Cleland-Huang and D. Schmelzer. Dynamic tracing nonfunctional requirements through design pattern invariants. In International Workshop on Traceability in Emerging Forms of Software Engineering, volume 2, 2003.
5. P. Constantopoulos, M. Jarke, J. Mylopoulos, and Y. Vassiliou. The software information base: A server for reuse. VLDB Journal, 4(1):l-43, 1995.
6. A. Egyed. A scenario-driven approach to traceability. In Proceedings of the 23rd International Conference on Software Engineering (ICSE), Toronto, Canada, pages 123-132, 2001.
7. A. Egyed, S. Biffl, M. Heindl, and P. Grünbacher. Determining the cost-quality trade-off for automated software traceability. In Proceedings of the 20th ACM/IEEE International Conference on Automated Software Engineering (ASE), pages 360-363, Long Beach, CA, 2005.
8. A. Egyed and P. Grünbacher. Automating requirements traceability: Beyond the record & replay paradigm. In Proceedings of the 17 th IEEE International Conference on Automated Software Engineering (ASE'02), pages 163-171, Edinburgh, 2002. IEEE CS.
9. A. F. Egyed and P. Grünbacher. Identifying requirements conflicts and cooperation: How quality attributes and automated traceability can help. IEEE Software, 21(6), 2004.
10. A. F. Egyed and P. Grunbacher. Supporting software understanding with automated traceability. International Journal of Software Engineering and Knowledge Engineering (IJSEKE), 2005.
11. O. C. Z. Gotel and A. C. W. Finkelstein. An analysis of the Requirements Traceability Problem. In International Conference on Requirements Engineering, volume 1, pages 94-101, 1994.
12. J. Huffman Hayes, A. Dekhtyar, and J. Osborne. Improving requirements tracing via information retrieval. In International Conference on Requirements Engineering, 2003.
13. P. Koletzke and P. Dorsey. Oracle Developer Advanced Forms and Reports. Osborne/McGraw-Hill, 2000.
14. N. Medvidovic, A. Egyed, and P. Grünbacher. Stemming architectural erosion by coupling architectural discovery and recovery. In STRAW'03: Second International Software Requirements to Architectures Workshop at ICSE 2003, Portland, Oregon, 2003.
15. D. L. Parnas. Software aging. In International Conference on Software Engineering, pages 279-287, 1994.
16. K. Pohl. PRO-ART: Enabling requirements pre-traceability. In International Conference on Requirements Engineering, pages 76-84, 1997.
17. B. Ramesh and M. Jarke. Toward reference models for requirements traceability. IEEE Transactions on Software Engineering, 27(4):58-93, 2001.
18. B. Ramesh, L. C. Stubbs, and M. Edwards. Lessons learned from implementing requirements traceability. Crosstalk -Journal of Defense Software Engineering, 8(4):11-15, 1995.
19. Rational. Using Rational RequisitePro Version 2000.02.10. Rational Software Corporation, 2000.
20. S. A. Sherba, K. M. Anderson, and M. Faisal. A framework for managing traceability relationships. Proceedings of the 2nd International Workshop on Traceability for Emerging forms of Software Engineering, 2:32-39, 2003.
21. Telelogic. Requirements management for co-located teams. http://www.telelogic.com/corp/products/doors/doors/highlights. cfm, 12/2005.
22. UGS. Teamcenter enterprise: Doors integration. http://www.ugs.com/ products/teamcenter/docs/fs_doors_integration.pdf, 12/2005.
23. A. Zisman, G. Spanoudakis, E. Perez-Minana, and P. Krause. Tracing software requirements artefacts. 2003.