The business requirements for large IT projects are inevitably hard to define. Users may not be able to easily articulate their needs, and different teams may have different perceptions of the way processes should work. What is more, the introduction of new business systems is often the catalyst for business process change. But getting it right is essential. The requirements definition not only provides the roadmap for the software development team, but also creates a framework for effective quality assurance and testing. If the requirements are incomplete or ambiguous, problems will occur later in the project that will be costly to resolve.