Terms in this set (15)
what is Stakeholders Analysis?
Process of seeking, uncovering, acquiring, and elaborating requirements for computer based systems.
Requirements are elicited rather than just captured or collected.
what are the Requirements Elicitation Techniques?
Who are stakeholders?
An individual, team or organisation who have interest in, or can influence or be affected by, or participate in the development of requirements and relative software system projects.
2 techniques for stakeholder analysis
Technique1: stakeholders list/map/register and
Technique2: empathy map
Why stakeholder analysis?
Stakeholder analysis is the review and consideration of the impact stakeholders have on your business. Companies need to understand the interests of each stakeholder. To understand the importance and influence of individual stakeholders on the project. And to gain support.
Advantages of Interviews
+ Allows the interviewer and participant to have full discussions and explanations of the questions and answers.
+ Personal contact allows responsiveness and adapting to what the user says.
+ Analyst can probe in greater depth than any other methods of elicitation
+ Allows interviewees to express opinions in private that they may be reluctant to express in public.
Disadvantages of Interviews
- time consuming and costly
- Requires considerable commitment and involvement of the participants.
- Interview results have to be transcribed and written and transcription and analysis of interview data can be complex and expensive.
- Can be subject to bias
- If conflicting information is given, it can be difficult to resolve and interviews are not an ideal means of reaching consensus across a group of stakeholders.
- There is a risk of unintentionally leading the interviewee.
Advantages of Surveys
+ An economical and quick method of gathering data from a large sample.
+ Can reach many people with low resource.
+ Used for answering specific questions.
+ Can be administered remotely.
+ Depending on how well it is designed, the results can be analysed easily by software applications.
+ Effective and efficient when stakeholders are not located in one location.
Disadvantages of Surveys
- Effective questionnaires are hard to design (e.g. leading questions, misinterpretation of questions).
- Questions are usually not answered completely.
- The response rates for surveys are often too low for statistical significance.
- There is no automatic way of follow up unless you do interviews later.
Advantages of Observation
+ Provide first hand experience of the way the current system works
+ Data are collected in real time and can have a high level of validity
+ Can be used to verify information from other sources or to look for exceptions
+ Baseline data about the performance of the existing system and of users can be collected
Disadvantages of Observation
- Could be very time consuming
- Need to analyse huge amounts of data
- Most people do not like to be observed and may be disruptive to the person being observed.
- Requires trained and skilled observer to be most effective.
- There may be ethical problems if the person being observed deals with sensitive private or personal data or directly with members of public.
- There may be logistical problems if the staff being observed work shifts.
- Unusual exceptions and critical situations that happen infrequently may not occur during the observation.
Advantages of Prototypes
+ A prototype allows for early user interaction and feedback.
+ can be an inexpensive means to quickly uncover and confirm a variety of requirements.
+ Supports users who are more comfortable and effective at articulating their needs by using pictures, as prototyping lets them "see" the future system's interface.
+ Provides a vehicle for designers and developers to learn about the users' interface needs and to evolve system requirements.
Disadvantages of Prototypes
- Depending on the complexity of the target system, using prototyping to elicit requirements can take considerable time.
- A prototype may lead users to develop unrealistic expectations regarding the delivered system's performance, completion date, reliability and usability characteristics. This is because an elaborated, detailed prototype can look a lot like a functional system.
Advantages of Workshops
+ Workshop sessions are very successful in reducing project development efforts and shortening the schedule.
+ Used to generate ideas for new features or products
+ To reach consensus on a topic or conflicting views
+ Is able to gauge reaction to stimulus material (e.g. storyboards, screenshots)
+ A requirements workshop provides a means for stakeholders to collaborate, make decisions and gain a mutual understanding of requirements.
Disadvantages of Workshops
- Risk involved in speeding up the decisions. Sometimes the decisions made about the requirements are not optimal.
- May suffer from dominance and submission.
- At times, details are inappropriately defined or missed altogether.