1.
Interview
o Purpose: Understand the needs from users or stakeholders.
o How to process: Engage in direct conversations with stakeholders to ask relevant
questions.
o Pros: Capture comprehensive opinions and needs of users.
o Cons: Time and effort-intensive to conduct.
2. Workshops
o Purpose: Gather a focused group to discuss and provide input.
o How to process: Organize focused meetings to facilitate discussion among involved
members.
o Pros: Quickly gather consensus from multiple stakeholders.
o Cons: Requires proactive and effective participation from all members.
3. Focus Groups
o Purpose: Collect opinions from a representative group of users.
o How to process: Gather a small group of representative users to discuss and provide
feedback.
o Pros: Obtain accurate insights from a group of representative users.
o Cons: May not be fully representative of all user groups.
4. Observations
o Purpose: Directly observe user actions or reactions.
o How to process: Monitor and take notes on user behaviors in real-world settings.
o Pros: Gather accurate information without intermediaries.
o Cons: Time-consuming and may not be suitable for all situations.
5. Questionnaires
o Purpose: Gather standardized responses from a large number of stakeholders.
o How to process: Distribute structured questionnaires to target participants for feedback.
o Pros/Cons: Scalable for large audiences but may not capture nuanced responses.
6. System Interface Analysis
o Purpose: Analyze existing system interfaces to understand user interactions.
o How to process: Review the current system interfaces to identify strengths and
weaknesses.
o Pros/Cons: Provides insights into existing system behavior but may not capture user
preferences.
7. User Interface Analysis
o Purpose: Evaluate user interfaces to ensure they meet user needs and preferences.
o How to process: Assess user interfaces for usability, accessibility, and user experience.
o Pros/Cons: Improves user satisfaction but may require iterative design changes.
8. Document Analysis
o Purpose: Review existing documentation to extract requirements and constraints.
o How to process: Analyze system specifications, reports, and documentation for
requirements.
o Pros/Cons: Helps in understanding system context but may miss out on implicit
requirements.
9. Prototyping
o Purpose: Create interactive prototypes to visualize and validate requirements.
o How to process: Develop low-fidelity or high-fidelity prototypes for user feedback.
o Pros/Cons: Facilitates early user involvement but may require additional time and
resources.
10. Brainstorming
o Purpose: Generate creative ideas and solutions through group discussions.
o How to process: Conduct brainstorming sessions to encourage team collaboration and
innovation.
o Pros/Cons: Stimulates idea generation but may lead to unstructured discussions.
11. Storyboards
o Purpose: Visualize user interactions and scenarios in a sequential manner.
o How to process: Create visual narratives depicting user journeys and system interactions.
o Pros/Cons: Enhances user understanding but may oversimplify complex processes.
