Abstract
Software development projects sometimes face a lot of requirement changes after requirements specifications are produced. Even though requirements changes sometimes cause the overrun of the project schedule, we must accept those requirements changes during the project. Our research has started with the intention not to miss the adequate timing to elicit requirements. In this context, requirements elicitation includes eliciting new requirements and changing requirements. We regard all these activities as necessary development activities for the project success. This paper focuses on a real project which was completed within the scheduled term. When the development was in progress, the engineers elicited requirements and changed requirements. We report and discuss that the risks avoidance in the project depend on the process of requirements elicitation.
