Research Article

Toward Requirements and Design Traceability Using Natural Language Processing

Omer Salih Dawood
College of Computer Science and Information Technology Sudan University of Science and Technology, Khartum, Sudan
* Corresponding author
Abd-El-Kader Sahraoui
LAAS-CNRS, Université de Toulouse, CNRS, UT2J, Toulouse, France.
DOI icon 10.24018/ejeng.2018.3.7.807

Read Counter
1362

Downloads
885

Citations

Share

Article Sidebar

Submitted 2018-07-02
Published 2018-07-31

Read counter = 1362 times

Table of Contents

Article Main Content

The paper aimed to address the problem of incompleteness and inconsistency between requirements and design stages, and how to make efficient linking between these stages. Software requirements written in natural languages (NL), Natural Language Processing (NLP) can be used to process requirements. In our research we built a framework that can be used to generate design diagrams from requirements in semi-automatic way, and make traceability between requirements and design phases, and in contrast. Also framework shows how to manage traceability in different levels, and how to apply changes to different artifacts. Many traceability reports can be generated based on developed framework. After Appling this model we obtained good results. Based on our case study the model generate a class diagram depends on central rule engine, and traceability was built and can be managed in visualize manner. We proposed to continue this research as its very critical area by adding more Unified Modeling Language(UML) diagrams, and apply changes directly inside software requirement document.

Keywords: Requirement Engineering Requirement Management NLP Requirement Traceability UML Software Design

