A Framework for Requirements Elicitation through Mixed-Initiative Dialogue
ICRE '98 Proceedings of the 3rd International Conference on Requirements Engineering: Putting Requirements Engineering to Practice
Requirements Elicitation Driven by Interviews: The Use of Viewpoints
IWSSD '96 Proceedings of the 8th International Workshop on Software Specification and Design
A study on the priority selection for information system project management model
ACOS'07 Proceedings of the 6th Conference on WSEAS International Conference on Applied Computer Science - Volume 6
Scenario generation with differential scenario
SEPADS'07 Proceedings of the 6th WSEAS International Conference on Software Engineering, Parallel and Distributed Systems
Personalized e-learning: a goal oriented approach
DIWEB'07 Proceedings of the 7th WSEAS international conference on Distance learning and web engineering
Communication gaps and requirements uncertainties in the information systems design
AIC'06 Proceedings of the 6th WSEAS International Conference on Applied Informatics and Communications
ACC'10 Proceedings of the 2010 international conference on Applied computing conference
| Hi-index | 0.00 |
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.