A Document-based Traceability Model: An Evaluation by Using Feature Analysis

Software traceability is one of the key quality factors in software development. However, many developers are still not putting enough effort and priority on traceability. In order to verify and validate the completeness and consistency with the requirement, traceability is crucial. This study aims to evaluate the developed traceability model and to compare it with other traceability model with respect to their abilities to support the test management. For this evaluation, the DESMET method will be used, and a feature analysis of the models will be conducted. The evaluation shows that each of the models has some strengths and some weaknesses. Based on the evaluation, it was found that the proposed model meets its expectations to support the test management and its traceability has achieved some promising output and remarkable understanding compared to existing models.

[1]  Matthias Jarke,et al.  Toward Reference Models of Requirements Traceability , 2001, IEEE Trans. Software Eng..

[2]  Aziz Deraman,et al.  Implementing a Document-based Requirements Traceability: A Case Study , 2005, IASTED Conf. on Software Engineering.

[3]  Shihong Huang,et al.  Towards a documentation maturity model , 2003, SIGDOC '03.

[4]  Suhaimi Ibrahim,et al.  Software Maintenance Testing Approaches to Support Test Case Changes - A Review , 2011, DICTAP.

[5]  Laurie A. Williams,et al.  Validating software metrics: A spectrum of philosophies , 2012, TSEM.

[6]  Stefan Wind,et al.  Test Management Framework for Managing IT Projects in Industry , 2013, 2013 IEEE 10th International Conference on e-Business Engineering.

[7]  Henrik Hedberg,et al.  A preliminary evaluation of software inspection tools, with the DESMET method , 2005, Fifth International Conference on Quality Software (QSIC'05).

[8]  Andrew J. Kornecki,et al.  Experimental evaluation of software development tools for safety-critical real-time systems , 2005, Innovations in Systems and Software Engineering.

[9]  Scott R. Tilley,et al.  Documentation for software engineers: what is needed to aid system understanding? , 2001, SIGDOC '01.

[10]  Barbara Kitchenham,et al.  DESMET: a methodology for evaluating software engineering methods and tools , 1997 .

[11]  Sigrid Eldh,et al.  Towards Fully Automated Test Management for Large Complex Systems , 2010, 2010 Third International Conference on Software Testing, Verification and Validation.

[12]  Richard N. Taylor,et al.  An end-to-end industrial software traceability tool , 2007, ESEC-FSE '07.

[13]  Francisca Losavio,et al.  Feature analysis for architectural evaluation methods , 2006, J. Syst. Softw..

[14]  Suhaimi Ibrahim,et al.  IMPLEMENTING TEST MANAGEMENT TRACEABILITY MODEL TO SUPPORT TEST DOCUMENTS , 2011 .

[15]  Vassilka Kirova,et al.  Effective requirements traceability: Models, tools, and practices , 2008, Bell Labs Technical Journal.

[16]  Pearl Brereton,et al.  Tools to support systematic reviews in software engineering: a feature analysis , 2014, EASE '14.

[17]  Pearl Brereton,et al.  Tools to support systematic reviews in software engineering: a cross-domain survey using semi-structured interviews , 2015, EASE.

[18]  B. Paech,et al.  Criteria for Software Testing Tool Evaluation – A Task Oriented View , 2005 .

[19]  Ahmed M. Salem.  Improving Software Quality through Requirements Traceability Models , 2006, IEEE International Conference on Computer Systems and Applications, 2006..

[20]  Roslina Mohd Sidek,et al.  The Preferable Test Documentation Using IEEE 829 , 2011, ICSECS.

[21]  Lei Gao.  Research on implementation of software test management , 2011, 2011 3rd International Conference on Computer Research and Development.