IS5411 Chap.3 Interviewing and Investigating Requirements
Interviewing and Investigating Requirements
Questions should change the model
Requirements interviews are structured investigations, not conversations about preferred features. Preparation identifies the process, current evidence and uncertainties that matter. A useful question reveals a trigger, actor, step, decision, information need or outcome.
Follow-up probes request a recent example, an exception and the rule behind what happened.
Instances expose the real workflow
Users often describe the intended procedure when asked what normally happens. Walking through a recent instance reveals hand-offs, workarounds and conditions omitted from the ideal account.
The analyst separates business facts from interface suggestions, preserves disagreement as an open requirement question and checks the account with other roles or documents when the process crosses functions.
Validation makes the evidence reviewable
Notes become a workflow by recording triggers, responsible actors, information used, decisions, branches and stable outcomes.
Showing the model back to participants allows specific correction. Asking for a missing case is more productive than asking whether a familiar-looking diagram is correct. Each session should leave an updated model and a precise list of evidence still needed.
What this chapter covers
- 01
Interview purpose
- 02
Question design
- 03
Recent examples
- 04
Exception probes
- 05
Actors and hand-offs
- 06
Workflow decisions
- 07
Conflicting accounts
- 08
Model validation
Worked example · free
Probe a vague approval statement
- 3Identify the hidden checks and decision owner.
- 3Add exception outcomes and stable statuses.
- 2State a validation question.
Key terms
- Interview Goal
- The specific uncertainty or process area an interview is intended to clarify.
- Probe
- A follow-up question that seeks an example, condition, exception or consequence.
- Trigger
- The occurrence that starts a process or requires a system response.
- Exception Path
- A branch followed when the normal processing condition does not hold.
- Stable Outcome
- A result in which the process and its data can safely remain until another event occurs.
- Validation
- The act of showing an interpreted model back to knowledgeable participants for correction.
Interviewing and Investigating Requirements FAQ
What makes an interview question useful?
A useful question produces evidence that changes or confirms a model. It identifies a step, rule, actor, input, output or exception. Questions that merely invite agreement with a proposed design test the analyst's idea rather than investigating the participant's work.
Why ask for a recent example?
A recent instance reduces the tendency to describe an ideal process and gives the analyst observable steps, decisions and outcomes. After the instance is clear, ask whether it represents the normal rule or an exception and who can confirm the distinction.
How should conflicting stakeholder accounts be handled?
Record each reading, the context in which it applies and the authority able to settle it. The difference may reveal an exception, policy-practice gap or two processes that were combined incorrectly. Smoothing the accounts into false agreement removes valuable evidence. A named unresolved question is safer than a diagram that conceals genuine disagreement.
Exam move
Choose a familiar approval process and write an interview plan with one goal, several open questions and probes for examples and exceptions. Convert an imagined answer into a workflow, then write the validation questions that would expose a missing branch. Keep interface suggestions separate from the business needs beneath them.
Rehearse three repairs: turn a leading question into a neutral request for a recent instance, split a compound question so the answer is attributable, and replace an abstract question with one that asks for an actor, condition and outcome. After the mock interview, colour-code each note as a confirmed fact, participant interpretation, design suggestion or open question.
Only confirmed business facts should enter the model without qualification. Ask another imagined participant to challenge the flow from a different organisational role, then preserve the disagreement rather than silently choosing a version. Finish with a validation script that asks what case is missing, where delay normally begins and what outcome would make the participant say the model is wrong.
This exercise turns interviewing into evidence management and prepares you to explain why a process branch exists instead of merely drawing it. End the rehearsal by writing a short evidence log: claim, participant, example and unresolved challenge. The log distinguishes confidence from corroboration and gives the next interview a precise agenda instead of another broad request to describe the process.
Working through Interviewing and Investigating Requirements in IS5411? Sia is AskSia’s AI Information Technology tutor — ask any IS5411 Interviewing and Investigating Requirements question and get a clear, step-by-step explanation grounded in how IS5411 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.