Modeling interactions between objects
UML: software development and visual modeling
Article REF: H3238 V1
Modeling interactions between objects
UML: software development and visual modeling

Author : Patrick GIROUX

Publication date: February 10, 2004 | Lire en français

Logo Techniques de l'Ingenieur You do not have access to this resource.
Request your free trial access! Free trial

Already subscribed?

7. Modeling interactions between objects

7.1 Scenario

At the end of the needs analysis phase, the UML model describes use cases and a number of object classes that represent what the user perceives. Each use case can be likened to the intervention of an actor who addresses a succession of stimuli to the system in order to control it and activate its functions. In UML, such a sequence of interactions between actors and the system is called a scenario. For a given use case, there may be different scenarios, each characterized by a beginning corresponding to its triggering, an end corresponding to the result it leads to, and successive sequences corresponding to the alternatives proposed and the reactions or decisions of the participants. A use case can be considered as a class of scenarios.

Initially,...

You do not have access to this resource.
Logo Techniques de l'Ingenieur

Exclusive to subscribers. 97% yet to be discovered!

You do not have access to this resource. Click here to request your free trial access!

Already subscribed?


Ongoing reading
Modeling interactions between objects

Article included in this offer

"Software technologies and System architectures"

( 227 articles )

Complete knowledge base

Updated and enriched with articles validated by our scientific committees

Services

A set of exclusive tools to complement the resources

View offer details