Please enable JavaScript.
Coggle requires JavaScript to display documents.
TECHNIQUES OF REQUIREMENTS GATHERING, ISSUES IN REQUIREMENTS GATHERING -…
TECHNIQUES OF REQUIREMENTS
GATHERING
Interview
unstructured
interviewer ask questions and require detail answer
some topic may be neglected
structured
are conducted where domain is specified
specific questions are asked and get to the point
answer
interviewer conduct a meeting with interviewee
semi structured
where elementary usual of the
question is organized and used.
questions should be according to the interviewee’s level
open ended
Questionnaires
questions are listed in paper.
Questions are filled by the stakeholders and get the answer
of these questions.
stakeholders cannot express their idea
focused on the limited information eliminated unnecessary information
Brainstorming
is group discussion in which members shares their ideas and find out the solution of specific problem
members generate idea it is more value able as of group
product and members enjoy the group activity
Subjects and design
Procedure
Results
Discussion
is encouraging open-minded and free ideas or innovation on particular predefine problem
Storyboard
customer and developers draw picture of what they want to develop software.
is just like paper prototyping
some attribute or elements
Level of details
describes existent of actor and objects
Inclusion of text
text could be including in design with
each section
Inclusion of people and emotions
design should be according to end user that affects the user or stakeholders
Number of frames
Number of frames should be in mind mostly 1 to 20
frames are included in each story
Portrayal of time
Time passing is include in storyboarding or used
transitions.
Prototyping
Through prototyping detailed requirements can be gathered if preliminary requirement are already collected
users provide relevant information and also provide feedback
is expensive in tenure of cost and time
Use cases
relationship between actor and system
include in use case analysis
Define how system will behave in particular situation. Use case can be used to represent business functionality
System is preserved such as black box, in which actor presents as whom, what will be interact as system and purpose or goal for interaction with the system without knowing about internal system
JAD (Joint Application Development)
With all parties decision can be made speedily
is used for solve business issues rather than technical issues
Project Definition
Define system goal, objective.
Identify JAD team fellows
Establish project schedule.
Background Research
Gather background knowledge of user requirement.
Known about general issues that will discuss in JAD session.
Pre workshop
Preparation
Organize for session.
Prepare all the documents and visual aids
Train the illuminator.
The Workshop
Conclude solution within three to five day session.
Finalize document meeting decision.
Final Documentation
Prepare Closing document that contain final decision attained at through workshop
ISSUES IN REQUIREMENTS GATHERING
Scope
Sometime user or stakeholders are not familiar or know the scope of project
Scope should be limited and clearly
define
It is seemed that some projects are very
worthy but due to limited scope these are not successful.
Communication and understanding
issue may be language issue
do not know the language or it may possible
they are not familiar with your condition and terms
are not able to understand your terms and they are
not able to specify their own requirement
Stakeholder participant and selection
Stakeholder interaction
Communication activities
Techniques
Quality of requirements
some users not provide
right information they are not serious
Requirement elicitation is a first phase for initial any project so information should be correct and complete
the end project quality not get
best due to quality of requirement
Solution is that carefully
gets information according to their need and put limited
Stakeholders
Actually stakeholders do not know what they
want and what their need is
They do no cooperate whole time with project team
members.
they are not able to finalize
the solution of decision of any problem
Practice
not expert analysts are available for requirement gathering or there may be some gap between requirement theory and practice.
hire experience analysts for this purpose.