D
database designer
Within the RUP, a database designer is a person playing the role of designing one or more logical database schemas and/or physical databases for the new system.data flow
A data flow is a connection within which an output pin provides one or more data values to an input pin.
data store node
A data store node is a central buffer node that handles persistent information.
datatype
A datatype is a description of a set of values
The UML defines two kinds of datatypes: enumeration and primitive type. There can also be user-defined datatypes.
data value
A data value is an instance of a datatype.The term decisionInput refers to a stereotype attached to a note to signify that the note specifies a decision criterion attached to a decision node.
decisionInput
decision node
A decision node is a control node that offers a choice among two or more outgoing activity edges, each of which has a guard. The decision criterion connected with the guards may appear in a note attached to the decision node under the decisionInput stereotype.
deep history
The term deep history refers to a pseudostate that "remembers" the innermost nested state at any depth.
default value (external)
A default value is a data value, expressed in an external language (such as a programming language), that serves as the starting value of a given parameter.default value (internal)
The term default value also refers to an expression that specifies the value that a given attribute holds upon initialization.
defect
Within the Unified Process, a defect is a symptom of a problem in the system that developers need to track and resolve.
deferred event
A deferred event is an event that a given
Define a Candidate Architecture
Within the RUP, Define a Candidate Architecture is an activity within the Analysis and Design discipline.
This activity involves creating an initial sketch of the system's architecture, identifying analysis classes from the architecturally significant use cases, and updating the use case realizations-analysis with the interactions among those analysis classes.
Define Evaluation Mission
Within the RUP, Define Evaluation Mission is an activity within the Test discipline.
This activity involves identifying the appropriate focus of the test effort for a given iteration and gaining agreement with stakeholders on the corresponding goals that will direct this effort.
Define the System
Within the RUP, Define the System is an activity within the Requirements discipline.
This activity involves establishing the set of system features to be considered for delivery, determine the criteria for prioritizing these features, and identifying the key actors and use cases needed for each key feature.
delegation
An object performs a delegation when it issues a message to another object in response to an initial message.Delegation is of interest primarily in the context of polymorphism.
delegation connector
A delegation connector is a connector that links the external contract of a component, as specified by its ports, to the internal realization of that behavior by the component’s parts.
A signal, which represents an operation request or an event, that arrives at a port that has a delegation connector to a part or to another port will be passed on to that target for handling.
dependency
A dependency is a directed relationship between two named elements within which a dependent element (the client) depends on an independent element (the supplier) for its specification or implementation.There are three basic categories of dependency:
 | abstraction |
