Lecture 7 User requirement Gathering Flashcards
(14 cards)
What is requirements gathering in system design?
It’s the process of collecting accurate, detailed information from stakeholders to guide system development. It helps reduce design errors and ensure the product meets user needs.
What is Human-Centered Design and its purpose?
HCD is an iterative design approach focused on user needs, involving cycles of designing, prototyping, and evaluating. It’s supported by the ISO 13407 framework and aims to improve usability and satisfaction.
What’s the difference between functional and non-functional requirements?
Functional Requirements: What the system does (e.g., login, search, notifications)
Non-Functional Requirements: How the system behaves (e.g., usability, performance, accessibility)
What is a persona and why is it used in design?
A persona is a fictional character representing a user group, based on research. It helps designers understand user behaviors, needs, goals, and pain points.
What is a user story?
A user story is a short, simple description of a feature told from the perspective of the user, e.g.,
“As a user, I want to reset my password so I can access my account.”
Helps development teams focus on user value.
Why is gathering user requirements critical?
Reduces design errors
Manages stakeholder expectations
Avoids conflicts
Ensures goals and metrics are well documented
Why is iteration key in gathering requirements?
Because user needs evolve, and early assumptions can be wrong. Continuous feedback ensures clarity, prioritization, and realignment with user expectations.
What is the ISO 13407 framework?
An international standard that outlines how to apply human-centered design to system development. It supports:
Early user involvement Iterative design High-fidelity prototyping Evaluation at each stage
What does “Context of Use” mean in design?
It refers to the users, their environment, and the tasks they perform. Understanding context helps in creating systems that are truly user-friendly and accessible.
What are the benefits and challenges of using personas?
Focuses design on real needs
Encourages empathy
Challenges:
Risk of generalization
May oversimplify complex user behaviors
How do scenarios differ from user stories?
Scenarios: Detailed narratives showing how users interact with the system in context
User Stories: Short, structured descriptions of user needs and goals
How can user stories inform functional & non-functional requirements?
User stories identify what users need, which are then translated into specific system functions (functional) and performance expectations (non-functional).
Why is it difficult to identify user needs accurately?
Users often don’t know what they need or can’t imagine what’s possible. Deep research and feedback loops are necessary for accurate understanding.
What makes requirement documentation effective?
Relevant
Clear and unambiguous
Measurable
Actionable
So they can properly guide design and development.
