Performing requirements elicitation activities supported by quality ontologies

Taiseera Hazeem Al Balushi, Pedro R Falcone Sampaio, Divyesh Dabhi, Pericles Loucopoulos

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Abstract

The requirements elicitation phase is often regarded as the most critical stage of the entire software engineering effort with strong evidence suggesting that increasing the effectiveness of requirements analysts and reducing requirements elicitation errors may be the key to improve project outcomes and deliver high quality software This paper presents a requirements elicitation approach and associated tool aimed at empowering requirements analysts with a knowledge repository that helps in the process of capturing precise non-functional requirements specifications during elicitation interviews The approach is based on the application of functional and nonfunctional domain ontologies (quality ontologies) to underpin the elicitation activities We also discuss how the approach and tool are being used to effectively support the requirements elicitation stage of the new student intranet project of the University of Manchester (Manchester Unity Web Project).
Original languageEnglish
Title of host publication18th International Conference on Software Engineering and Knowledge Engineering, SEKE 2006|Int. Conf. Softw. Eng. Knowl. Eng., SEKE
Pages343-348
Number of pages5
Publication statusPublished - 2006
Event18th International Conference on Software Engineering and Knowledge Engineering, SEKE 2006 - San Francisco Bay, CA
Duration: 1 Jul 2006 → …

Conference

Conference18th International Conference on Software Engineering and Knowledge Engineering, SEKE 2006
CitySan Francisco Bay, CA
Period1/07/06 → …

Keywords

  • Non-functional requirements
  • Ontologies
  • Requirements elicitation
  • Requirements engineering

Fingerprint

Dive into the research topics of 'Performing requirements elicitation activities supported by quality ontologies'. Together they form a unique fingerprint.

Cite this