Are you an EPFL student looking for a semester project?
Work with us on data science and visualisation projects, and deploy your project as an app on top of Graph Search.
Concept
Scenario (computing)
Summary
In computing, a scenario (UKsɪˈnɑːriəʊ, USsəˈnɛərioʊ; loaned (ʃeˈnaːrjo), ) is a narrative of foreseeable interactions of user roles (known in the Unified Modeling Language as 'actors') and the technical system, which usually includes computer hardware and software.
A scenario has a goal, which is usually functional. A scenario describes one way that a system is used, or is envisaged to be used, in the context of an activity in a defined time-frame. The time-frame for a scenario could be (for example) a single transaction; a business operation; a day or other period; or the whole operational life of a system. Similarly the scope of a scenario could be (for example) a single system or a piece of equipment; an equipped team or a department; or an entire organization.
Scenarios are frequently used as part of the system development process. They are typically produced by usability or marketing specialists, often working in concert with end users and developers. Scenarios are written in plain language, with minimal technical details, so that stakeholders (designers, usability specialists, programmers, engineers, managers, marketing specialists, etc.) can have a common ground to focus their discussions.
Increasingly, scenarios are used directly to define the wanted behaviour of software: replacing or supplementing traditional functional requirements. Scenarios are often defined in use cases, which document alternative and overlapping ways of reaching a goal.
Many types of scenario are in use in system development. Alexander and Maiden list the following types:
Story: "a narrated description of a causally connected sequence of events, or of actions taken". Brief User stories are written in the Agile style of software development.
Situation, Alternative World: "a projected future situation or snapshot". This meaning is common in planning, but less usual in software development.
Simulation: use of models to explore and animate 'Stories' or 'Situations', to "give precise answers about whether such a scenario could be realized with any plausible design" or "to evaluate the implications of alternative possible worlds or situations".
Official source
About this result
This page is automatically generated and may contain information that is not correct, complete, up-to-date, or relevant to your search query. The same applies to every other page on this website. Please make sure to verify the information with EPFL's official sources.
Related courses (2)
CS-489: Experience design
As we move towards a design economy, the success of new products, systems and services depend increasingly on the excellence of personal experience. This course introduces students to the notion and p
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
Related lectures (9)
Enterprise and Service-Oriented Architecture: Solutions for Business IT Alignment
Explores solutions for business IT alignment through enterprise and service-oriented architecture.
Scenarios and Requirements: Design Ideation and Solutions
Covers design ideation, scenarios, requirements, and the importance of storytelling in design solutions.
Scenarios and Requirements
Delves into the significance of scenarios and requirements in design, emphasizing storytelling for design solutions.