U
Understand Stakeholder Needs
U
Understand Stakeholder NeedsWithin the RUP, Understand Stakeholder Needs is an activity within the Requirements discipline.
This activity involves gathering stakeholder requests and obtaining a clear understanding of the real needs of them and the users of the system being modeled.
uninterpreted
The term uninterpreted refers to a type or value whose implementation the UML does not specify.uninterpreted action
An uninterpreted action is an action whose syntax and evaluation is not defined within the UML.union
The term union refers to an OCL operation that combines two Sets, two Bags, a Bag and a Set, or two Sequences into a new Collection.The term unlimited natural refers to a primitive type that represents unlimited natural values.
usage
A usage relationship is a dependency within which the target requires the presence of the source for its correct functioning or implementation.One models a regular usage relationship using the use keyword. There are also several variations, including:
 |
call |
| create |
|
instantiate |
|
responsibility |
|
send |
use
The term use is a stereotype that signifies a usage dependency.use case
A use case is a behaviored classifier that
A use case always has one main flow of events (also known as a basic course of action, and will generally have at least one exceptional flow of events (or alternate course of action).
use case diagram
A use case diagram is a behavior diagram that shows a set of use cases and actors and the relationships among them.
use case driven
A process is use case driven if it involves using use cases at the center of the following tasks:
|
Establishing the desired behavior of the system |
|
Creating, verifying, and validating the system's architecture |
|
Testing |
|
Communicating among project stakeholders |
use-case engineer
A use-case engineer is a person playing the role of being responsible for the integrity of one or more use-case realizations-analysis.
use case generalization
The term use case generalization refers to a generalization within which the parent and the child are both use cases.use case instance
A use case instance is an instance of a use case, which represents the execution of the sequence of actions that use case specifies.use case model
Within the Unified Process, the term use case model is a stereotype attached to a model to signify that the model contains use cases and actors and the relationships among them.The following comprise the use case model:
| actors |
| use cases |
| use case packages |
The use case model is meant to describe the complete functionality of the system being built. The idea is that this model lends itself to developers and customers agreeing on the requirements and becomes something of a "contractual agreement."
Within the RUP, the use-case model is part of the Requirements artifact set.
Within the Unified Process, the term use case package is a stereotype attached to a package to signify that the package organizes use cases, actors, relationships, and diagrams within a use case model.
A use case package can also contain other use case packages.
use case realization-analysis
Within the Unified Process, the term use case realization-analysis is a stereotype attached to a collaboration within an analysis model to signify that the collaboration that describes how a given use case is realized and performed, expressed in terms of analysis classes and their associated objects.A use-case realization-analysis contains four parts:
|
Text that describes the flow of events of the associated use case |
|
One or more class diagrams that show the analysis classes |
|
One or more interaction diagrams that show how objects interact to realize the use case |
|
Any special requirements associated with the use case |
Within the RUP, use case realizations-analysis are part of the Analysis and Design artifact set.
use case realization-design
Within the Unified Process, the term use case realization-design is a stereotype attached to a collaboration within a design model to signify that the collaboration describes how a given use case is realized and performed, expressed in terms of design classes and their associated objects.A use-case realization-design contains four parts:
|
Text that describes the flow of events of the associated use case |
|
One or more class diagrams that show the design classes |
|
One or more interaction diagrams that show how objects interact to realize the use case |
|
Any implementation requirements associated with the use case |
use-case specifier
Within the Unified Process, a use-case specifier is a worker who writes one or more use cases.
use case system
Within the Unified Process, the term use case system is a stereotype that refers to the top-level package within the use case model.use case view
The term use case view refers to the set of use cases that together describe the behavior of a given system as seen by its actors. This view exists to specify the internal and external forces that shape the architecture of the system.The use case view is captured in use case diagrams, interaction diagrams, state machine diagrams, and activity diagrams.
The use case view is a part of the static view and the dynamic view. The use case view is also one of the five interlocking views that comprise the architecture.
user-interface designer
Within the Unified Process, a user-interface designer is a worker who leads and coordinates the prototyping and design of the user interface for the new system.
user interface prototype
Within the Unified Process, a user interface prototype is a prototype whose purpose is to help the development team understand and specify the interactions between human actors and the system being built.Within the RUP, the user-interface prototype is part of the Analysis and Design artifact set.
utility
The term utility is a stereotype attached to a class to signify that the attributes and operations associated with that class all have class scope. (This means that a utility has no instances.)
