Lecture

Scenarios and Requirements

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 explores the importance of scenarios and requirements in the design process, focusing on how they bridge research and design to create interactive software. It covers different types of scenarios, the qualitative research involved, and the development of context scenarios using storytelling. The instructor emphasizes the use of narratives to illustrate design solutions and the key differences between persona-based scenarios and use cases.

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 (21)

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.

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.

Non-functional requirement

In systems engineering and requirements engineering, a non-functional requirement (NFR) is a requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviours. They are contrasted with functional requirements that define specific behavior or functions. The plan for implementing functional requirements is detailed in the system design. The plan for implementing non-functional requirements is detailed in the system architecture, because they are usually architecturally significant requirements.

Software requirements specification

A software requirements specification (SRS) is a description of a software system to be developed. It is modeled after the business requirements specification (CONOPS). The software requirements specification lays out functional and non-functional requirements, and it may include a set of use cases that describe user interactions that the software must provide to the user for perfect interaction.

Related lectures (45)

Requirements Definition

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

Neural Amplifiers: Circuit Block Diagram and Design Requirements

Discusses the circuit block diagram and design requirements for neural amplifiers.

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.

Mono Panel Design: TopSolid 7

Explores the design process of a mono panel and its integration into a larger pavilion structure.

Systems Engineering: Requirements, Architecture, and Standards