Eliciting Requirements

Eliciting Requirements is helpful to create scenarios that identify a thread of usage for the system to be constructed. These scenarios are often called use cases. The use cases tell a story about how an end user interacts with the system under a specific set of circumstances. Eliciting requirement steps are as follows :

1. Collaborative requirements gathering :  Requirements are gathered by conducting the meetings between developer and customer. and also need to fix the rules for preparation and participation. The main motive of Collaborative requirements gathering is to identify the problem, give the solutions  for the elements, negotiate the different approaches  and specify the primary set of solution requirements in an environment which is valuable for achieving goal.

2. Quality Function Deployment (QFD) : In this technique, translate the customer need into the technical requirement for the software. QFD system designs a software according to the demands of the customer. QFD consist of three types of requirement :

  • Normal requirements : The objective and goal are stated for the system through the meetings with the customer. For the customer satisfaction these requirements should be there.
  • Expected requirements : These requirements are implicit. These are the basic requirement that not be clearly told by the customer, but also the customer expect that requirement.
  • Exciting requirements : These features are beyond the expectation of the customer. The developer adds some additional features or unexpected feature into the software to make the customer more satisfied. For example, the mobile phone with standard features, but the developer adds few additional functionalities like voice searching, multi-touch screen etc. then the customer more exited about that feature.

3. Usage Scenarios : Till the software team does not understand how the features and function are used by the end users it is difficult to move technical activities. To achieve above problem the software team produces a set of structure that identify the usage for the software. This structure is called as 'Use Cases'.

4. Elicitation work product : The work product created as a result of requirement elicitation that is depending on the size of the system or product to be  built. The work product consists of a statement need, feasibility, statement scope for the system. It also consists of a list of users participate in the requirement elicitation.

Next Topic :

No comments:

Post a Comment