~S~ |
|
scenario
| 1. | A specific sequence of actions that illustrates behaviors. A scenario can be used to illustrate an interaction or the execution of a use case instance. See also: interaction. |
| 2. | A sequence of operations carried out in some order to produce a known result. Can apply to use cases where it is the equivalent of a sequence diagram, or to other objects to describe how they are used at run-time. |
schema [MOF]
In the context of the MOF, analogous to a package that is a container of model elements. Schema corresponds to an MOF package.
Contrast: metamodel, package
self-message
Reflects a new process or method invoked within the calling lifeline's operation. It is a specification of a message.
semantic variation point
A point of variation in the semantics of a metamodel. It provides an intentional degree of freedom for the interpretation of the metamodel semantics.
send [a message]
The passing of a stimulus from a sender instance to a receiver instance.
See also: sender, receiver
sender [object]
The object passing a stimulus to a receiver object.
Contrast: receiver
sequence diagram
A diagram that shows object interactions arranged in time sequence. In particular, it shows the objects participating in the interaction and the sequence of messages exchanged. Unlike a Collaboration diagram, a Sequence diagram includes time sequences but does not include object relationships. A Sequence diagram can exist in a generic form (describes all possible scenarios) and in an instance form (describes one actual scenario). Sequence diagrams and Collaboration diagrams express similar information, but show it in different ways.
See also: collaboration diagram
signal
The specification of an asynchronous stimulus communicated between instances. Signals can have parameters.
signature
The name and parameters of a behavioral feature. A signature can include an optional returned parameter.
single inheritance
A semantic variation of generalization in which a type can have only one supertype.
Synonym: multiple inheritance [OMA]
Contrast: multiple inheritance
single valued [MOF]
A model element with multiplicity defined is single valued when its Multiplicity Type: upper attribute is set to one. The term single-valued does not pertain to the number of values held by, for example, an attribute or parameter at any point in time, since a single-valued attribute (for instance, with a multiplicity lower bound of zero) could have no value.
Contrast: multi-valued
specification
A declarative description of what something is or does.
Contrast: implementation
state
A condition or situation during the life of an object during which it satisfies some condition, performs some activity, or waits for some event.
Contrast: state [OMA]
state invariant
A condition applied to a lifeline that must be fulfilled for the lifeline to exist.
state machine
A behavior that specifies the sequences of states that an object or an interaction goes through during its life in response to events, together with its responses and actions.
state machine diagram
A diagram that illustrates how an element, often a class, can move between states classifying its behavior, according to transition triggers, constraining guards, and other aspects of state machine diagrams that depict and explain movement and behavior.
state chart
A diagram that shows a state machine.
See also: state machine
state continuation
A symbol that serves two different purposes for interaction diagrams - as state invariants and as continuations. A State Invariant is a condition applied to a lifeline that must be fulfilled for the lifeline to exist. A Continuation is used in seq and alt combined fragments to indicate the branches of continuation that an operand follows.
state lifeline
A State Lifeline follows discrete transitions between states, which are defined along the y-axis of the timeline. Any transition has optional attributes of timing constraints, duration constraints and observations.
static classification
A semantic variation of generalization in which an object can not change classifier.
Contrast: dynamic classification
stereotype
A new type of modeling element that extends the semantics of the metamodel. Stereotypes must be based on certain existing types or classes in the metamodel. Stereotypes can extend the semantics, but not the structure of pre-existing types and classes. Certain stereotypes are predefined in the UML, others can be user defined. Stereotypes are one of three extensibility mechanisms in UML.
See also: constraint, Tagged Value
stimulus
The passing of information from one instance to another, such as raising a signal or invoking an operation. The receipt of a signal is normally considered an event.
See also: message
string
A sequence of text characters. The details of string representation depend on implementation, and can include character sets that support international characters and graphics.
structural diagram
A diagram that depicts the structural elements composing a system or function. These diagrams can reflect the static relationships of a structure, as do class or package diagrams, or run-time architectures, such as object or composite structure diagrams. Structural diagrams include Class diagrams, Composite Structure diagrams, Component diagrams, Deployment diagrams, Object diagrams and Package diagrams.
structural feature
A static feature of a model element, such as an attribute.
structural model aspect
A model aspect that emphasizes the structure of the objects in a system, including their types, classes, relationships, attributes and operations.
subactivity state
A state in an activity graph that represents the execution of a non-atomic sequence of steps that has some duration.
subclass
In a generalization relationship, the specialization of another class; the superclass.
See also: generalization
Contrast: superclass
submachine state
A state in a state machine that is equivalent to a composite state but its contents are described by another state machine.
subpackage
A package that is contained in another package.
substate
A state that is part of a composite state.
See also: concurrent state, disjoint state
subsystem
A grouping of model elements that represents a behavioral unit in a physical system. A subsystem offers interfaces and has operations. In addition, the model elements of a subsystem can be partitioned into specification and realization elements.
See also: package, physical system
subtype
In a generalization relationship, the specialization of another type; the supertype.
See also: generalization
Contrast: supertype
superclass
In a generalization relationship, the generalization of another class; the subclass.
See also: generalization
Contrast: subclass
supertype
In a generalization relationship, the generalization of another type; the subtype.
See also: generalization
Contrast: subtype
supplier
A classifier that provides services that can be invoked by others.
Contrast: client
swimlane
A partition on a activity diagram for organizing the responsibilities for actions. Swimlanes typically correspond to organizational units in a business model.
See also: partition
synch
A state used for indicating that concurrent paths of a state machine are synchronized. After bringing the paths to a synch state, the emerging transition indicates unison.
synchronize code
The process of importing and exporting code changes to ensure the model and source code match
system
A top-level subsystem in a model.
Contrast: physical system
system boundary
An element used to delineate a particular part of the system.