Ontology-Driven Guidance for Requirements Elicitation

Requirements managers aim at keeping their sets of requirements well-defined, consistent and up to date throughout a project's life cycle. Semantic web technologies have found many valuable applications in the field of requirements engineering, with most of them focusing on requirements analysis. However the usability of results originating from such requirements analyses strongly depends on the quality of the original requirements, which often are defined using natural language expressions without meaningful structures. In this work we present the prototypic implementation of a semantic guidance system used to assist requirements engineers with capturing requirements using a semiformal representation. The semantic guidance system uses concepts, relations and axioms of a domain ontology to provide a list of suggestions the requirements engineer can build on to define requirements. The semantic guidance system is evaluated based on a domain ontology and a set of requirements from the aerospace domain. The evaluation results show that the semantic guidance system effectively supports requirements engineers in defining well-structured requirements.

[1]  Hanan Hamed Elazhary REAS: An Interactive Semi-Automated System for Software Requirements Elicitation Assistance , 2010 .

[2]  Wan M. N. Wan-Kadir,et al.  Propagating Requirement Change into Software High Level Designs towards Resilient Software Evolution , 2009, 2009 16th Asia-Pacific Software Engineering Conference.

[3]  Jeremy Dick,et al.  Requirements Engineering , 2002, Springer International Publishing.

[4]  Ian Sommerville,et al.  Requirements Engineering: Processes and Techniques , 1998 .

[5]  J. Jackson A keyphrase based traceability scheme , 1991 .

[6]  Lora Aroyo,et al.  The Semantic Web: Research and Applications , 2009, Lecture Notes in Computer Science.

[7]  Atsushi Ohnishi,et al.  Automatic transformation of organization of software requirements specifications , 2010, 2010 Fourth International Conference on Research Challenges in Information Science (RCIS).

[8]  John Domingue,et al.  A Core Ontology for Business Process Analysis , 2008, ESWC.

[9]  Boris Motik,et al.  OWL 2 Web Ontology Language: Direct Semantics , 2009 .

[10]  Lawrence D. Pohlmann,et al.  Requirements By Collaboration , 2003 .

[11]  J. M. Singer,et al.  IEEE Recommended Practice for Software Requirements SpeciÞcations , 1993 .

[12]  Mark Neal,et al.  Why and how of requirements tracing , 1994, IEEE Software.

[13]  Hermann Kaindl,et al.  The missing link in requirements engineering , 1993, SOEN.

[14]  Erik Kamsties,et al.  Higher quality requirements specifications through natural language patterns , 2003, Proceedings 2003 Symposium on Security and Privacy.

[15]  Stefan Biffl,et al.  A Domain Ontology Building Process for Guiding Requirements Elicitation , 2010, REFSQ.

[16]  Haruhiko Kaiya,et al.  Ontology based requirements analysis: lightweight semantic processing approach , 2005, Fifth International Conference on Quality Software (QSIC'05).

[17]  Tor Stålhane,et al.  Ontology-guided requirements and safety analysis , 2010 .

[18]  Haruhiko Kaiya,et al.  A Supporting Tool for Requirements Elicitation Using a Domain Ontology , 2007, ICSOFT/ENASE.

[19]  Alexander Egyed,et al.  Identifying requirements conflicts and cooperation: how quality attributes and automated traceability can help , 2004, IEEE Software.

[20]  Olly Gotel,et al.  An analysis of the requirements traceability problem , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[21]  George S. Avrunin,et al.  User guidance for creating precise and accessible property specifications , 2006, SIGSOFT '06/FSE-14.