| permission |
| usage |
A deployed artifact is an artifact involved in one or more deployments to a deployment target.
The term deployment refers to a dependency that indicates the allocation of an artifact or artifact instance to a deployment target.
The details of a deployment may appear in a deployment specification.
Within the RUP, the Deployment artifact set is a set of artifacts related to the physical deployment of a system.
The deployment set contains the following artifacts:
|
bill of materials |
|
deployment plan |
| installation artifacts |
| product artwork |
| release notes |
| support material |
| training material |
deployment diagram
A deployment diagram is a structure diagram that shows the configuration of a set of run-time processing nodes and, optionally, the artifacts that reside on them.deployment manager
Within the RUP, the deployment manager is a person playing the role of planning and overseeing transition of the new system to the user community.deployment model
Within the Unified Process, the term deployment model refers to a stereotype attached to a model to signify that the model describes the physical distribution of the system being built, in terms of how functionality is distributed among computational nodes.Within the RUP, the deployment model is part of the Analysis and Design artifact set.
The term deployment spec refers to a stereotype that signifies a deployment specification.
A deployment specification is an artifact that specifies a set of properties that determine the execution parameters of a component deployed on a node.
A deployment target is a named element that represents the location of a deployed artifact.
deployment view
The deployment view shows the nodes within a distributed system, the components stored on each node, and the objects contained within those components. This view focuses on distribution, delivery, and installation.The deployment view is captured primarily on deployment diagrams, and also on interaction diagrams, state machine diagrams, and activity diagrams.
The deployment view is a part of the static view. The deployment view is also one of the five interlocking views that comprise the architecture.
Deployment discipline
Within the RUP, the purpose of the Deployment discipline is to deliver the new system to its customers.
derivation
A derivation is a dependency within which the client can be computed or inferred from the supplier, as specified by a mapping.derivation rule
A derivation rule is an OCL expression that specifies how to determine the value of a derived attribute or association.
A
derive
The term derive is a stereotype that signifies a derivation.derived element
A derived element is a model element that can be computed or inferred from other model elements.descendant
The term descendant refers to any element that sits "below"-in other words, is more specific than-a given element within a particular generalization or hierarchy of generalizations.Describe Current Business
Within the RUP, Describe Current Business is an activity within the Business Modeling discipline.
The purpose of this activity is to build a business object model and a business use case model for the current business.
descriptor
A descriptor is a model element that describes the common properties of a set of instances.
A descriptor has both an intent and an extent.
Design a Class
Within the Unified Process, Design a Class is an activity within the Design workflow.
There are eight steps involved in this activity:
|
Outlining each design class in terms of analysis classes and/or interfaces |
|
Identifying the operations that each design class needs to provide |
|
Identifying the attributes that each design class needs |
|
Identifying the associations and aggregations connected with those design classes |
|
Identifying generalizations in which those design classes should participate |
|
Describing methods that those design classes should implement |
|
Describing the possible states of objects instantiated from those design classes |
|
Handling special requirements associated with those design classes |
Design Components
Within the RUP, Design Components is an activity within the Analysis and Design discipline.
This activity involves working out the details of how the elements of the design-design classes, collaborations, and subsystems-implement the required behavior, refining and updating the use case realizations-design, and reviewing the design as it evolves.
Design the Database
Within the RUP, Design the Database is an activity within the Analysis and Design discipline.
This activity involves identifying the persistent classes within the design, designing appropriate database structures to house these classes, and defining mechanisms and strategies for storing and retrieving persistent data.
Design a Subsystem
Within the Unified Process, Design a Subsystem is an activity within the Design workflow.
There are three steps involved in this activity:
|
Ensuring, for each subsystem, that the subsystem is highly independent of other subsystems and their interfaces |
|
Ensuring that each subsystem provides the appropriate interfaces |
|
Ensuring that each subsystem offers a correct realization of the operations behind those interfaces |
Design a Use Case
Within the Unified Process, Design a Use Case is an activity within the Design workflow.There are five steps involved in this activity:
|
Identifying the design classes that are needed in order to perform each use case |
|
Distributing the behavior of each use case across the objects associated with those design classes |
|
Identifying the necessary subsystems and interfaces |
|
Describing the interactions of those subsystems |
|
Capturing requirements, associated with each use case, that should be addressed during implementation |
Design Business Process Realizations
Within the RUP, Design Business Process Realizations is an activity within the Business Modeling discipline.
The purpose of this activity is to define how the business processes that underlie the system being modeled will be realized within the new system..
design class
Within the Unified Process, the term design class refers to a stereotype attached to a class to signify that
designer
Within the RUP, a designer is a person playing the role of defining the responsibilities, operations, attributes, and relationships for one or more classes, and also determines how those definitions should be adjusted with regard to implementation.
design model
Within the Unified Process, the term design model is a stereotype attached to model to signify that that
Within the RUP, the following comprise the design model:
|
capsules |
|
design subsystems |
|
events |
|
interfaces |
|
protocols |
|
signals |
|
testability classes |
|
test designs |
Within the RUP, the design model is part of the Analysis and Design artifact set.
Within the Unified Process, the term design package is a stereotype attached to a package to signify that the package collects design classes, relationships, use case realizations–design, and diagrams that belong to the design model.
A design package can also contain other design packages.
design pattern
A design pattern is a pattern that defines a structure (shown on a class diagram) and an interaction (generally shown on a sequence diagram) that is part of the design view of a given model.
design reviewer
Within the RUP, a design reviewer is a person playing the role of planning and conducting a formal review of the design model.design subsystem
Within the Unified Process, the term design subsystem is a stereotype attached to a package to signify that the package contains design classes, class and subsystem interfaces, and use case realizations-design.
A design subsystem can also contain other design subsystems.
design system
Within the Unified Process, the term design system is a stereotype that refers to the top-level package within the design model.
Design Test
Within the Unified Process, Design Test is an activity within the Test workflow.
This activity involves identifying and describing integration, system, and regression test cases for each build and identifying and structuring test procedures.
design view
The term design view refers to the set of classes, interfaces, and collaborations that together describe the problem space and the solution space associated with a given system. This view exists to specify the functional requirements of the system.
The design view is captured in class diagrams, object diagrams, interaction diagrams, state machine diagrams, and activity diagrams.
The design view is one of the five interlocking views that comprise the architecture.
Design workflow
Within the Unified Process, the purpose of the Design workflow is to create a design model that describes the physical realizations of the use cases and serves as an abstraction of the system's implementation.
The following activities comprise the Design workflow:
|
Architectural Design |
|
Design a Class |
|
Design a Subsystem |
|
Design a Use Case |
destroy (action)
To destroy an object is to eliminate it and reclaim the system resources it had been using.destroy (behavioral feature)
The term destroy is also a stereotype on a behavioral feature that indicates that the feature destroys an instance of the enclosing classifier.destroy link action
A destroy link action is a write link action that destroys one or more links or link objects.
destroy object action
A destroy object action is an action that destroys a specified object.
Destruction includes the elimination of links associated with the given object. If the object is a composite object, all of its parts are eliminated as well.
Detail a Use Case
Within the Unified Process, Detail a Use Case is an activity within the Requirements workflow.
This activity involves describing the basic and alternate courses of action (flows of events) through each use case in detail, including how the use case starts and ends and the involvement of actors.
Develop a Domain Model
Within the RUP, Develop a Domain Model is an activity within the Business Modeling discipline.
The purpose of this activity is to build a domain model for the business being modeled. (The domain model is a subset of the business analysis model.)
Within the RUP, a development case is a specification of a tailored version of the process framework.
The development case is part of the Environment artifact set. Develop Software Development Plan Within the RUP, Develop Software Development Plan is an activity within the Project Management discipline. The purpose of this activity is to build the various elements of the software development plan, and also to perform tasks such as defining the project organization and staffing and planning phases and iterations.
Within the RUP, Develop Support Material is an activity within the Deployment discipline.
This activity involves developing the full range of information that the end user will require to install, operate, use and maintain the delivered system, including training material.
The term device is a stereotype attached to a node to signify a physical computational resource with processing capability upon which artifacts may be deployed for execution.
A device may also contain other devices via a composition relationship.
diagram
A diagram is a graphical presentation of a collection of model elements. This presentation is a projection of those elements of a given model.The UML defines two basic types of diagrams: behavior diagrams and structure diagrams.
direct class
An object's direct class is the class that most completely describes that object.directed relationship A directed relationship is a relationship, which works in one primary direction, between one or more sources and or more targets. The UML defines 11 kinds of directed relationships:
|
dependency |
|
element import |
|
extend |
|
generalization |
|
include |
|
information flow |
|
package import |
|
package merge |
|
protocol conformance |
|
realization |
|
template binding |
An object is a direct instance of a given class if that class describes the instance and no descendant class also describes that object.
A direct substate is a substate that is contained by only one state.
direct substate
A discipline is a sequence of activities that produces a result of observable value.
The RUP contains nine "core" disciplines:
|
Requirements discipline |
|
Test discipline |
A discriminator is a pseudoattribute that selects a child element from a set of children within a generalization relationship.
disjoint
The term disjoint is a constraint attached to a generalization set to signify that given multiple inheritance, no object can be an instance of more than one child within the set.disjoint substate
The term disjoint substate is a synonym for sequential substate.distribution unit
A distribution unit is a set of objects or components allocated to a node as a group (for example, a set of tables that together form the contents of a database).do
The term do is a reserved word used in conjunction with an activity expression in the context of a state machine.document
The term document is a stereotype attached to an artifact to signify a file that contains static information about the system being modeled.
domain model
Within the Unified Process, a domain model is a model that captures the most important types of business objects and real-world objects and concepts that exist, and also events that transpire, in the environment in which a given system will work.
A domain model is generally represented by class diagrams.
duration
The term duration refers to a value specification that denotes some duration in time, expressed as the difference between a starting point in time and an ending point in time.
duration constraint
A duration constraint is a constraint that applies to a duration interval.
duration interval
A duration interval is an interval that defines a range between two durations.
duration observation action
A duration observation action is a write structural feature action that measures a duration.
dynamic classification
The term dynamic classification refers to a variation of generalization in which an object can change its type or role.dynamic view
The term dynamic view refers to those aspects of a given model having to do with the specification and implementation of behavior over time.Four views comprise the dynamic view:
|
activity view |
|
interaction view |
|
state machine view |
|
use case view |
