Reasoning about traceability in imperfect UML projects

• Autorzy: Derezińska A.
• Konferencja: Polish Conference on Software Engineering : KKIO'03 / sympozjum [5; 14-17 October 2003; Szklarska Poręba, Polska]
• Języki publikacji: EN

Słowa kluczowe

EN

software engineering; traceability; UML

PL

inżynieria oprogramowania; identyfikowalność; UML

• Wydawca: Wydawnictwo Politechniki Poznańskiej
• Czasopismo: Foundations of Computing and Decision Sciences
• Rocznik: 2004
• Tom: Vol. 29, No. 1-2
• Strony: 43--58
• Opis fizyczny: Bibliogr. 17 poz.

Twórcy

autor

Derezińska A.

• Institute of Computer Science, Warsaw University of Technology, Nowowiejska 15/19, 00-665 Warszawa, Poland,

Bibliografia

• [1] Cerbah F., Euzenat J., Using Terminology Extraction to Improve Traceability from Formal Models to Textual Requirements, in: M. Bouzeghoub et al. (eds.), Proceeding of NLDB 2000, LNCS 1959, Springer, 2001, 115-126.
• [2] Denisoff M., Traceability of requirement changes in UML project and their impact into the code reliability, master thesis (in Polish), Inst, of Computer Science, Warsaw University of Technology, 2003.
• [3] Ebner G., Kaindl H., Tracing all around, in: B. Wangler, L. Bergman (eds.). Proceeding of CAiSE 2000, LNCS 1789, Springer, 2000, 355-368.
• [4] Egyed A., A Scenario-Driven Approach to Trace Dependency Analysis. IEEE Trans, on Software Engineering, 29, 2, 2003, 116-132.
• [5] Insfran E., Pastor O., Wieringa R., Requirements Engineering-Based Conceptual Modelling, Requirements Eng., 1, Springer, 2002, 61-72.
• [6] Krutchen P., The Rational Unified Process An Introduction, Addison-Wesley, 2000
• [7] Letelier P., A Framework for Requirements Traceability in UML-based Projects, in: Proc. of 1st Int. Workshop on Traceability in Emerging Forms of Soft. Eng. by IEEE Conf. on ASE, Sept. 28, Edinburg, 2002.
• [8] Madeira H., Duraes J., Vieira M., Emulation of Software Faults: Representativeness and Usefulness, in: R. de Lemos et al. (eds.). Proc. of LADC 2003, LNCS 2847, Springer, Berlin, 2003, 137-159.
• [9] Mason P.A.J., Saeed A., Riddle S., On the Role of Traceability for Standards Compliance: Tracking Requirements to Code, in: S.Anderson et al. (eds.), SAFECOMP 2003, LNCS 2788, Springer Berlin, 2003, 303-316.
• [10] OMG Unified Language Specification - ver. 1.4, Sept. 2001, www.omg.org/uml
• [11] Pinheiro F.A.C., Goguen J.A., An object-oriented Tool for Tracing Requirements, IEEE Software, 13, 3, 1996, 52-64.
• [12]Ramesh B, Jarke M., Toward Reference Models for Requirements Traceability, IEEE Trans, on Soft. Engin, 27, 1, 2001, 58-92.
• [13] Rational Suite, www.rational.com/products
• [14] Sosnowski J., Lesiak A., Gawkowski P., Włodawiec P., Software Implemented Fault Inserters, in: Proceeding of IFAC Workshop on Programmable Devices and Systems, Ostrava, 2003, 427-432.
• [15] Spanoudakis G., Plausible and Adaptive Requirement Traceability Structures, in: Proceeding of SEKE'02 July 15-19, Ischia, Italy, ACM, 2002, 135-142.
• [16] Spence I., Probasco L., Traceability Strategies for Managing Requirements with Usecases, Rational Software 2000, http://www.rational.com/products/whitepapers/ 02270 l.jsp
• [17] Wong W. E. (eds.). Mutation Testing for the New Century, Kluwer Acad. Publ., 2001.