S

scenario

A scenario is a sequence of user and system actions that illustrates some behavior.

An instance of a use case is sometimes referred to as a scenario.
 

scope

The term scope refers to the context that gives meaning to the name of a given feature.

script

The term script is a stereotype on an artifact that signifies that the artifact is a script file that can be interpreted by a computer system.
 

select

The term select refers to an OCL operation that creates a Collection that contains all of the elements in a given Collection for which a specified Boolean expression is True.
 

self

The term self refers to the instance of the type that is the context of a given OCL constraint.
 

self-transition

A self-transition is a transition for which the source state and target state are the same, but which results in a change in state, and therefore the execution of the appropriate exit action and entry action.
 

send

The term send refers to a stereotype attached to a usage dependency within which the source object sends a signal to the target object.
 

sender

A sender is an object that sends a message to another object.
 

send object action

A send object action is an invocation action that transmits a given object to a particular target object.


send signal action

A send signal action is an invocation action that creates a signal and transmits it to a target object, where it may cause the triggering of a transition and/or the execution of a procedure that uses the signal’s arguments.
 

Sequence

A Sequence is an ordered Collection of elements, each of which may appear more than once.

One ends up with a Sequence when one navigates through an ordered association.

One can perform the following operations on a Sequence, in addition to all of the operations that one can perform on a Collection:
 

	append
	at
	first
	last
	prepend

sequence diagram

A sequence diagram is an interaction diagram that focuses on the time-ordering of message between objects.

Sequence diagrams and communication diagrams are semantically equivalent, which means you can convert one type of diagram to the other without losing any information. However, a sequence diagram has two key features that a collaboration diagram does not: lifelines and focuses of control.
 

sequence number

A sequence number is a piece of text on a communication diagram that indicates the relative execution order of the associated message in the interaction being modeled.
 

sequential substate

A sequential substate is a substate in which an object can reside to the exclusion of all other substates at that same level within the given composite state.

service (Unified Process)

Within the Unified Process, the term service refers to an atomic (indivisible) chunk of functionality that appears in one or more use cases.
 

service (UML)

The term service also refers to a stereotype attached to a component to signify that the component is stateless and its only purpose is to compute some value.
 

service package

Within the Unified Process, the term service package is a stereotype attached to a package to signify that the package is being used to structure the system being built according to the services it will provide.

A service package is a kind of analysis package. It sits lower in the hierarchy than regular analysis packages.
 

service subsystem

Within the Unified Process, the term service subsystem is a stereotype attached to a subsystem to signify that the subsystem is being used to structure the system being built according to the services it will provide.

A service subsystem is a kind of design subsystem. It sits lower in the hierarchy than regular design subsystems.
 

Set

A Set is a Collection of elements, each of which may only appear once.

One ends up with a Set when one navigates through one association whose multiplicity is greater than 1.

One can perform the minus and symmetricDifference operations on a Set, in addition to all of the operations one can perform on a Collection.

shallow history

The term shallow history refers to a pseudostate that "remembers" only the outermost nested state.
 

signal

A signal is a specification of a type of send request instance that is dispatched synchronously or asynchronously by one object and received by another object.

The attributes of a signal serve as its parameters. The signal is associated with one or more behavioral features that raise it, and with one or more receptions.
 

signal event

A signal event is an event that represents an object's reception of a signal.

signal trigger

A signal trigger is a message trigger that specifies that a behavior execution may be triggered by receipt of a particular signal.
 

signature

The signature of a behavioral feature consists of that feature's name and parameters. (The parameters are expressed as a parameter list.)
 

simple name

A simple name is a name that stands alone.
 

simple state

A simple state is a state that has no substates.
 

simple transition

A simple transition is a transition that has one source state and one target state.
 

single classification

The term single classification refers to a type of generalization in which each object has exactly one direct class.
 

single inheritance

The term single inheritance refers to a type of generalization within which an element may have only one parent.
 

singleton

A singleton is a class that has exactly one instance.
 

size

The term size refers to an OCL operation that returns the number of elements in a given Collection.

slot

A slot is a specification that an entity modeled by an instance specification has one or more values for a specific structural feature.

