Managing implicit requirements using semantic case-based reasoning research preview

  • Authors:

  • Olawande Daramola;Thomas Moser;Guttorm Sindre;Stefan Biffl

  • Affiliations:

  • Department of Computer and Information Science, Norwegian University of Science and Technology, Trondheim, Norway;Christian Doppler Laboratory for Software Engineering, Integration for Flexible Automation Systems, Vienna University of Technology, Austria;Department of Computer and Information Science, Norwegian University of Science and Technology, Trondheim, Norway;Christian Doppler Laboratory for Software Engineering, Integration for Flexible Automation Systems, Vienna University of Technology, Austria

  • Venue:
  • REFSQ'12 Proceedings of the 18th international conference on Requirements Engineering: foundation for software quality
  • Year:
  • 2012

Quantified Score

Hi-index 0.00

Visualization

Abstract

[Context and motivation] Implicit requirements (ImRs) are defined as requirements of a system which are not explicitly expressed during requirements elicitation, often because they are considered so basic that developers should already know them. Many products have been rejected or users made unhappy because implicit requirements were not sufficiently addressed. [Question/Problem] Requirement management tools have not addressed the issue of managing ImRs, also despite the challenges of managing ImRs that exist in practice the issue has not received sufficient attention in the literature. [Principal Idea/results] This planned research will investigate how automated support can be provided for managing ImRs within an organizational context, which is currently lacking in practice. This work proposed an approach that is based on semantic case-based reasoning for managing ImRs. [Contribution] We present the concept of a tool which enables managing of ImRs through the analogy-based requirements reuse of previously known ImRs. This ensures the discovery, structured documentation, proper prioritization, and evolution of ImRs, which improves the overall success of software development processes.