Towards practical software traceability

Proceedings - International Conference on Software Engineering

Volumn , Issue , 2008, Pages 1023-1026

  Asuncion, Hazeline U ^a  

^a UNIVERSITY OF CALIFORNIA   (United States)

Author keywords

Documentation; Management

Indexed keywords

DOCUMENTATION; E SCIENCE; EVALUATION PLANS; MANAGEMENT; OPEN HYPERMEDIA; SOCIAL PERSPECTIVES; SOFTWARE DEVELOPMENT; SOFTWARE TRACEABILITYS;

SOFTWARE ENGINEERING; SOFTWARE DESIGN;

DOCUMENTATION; E-SCIENCE; EVALUATION PLANS; OPEN HYPERMEDIA; SOCIAL PERSPECTIVE; SOFTWARE DEVELOPMENT; SOFTWARE TRACEABILITY;

EID: 57349108026     PISSN: 02705257     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1145/1370175.1370228     Document Type: Conference Paper

References (21)

1. Topic Maps. http://www.topicmap.com/
2. Anderson, K. M., Sherba, S. A., et al. Towards Large-Scale Information Integration. In Proc. of the 24th ICSE. Orlando, Florida, May, 2002.
3. Apache Software Foundation. Cocoon. http://cocoon.apache.org.
4. Asuncion, H., François, F., et al. An End-To-End Industrial Software Traceability Tool. In Proc. of the 6th Joint Meeting of the ESEC/FSE. Dubrovnik, Croatia, Sep, 2007.
5. Asuncion, H. and Taylor, R. N. Establishing the Connection Between Software Traceability and Data Provenance. ISR, UC, Irvine, Tech Report UCI-ISR-07-9, Nov, 2007.
6. Cheung, K. and Hunter, J. Provenance Explorer-Customized Provenance Views Using Semantic Inferencing. In Proc. of the 5th Int'l Semantic Web Conference. Athens, GA, Nov 5-9, 2006.
7. Cubranic, D., Murphy, G. C., et al. Hipikat: a Project Memory for Software Development. IEEE TSE. 31(6), p. 446-65, 2005.
8. Domges, R. and Pohl, K. Adapting Traceability Environments to Project Specific Needs. CACM. 41(12), p. 54-62, 1998.
9. Evans, M. SPMN Director Identifies 16 Critical Software Practices. CrossTalk, The Journal of Defense Software Engineering. Mar, 2001.
10. Horner, J. and Atwood, M. E. Design Rationale: the Rationale and the Barriers. In 4th Nordic Conf on HCI: Changing Roles: Oslo, Norway, 2006.
11. Institute for Software Research. xADL 2.0. http://www.isr.uci.edu/ projects/xarchuci/, UC, Irvine, 2005.
12. Institute for Software Research. ArchStudio 4. http://www.isr.uci.edu/ projects/archstudio/, UC, Irvine, 2006.
13. Jarke, M. Requirements Tracing. CACM. 41(12), p32-36, Dec 1998.
14. Lopes, C. V. and Baldi, P. The Sourcerer Project. http://sourcerer.ics. uci.edu/.
15. Marcus, A. and Maletic, J. I. Recovering Documentation-To-Source-Code Traceability Links Using Latent Semantic Indexing. In Proc. of 25th ICSE. Portland, OR, May 3-10, 2003.
16. Merrill, D. Mashups: The New Breed of Web App. http://www.ibm.com/ developerworks/xml/library/x-mashups.html, 2006.
17. Ramesh, B., Powers, T., et al. Implementing Requirements Traceability: A Case Study. In Proc. of the 1995 Intl. Symp on Req Eng (RE'95). p. 89-95, York, UK, Mar 27-29 1995.
18. Senior, I. e-Science Definitions. http://e-science.ox.ac.uk/public/ general/definitions.xml, 2002.
19. Spanoudakis, G. and Zisman, A. Software Traceability: A Roadmap Advances in Software Eng & Knowledge Eng. Chang, S. K. ed. 3, World Scientific Publishing, 2005.
20. Tang, A. and Han, J. Architecture Rationalization: A Methodology for Architecture Verifiability, Traceability and Completeness. Proc. of 12th IEEE Int'l Conf & Workshop on the Eng of Comp-Based Systems. Greenbelt, MD, Apr 4-7, 2005.
21. Zimmermann, T., Weibgerber, P., et al. Mining Version Histories to Guide Software Changes. In Proc. of the 26th ICSE Edinburgh, UK, May 23-28 2004.