Verbal use case specifications for informal requirements elicitation

  • Authors:

  • Eliezer Kantorowitz

  • Affiliations:

  • Technion -- Israel Institute of Technology, Technion City, Haifa, Israel

  • Venue:
  • Proceedings of the 29th Annual European Conference on Cognitive Ergonomics
  • Year:
  • 2011

Quantified Score

Hi-index 0.00

Visualization

Abstract

Requirements elicitation is considered by some to be the most difficult and most critical phase of system development. Some of the most difficult to correct bugs are due to deficiencies in the requirement specifications. Requirements elicitation is basically an informal process where the insights of the stakeholders and end users are most useful. Dan Beery claims [1] that it is also useful to have persons that are not familiar with the problem domain in the requirement elicitation team. Such domain ignorant people may raise questions outside the train of thoughts of the domain experts. The requirements elicitation team need also computer scientists to evaluate the technical feasibility of the requirements. The team that elicits the requirements and specify the system may thus be composed of persons having very different backgrounds. A productive collaboration between such team members is in itself an interesting challenge.