Skip to main content
SpringerLink
Log in
Book cover

International Conference on Digital Information and Communication Technology and Its Applications

DICTAP 2011: Digital Information and Communication Technology and Its Applications pp 21–32Cite as

Test Management Traceability Model to Support Software Testing Documentation

  • Conference paper

  • 1802 Accesses

Part of the book series: Communications in Computer and Information Science ((CCIS,volume 167))

Abstract

Software Documentation is one of the key quality factors in software development. However, many developers are still putting less effort and less priority on documentation. To them writing documentation during project development is very tedious and time consuming. As a result, the documentation tends to be significantly out-dated, poor quality and difficult to access that will certainly lead to poor software maintenance. Current studies have proved that the key point to this problem is software traceability. Traceability relates to an ability to trace all related software components within a software system that includes requirements, test cases, test results and other artefacts. This research reveals some issues related to current software traceability and attempts to suggest a new software traceability model that focuses on software test documentation for test management. This effort leads to a new software test documentation generation process model based on software engineering standards.

This is a preview of subscription content, log in via an institution.

Chapter
USD   29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD   84.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD   109.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Learn about institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Boehm, B.: Value-based software engineering: reinventing. ACM SIGSOFT Software Engineering Notes 28(3), 3 (2003)

    Article  Google Scholar 

  2. Thomas, B., Tilley, S.: Documentation for software engineers: what is needed to aid system understanding? In: Proceedings of the 19th Annual International Conference on Computer Documentation, p. 236 (2001)

    Google Scholar 

  3. Huang, S., Tilley, S.: Towards a documentation maturity model. In: Proceedings of the 21st Annual International Conference on Documentation, pp. 93–99. ACM, San Francisco (2003)

    Google Scholar 

  4. Sommerville, I.: Software engineering:the supporting process., vol. 2. Addison-Wesley, Reading (2002)

    Google Scholar 

  5. Albinet, A., Boulanger, J.L., Dubois, H., Peraldi-Frati, M.A., Sorel, Y., Van, Q.D.: Model-based methodology for requirements traceability in embedded systems. In: 3rd ECMDA Workshop on Traceability (June 2007)

    Google Scholar 

  6. Knethen, A., Paech, B.: A survey on tracing approaches in practice and research. IESE-Report No. 095.01/E. 95 (2002)

    Google Scholar 

  7. Ramesh, B., Jarke, M.: Toward reference models for requirements traceability. IEEE Transactions on Software Engineering 27, 58–93 (2001)

    Article  Google Scholar 

  8. Geraci, A.: IEEE standard computer dictionary: compilation of IEEE standard computer glossaries. Institute of Electrical and Electronics Engineers Inc. (1991)

    Google Scholar 

  9. Aizenbud-Reshef, N., Nolan, B.T., Rubin, J., Shaham-Gafni, Y.: Model traceability. IBM Systems Journal 45, 515–526 (2006)

    Article  Google Scholar 

  10. Cleland-Huang, J., Chang, C.K., Sethi, G., Javvaji, K., Hu, H., Xia, J.: Automating speculative queries through event-based requirements traceability. In: Proceedings of the IEEE Joint International Requirements Engineering Conference (RE 2002), pp. 9–13 (2002)

    Google Scholar 

  11. Chang, C.K., Christensen, M.: Event-based traceability for managing evolutionary change. IEEE Transactions on Software Engineering 29, 796–810 (2003)

    Article  Google Scholar 

  12. Cleland-Huang, J.: Requirements traceability: When and how does it deliver more than it costs? In: 14th IEEE International Conference Requirements Engineering, pp. 330–330 (2006)

    Google Scholar 

  13. Ramesh, B.: Factors influencing requirements traceability practice (1998)

    Google Scholar 

  14. Knethen, A., Paech, B., Kiedaisch, F., Houdek, F.: Systematic requirements recycling through abstraction and traceability. In: Proc. of the Int. Conf. on Requirements Engineering, pp. 273–281 (2002)

    Google Scholar 

  15. Antoniol, G., Canfora, G., Casazza, G., De Lucia, A., Merlo, E.: Recovering traceability links between code and documentation. IEEE Transactions on Software Engineering, 970–983 (2002)

    Google Scholar 

  16. Marcus, A., Maletic, J.I.: Recovering documentation-to-source-code traceability links using latent semantic indexing. In: Proceedings of the 25th International Conference on Software Engineering, pp. 125–135 (2003)

    Google Scholar 

  17. Egyed, A., Grünbacher, P.: Automating requirements traceability: Beyond the record & replay paradigm. In: Proceedings of the 17th IEEE International Conference on Automated Software Engineering, pp. 163–171 (2002)

    Google Scholar 

  18. Aiken, P., Arenson, B., Colburn, J.: Microsoft computer dictionary. Microsoft Press (2002)

    Google Scholar 

  19. Kirova, V., Kirby, N., Kothari, D., Childress, G.: Effective requirements traceability: Models, tools, and practices. Bell Labs Technical Journal 12, 143–158 (2008)

    Article  Google Scholar 

  20. Narmanli, M.: A business rule approach to requirements traceability (2010)

    Google Scholar 

  21. Ibrahim, S., Idris, N.B., Uk, M.M., Deraman, A.: Implementing a document-based requirements traceability: A case study. In: IASTED International Conference on Software Engineering, pp. 124–131 (2005)

    Google Scholar 

  22. Salem, A.M.: Improving software Quality through requirements traceability models. In: IEEE International Conference on Computer Systems and Applications 2006, pp. 1159–1162 (2006)

    Google Scholar 

  23. Asuncion, H.U., François, F., Taylor, R.N.: An end-to-end industrial software traceability tool. In: Proceedings of the the 6th Joint Meeting of the European Software Engineering Conference and the ACM SIGSOFT Symposium on the Foundations of Software Engineering, pp. 115–124. ACM, Dubrovnik (2007)

    Google Scholar 

  24. Wang, Y.: Software engineering foundations: A software science perspective. AUERBACH (2008)

    Google Scholar 

  25. Forward, A.: Software Documentation–Building and Maintaining Artefacts of Communication (2002)

    Google Scholar 

  26. Ambler, S.W., Jeffries, R.: Agile modeling: effective practices for extreme programming and the unified process. Wiley, New York (2002)

    Google Scholar 

  27. Sulaiman, S., Idris, N.B., Sahibuddin, S.: Production and maintenance of system documentation: what, why, when and how tools should support the practice (2002)

    Google Scholar 

  28. Buckley, J., Mens, T., Zenger, M., Rashid, A., Kniesel, G.: Towards a taxonomy of software change. Journal of Software Maintenance and Evolution 17, 309–332 (2005)

    Article  Google Scholar 

  29. Asuncion, H., Taylor, R.N.: Establishing the Connection Between Software Traceability and Data Provenance (2007)

    Google Scholar 

  30. Azmi, A., Ibrahim, S., Mahrin, M.N.: A software traceability model to support software testing documentation. In: Proc. 10th IASTED International Conference on Software Engineering, pp. 152–159. IASTED, Innsbruck (2011)

    Google Scholar 

  31. da Cruz, J.L., Jino, M., Crespo, A.: PROMETEU-a tool to support documents generation and traceability in the test process (2003)

    Google Scholar 

  32. Valderas, P., Pelechano, V.: Introducing requirements traceability support in model-driven development of web applications. Information and Software Technology 51, 749–768 (2009)

    Article  Google Scholar 

