Visualization representing benefits of pre-requirement specification traceability

 
 
 
  • Abstract
  • Keywords
  • References
  • PDF
  • Abstract


    Representation of Pre-RST information is very useful using visualized elements for realization of benefits of requirement traceability. This improves the practitioner motivation to maintain Pre-RST information during life cycle processes. Few researchers proposed visualization for Post-RST due to which many benefits of requirement traceability cannot be realized. This paper proposed an improved visualization representing Pre-RST information that demonstrates various benefit of requirement traceability. In order to evaluate empirically, an experiment is conducted and textual representation of traceability information is obtained. In order to strengthen our claim a survey is conducted to compare textual representation of traceability information with proposed visualization and results are compiled.


  • Keywords


    Pre-Requirement Specification Traceability Pre-RST, Requirement Traceability, Software Requirement Specification SRS, Benefit of Tracea-bility, Requirement Visualization, Value Based Traceability

  • References


      [1] Oxford English Dictionary, 1989

      [2] Gotel, Orlena CZ, Francis T. Marchese, and Stephen J. Morris. "On requirements visualization." Requirements Engineering Visualization,

      [3] 2007. REV 2007. Second International Workshop on. IEEE, 2007. Cleland-Huang, Jane, and RafalHabrat. "Visual support in automated tracing."Requirements Engineering Visualization, 2007. REV 2007. Second International Workshop on. IEEE, 2007.

      [4] Walia, Gursimran Singh, and Jeffrey C. Carver. "A systematic literature review to identify and classify software requirement errors." Information and Software Technology 2009. 1087-1109.

      [5] Martin, Sacha, et al. "Requirements engineering process models in practice."7th Australian workshop on requirements engineering.Deakin University, Melbourne, Australia. 2002.

      [6] Faily, Shamal, et al. "Requirements sensemaking using concept maps."Human-Centered Software Engineering. Springer Berlin Heidelberg, 2012. 217-232.

      [7] Gotel, Orlena, and Anthony Finkelstein. "Extended requirements traceability: results of an industrial case study." Requirements Engineering, 1997

      [8] Pohl, Klaus. "PRO-ART: Enabling requirements pre-traceability." Requirements Engineering, 1996, Proceedings of the Second International Conference on. IEEE, 1996.

      [9] Chikh, Azeddine, and MashaelAldayel. "Reengineering Requirements Specification Based on IEEE 830 Standard and Traceability." NewPerspectives in Information Systems and Technologies, Volume 1.Springer International Publishing, 2014. 211-227.

      [10] Gough, Paul A., et al. "Scenarios-an industrial case study and hypermedia enhancements." Requirements Engineering, 1995.Proceedings of the Second IEEE International Symposium on. IEEE

      [11] Arkley, Paul, and Steve Riddle. "Overcoming the traceability benefit problem."Requirements Engineering, 2005. Proceedings. 13th IEEE. International Conference on. IEEE, 2005.

      [12] Arkley, Paul, Paul Mason, and Steve Riddle. "Position paper: Enabling traceability." Proceedings of the 1st International Workshop on Traceability in Emerging Forms of Software Engineering, Edinburgh, Scotland (September 2002). 2002.

      [13] https://codebeamer.com/

      [14] Pohl, Klaus. "PRO-ART: Enabling requirements pre-traceability." Requirements Engineering, 1996, Proceedings of the Second International Conference on. IEEE, 1996

      [15] Cleland-Huang, Jane, Grant Zemont, and Wiktor Lukasik. "A heterogeneous solution for improving the return on investment of requirements traceability."Requirements Engineering Conference, 2004. Proceedings. 12th IEEE International. IEEE, 2004.

      [16] Gotel, Orlena CZ, and Anthony CW Finkelstein. "An analysis of the requirements traceability problem." Requirements Engineering, 1994., Proceedings of the First International Conference on. IEEE, 1994.

      [17] Gotel, Orlena, and Anthony Finkelstein. "Contribution structures [Requirements artifacts]." Requirements Engineering, 1995., Proceedings of the Second IEEE International Symposium on. IEEE, 1995.

      [18] Merten, Thorsten, Daniela Jüppner, and Alexander Delater. "Improved representation of traceability links in requirements engineering knowledge using Sunburst and Netmap visualizations." Managing Requirements Knowledge (MARK), 2011 Fourth International Workshop on. IEEE, 2011.

      [19] Ernst, Neil, Yijun Yu, and John Mylopoulos. "Visualizing non-functional requirements." Requirements Engineering Visualization, 2006. REV'06. First International Workshop on. IEEE, 2006.

      [20] Marcus, Andrian, XinrongXie, and Denys Poshyvanyk. "When and how to visualize traceability links?." Proceedings of the 3rd international workshop on Traceability in emerging forms of software engineering. ACM, 2005.

      [21] Cleland-Huang, Jane, et al. "Utilizing supporting evidence to improve dynamic requirements traceability." Requirements Engineering, 2005. Proceedings. 13th IEEE International Conference on. IEEE, 2005. [22] Aizenbud-Reshef, Neta, et al. "Model traceability." IBM Systems Journal 45.3 (2006): 515-526.

      [22] Pichler, Mario, and Hildegard Rumetshofer. "Business process-based requirements modeling and management." Requirements Engineering Visualization, 2006. REV'06. First International Workshop on. IEEE, 2006.

      [23] Schneider, Florian, Helmut Naughton, and Brian Berenbach. "A modeling language to support early lifecycle requirements modeling for systems engineering." Procedia Computer Science 8 (2012): 201-206.

      [24] Wnuk, Krzysztof, Björn Regnell, and Lena Karlsson. "What happened to our features? Visualization and understanding of scope change dynamics in a large-scale industrial setting." Requirements Engineering Conference, 2009. RE'09. 17th IEEE International. IEEE, 2009.

      [25] Herrmann, Korbinian. "Visualization of release planning." Requirements Engineering Visualization, 2006. REV'06. First International Workshop on. IEEE, 2006

      [26] Eppler, Martin J., and Ken W. Platts. "Visual strategizing: the systematic use of visualization in the strategic-planning process." Long Range Planning42.1 (2009): 42-74.

      [27] Cleland-Huang, Jane. "Toward improved traceability of non-functional requirements." Proceedings of the 3rd international workshop on Traceability in emerging forms of software engineering. ACM, 2005. [29] Asuncion, Hazeline U., Arthur U. Asuncion, and Richard N. Taylor. "Software traceability with topic modeling." Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering-Volume 1. ACM, 2010.

      [28] Decker, Björn, et al. "Wiki-based stakeholder participation in requirements engineering." Software, IEEE 24.2 (2007): 28-35

      [29] DOORS, Web Page: Dynamic Object Oriented Requirements System, http://www.telelogic.com/doors.

      [30] www.ibm.com/software/products/en/ratidoor

      [31] IEEE Computer Society. Software Engineering Standards Committee, and IEEE-SA Standards Board. "IEEE Recommended Practice for Software Requirements Specifications." Institute of Electrical and Electronics Engineers, 1998.

      [32] Ramesh, Balasubramaniam, and Matthias Jarke. "Toward reference models for requirements traceability." Software Engineering, IEEE Transactions on27.1 (2001): 58-93.

      [33] Nair, Sunil, Jose Luis de la Vara, and Sagar Sen. "A review of traceability research at the requirements engineering conference re@21." Requirements Engineering Conference (RE), 2013 21st IEEE International. IEEE, 2013.

      [34] Geisser, Michael, et al. "New Applications for Wikis in Software Engineering." PRIMIUM. 2008.

      [35] www.sei.cmu.edu

      [36] Process Traceability-Systematic Review, Nitin, Vivekanand S Gogi, Dr. N S Narahari, International Journal of Innovative Research inScience, Engineering and Technology

      [37] Center of Excellence for Software Traceability, www.coest.org

      [38] Ko, Youngjoong, Sooyong Park, and JungyunSeo. "Web-based requirements elicitation supporting system using requirements

      [39] categorization." Proceedings of Twelfth International Conference on Software Engineering and Knowledge Engineering (SEKE 2000),Chicago, USA. 2000.

      [40] Walia, Gursimran Singh, and Jeffrey C. Carver. "A systematic Literature review to identify and classify software requirementerrors." Information and Software Technology 51.7 (2009). 1087-1109.

      [41] http://www.standishgroup.com/

      [42] Mäder, Patrick, and Alexander Egyed. "Do developers benefit from requirements traceability when evolving and maintaining a software system?." Empirical Software Engineering (2014): 1-29.

      [43] ISO (2011) ISO:26262-6:2011 Road vehicles - functional safety - part 6: Product development at the software level

      [44] RTCA / EUROCAE.“Software Considerations in Airborne Systems and Equipment Certification”, DO- 178C/ED-12C, (2011).

      [45] Ahmad, Arslan, and Muhammad Ahmad Ghazali. "Documenting requirements traceability information for small projects." Multitopic Conference, 2007. INMIC 2007. IEEE International. IEEE, 2007.

      [46] Bouillon, Elke, Patrick Mäder, and Ilka Philippow. "A survey on usage scenarios for requirements traceability in practice." Requirements Engineering: Foundation for Software Quality. Springer Berlin Heidelberg, 2013. 158-173.

      [47] Gotel, Orlena, and Patrick Mäder. "Acquiring tool support for traceability."Software and Systems Traceability. Springer London, 2012. 43-68.

      [48] Rempel, Patrick, et al. "Mind the gap: assessing the conformance of software traceability to relevant guidelines." Proceedings of the 36th International Conference on Software Engineering. ACM, 2014.


 

View

Download

Article ID: 10052
 
DOI: 10.14419/ijet.v7i2.5.10052




Copyright © 2012-2015 Science Publishing Corporation Inc. All rights reserved.