Dimensions of Requirement Gathering Last Updated : 17 Jul, 2020 Comments Improve Suggest changes Like Article Like Report 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: 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. Comment More infoAdvertise with us Next Article Dimensions of Requirement Gathering M madhurihammad Follow Improve Article Tags : Software Engineering Similar Reads Distribution Requirement Planning (DRP) Distribution Requirements Planning (DRP) is a method used to manage the distribution of products by calculating the quantities needed and the timing for delivery across various locations. It helps businesses ensure that the right products are available at the right places and times, optimizing inven 4 min read Importance of Requirement Gathering in Software Development Requirement gathering is a crucial phase in the software development process, as it lays the foundation for the entire project. Getting requirements is one of the most crucial phases in the software development process. The process of determining and specifying what a software system must be able to 10 min read Elements of the Requirements Model Requirements for a computer-based system can be seen in many different ways. Some software people argue that it's worth using a number of different modes of representation while others believe that it's best to select one mode of representation. The specific elements of the requirements model are de 3 min read Requirements Gathering - Introduction, Processes, Benefits and Tools In the world of software development, the success of a project relies heavily on a crucial yet often overlooked phase: Requirement Gathering. This initial stage acts as the foundation for the entire development life cycle, steering the course of the software and ultimately determining its success. L 15 min read Functional vs. Non Functional Requirements Requirements analysis is an essential process that enables the success of a system or software project to be assessed. Requirements are generally split into two types: Functional and Non-functional requirements. functional requirements define the specific behavior or functions of a system. In contra 6 min read Like