Rule-based maintenance of post-requirements traceability relations

Proceedings of the 16th IEEE International Requirements Engineering Conference, RE'08

Volumn , Issue , 2008, Pages 23-32

  Mäder, Patrick ^a   Gotel, Orlena ^b   Philippow, Ilka ^a  

^a ILMENAU UNIVERSITY OF TECHNOLOGY   (Germany)

^b PACE UNIVERSITY   (United States)

Author keywords

Change; Post requirements traceability; Rule based traceability; Traceability maintenance

Indexed keywords

MAINTENANCE; REQUIREMENTS ENGINEERING; SOFTWARE DESIGN; SOFTWARE ENGINEERING; UNIFIED MODELING LANGUAGE;

ANALYSIS AND DESIGN MODELS; AUTOMATED TECHNIQUES; CHANGE; COMMERCIAL SOFTWARE DEVELOPMENTS; DEVELOPMENT ACTIVITIES; EVOLUTIONARY CHANGES; EVOLUTIONARY DEVELOPMENTS; POST-REQUIREMENTS TRACEABILITY; REQUIREMENTS SPECIFICATIONS; RULE-BASED TRACEABILITY; SOFTWARE DEVELOPMENTS; TIME CONSUMING; TRACEABILITY MAINTENANCE;

COMPUTER SOFTWARE MAINTENANCE;

EID: 58049185860     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/RE.2008.24     Document Type: Conference Paper

References (19)

1. I. Alexander. Toward automatic traceability in industrial practice. In Proc. 1st Int'l Workshop on Traceability in Emerging Forms of Software Engineering, pages 26-31, Edinburgh, UK, Sept. 2001.
2. G. Antoniol, G. Canfora, G. Casazza, A. D. Lucia, and E. Merlo. Recovering traceability links between code and documentation. IEEE TSE, 28(10):970-983, 2002.
3. P. Arkley, P. Mason, and S. Riddle. Position paper: enabling traceability. In Proc. 1st Int'l Workshop on Traceability in Emerging Forms of Software Engineering, pages 61-65, Edinburgh, UK, Sept. 2001.
4. J. Arlow and I. Neustadt. UML 2 and the Unified Process Second Edition: Practical Object-Oriented Analysis and Design. Addison-Wesley, 2005.
5. J. Cleland-Huang, C. K. Chang, and M. J. Christensen. Event-based traceability for managing evolutionary change. IEEE TSE, 29(9):796-810, 2003.
6. J. Cleland-Huang, C. K. Chang, and Y. Ge. Supporting event based traceability through high-level recognition of change events. In COMPSAC, pages 595-602. IEEE Computer Society, 2002.
7. D. Coleman. Object-Oriented Development: The Fusion Method. Prentice-Hall, 1994.
8. A. Dekhtyar, J. Hayes, S. Sundaram, A. Holdbrook, and O. Dekhtyar. Two heads are better than one, or too many cooks in the kitchen? Technique integration for requirements assessment. In Proc. 15th Int'l Requirements Eng. Conf., pages 69-83, Oct. 2007.
9. Extessy AG. ToolNET. www.extessy.com.
10. M. Fowler. Refactoring: Improving the Design of Existing Code. Addison Wesley, 1999.
11. O. C. Z. Gotel and A. C. W. Finkelstein. An analysis of the requirements traceability problem. In First International Conference on Requirements Engineering (ICRE'94), pages 94-101. IEEE CS Press, 1994.
12. J. H. Hayes, A. Dekhtyar, and J. Osborne. Improving requirements tracing via information retrieval. In RE, page 138. IEEE Computer Society, 2003.
13. I. Jacobson, J. Rumbaugh, and G. Booch. The Unified Software Development Process. Object Technology Series. Addison-Wesley, Reading/MA, 1999.
14. A. Marcus and J. I. Maletic. Recovering documentation-to-source-code traceability links using latent semantic indexing. In Proc. of the 25th Int'l Conf. on Software Eng. (ICSE-03), pages 125-137, Piscataway, NJ, May 3-10 2003. IEEE CS.
15. T. Olsson and J. Grundy. Supporting traceability and inconsistency management between software artefacts. In Int'l Conf. Software Eng. and Appl., Nov. 2002.
16. B. Ramesh and M. Jarke. Toward reference models of requirements traceability. IEEE Trans. Software Eng, 27(1):58-93, 2001.
17. V. Schuppan and W. Rußwurm. A CMM-based evaluation of the V-model 97. In R. Conradi, editor, EWSPT, volume 1780 of LNCS, pages 69-83, 2000.
18. J. Siedersleben. Moderne Software-Architektur. Dpunkt Verlag, August 2004.
19. G. Spanoudakis, A. Zisman, E. Pérez-Miñana, and P. Krause. Rule-based generation of requirements traceability relations. JSS, 72(2):105-127, 2004.