Software engineering
- 1. SOFTWARE ENGINEERING Eliciting Requirements,Developing Use Cases BY R.RENUKA
- 2. ELICITING REQUIREMENTS Eliciting Requirements Eliciting requirement helps the user for collecting the requirement. Eliciting requirement steps are as follows: 1. Collaborative requirements gathering 2. Quality Function Deployment (QFD) QFD consist of three types of requirement: * Normal requirements *Expected requirement *Exciting requirements 3. Usage scenarios 4. Elicitation work product
- 3. 1. Collaborative requirements gathering Gathering the requirements by conducting the meetings between developer and customer. Fix the rules for preparation and participation. The main motive 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.
- 4. 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.
- 5. Expected requirement 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.
- 6. 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'.
- 7. 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.