References

  1. Satyarthi, Sandhya, and Dhirendra Pandey. "Framework for Requirement Management using Requirement Traceability." International Journal of Advanced Research in Computer Science 8, no. 5 (2017).
     Google Scholar
  2. Pinheiro, Francisco AC. "Requirements traceability." In Perspectives on software requirements, pp. 91-113. Springer, Boston, MA, 2004.
     Google Scholar
  3. Ian. “Requirements Engineering Processes”. ”Software Engineering”. ”lecture notes”.”Chapter 7”
     Google Scholar
  4. Kok, H. M. R. "Tracing Requirements in an Insurance Software Development Company." Master's thesis, 2016.
     Google Scholar
  5. Nicolas Sannier.”Requirements Prioritization Requirements Management Requirements Traceability and Variability”.”lecture notes”
     Google Scholar
  6. “CDC unified process practice guide requirements traceability”.2006.[online] https://www2.cdc.gov/cdcup/library/practices_guides/CDC_UP_Requirements_Definition_Practices_Guide.pdf
     Google Scholar
  7. Winkler, Stefan, and Jens von Pilgrim. "A survey of traceability in requirements engineering and model-driven development." Software & Systems Modeling 9, no. 4 (2010): 529-565.
     Google Scholar
  8. Min, Hyun-Seok. "Traceability Guideline for Software Requirements and UML Design." International Journal of Software Engineering and Knowledge Engineering 26, no. 01 (2016): 87-113.
     Google Scholar
  9. Linda Westfall.” Bidirectional Requirements Traceability”.2006
     Google Scholar
  10. Gotel, Orlena CZ, and C. W. Finkelstein. "An analysis of the requirements traceability problem." In Requirements Engineering, 1994., Proceedings of the First International Conference on, pp. 94-101. IEEE, 1994.
     Google Scholar
  11. Williams, Jeandre Charisse. "A case study of pre-requirements specification traceability practices in a retail environment." PhD diss., University of Cape Town, 2015.
     Google Scholar
  12. Requirements traceability. https://en.wikipedia.org/wiki/Requirements_traceability#Usage_of_traceability_information .2018
     Google Scholar
  13. Li, Yang, and Walid Maalej. "Which traceability visualization is suitable in this context? a comparative study." In International Working Conference on Requirements Engineering: Foundation for Software Quality, pp. 194-210. Springer, Berlin, Heidelberg, 2012.
     Google Scholar
  14. Haidrar, Saida, Adil Anwar, and Ounsa Roudies. "Towards a generic framework for requirements traceability management for SysML language." In Information Science and Technology (CiSt), 2016 4th IEEE International Colloquium on, pp. 210-215. IEEE, 2016.
     Google Scholar
  15. Wolfenstetter, Thomas, Kathrin Füller, Markus Böhm, Helmut Krcmar, and Simon Bründl. "Towards a requirements traceability reference model for Product Service Systems." In Industrial Engineering and Systems Management (IESM), 2015 International Conference on, pp. 1213-1220. IEEE, 2015.
     Google Scholar
  16. Kaufmann, Andreas, and Dirk Riehle. "Improving traceability of requirements through qualitative data analysis." Software-engineering and management 2015 (2015).
     Google Scholar
  17. Jirapanthong, Waraporn. "Requirements traceability on web applications." In Information Technology and Electrical Engineering (ICITEE), 2015 7th International Conference on, pp. 18-23. IEEE, 2015.
     Google Scholar
  18. Ishibashi, Shota, Kenji Hisazumi, Tsuneo Nakanishi, and Akira Fukuda. "Establishing traceability between requirements, design and operation information in lifecycle-oriented architecture." In Advanced Applied Informatics (IIAI-AAI), 2016 5th IIAI International Congress on, pp. 234-239. IEEE, 2016.
     Google Scholar
  19. Plataniotis, Georgios, Qin Ma, Erik Proper, and Sybren de Kinderen. "Traceability and modeling of requirements in enterprise architecture from a design rationale perspective." In Research Challenges in Information Science (RCIS), 2015 IEEE 9th International Conference on, pp. 518-519. IEEE, 2015.
     Google Scholar
  20. Satyarthi, Sandhya, and Dhirendra Pandey. "Framework for Requirement Management using Requirement Traceability." International Journal of Advanced Research in Computer Science 8, no. 5 (2017).
     Google Scholar
  21. Duarte, Ana Marcia Debiasi, Denio Duarte, and Marcello Thiry. "TraceBoK: Toward a software requirements traceability body of knowledge." In Requirements Engineering Conference (RE), 2016 IEEE 24th International, pp. 236-245. IEEE, 2016.
     Google Scholar
  22. Alsalemi, Ahmed Mubark, and Eng-Thiam Yeoh. "A survey on product backlog change management and requirement traceability in agile (Scrum)." In Software Engineering Conference (MySEC), 2015 9th Malaysian, pp. 189-194. IEEE, 2015.
     Google Scholar
  23. Shinde, Subhash K., Varunakshi Bhojane, and Pranita Mahajan. "Nlp based object oriented analysis and design from requirement specification." International Journal of Computer Applications 47, no. 21 (2012).
     Google Scholar
  24. Arellano, Andres, Edward Carney, and Mark A. Austin. "Natural language processing of textual requirements." In The Tenth International Conference on Systems (ICONS 2015), Barcelona, Spain, pp. 93-97. 2015.
     Google Scholar
  25. “Traceability Analysis”. http://www.chambers.com.au/glossary/traceability_analysis.php
     Google Scholar
  26. Paul Nelson . “Natural Language Processing (NLP) Techniques for Extracting Information” Available: https://www.searchtechnologies.com/blog/natural-language-processing-techniques . 2018
     Google Scholar
  27. Agarwal, Renuka, Rajiv R. Chetwani, M. Ravindra, and K. M. Bharadwaj. "Novel methodology for requirements to design traceability of onboard software." In Advances in Electronics, Computers and Communications (ICAECC), 2014 International Conference on, pp. 1-6. IEEE, 2014.
     Google Scholar
  28. Turban, Bernhard, Markus Kucera, Athanassios Tsakpinis, and Christian Wolff. "Bridging the requirements to design traceability gap." In Intelligent Technical Systems, pp. 275-288. Springer, Dordrecht, 2009.
     Google Scholar
  29. “Analysis and designing of the automated mobile money
     Google Scholar
  30. transfer syste”, chapter 5. Available:
     Google Scholar
  31. http://dl.lib.mrt.ac.lk/bitstream/handle/123/1785/Chapter05.pdf?sequence=5
     Google Scholar