Determining the cost-quality trade-off for automated software traceability

20th IEEE/ACM International Conference on Automated Software Engineering, ASE 2005

Volumn , Issue , 2005, Pages 360-363

  Egyed, Alexander ^a   Biffl, Stefan ^b   Heindl, Matthias ^b   Grünbacher, Paul ^c  

^a Teknowledge Corporation   (United States)

^b VIENNA UNIVERSITY OF TECHNOLOGY   (Austria)

^c JOHANNES KEPLER UNIVERSITY LINZ   (Austria)

Author keywords

Automated trace analysis; Cost quality trade off; Experience report; Value based software engineering

Indexed keywords

AUTOMATED TRACE ANALYSIS; EXPERIENCE REPORT; VALUE-BASED; VALUE-BASED SOFTWARE ENGINEERING;

AUTOMATION; COMMERCE; COMPUTER SOFTWARE SELECTION AND EVALUATION; COST BENEFIT ANALYSIS; COSTS; QUALITY CONTROL; SOFTWARE DESIGN; STANDARDIZATION; TRACE ELEMENTS;

TRACE ANALYSIS;

EID: 34547417856     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1145/1101908.1101970     Document Type: Conference Paper

References (13)

1. Antoniol, G., Capril, B., Potrich, A., Tonella, P., Design-Code Traceability Recovery: Selecting the Basic Linkage Properties, Science of Computer Programming, vol. 40, no. 2-3, pp. 213-234, July 2001.
2. Biffl, S., Aurum, A., Boehm, B. W., Erdogmus, H., and Grünbacher, P. (eds.), Value-Based Software Engineering. September 2005, Springer-Verlag.
3. Boehm, B. W.: Value-Based Software Engineering. Software Engineering Notes, 28 (2), (March 2003)
4. Egyed, A. and Grünbacher, P., Automating Requirements Traceability: Beyond the Record & Replay Paradigm. Proc. of the 17th IEEE International Conference on Automated Software Engineering (ASE'02), Edinburgh, 2002.
5. Egyed, A., A Scenario-Driven Approach to Trace Dependency Analysis. IEEE Transactions on Software Engineering, 2003 29 (2):116-132.
6. Egyed, A. and Grünbacher, P., Identifying Requirements Conflicts and Cooperation: How Quality Attributes and Automated Traceability Can Help. IEEE Software, 2004. 21 (6).
7. Egyed, A., Tailoring Software Traceability to Value-based Needs, In: Biffl, S., Aurum, A., Boehm, B. W., Erdogmus, H., and Grünbacher, P. (eds.), Value-Based Software Engineering, Sept. 2005, Springer Verlag
8. Egyed, A. and Grünbacher, P., Supporting Software Understanding with Automated Traceability. in: International Journal of Software Engineering and Knowledge Engineering (IJSEKE) (in press), 2005.
9. Gotel, O. and Finkelstein, A., An Analysis of the Requirements Traceability Problem. Proc. 1st International Conference on Rqts. Eng., pp. 94-101, 1994.
10. Heindl, M. and Biffl, S, A Process for Value-based Requirements Tracing - A Case Study on the Impact on Cost and Benefit, Proc. ESEC/FSE, Lisbon, Sept. 2005.
11. Ramesh, B., Stubbs, L., and Edwards, M., "Lessons Learned from Implementing Requirements Traceability." Crosstalk, Journal of Defense Software Engineering 8, 4 (April 1995):11-15. Online at: http://www.stsc.hill. af.mil/crosstalk-/1995/apr/Lessons.asp.
12. th Int. IEEE Conf. on Automated SE, Linz, Austria, pp. 24-33, 2004.
13. Spanoudakis, G., Zisman, A., Perez-Minana, E., and Krause, P. Rule-based generation of requirements traceability relations. J. Systems and Software, 72 (2):105-127, 2004.