Publication

From one virtual actor to virtual crowds: requirements and constraints

Daniel Thalmann
2000
Conference Papers

Abstract

A crowd is not only a group of many individuals. Crowd modelling involves problems that arise only when we focus on crowds. For instance, avoiding collision problems related to a big number of individuals in the same place require different strategies in comparison with the methods used to avoid collision between individuals. The paper is concerned with a discussion about the requirements to model behaviours of crowds of virtual actors

Official source

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.

Daniel Thalmann
2000
Conference Papers

Abstract

Official source

Related concepts (11)

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.

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.

Related publications (8)

From one virtual actor to virtual crowds: requirements and constraints

Chat with Graph Search

A Field Guide to Federated Optimization

Initial experimental tests, setups, discussions and challenges for OSB connections

Review and Classification of Gain Cell eDRAM Implementations