Unstructured source artifacts ontology for requirement validation in GDSD

  • Abstract
  • Keywords
  • References
  • PDF
  • Abstract

    Analyst while transformation, may not capture true representation of user opinion thus creating deviation from actual user needs. Role of stakeholder is primary in both requirement elicitation and validation process. In elicitation stage they are initiator whereas in validation stage they are authenticator of their needs. Invalid requirements if verified may not be a deviation from specified behavior but deviation from user needs. Requirement validation process ensure that requirements should be representing all primary and intermediary artifacts as well a shared opinions of their contributors. This highlights the importance of source artifacts without which requirement validation cannot assured. Researchers didn’t propose any framework for requirement validation in context of GDSD in which source artifacts grows exponentially, and stakeholders are located in diversified locations. Due to unstructured nature of source artifacts, they are not electronically indexed and versioned controlled and this makes difficulty in preserving them. Requirement validation is not possible when source artifacts are not available along with their contributors. The major contribution of this paper to address problem of requirement validation in GDSD in absence of stakeholder to make it collocating environment. This paper introduced ontological solution of requirement validation in which target artifacts are validated against source artifact using their semantic relationship. This paper proposed an unstructured source artifact based ontological model for requirement validation in GDSD environment.

  • Keywords

    Pre-Requirement Specification Traceability Pre-RST, Globally Distributed Software Development GDSD, Requirement Validation, Requirement Artefacts.

  • References

      [1] Kof, Leonid, et al. "Ontology and Model Alignment as a Means for Requirements Validation." ICSC. 2010.

      [2] Dermeval, Diego, et al. "Applications of ontologies in requirements Engineering: a systematic review of the literature." Requirements Engineering (2015): 1-33.

      [3] Castañeda, Verónica, et al. "The use of ontologies in requirements engineering." Global journal of researches in engineering 10.6 (2010).

      [4] Castañeda, Verónica, Luciana C. Ballejos, and Maria Laura Caliusco. "Improving the Quality of Software Requirements Specifications with Semantic Web Technologies." WER. 2012.

      [5] Farfeleder, Stefan, et al. "Ontology-driven guidance for requirements elicitation."TheSemanic Web: Research and Applications. Springer Berlin Heidelberg, 2011. 222-226.

      [6] Decker, Björn, et al. "Self-organized reuse of software engineering knowledge supported by semantic wikis." Proceedings of the Workshop on Semantic Web Enabled Software Engineering (SWESE). 2005

      [7] Sommerville, Ian, and Gerald Kotonya. Requirements engineering: processes and techniques. John Wiley & Sons, Inc., 1998.

      [8] Westfall, Linda. "Software requirements engineering: what, why, who, when, and how." Software Quality Professional 7.4 (2005): 17.

      [9] Al Balushi, TaiseeraHazeem, Pedro R. Falcone Sampaio, and Pericles Loucopoulos. "Eliciting and prioritizing quality requirements supported by ontologies: a case study using the ElicitO framework and tool." Expert Systems30.2 (2013): 129-151.

      [10] Gotel, Orlena, et al. "Traceability fundamentals." Software and Systems Traceability. Springer London, 2012. 3-22.

      [11] Botzenhardt, Achim, Andreas Witt, and Alexander Maedche. "A Text Mining Application for Exploring the Voice of the Customer." AMCIS. 2011.

      [12] Sommerville, Ian, Peter Sawyer, and Stephen Viller. "Viewpoints for requirements elicitation: a practical approach." Requirements Engineering, 1998. Proceedings. 1998 Third International Conference on. IEEE, 1998.

      [13] Sutcliffe, Alistair G., et al. "Supporting scenario-based requirements engineering." Software Engineering, IEEE Transactions on 24.12 (1998): 1072-1088.

      [14] Maiden, Neil A. M. "CREWS-SAVRE: Scenarios for acquiring and validating requirements." Automated Software Engineering 5.4 (1998): 419-446.

      [15] Prakash, N., C. Rolland, and B. Pernici. "Use of domain knowledge for requirements validation." Information System Development Process: Proceedings of the IFIP WG8. 1 Working Conference on Information System Development Process, Como, Italy, 1-3 September, 1993. Elsevier, 2014.

      [16] Hallerstede, Stefan, Michael Jastram, and Lukas Ladenberger. "A method and tool for tracing requirements into specifications." Science of Computer Programming 82 (2014): 2-22.

      [17] Van Lamsweerde, Axel. "Goal-oriented requirements engineering: A guided tour." Requirements Engineering, 2001. Proceedings. Fifth IEEE International Symposium on. IEEE, 2001.

      [18] Fairley, Richard E. Managing and leading software projects. John Wiley & Sons, 2011

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

      [20] Yue, Tao, Lionel C. Briand, and Yvan Labiche. "A systematic review of transformation approaches between user requirements and analysis models."Requirements Engineering 16.2 (2011): 75-99.

      [21] Yang, Yanwu, et al. "Towards semantic requirement engineering." Semantic Computing and Systems, 2008. WSCS'08. IEEE International Workshop on. IEEE, 2008.

      [22] Meth, Hendrik, Manuel Brhel, and Alexander Maedche. "The state of the art in automated requirements elicitation." Information and Software Technology55.10 (2013): 1695-1709.

      [23] Damian, Daniela. "Stakeholders in global requirements engineering: Lessons learned from practice." Software, IEEE 24.2 (2007): 22-27.

      [24] Ambriola, Vincenzo, and Vincenzo Gervasi. "Processing natural language requirements." Automated Software Engineering, 1997. Proceedings., 12th IEEE International Conference. IEEE, 1997.

      [25] Christel, Michael G., David P. Wood, and Scott M. Stevens. AMORE; The Advanced Multimedia Organizer for Requirements Elicitation. No. CMU/SEI-93-TR-12. Carnegie-mellonunivpittsburgh pa software Engineering inst, 1993.

      [26] Konaté, Jacqueline, Abd El Kader Sahraoui, and Gwendolyn L. Kolfschoten. "Collaborative Requirements Elicitation: A Process-Centred Approach." Group Decision and Negotiation 23.4 (2014): 847-877.

      [27] Coulin, Chad Raymond. A situational approach and intelligent tool for collaborative requirements elicitation. Diss. Université Toulouse III-Paul Sabatier, 2007.

      [28] Davis, Alan M. Software requirements: objects, functions, and states. Prentice-Hall, Inc., 1993.

      [29] Cheng, Betty HC, and Joanne M. Atlee. "Research directions in requirements engineering." 2007 Future of Software Engineering. IEEE Computer Society, 2007.

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

      [31] IHMC: CmapTools web site. http://cmap.ihmc.us (June 2012)

      [32] Gall, Mark, and Brian Berenbach. "Towards a Framework for Real Time Requirements Elicitation." Multimedia Requirements Engineering, 2006. MERE'06. First International Workshop on. IEEE, 2006.

      [33] Antón, Annie, and Colin Potts. "The use of goals to surface requirements for evolving systems." Software Engineering, 1998. Proceedings of the 1998 International Conference on. IEEE, 1998.

      [34] Sutcliffe, Alistair. "Requirements rationales: integrating approaches to requirement analysis." Proceedings of the 1st conference on Designing interactive systems: processes, practices, methods, & techniques. ACM, 1995.

      [35] Gervasi, Vincenzo, and Bashar Nuseibeh. "Lightweight validation of natural language requirements." Software: Practice and Experience 32.2 (2002): 113-133.

      [36] Coulin, Chad Raymond. A situational approach and intelligent tool for collaborative requirements elicitation. Diss. Université Toulouse III-Paul Sabatier, 2007.

      [37] Stone, Andrew, and Peter Sawyer. "Using pre-requirements tracing to investigate requirements based on tactic knowledge." ICSOFT (1). 2006.

      [38] Syed, Zareen Saba, Tim Finin, and Anupam Joshi. "Wikitology: Using wikipedia as an ontology." Proc. the Second International Conf. on Weblogs and Social Media. 2008.

      [39] Omoronyia, Inah, et al. "A domain ontology building process for guiding requirements elicitation." Requirements Engineering: Foundation for Software Quality. Springer Berlin Heidelberg, 2010. 188

      [40] Dermeval, Diego, et al. "A systematic review on the use of ontologies in requirements engineering." Software Engineering (SBES), 2014 Brazilian Symposium on. IEEE, 2014.

      [41] Dobson, Glen, and Peter Sawyer. "Revisiting ontology-based requirements engineering in the age of the semantic web." Proceedings of the International Seminar on Dependable Requirements Engineering of Computerised Systems at NPPs. 2006.

      [42] Sutcliffe, Alistair, and Pete Sawyer. "Requirements elicitation: Towards the unknown unknowns." Requirements Engineering Conference (RE), 2013 21st IEEE International. IEEE, 2013.




Article ID: 10051
DOI: 10.14419/ijet.v7i2.5.10051

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