10 ESTABLISHING REQUIREMENTS

Summary

This video explores the crucial process of establishing requirements in Human-Computer Interaction (HCI) design. It covers the importance of understanding user needs, types of requirements—including functional, non-functional, data, environmental, and user-related—and effective data gathering techniques such as interviews, observations, and questionnaires. The lecture emphasizes analysis tools like scenarios, personas, use cases, essential use cases, and hierarchical task analysis to translate user needs into actionable system specifications. Real-world examples, including a travel organizer scenario, illustrate these methods. The session concludes with a practical assignment, guiding learners to design and evaluate an online ticket booking system by applying these principles iteratively.

Takeaways

• 😀 Establishing requirements in HCI design is a crucial step for creating user-centered interactive systems that meet users' expectations and needs.
• 😀 Requirements can be categorized into functional (what the system should do), non-functional (security, response time), and data-related (data storage and management).
• 😀 It's important not to overload presentation slides with too much content, as audiences cannot process both reading and listening at the same time.
• 😀 Different types of requirements include environmental (physical factors like noise or humidity) and social (e.g., sharing files, communication needs).
• 😀 User characteristics, such as nationality, education, and attitude to technology, must be considered to tailor requirements effectively.
• 😀 Personas, which are synthesized user profiles, help capture key user characteristics and goals to design for real-world scenarios.
• 😀 Various data gathering techniques, including interviews, focus groups, and direct observation, are essential for collecting accurate user requirements.
• 😀 Contextual inquiry is a key method where the designer works alongside the user in their environment to better understand their tasks and challenges.
• 😀 Scenarios and use cases are tools to describe and visualize how users interact with a system, helping to define clear user goals and system responses.
• 😀 Hierarchical Task Analysis (HTA) helps break down tasks into smaller subtasks, facilitating the understanding of user goals and system interactions.
• 😀 The process of defining requirements is iterative, involving refinement and rescoping, and it is essential to get these requirements right to avoid failure in the design process.

Q & A

Why is establishing requirements critical in HCI design?

Establishing requirements is critical because it defines what the system should do, how it should behave, and what the users need and expect. Failure at this stage is the most common cause of unsuccessful system design.

What are the main types of requirements in HCI design?

The main types of requirements are functional (what the system should do), non-functional (security, response time, usability), data (types of data and storage), environmental/contextual (physical, social, organizational), and user characteristics (capabilities, preferences, and limitations).

What role do personas play in requirements gathering?

Personas capture a set of user characteristics, goals, and backgrounds, providing a realistic but synthesized representation of users. They help designers understand user behavior, motivations, and needs without relying on idealized assumptions.

How do scenarios differ from use cases?

Scenarios are informal, narrative stories describing how a persona behaves in context, while use cases are detailed step-by-step interactions between a user and the system. Essential use cases abstract away implementation details and focus on goals rather than specific interactions.

What is Hierarchical Task Analysis (HTA) and why is it used?

HTA breaks a task into subtasks and sub-subtasks, grouped into plans specifying how tasks are performed. It focuses on physical and observable actions and is used to analyze complex tasks to improve system usability.

What are common techniques for gathering data for requirements?

Common techniques include interviews, focus groups, questionnaires, direct and indirect observation, studying documentation, researching similar products, ethnographic studies, contextual inquiry, and cultural probes.

What are key considerations when involving stakeholders in data gathering?

Key considerations include identifying and involving all relevant stakeholder groups, including real users, managing political dynamics within the organization, and balancing functional and usability demands while ensuring participation from diverse representatives.

How should data gathered from users be analyzed?

Data should be initially interpreted soon after gathering, followed by deeper analysis using various representation techniques such as diagrams, task descriptions, scenarios, and use cases. This ensures that the requirements reflect actual user needs and context.

What is the purpose of documenting requirements using a template like Valair Shell?

The Valair Shell template provides a structured way to capture and communicate requirements, ensuring clarity, completeness, and traceability. It supports iterative refinement and helps relate requirements to gathered data and user needs.

In the example of the travel organizer, how are personas, scenarios, and use cases connected?

A persona defines who the story is about, including motivations and goals. The scenario describes when, where, and how the persona performs tasks. The use case breaks down the interaction with the system into specific steps, detailing how the scenario is executed.

What are alternative courses in a use case, and why are they important?

Alternative courses describe variations or exceptions in the main use case, such as invalid inputs or errors. They are important for anticipating potential issues and ensuring the system can handle different user behaviors robustly.

How can the analysis of existing systems or tasks improve requirement gathering?

Analyzing existing systems or tasks using HTA or studying documentation provides insights into real user behaviors, task sequences, and potential pain points. This helps identify realistic requirements and areas for improvement in the new system.