American Science Institute of Technology  


   U to Z
Home Up Feedback Legal News




Unified Modeling Language [UML98]. In the Rational Unified Process Glossary, definitions from the Unified Modeling Language are indicated by the symbol: 
A placeholder for a type or types whose implementation is not specified by the UML. Every uninterpreted value has a corresponding string representation. See: any [CORBA].
A dependency in which one element (the client) requires the presence of another element (the supplier) for its correct functioning or implementation.
use case (class)
A use case defines a set of use-case instances, where each instance is a sequence of actions a system performs that yields an observable result of value to a particular actor. A use-case class contains all main, alternate flows of events related to producing the 'observable result of value'. Technically, a use-case is a class whose instances are scenarios.
The specification of a sequence of actions, including variants, that a system (or other entity) can perform, interacting with actors of the system. See: use-case instances.
use-case diagram
A diagram that shows the relationships among actors and use cases within a system.
use-case instance
A sequence of actions performed by a system that yields an observable result of value to a particular actor.
The performance of a sequence of actions being specified in a use case. An instance of a use case. See: use-case class.
use-case model
A model that describes a systemís functional requirements in terms of use cases.
use-case package
A use-case package is a collection of use cases, actors, relationships, diagrams, and other packages; it is used to structure the use-case model by dividing it into smaller parts.
use-case realization
A use-case realization describes how a particular use case is realized within the design model, in terms of collaborating objects.
use-case view
An architectural view that describes how critical use cases are performed in the system, focusing mostly on architecturally significant components (objects, tasks, nodes). In the Unified Process, it is a view of the use-case model.
A stereotype that groups global variables and procedures in the form of a class declaration. The utility attributes and operations become global variables and global procedures, respectively. A utility is not a fundamental modeling construct, but a programming convenience.



A variant of some artifact; later versions of an artifact typically expand on earlier versions.
A simplified description (an abstraction) of a model, which is seen from a given perspective or vantage point and omits entities that are not relevant to this perspective. See also architectural view.
A projection of a model, which is seen from a given perspective or vantage point and omits entities that are not relevant to this perspective.
view element
A view element is a textual and/or graphical projection of a collection of model elements.
view projection
A projection of model elements onto view elements. A view projection provides a location and a style for each view element.
An enumeration whose value (public, protected, or private) denotes how the model element to which it refers may be seen outside its enclosing namespace.
The user's or customer's view of the product to be developed, specified at the level of key stakeholder needs and features of the system.
An element of a type domain.
A source or a target for a transition in a state machine. A vertex can be either a state or a pseudo-state. See: state, pseudo-state.

[W ]

work guideline
A description which provides practical guidance on how to perform an activity or set of activities. It usually considers techniques which are useful during the activity.
A definition of the behavior and responsibilities of an individual, or a set of individuals working together as a team, within the context of a software engineering organization. The worker represents a role played by individuals on a project, and defines how they carry out work.
The sequence of activities performed in a business that produces a result of observable value to an individual actor of the business.
workflow detail
A grouping of activities which are performed in close collaboration to accomplish some result. The activities are typically performed either in parallel or iteratively, with the output from one activity serving as the input to another activity. Workflow details are used to group activities to provide a higher level of abstraction and to improve the comprehensibility of workflows.

[X Y Z]


Hit Counter

Home ] Up ]

Send mail to with questions or comments about this web site.
Copyright © 1997 - 2006 American Science Institute of Technology