Popular in Course
verified elite notetaker
Popular in Department
This 3 page One Day of Notes was uploaded by Gaurav Mandilwar on Monday September 8, 2014. The One Day of Notes belongs to a course at a university taught by a professor in Fall. Since its upload, it has received 75 views.
Reviews for Requirementgathering.pdf
Report this Material
What is Karma?
Karma is the currency of StudySoup.
You can buy or earn more Karma at anytime and redeem it for class notes, study guides, flashcards, and more!
Date Created: 09/08/14
Name Mandilwar Gaurav Somendra Requirement gathering What is requirement gathering Gathering information from all the relevant sources which is pertaining towards the project objective is called requirement gathering or requirement elicitation Benefits of requirement gathering 1 2 3 Avoiding rework thus saving time and effort Setting clear project expectations ie scoping Improves quality and saves time in all the project phases namely planning design development testing and delivery Steps before requirement gathering 39gtS quotquot Identify all project stakeholders What information regarding previous experience can be brought to light What are the drawbacks of the existing system Are the processes and tools in place in order to document communicate and manage requirements How will changes be managed Result and objective of requirement gathering A statement of requirement needs to be developed by the end of the process which clearly defines the following Uquot39gtS quot A succinct requirement specification for management purposes A clearly stated scope of the project A statement of key objectives a cardinal points specification within the scope of the project A description of the environment in which the system will work Information on major design and technical constraints The content of this document should be stable or changed less frequently All stakeholders should agree upon and signup for this document and understand that project will strictly adhere to the statement of requirement also called as the Business Requirement Document BRD Types of requirement gathering techniques and their pros amp cons Forms of Requirement Gathering one to one 1 interview Group 2 interviews 3 Delphi Brain 4 Storming 5 Prototyping Definition BA interviews a single person Open ended followed by closed ended questions are asked BA interviews 3 5 people at a time Consensus is achieved through iterative group questionnaires and forecasting Experts discuss over the subject matter in an orderly fashion Ideas are proposed and consensus is achieved A model of the requirement is created and it is presented to the stakeholders Post demo session further changes are suggested and thus iteratively a final result is achieved Usage to get in depth knowledge about requirement quick requirement gathering with multiple viewpoints can be achieved The group alters its decision by analyzing the results from the last questionnaire When solutions and consensus needs to be achieved quickly on spot It is used when the requirement is unclear Pros stake holder is one person management is easier Time Saver as compared to one to one interviews Consensus can be achieved with people in distant locations Consensus or extreme divergence among the group can be measured Multiple solutions and ideas can be proposed Consensus can be achieved on spot Hence this method helps in quick decision making Helps in the gradual growth in requirement Also some development activity also carries on Cons Post Interview work is crucial It is time consuming Members of the group ideally should be of the same role They should be focused as GD can go Haywire easily Time consuming Requires written communication skills on the part of the group members Strictly needs to be conducted in an orderly fashion Time consuming risky if the investment for building the prototype is high Also chances of the module being scrapped is high due to uncertainty This method is followed after a development of a prototype The group is used to collect Focused Groupfeedbacks on the developed solution The focused group is generally outside of the project team Used to collect Helps in collecting feedbacks feedback and Expensive to execute regarding the improve the Not suited for in depth developed solution Also used analysis of issues at solution from the for comparing hand sample user solutions
Are you sure you want to buy this material for
You're already Subscribed!
Looks like you've already subscribed to StudySoup, you won't need to purchase another subscription to get this material. To access this material simply click 'View Full Document'