A proposal of a method to navigate interview-driven software requirements elicitation work

Abstract:- System development for software is in accordance with requirements specification. Omissions or errors in requirements specification cause omissions or errors in subsequent deliverables. Therefore, requirements elicitation work in order to prepare requirements specification is a very important process. However, it is very difficult to extract customer requirements for software development without omissions or errors, mainly because customers and software engineers (SE) do not share common knowledge resulting in omissions or errors in the requirements elicitation work due to poor mutual communication. Therefore, in this paper we are proposing a structure to navigate requirements elicitation work through interviews in order for SEs to elicit customer requirements without omissions or errors by using the interview technique. We are also conducting a comparative experiment in regards to the cases that requirements elicitation work is conducted by both utilizing and not utilizing this structure. As a result, we were better able to elicit customer requirements without omissions or errors in the case of the former rather than the latter; therefore we successfully verified that the structure proposed in this paper by utilizing this structure is effective.