Dimensions of Requirement Gathering
The requirement gathering is process of requirements discovery or generating list of requirements or collecting many requirements as possible by stakeholders. It is also called as requirements elicitation or requirement capture.
Various Dimensions of requirements gathering are:
Attention reader! Don’t stop learning now. Get hold of all the important CS Theory concepts for SDE interviews with the CS Theory Course at a student-friendly price and become industry ready.
- Stakeholders –
The stakeholder means person with interest or concern in outcome of project who is affected by system.
For example- end-user, system maintenance engineer or administrator, software developer, direct user, indirect user, senior manager, etc. By collecting requirements from these stakeholders, understanding system requirements can be very easy.
- Interviewing –
Interviewing is important and very effective method of requirement gathering. Different questions are being asked about system and its uses to stakeholders by team of requirement engineering so that identification of requirements can be done using these answers. There are two types of interviewers:
Interviewers are useful for understanding stakeholders but they are not much useful for understanding application domain.
- Use Case Modeling –
Use cases are fundamental units of modeling language, in which functionalities are distinctly presented. The use case is scenario-based technique. Individual interactions with system can be identified using or with help of Use case model. Using of use case model is extremely done for requirements gathering. Important system requirements can be traced or identified by designing proper use cases for different scenarios. In use cases, typical notations used are:
The use case for ATM system is as shown below:
- Facility Application Specification Technique (FAST) –
Facility Application Specification Technique is approach in which joint team of customers and developers work together to identify problem, propose elements of solution, negotiate different approaches and prepare specification for preliminary set of solutions requirements. Preparing- list of objects, list of services, and list of constraints are always asked each FAST attendee in every FAST meeting. Constraints of system such as cost, rules, memory requirement, speed accuracy, etc. are mentioned in list of constraints. As soon as FAST meeting begins, need and justification for new product is first issue that arises at point of discussion. Every participant has to present his lists once everyone agrees upon fact that product is justified.