The value of an attribute within the description of an object is an example of a slot.
 

snapshot

A snapshot is a collection of objects, links, and values of a given system at a particular moment in time.

An object diagram captures a snapshot.
 

software architect

Within the RUP, a softwarerchitect is a person playing the role of leading and coordinating the technical activities, and the production of the associated artifacts, throughout the project.

The software architect also establishes the overall structure for the five views that comprise the architecture.
 

software architecture document

Within the RUP, the software architecture document is the artifact that describes the architectural views of the various models that represent the new system at the end of the Elaboration phase.

The software architecture description is part of the Analysis and Design artifact set.

software development plan

Within the RUP, a software development plan is an artifact that gathers the key information that the project manager requires.

The following comprise the software development plan:
 

	measurement plan
	problem resolution plan
	product acceptance plan
	quality assurance plan
	risk management plan

The software development plan is part of the Project Management artifact set.
 

solution domain

The term solution domain refers to a conceptual area within the domain model that involves the solution to the problem being solved by the system being built.

sortedBy

The term sortedBy refers to an OCL operation that returns a Sequence whose first element is the element of a given Collection for which a specified Ocl expression resolves to the lowest value, and whose last element is the one for which the expression resolves to the highest value, using the appropriate sort order.
 

source (client)

The term source is a synonym for client.
 

source (stereotype)

The term source is also a stereotype attached to an artifact to signify a file that contains source code.
 

source scope

The term source scope is a synonym of owner scope.
 

source state

A source state is a state within a state machine from which a transition leaves.

A source state may be either a substate or a composite state as a whole.
 

specialization

The term specialization refers to producing a more specific description of a model element by adding one or more children.

special requirements

Within the Unified Process, the term special requirements is a tag definition whose value contains text describing one or more nonfunctional requirements.
 

	For an analysis class, special requirements are requirements identified and specified during analysis that are better handled during design and/or implementation.
	For a use case, special requirements are requirements not captured within that use case's flow of events.
	For a use-case realization-analysis, special requirements are requirements identified and specified during analysis that are better handled during design and/or implementation.

specification

The term specification refers to a stereotype on a classifier that signifies that the classifier specifies a domain of objects without defining the physical implementation of those objects.

stakeholder

A stakeholder is a person playing the role of someone who is materially affected by the outcome of the project.
 

start owned behavior

The term start owned behavior refers to an action that starts a behavior owned by a given object.
 

state

A state is a named condition or situation in the life of an object, that lasts for some finite amount of time, during which the object satisfies some condition, performs some activities and/or actions, or waits for some event.

A state may have any or all of these:
 

	deferred events
	entry actions
	exit actions
	internal transitions
	state invariants
	substates

There are three kind of states:
 

	composite state
	simple state
	submachine state

state invariant

A state invariant is an interaction fragment that serves as a runtime constraint on a given lifeline.
 

state machine

A state machine is a behavior that specifies a sequence of states that an object goes through during its lifetime, in response to events, and also the responses that the given object makes to those events.

A state machine diagram depicts a state machine.
 

state machine diagram

A state machine diagram is a behavior diagram that shows a state machine.

Within a state machine diagram, the emphasis is the flow of control between states.
 

state machine view

The term state machine view refers to those aspects of a given system that involve the specification of behavior of individual model elements over their lifetimes.

The state machine view is comprised of state machine diagrams.

The state machine view is a part of the dynamic view.
 

static classification

The term static classification refers to a type of generalization relationship in which an object may not change its type or role.
 

static view

The term static view refers to those aspects of a given model having to do with the kinds of things that exist within the model, their internal structure, and the relationships that exist among those things.

The static view is captured primarily in class diagrams.

The static view is part of the structural view.
 

stereotype (mechanism)

A stereotype is an extensibility mechanism that allows one to create new kinds of model elements that are derived from existing ones. These new elements have their own special properties (expressed as tagged values), semantics, and notation.

A stereotype applies to one or more kinds of model elements. A stereotype may also have an associated visual icon, such as the one for a boundary object.

A model element can have at most one stereotype. However, stereotypes can have children.

