Problems with requirements engineering
Requirements, seen by users as the uncomplicated bit of a new service development, are actually the most problematic aspect, and yet the time allocated is far less than for the other phases.
Tight timescales and tight budgets – both the result of constraints on the business – place pressures on the development team to deliver a service. The trouble is that without the due time to understand and define the requirements properly, the service that is delivered on time may not be the service that the business thought it was asking for.
Studies carried out into IT project failures tell a common story. Many of the projects and unsatisfactory IT services suggest the following conclusions:
These findings are particularly significant because the cost of correcting errors in requirements increases dramatically the later into the development lifecycle they are found.
One of the main problems with requirements engineering is the lack of detailed skill and overall understanding of the area when people use it. If accurately performed, the work can integrate requirements from numerous areas in a few questions.
Other typical problems with requirements have been identified as:
Another problem is an apparent inability on the part of the users to articulate clearly what it is they wish the service to do for them. Very often they are deterred from doing so because the nature of the requirement is explained in a straightforward statement.
220.127.116.11 Resolving requirements engineering problems
There are some participants that must take part in the requirements process. They represent three broad stakeholder groups:
The user community should be represented by the domain expert (or subject-matter expert) and end-users.