Download references

Author information

Authors and Affiliations

  1. Advanced Informatics School (UTM AIS), Universiti Teknologi Malaysia, 54100, Kuala Lumpur, Malaysia

    Azri Azmi & Suhaimi Ibrahim

Authors
  1. Azri Azmi
    View author publications

    You can also search for this author in PubMed Google Scholar

  2. Suhaimi Ibrahim
    View author publications

    You can also search for this author in PubMed Google Scholar

Editor information

Editors and Affiliations

  1. LE2I, UMR, CNRS 5158, Faculté des Sciences BP 47870, Mirande, 9 , avenue Alain Savary, 21078, DIJON, France

    Hocine Cherifi

  2. Faculty of Computer Systems and Software Engineering, University Malaysia Pahang, Lebuhraya Tun Razak, 26300 Gambang, Kuantan, Pahang, Malaysia

    Jasni Mohamad Zain

  3. Information Systems Dept., Faculty of Computer and Information Science, King Saud University, 11543, Riyadh, Saudi Arabia

    Eyas El-Qawasmeh

Rights and permissions

Reprints and permissions

Copyright information

© 2011 Springer-Verlag Berlin Heidelberg

About this paper

Cite this paper

Azmi, A., Ibrahim, S. (2011). Test Management Traceability Model to Support Software Testing Documentation. In: Cherifi, H., Zain, J.M., El-Qawasmeh, E. (eds) Digital Information and Communication Technology and Its Applications. DICTAP 2011. Communications in Computer and Information Science, vol 167. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-22027-2_3

Download citation

  • DOI: https://doi.org/10.1007/978-3-642-22027-2_3

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-642-22026-5

  • Online ISBN: 978-3-642-22027-2

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics

Search

Navigation