What are we looking at?
How do we draw needs out of the organisation and the users’ minds?
Having seen why requirements analysis matters, it is time for the tools that help us draw these needs out of the organisation and the users’ minds. This stage looks simple but in practice is full of challenges and misunderstanding, and with the right techniques it can be done in a structured way.
The aim of gathering requirements is to collect the data, wishes, limits and expectations of end users, stakeholders and managers, and to document them so that they become the reference for decisions in later stages.
Five main techniques
Interviews. Face-to-face conversations with users or key stakeholders. Strengths: you can ask open and closed questions, understand real problems more deeply and build trust between analyst and users. Challenges: the respondent may give wrong or incomplete information, and you must listen and analyse at the same time. Tip: start with general questions and move gradually to detail.
Questionnaires. Distributing written or digital forms to get structured answers from many people. Strength: suited to large, scattered audiences and produces data that can be analysed statistically. Challenges: answers are shallow and the response rate is low. Tip: keep questions clear, short and purposeful.
Direct observation. The analyst watches processes in the field and studies users’ behaviour. Strength: you discover problems users themselves don’t notice, and see real behaviour against what they say. Challenges: behaviour can be misread, and there is the “observer effect”: people behave differently when they know they are watched.
Reviewing existing documents. Reading reports, forms, earlier diagrams and official records. Strengths: you get to know the current structure and gain historical and background information. Challenge: documents are outdated or incomplete. A good complement to interviews.
Group sessions (Focus Group / JAD). An interactive session with different stakeholders. Strength: diverse views are gathered fast and synergy creates new ideas. Challenges: the session needs careful management, and stronger views may dominate. Tip: use facilitation techniques so everyone is heard.
Complementary methods
Building a prototype and taking feedback (prototyping), drawing scenarios of how the system will be used (storyboarding), drawing users’ behaviour with the system as a diagram (use-case modelling), and mapping concepts and requirements graphically (mind mapping).
When to use which?
| Scenario | Suggested method |
|---|---|
| Many scattered users | Questionnaire |
| Need for analytical depth | Interview |
| Innovative projects | Group session or prototyping |
| Need to find hidden problems | Direct observation |
None of these is enough alone. A professional analyst combines several methods. For example, combining interviews with observation and document review shows reality, the user’s perception and the official data together.