Getting requirements from stakeholders: Difference between revisions

From Computer Science Wiki
 
(One intermediate revision by the same user not shown)
Line 30: Line 30:
# May not be suitable for all stakeholders: Some stakeholders may not be comfortable or able to participate in an interview, in which case alternative methods may be necessary to gather their input.
# May not be suitable for all stakeholders: Some stakeholders may not be comfortable or able to participate in an interview, in which case alternative methods may be necessary to gather their input.
|-
|-
| '''Direct observations''' || Observing stakeholders as they perform their daily tasks can provide valuable insights into their needs and requirements. ||  The main advantage of observational research is flexibility. The researchers can change their approach as needed. Also it measures behavior directly, not reports of behavior or intentions.|| The problem with this approach is subjects may modify their behaviour when they know they are being watched. They portray their “ideal self” rather than their true self in what is called the Hawthorne Effect.<ref>https://en.wikipedia.org/wiki/Observational_techniques#Three_Approaches</ref>
| '''Direct observations''' || Observing stakeholders as they perform their daily tasks can provide valuable insights into their needs and requirements. ||   
 
# Provides real-time insights: Observation allows the facilitator to see firsthand how stakeholders perform their tasks and interact with the current system or product, which can provide valuable insights into their needs and requirements.
# Allows for the gathering of context: Observation allows the facilitator to gather information about the environment in which stakeholders work, which can provide context for their needs and requirements.
# Can identify unanticipated needs: Observing stakeholders in their natural environment can reveal needs and requirements that may not have been identified through other methods such as interviews or surveys.
||  
# May be disruptive: Observation can be disruptive to the stakeholders being observed, which may affect their performance and the accuracy of the observations.
# Can be resource-intensive: Observation requires a facilitator to be present and actively observing, which can be a resource-intensive process.
# May not be suitable for all stakeholders: Some stakeholders may not be comfortable with being observed, in which case alternative methods may be necessary to gather their input.
# May be limited in scope: Observation can only provide insights into the specific tasks and processes being observed, which may not provide a complete picture of the stakeholder's needs and requirements.
|}
|}


== Real-world practical advice ==
== Real-world practical advice ==


Make sure you are talking to the right people about system requirements. Many software projects have been doomed to fail because they were built on faulty requirements or poorly understood requirements.
Make sure you are talking to the right people about system requirements. Many software projects have been doomed to fail because they were built on faulty requirements or poorly understood requirements. Also, a combination of the techniques are also usually most effective.


== Standards ==
== Standards ==

Latest revision as of 05:56, 8 January 2023

System Fundamentals[1]

Understanding what your users want is very important. Your goal is to build software which meets the needs of users. There are different, complementary ways of gathering information from stakeholders. Different ways of collecting information can include surveys, interviews, and direct observations. There are other methods of gathering information but this is what you should minimally understand. You should understand each method for gathering requirements provides a different view (or lens, if you will) of client requirements. It is critical you understand the requirements prior to building a system.

Requirements[edit]

Method Definition Advantages Disadvantages
Surveys (questionnaires) Surveys can be used to gather input from a large number of stakeholders quickly and efficiently.
  1. Are efficient: Surveys can be distributed to a large number of stakeholders quickly and easily, and the responses can be collected and analyzed automatically.
  2. Are cost-effective: Surveys are a relatively inexpensive method for gathering information compared to other methods such as interviews or focus groups.
  3. Allow anonymity: Surveys allow stakeholders to provide input anonymously, which can encourage honesty and openness.
  4. Can be completed at the respondent's convenience: Surveys do not require stakeholders to take time out of their busy schedules to meet with a facilitator, which can increase response rates.
  1. May not provide sufficient detail: Surveys typically ask questions that can be answered briefly, which may not provide enough detail to fully understand the stakeholder's needs and requirements.
  2. Can be prone to bias: The way a question is phrased or the options provided in a survey can influence the response, leading to biased results.
  3. May have low response rates: Depending on the audience, surveys may have a low response rate, which can make it difficult to accurately represent the needs of all stakeholders.
  4. May not be suitable for all stakeholders: Some stakeholders may not be comfortable or able to complete a survey, in which case alternative methods may be necessary to gather their input.
Interviews This involves one-on-one or small group meetings with stakeholders to gather information about their needs and expectations.
  1. Allow for in-depth discussion: Interviews allow for a more in-depth and detailed exploration of a stakeholder's needs and requirements compared to methods such as surveys.
  2. Provide the opportunity to clarify and validate understanding: During an interview, a facilitator can ask follow-up questions and seek clarification to ensure that they fully understand the stakeholder's needs and requirements.
  3. Can build rapport and trust: Interviews allow for a more personal interaction between the facilitator and the stakeholder, which can help to build rapport and trust. This can be especially useful when working with stakeholders who are hesitant to share their needs and expectations.
  4. Can be tailored to the individual stakeholder: Interviews can be customized to the specific needs and preferences of the individual stakeholder, which can make them more engaging and effective at gathering information.
  1. Can be time-consuming: Interviews can be time-consuming, especially if a large number of stakeholders need to be interviewed.
  2. Can be resource-intensive: Interviews require a facilitator to be present, which can be a resource-intensive process.
  3. May not be suitable for all stakeholders: Some stakeholders may not be comfortable or able to participate in an interview, in which case alternative methods may be necessary to gather their input.
Direct observations Observing stakeholders as they perform their daily tasks can provide valuable insights into their needs and requirements.
  1. Provides real-time insights: Observation allows the facilitator to see firsthand how stakeholders perform their tasks and interact with the current system or product, which can provide valuable insights into their needs and requirements.
  2. Allows for the gathering of context: Observation allows the facilitator to gather information about the environment in which stakeholders work, which can provide context for their needs and requirements.
  3. Can identify unanticipated needs: Observing stakeholders in their natural environment can reveal needs and requirements that may not have been identified through other methods such as interviews or surveys.
  1. May be disruptive: Observation can be disruptive to the stakeholders being observed, which may affect their performance and the accuracy of the observations.
  2. Can be resource-intensive: Observation requires a facilitator to be present and actively observing, which can be a resource-intensive process.
  3. May not be suitable for all stakeholders: Some stakeholders may not be comfortable with being observed, in which case alternative methods may be necessary to gather their input.
  4. May be limited in scope: Observation can only provide insights into the specific tasks and processes being observed, which may not provide a complete picture of the stakeholder's needs and requirements.

Real-world practical advice[edit]

Make sure you are talking to the right people about system requirements. Many software projects have been doomed to fail because they were built on faulty requirements or poorly understood requirements. Also, a combination of the techniques are also usually most effective.

Standards[edit]

These standards are used from the IB Computer Science Subject Guide[2]

  • Describe methods of obtaining requirements from stakeholders.

References[edit]

  1. ↑ http://www.flaticon.com/
  2. ↑ IB Diploma Programme Computer science guide (first examinations 2014). Cardiff, Wales, United Kingdom: International Baccalaureate Organization. January 2012.

A unit of abstract mathematical system subject to the laws of arithmetic.

Offer for display, observation, examination or consideration.

The circumstances that form the setting for an event, statement, or idea, and in terms of which it can be fully understood and assessed.

Provide an answer from a number of possibilities. Recognize and state briefly a distinguishing fact or feature.

Give a detailed account or picture of a situation, event, pattern or process.

Retrieved from "https://computersciencewiki.org/index.php?title=Getting_requirements_from_stakeholders&oldid=11941"