Getting requirements from stakeholders: Difference between revisions
| Line 9: | Line 9: | ||
| '''Method''' || '''Definition''' || '''Advantages''' || '''Disadvantages''' | | '''Method''' || '''Definition''' || '''Advantages''' || '''Disadvantages''' | ||
|- | |- | ||
| '''Surveys (questionnaires)''' || | | '''Surveys (questionnaires)''' || Surveys can be used to gather input from a large number of stakeholders quickly and efficiently. || You can easily reach many people, good to reach people in remote locations || provides less information than direct contact or interviews. Interpreting the meaning of a question or answer can be difficult. | ||
|- | |- | ||
| '''Interviews''' || | | '''Interviews''' || This involves one-on-one or small group meetings with stakeholders to gather information about their needs and expectations. || You can gather in-depth information and explore topics which are tangentially related to the system. There is flexibility in information || You are usually limited to few people, not many people. If an interview isn't structured, you may get fragmented information. It can be harder to quantify requirements from an interview. | ||
|- | |- | ||
| '''Direct observations''' || | | '''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> | ||
|} | |} | ||
Revision as of 05:45, 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. | You can easily reach many people, good to reach people in remote locations | provides less information than direct contact or interviews. Interpreting the meaning of a question or answer can be difficult. |
| Interviews | This involves one-on-one or small group meetings with stakeholders to gather information about their needs and expectations. | You can gather in-depth information and explore topics which are tangentially related to the system. There is flexibility in information | You are usually limited to few people, not many people. If an interview isn't structured, you may get fragmented information. It can be harder to quantify requirements from an interview. |
| 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.[2] |
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.
Standards[edit]
These standards are used from the IB Computer Science Subject Guide[3]
- Describe methods of obtaining requirements from stakeholders.
References[edit]
- ↑ http://www.flaticon.com/
- ↑ https://en.wikipedia.org/wiki/Observational_techniques#Three_Approaches
- ↑ IB Diploma Programme Computer science guide (first examinations 2014). Cardiff, Wales, United Kingdom: International Baccalaureate Organization. January 2012.