The following stereotypes are predefined within the UML:
 

	access
	apply
	artifact
	auxiliary
	bind
	buildComponent
	call
	create
	datatype
	decisionInput
	deployment spec
	derive
	destroy
	device
	document
	element import
	entity
	enumeration
	exception
	executable
	execution environment
	extend
	file
	flow
	focus
	framework
	implement
	implementationClass
	import
	information
	interface
	library
	localPostcondition
	localPrecondition
	manifest
	metaclass
	metamodel
	modelLibrary
	permit
	postcondition
	precondition
	process
	profile
	realize
	refine
	represents
	responsibility
	script
	send
	service
	source
	specification
	stereotype
	substitute
	subsystem
	systemModel
	trace
	type
	use
	utility

The following stereotypes have been defined as extensions of the UML for the Unified Process:
 

	analysis model
	analysis package
	analysis system
	boundary class
	control class
	design class
	deployment model
	design model
	design subsystem
	design system
	entity class
	implementation model
	implementation subsystem
	implementation system
	service package
	service subsystem
	test model
	test component
	test system
	use case model
	use case realization-analysis
	use case realization-design
	use case system

stereotype (stereotype)

The term stereotype also refers to a stereotype attached to a classifier to signify that the classifier is itself a stereotype that can be applied to other model elements.

stop

The term stop refers to an event occurrence that defines the termination of the instance connected to a given lifeline.
 

storyboard

Within the Unified Process, a storyboard is an artifact that describes how part of the user interface addresses a use case.

Within the RUP, the storyboard is part of the Requirements artifact set.
 

string

A string is a primitive type that represents a sequence of text characters.

string constant expression

A string constant expression is a constant expression that refers to a string.
 

structural feature

A structural feature is a typed feature of a classifier that specifies part of the structure of instances of the classifier.

An attribute is an example of a structural feature.

structural feature action

A structural feature action is an action that acts upon a structural feature.

There are three types of structural feature actions:

	clear structural feature action
	read structural feature action
	write structural feature action

structural thing

A structural thing is a noun that represents a mostly static conceptual or physical part of a model.

There are seven kinds of structural things:
 

	active class
	class
	collaboration
	component
	interface
	node
	use case

structural view

The term structural view refers to a view of a given model that focuses on the structure of the instances of the system being modeled.

Four views comprise the structural view:
 

	deployment view
	implementation view
	static view
	use case view

structured activity node

A structured activity node is an executable node that represents a structured portion of a given activity that is not shared with any other structured node, except for nodes that are nested.

There are three kinds of structured activity node:

	conditional node
	expansion region
	loop node

structured classifier

A structured classifier is a classifier whose behavior can be fully or partly described by the collaboration of owned or referenced instances.


structure diagram

A structure diagram is a diagram that shows aspects of the structure of the system being modeled.

The UML defines six types of structure diagrams:

	class diagram
	component diagram
	composite structure diagram
	deployment diagram
	object diagram
	package diagram

Structure the Implementation Model

Within the RUP, Structure the Implementation Model is an activity within the Implementation discipline.

The purpose of this activity is to ensure that the implementation model is organized such that the development of components and the build process are as conflict-free as possible.

Structure the Use Case Model

Within the Unified Process, Structure the Use Case Model is an activity within the Requirements workflow.

There are three steps involved in this activity:
 

	Identifying and extracting general and shared descriptions of functionality that can be used by more specific use cases in the context of a generalization
	Identifying and extracting additional and optional descriptions of functionality that can be used to extend use cases
	Identifying other relationships among use cases that can be expressed using the include construct

stubbed transition

A stubbed transition is a notation that indicates that a given transition involves a transfer into a particular composite state, but the details have been suppressed on the state machine diagram.
 

subclass

A subclass is a child of another class within a generalization.
 

submachine

A submachine is a state machine that can be invoked as part of one or more other state machines.
 

submachine state

A submachine state is a state that references a submachine such that a copy of that submachine is implicitly part of the enclosing state machine where the reference occurs.
 

subOrderedSet

The term subOrderedSet refers to an OCL operation that creates an OrderedSet consisting of the objects that reside between specified lower and upper bounds, inclusive, within a given OrderedSet.

subpackage

A subpackage is a package contained within another package.
 

