Requirements Elicitation and Analysis
Requirements Elicitation and Analysis
Term Definition
analysis Examines data elicited to understand where the gaps and impacts are
context diagram Analysis technique used to identify scenarios, users, user goals, and external
systems
mindset State of mind that keeps attention focused on building the right product for
customers, users, and business
process model Multipurpose tool used as a dialogue starter to create a visual to explain the
process or sequence of activities; involves visualization, organization, and
analysis
Decision about how the business and technology will work together on a
requirement project
requirements Tool used to strategically draw out information from stakeholders and
workshop customers
INTERVIEWING QUESTIONS
Engaging Questions
Probing Questions
Domain-Specific Questions
1. What team do you work on and how do they fit into the bigger picture?
2. What are your major responsibilities?
3. What business decisions (business rules) do you make in your job?
4. With whom do you interact to carry out your responsibilities?
5. What information, resources, and documents do you use in your job?
6. What forms (online, system, or paper) do you use?
7. What computer systems do you use in your job?
8. Are there any events for which the system provides alerts?
9. Are there any new alerts needed?
10. How do you measure success in your job?
11. What is occurring that is helping or inhibiting you to do your job?
12. What skills are needed in your present job?
13. What training did you receive for your present job?
14. What training should someone starting this role have?
15. What would you change about the way you carry out your responsibilities?
16. What do you see as the major critical issues facing the organization or team?
17. What areas for improvement have you observed?
Books
Gamestorming: A Playbook for Innovators, Rulebreakers, and Changemakers
https://www.amazon.com/Gamestorming-Playbook-Innovators-Rulebreakers-
Changemakers/
Thinkertoys: A Handbook of Creative-Thinking Techniques
https://www.amazon.com/Thinkertoys-Handbook-Creative-Thinking-Techniques-
2nd/dp/1580087736/
ref=pd_lpo_sbs_14_img_0?_encoding=UTF8&psc=1&refRID=80G69A4TRRV1THQA34WP
Online Tools
Mind Tools: Brainstorming
https://www.mindtools.com/brainstm.html
Lucid Meetings: Tools for Online Brainstorming and Decision Making in Meetings
http://blog.lucidmeetings.com/blog/25-tools-for-online-brainstorming-and-decision-
making-in-meetings
Virtual Brainstorming
CardBoard It: http://www.cardboardit.com/
Conteneo Weave: https://weave.conteneo.co/a/innovationgames/1
Stormboard: https://stormboard.com/
MODEL WORDS
In your models, dialog, and written requirements, you must use powerful words that describe
the actions users take when using the system or product.
• Concise
• Testable
• Easy for customers, developers, and business people and leaders to understand
• Ambiguous
BLENDING
Discover all the users Workshops Context diagram Context diagrams focus
who are impacted by the on interactions and
Brainstorming Process model
process or function being integrations, and process
changed or added Interviews Story maps flows focus on sequence.
Both are great views into
identifying the user roles
impacted.
Discover the data that Observation Data flow diagrams
Remember to think
users rely on for about what data the user
Interviews Process models
performing their goals expects to see and use,
Workshops Context diagrams and when. Where is the
same data used
repeatedly in the same
end-to-end user goal?
Process models
Experiments
INTEGRATION
The following considerations are important for integration requirements. Many of these are
related to the business context of the integration, which many teams struggle with. Without the
business context, teams make poor assumptions about the data and data transformation, which
result in defects and poor user experience.
Integration title What is the team calling this integration? This should be a
name understandable to the business stakeholders.
Purpose of integration What is the business value this integration provides? How
does it enhance the user experience? What would the user
experience be like if the integration were not in place?
Value of integration How would the business operate if the integration failed and
had to resort to manual processes rather than automated?
Source system What system is the data coming from?
Trigger for integration data to be What triggers the data to be pulled and sent? Business
processed triggers?
Known data quality issues Are there any known data quality issues with the source
data?
Common data errors What common data errors typically happen with the data
being pulled or sent?
What does the target system do with the What does the target system do with the data it receives
data? from this integration?
What is a record of data for this interface? In plain language terms, describe what a record or
transaction of data consists of for this interface?