Journal of Information Processing Systems

Korea Information Processing Society (한국정보처리학회)
권호 표지
DOI QR코드

DOI QR Code

An Experiment of Traceability-Driven System Testing

  • Choi, Eun-Man (Dept. of Computer Engineering, Dongguk University) ;
  • Seo, Kwang-Ik (Dept. of Computer Engineering, Dongguk University)
  • Published : 2008.03.31
Download PDF
⟨ Previous Next ⟩

Abstract

Traceability has been held as an important factor in testing activities as well as model-driven development. Vertical traceability affords us opportunities to improve manageability from models and test cases to a code in testing and debugging phase. This paper represents a vertical test method which connects a system test level and an integration test level in testing stage by using UML. An experiment how traceability works to effectively focus on error spots has been included by using concrete examples of tracing from models to the code.

Keywords

References

  1. E. Dustine, Effective Software Testing: 50 specific ways to improve your testing (Addison-Wesley, 2003)
  2. Lionel Briand and Yvan Labiche, A UML-based approach to system testing, Proc. 4th International Conf. on UML - The Unified Modeling Language, Modeling Languages, Concepts, and Tools, Toronto, CA, 2001, pp.194-208
  3. Lionel Brian and Yvan Labiche, A UML-based approach to system testing, Software and System Modeling, 1(1), 2002, pp.10-42 https://doi.org/10.1007/s10270-002-0004-8
  4. Aynur Abdurazik and Jeff Offutt, Using UML collaboration diagrams for static checking and test generation, Proc. 3rd International Conf. on UML - - The Unified Modelling Language, Advancing the Standard, York, UK, Vol. 1939 of LNCS, 2000, pp.383-395 https://doi.org/10.1007/3-540-40011-7_28
  5. Jeff Offutt and Anyur Abdurazik, Generating tests from UML specifications, Proc. 2nd International Conf. on UML, 1999, pp.416-429
  6. M. Scheetz, A. von Mayrhauser, R. France, E. Dahlman, and A. E. Howe, Generating test cases from an OO model with an AI planning system, Proc. 10th International Symposium on Software Reliability Engineering, Boca Raton, Florida, 1999, pp.250-259
  7. J. Hartmann, C. Imoberdorf and M. Meisinger, UMLBased integration testing, Proc. ACM SIGSOFT International Symposium on Software Testing and Analysis, Portland, 2002, pp.60-70
  8. O. Gotel and A. W. Finkelstein, An analysis of the requirements traceability problem, Proc. of the International Conf. on Requirements Engineering, Colorado Springs, CO, 1994, pp.94-102
  9. B. Ramesh, Factors influencing requirements traceability in practice, Communications of the ACM, 41(12), 1998, pp.34-44 https://doi.org/10.1145/290133.290147
  10. Marcus, A and Maletic, J. I, Recovering documentation-to-source-code traceability links using latent semantic indexing, Proc. 25th International Conference Software Engineering, 2003, pp.125-135
  11. G. Antonio and G. Canfora, G. Casazza, Recovering traceability links between code and documentation, IEEE Transaction, Vol 28, 2002, pp.970-983 https://doi.org/10.1109/TSE.2002.1041053
  12. L. Naslavsky, T. Alspaugh, D. Richardson, and H. Ziv, Using scenarios to support traceability, Proc. TEFSE 2005, California, pp.25-31
  13. T. Kastren, Towards Trace Based Model Synthesis for Program Understanding and Test Automation, Proc. International Conference on Software Engineering Advances, 2007, pp.46-56
  14. J. Hayes, A. Dekhtyar, and J. Osborne, Improving requirements tracing via information retrieval, Proc. 11th IEEE Interantioanl Requirements Engineering Conference, 2003, pp.138-147
  15. J. Richardson and J Green, Automating traceability for generated software artefacts, Proc, 19th International Conference on Automated Software Engineering, 2004, pp.356-366
  16. M. Lormans and A. Van Deursen, Can LSI help reconstructing requirements traceability in design and test?, Proc. Conference on Software Maintenance and Reengineering, 2006, pp.47-56
  17. M. Deng and B. Cheng, Retrieval By Construction: A traceability technique to support verification and validation of UML formalizations, Proc. International Jounal of Software Engineering and Knowledge Engineering, Vol. 15, 2005, pp.837-872 https://doi.org/10.1142/S0218194005002531
  18. K. Seo and E. M. Choi, Comparison of five black-box testing methods for object-oriented software,” Proc. 4th ACIS International Conference on Software Engineering Research, Management & Applications, Seattle, WA, 2006, pp.213-220
  19. D. Wood, J. Reis, Use case derived test cases, Proc. on Conf. on Software Quality Engineering STAREAST, 1999, http://www.stickyminds.com/s.asp?F =S2021_ ART_2
  20. Chun-Yu Chen, Constructing usage-based testing on Object-Z formal specification based specification, Ph.D. Dissertation, Auburn University, 1999
  21. E. M. Choi, Generating test cases for object-oriented design specification described by OCL,” Journal of Korean Information Processing Society, 8-D(6), 2001, pp.843-852
  22. E. M. Choi, Use-case driven test for object-oriented system, Proc. the IASTED International Conference, ACTA Press, 2001, pp.164-169
  23. Droschedl. W and Wiemers. M, Das V-Modell 97, (German, Oldenbourg, 1999)
  24. Roger S. Pressman, Software Engineering A Practitioner's Approach 6th, (McGraw-Hill, 2005)
  25. Paul C. Jorgensen and Carl Erickson, Object-Oriented Integration Testing, Communications of the ACM, 37(9), 1994, pp.30-37 https://doi.org/10.1145/182987.182989

Cited by

  1. Fault Localization by Comparing Memory Updates between Unit and Integration Testing of Automotive Software in an Hardware-in-the-Loop Environment vol.8, pp.11, 2018, https://doi.org/10.3390/app8112260