Browse > Article
http://dx.doi.org/10.7472/jksii.2021.22.3.59

Visualization models for tracking software requirements and managing their changes  

Song, YooRi (Department of Computer Science & Engineering, Chungnam National University)
Kim, Hyeon Soo (Department of Computer Science & Engineering, Chungnam National University)
Publication Information
Journal of Internet Computing and Services / v.22, no.3, 2021 , pp. 59-66 More about this Journal
Abstract
This study proposes a requirements monitoring method that systematically performs traceability management and change management for requirements in order to improve the quality of software systems in the software development process. To this end, we present the artifact change history management models to systematically perform change management for individual artifacts and the traceability matrixes to define the relationship between artifacts. It also proposes a visual dashboard that makes it easy to grasp the situation in which changes are propagated to related artifacts when specific artifacts change.
Keywords
Software Requirement; Traceability; Software Change Management; Visualization Model;
Citations & Related Records
연도 인용수 순위
  • Reference
1 P. Mader and A. Egyed, "Do developers benefit from requirements traceability when evolving and maintaining a software system?" Empirical Software Engineering, Vol. 20, pp. 413-441, 2015. https://doi.org/10.1007/s10664-014-9314-z   DOI
2 J. Y. Kim, et. al., "A study of requirement change management and traceability effect using traceability table," The KIPS Transactions: Part D, Vol. 17, No. 4, pp.271-282, 2010. https://doi.org/10.3745/KIPSTD.2010.17D.4.271   DOI
3 J. C. Huang, C. K. Chang, and M. Christensen, "Event-based traceability for managing evolutionary change," IEEE Transactions on Software Engineering, Vol. 29, No. 9, pp. 796-810, 2003. http://dx.doi.org/10.1109/TSE.2003.1232285   DOI
4 M. Rahimi, and J. C. Huang, "Evolving software trace links between requirements and source code," Empirical Software Engineering, Vol. 23, pp. 2198-2231, 2018. https://doi.org/10.1007/s10664-017-9561-x   DOI
5 Jama Software White Paper, "Better Product Development: Five Tips for Traceability," https://resources.jamasoftware.com/whitepaper/better-product-development-five-tips-for-traceability
6 D. Baek, B. Lee, and J. W. Lee, "Content-based configuration management system for software research and development document artifacts," KSII Transactions on Internet and Information Systems, Vol. 10, No. 3, pp. 1404-1415, 2016. http://dx.doi.org/10.3837/tiis.2016.03.027   DOI
7 K. Mohan, P. Xu, L. Cao, and B. Ramesh "Improving change management in software development: Integrating traceability and software configuration management," Decision Support Systems, Vol. 45, Issue 4, pp. 922-936, 2008. https://doi.org/10.1016/j.dss.2008.03.003   DOI
8 E. Y. Byun, et. al., "Requirement traceability matrix based on closed architecture mechanism," Proc. of KIPS 2017 Fall Conference, Vol. 24, No. 2, pp. 631-634, 2017. https://doi.org/10.3745/PKIPS.y2017m11a.631   DOI
9 IBM Rational DOORS V9.6.0 Document, https://www.ibm.com/support/knowledgecenter/ko/SSYQBZ_9.6.0/com.ibm.doors.requirements.doc/topics/c_welcome.html