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 a customer and software engineer (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 would like to suggest a structure to guide requirements elicitation work through interviews in order for SEs to extract customer requirements without omissions or errors by using interview skills. Furthermore, we conducted comparative experiments in regards to the cases of conducting requirements elicitation work by using and not using this structure. As a result, we found that customer requirements were extracted without omissions or errors with the structure proposed in this paper, and successfully verified the effectiveness.
