Lecture

Quiz Results: Design Process

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 covers the instructor's announcement of quiz results, emphasizing the meticulous grading process and fair treatment of students. Additionally, the lecture delves into the design process, showcasing new videos on scenarios and requirements, and providing guidance on developing a contact scenario for a project.

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

Computer engineering

Software development: Human–computer interaction

Systems science and engineering

Systems thinking: Systems engineering

Related concepts (27)

Requirement

In product development and process optimization, a requirement is a singular documented physical or functional need that a particular design, product or process aims to satisfy. It is commonly used in a formal sense in engineering design, including for example in systems engineering, software engineering, or enterprise engineering. It is a broad concept that could speak to any necessary (or sometimes desired) function, attribute, capability, characteristic, or quality of a system for it to have value and utility to a customer, organization, internal user, or other stakeholder.

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.

Interaction design pattern

Interaction design patterns are design patterns applied in the context human-computer interaction, describing common designs for graphical user interfaces. A design pattern is a formal way of documenting a solution to a common design problem. The idea was introduced by the architect Christopher Alexander for use in urban planning and building architecture and has been adapted for various other disciplines, including teaching and pedagogy, development organization and process, and software architecture and design.

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.

User experience

The user experience (UX) is how a user interacts with and experiences a product, system or service. It includes a person's perceptions of utility, ease of use, and efficiency. Improving user experience is important to most companies, designers, and creators when creating and refining products because negative user experience can diminish the use of the product and, therefore, any desired positive impacts; conversely, designing toward profitability often conflicts with ethical user experience objectives and even causes harm.

Related lectures (48)

Systems Engineering: Introduction and Stakeholders

Introduces Systems Engineering, emphasizing stakeholder analysis and clear requirement definition for project success.

Introduction to HCI and Interaction Design

Covers the basics of HCI, emphasizing usability, playfulness, and the importance of professional training in design.

MATLAB Tools: Installation and Requirements

Covers the installation of pre-requirements for MATLAB tools and introduces Thermodynamics-based Flux Analysis packages.

Designing Solutions: Prototyping and User Experience

Covers the principles of prototyping and user experience design, emphasizing iterative processes and user feedback in creating effective solutions.

Matlab Widgets: GUI Elements Programming