Lecture

Scenarios and Requirements: Design Ideation and Solutions

Graph Chat

Chat with Graph Search

Ask any question about EPFL courses, lectures, exercises, research, news, etc. or try the example questions below.

DISCLAIMER: The Graph Chatbot is not programmed to provide explicit or categorical answers to your questions. Rather, it transforms your questions into API requests that are distributed across the various IT services officially administered by EPFL. Its purpose is solely to collect and recommend relevant references to content that you can explore to help you answer your questions.

In course

CS-486: Interaction design

This course focuses on goal-directed design and interaction design, two subjects treated in depth in the Cooper book (see reference below). To practice these two methods, we propose a design challenge, which is further divided into mini-projects evenly spa ...

Description

This lecture introduces the concept of design ideation through context scenarios, key path scenarios, and validation scenarios. It covers the process of bridging research and design, the development of design solutions based on user understanding, and the definition of requirements. The importance of storytelling in illustrating design solutions is emphasized, along with the distinction between scenarios and use cases. The lecture also discusses the requirement definition phase, the difference between needs and features, and the sources of requirements. Practical steps for requirement definition are outlined, including creating problem statements, brainstorming, and identifying persona expectations.

This video is available exclusively on Mediaspace for a restricted audience. Please log in to MediaSpace to access it if you have the necessary permissions.

Watch on Mediaspace

Instructor

Pearl Pu Faltings

Expertise Human computer interaction, artificial intelligence, user experience research, user modeling, preference-based search, intelligent user interfaces, information visualization. Teaching & PhD Past EPFL PhD Students Denis Lalanne, Georgios Melissargos, Frank Paul Janecek, Li Chen, Jiyong Zhang, Nicolas Jones, Rong Hu, Yu Chen, Valentina Sintsova, Onur Yürüten, Yubo Xie, Ekaterina Svikhnushina, Kalpani Anuradha Welivita Past EPFL PhD Students as codirector Marina Boia, Igor Kulev Courses Interaction

Official source

Ontological neighbourhood

Systems science and engineering

Systems thinking: Systems engineering

Related concepts (28)

Requirements analysis

In systems engineering and software engineering, requirements analysis focuses on the tasks that determine the needs or conditions to meet the new or altered product or project, taking account of the possibly conflicting requirements of the various stakeholders, analyzing, documenting, validating and managing software or system requirements. Requirements analysis is critical to the success or failure of a systems or software project.cite book |editor1= Alain Abran |editor2=James W.

Requirements engineering

Requirements engineering (RE) is the process of defining, documenting, and maintaining requirements in the engineering design process. It is a common role in systems engineering and software engineering. The first use of the term requirements engineering was probably in 1964 in the conference paper "Maintenance, Maintainability, and System Requirements Engineering", but it did not come into general use until the late 1990s with the publication of an IEEE Computer Society tutorial in March 1997 and the establishment of a conference series on requirements engineering that has evolved into the International Requirements Engineering Conference.

User-centered design

User-centered design (UCD) or user-driven development (UDD) is a framework of process (not restricted to interfaces or technologies) in which usability goals, user characteristics, environment, tasks and workflow of a product, service or process are given extensive attention at each stage of the design process. These tests are conducted with/without actual users during each stage of the process from requirements, pre-production models and post production, completing a circle of proof back to and ensuring that "development proceeds with the user as the center of focus.

Business requirements

Business requirements, also known as stakeholder requirements specifications (StRS), describe the characteristics of a proposed system from the viewpoint of the system's end user like a CONOPS. Products, systems, software, and processes are ways of how to deliver, satisfy, or meet business requirements. Consequently, business requirements are often discussed in the context of developing or procuring software or other systems. Three main reasons for such discussions: A common practice is to refer to objectives, or expected benefits, as 'business requirements.

Design thinking

Design thinking refers to the set of cognitive, strategic and practical procedures used by designers in the process of designing, and to the body of knowledge that has been developed about how people reason when engaging with design problems. Design thinking is also associated with prescriptions for the innovation of products and services within business and social contexts. Design thinking has a history extending from the 1950s and '60s, with roots in the study of design cognition and design methods.

Related lectures (32)

Scenarios and Requirements

Delves into the significance of scenarios and requirements in design, emphasizing storytelling for design solutions.

Requirements Definition

Explores the fundamentals of requirements definition in systems engineering, emphasizing the importance of clear and concise requirements for successful system design.

An Introduction to Systems Engineering: Requirements, Architecture, and Concept Generation

Covers the 'V-Model' of Systems Engineering, emphasizing good requirements, system architecture, concept generation, and concept selection.

Requirements: User Stories

Covers the importance of user input in defining requirements and developing user stories.

Systems Engineering: Requirements, Architecture, and Standards