subSequence

The term subSequence refers to an OCL operation that creates a Sequence consisting of the objects that reside between specified lower and upper bounds, inclusive, within a given Sequence.

subset

Within the OCL, the term subset is a constraint attached to a pair of associations to signify that the set of links belonging to one of the associations is a subset of the set of links belonging to the other association.
 

substate

A substate is a state that is part of a composite state.

There are two kinds of substates: concurrent substates and sequential substates.
 

substitutability principle

The substitutability principle states that an instance of a descendant element can be substituted for an instance of one of that element's ancestors with no loss of information or functionality.

substitute

The term substitute is a stereotype that indicates a substitution dependency.
 

substitution

A substitution is a type of realization within which the client will comply with the contract specified by the supplier at program execution time.
 

subsystem

The term subsystem is a stereotype attached to a package to signify that the package represents an independent part of the system being modeled.

A subsystem generally offers interfaces; the notation is the same as it is for interfaces connected to classes.

A subsystem can be instantiated—in other words, it can have more than one version in the finished system.

subsystem instance

A subsystem instance is an instance of a subsystem.
 

subtype

A subtype is a type that is a child of another type.
 

sum

The term sum refers to an OCL operation that returns the sum of all elements within a given Collection of real numbers or integers.
 

summarization

The term summarization refers to act of filtering, combining, and abstracting the properties of a set of elements onto their container in order to give a higher-level, more abstract view of a system.
 

superclass

A superclass is a parent of another class within a generalization.
 

supertype

A supertype is a type that is a parent of another type.
 

supertypes

The term supertypes refers to an OCL operation that returns the Set of direct supertypes associated with a given model element.
 

supplementary business specification

Within the RUP, a supplementary business specification is an artifact that contains definitions of business terms that are not represented within the business use case model and the business object model.

The supplementary business specification is part of the Business Modeling artifact set.
 

supplementary requirement

A supplementary requirement is a requirement that cannot be associated with any particular use case.

Supplementary requirements generally involve nonfunctional issues such as performance and constraints associated with implementation.
 

supplementary specification

Within the RUP, a supplementary specification is an artifact that contains information about requirements that are not represented within the use-case model.

The supplementary specification is part of the Requirements artifact set.
 

supplier

The term supplier refers to the element within a given dependency that provides one or more services to the client. (The supplier is the independent element in the relationship.)
 

Support Environment During Iteration

Within the RUP, Support Environment During Iteration is an activity within the Environment discipline.

This activity involves supporting developers in their use of tools and the process during the given iteration.

survey description

Within the Unified Process, the term survey description is a tag definition whose value contains a text description of a use case model as a whole.
 

swimlane

A swimlane is a pair of parallel vertical or horizontal lines on an activity diagram used to delineate a partition.
 

symmetricDifference

The term symmetricDifference refers to an OCL operation that creates a Set that contains all of the elements that are in one Set or another, but not both.
 

synchronous action

A synchronous action is a request that an object makes that includes waiting for a response.
 

synch state

A synch state is a state that enables synchronization of control between two concurrent regions within a state machine.

A key aspect of a synch state is bound, the value of which indicates the difference between the number of times the incoming transition is fired and the number of times the outgoing transition is fired. This value can be an integer or the word unlimited. (The latter is represented on a state machine diagram with an asterisk, just as the multiplicity value "many" is.)
 

system administrator

Within the RUP, the system administrator is a person playing the role of maintaining the hardware and software development environments and performing tasks such as account administration and backup.
 

system analyst

Within the Unified Process, a system analyst is a worker who leads and coordinates the effort to identify requirements and build the use case model.
 

system integrator

Within the Unified Process, a system integrator is a worker who plans the sequence of builds required in an iteration and integrates each build when its parts have been implemented.

systemModel

The term systemModel is a stereotype attached to a package to signify that the package contains a collection of models that taken together represent the entire system being modeled.
 

system-software layer

Within the Unified Process, the term system-software layer refers to a layer of a system that contains the software for the computing and networking infrastructure (for instance, the operating system and the database management system [DBMS]).
 

system tester

Within the Unified Process, a system tester is a worker who performs system tests.

---

vyhledat