Professional Documents
Culture Documents
Referencias
Referencias
Referencias
1. Cleland-Huang J, Berenbach B., Clark S., Settimi R., Romanova E. “Best Practices for
Automated Traceability,” Computer, 2007, vol. 40, no. 6, pp. 9.
6. Hayes J.H., Dekhtyar A., Osborne J. Improving requirements tracing via information
retrieval. In RE, page 138. IEEE Computer Society, 2003.
7. Cleland-Huang J., Chang C.K, Christensen M.J. Event-based traceability for managing
evolutionary change. IEEE TSE, 29(9):796– 810, 2003.
8. [*] Institute of Electrical and Electronics Engineers Inc., IEEE Standard Computer Dictionary:
A Compilation of IEEE Standard Computer Glossaries. New York, NY, USA: IEEE, 1991.
9. Palmer D. “Traceability”, in Software Requirements Engineering, R. Thayer and M. Dorfman,
Eds., 2nd ed., Los Alamitos, California: IEEE Computer Society Press, 2000, pp. 412-422.
10. UML (2004). Unified Modeling Language 2.0 Superstructure Specification. Retrieved
October, 2004 from http://www.omg.org/cgi-bin/doc?ptc/2004-10-02
11. D¨omges R.m, 41(12):54– 62, 1998. Pohl K. Adapting traceability environments to project
specific needs. CACM,
12. Cleland-Huang J., Berenbach B., Clark S., Settimi R., Romanova E. “Best Practices for
Automated Traceability,” Computer, 2007, vol. 40, no. 6, pp. 9.
13. Antoniol G., Canfora G., Casazza G., De Lucia, A. Identifying the Starting Impact Set of a
Maintenance Request: a Case Study in Proceedings of European Conference on Software
Maintenance and Reengineering (CSMR’00) (Zurich, Switzerland, February 29 - March 3,
2000), 227-230.