Index_D

---

D

dash. See hyphen

dashed line

with arrow, from object to class, 54–55

for dependencies, 76, 125, 347

dividing concurrent substates, 307

for included use cases, 162–163

for lifelines, 190

dashed oval, for collaborations, 250, 252–253

data flow. See object flow

data slots. See attributes

data subsystem, 322

database subsystem, 355

databases

as actors, 134–135

internal compared to external, 135

for object persistence, 318

terminology, compared to classes and objects, 44

UML modeling tools for, 32–33

Data-Description Language. See DDL

data-flow diagram, avoiding, 309. See activity diagram

datatypes

analysis packages based on, 342

for arguments, 49–50

for attributes, 44–45

implementation compared to conceptual types, 48

inheritance and, 103

intrinsic, 45

of qualifiers, 77

data-validation rules, in use case scenarios, 160

DDL (Data-Description Language), UML modeling tools supporting, 33

decision node, 215

decomposition of system

creating subsystems, 318, 321–323

definition of, 318, 320–321

process for, 322–323

deep history pseudostate, 301

default values, attribute

definition of, 46–47

inheritance and, 103

/defer, for deferred events, 287

deferred event, 287

«delegate» stereotype, 331

delegates, for components, 331

delegation connector, 90

Department of Defense’s Architecture Framework. See DODAF

dependencies

dashed line for, 76, 125, 347

with diagrams, 12

with interfaces, 329–330

with merged subsystems, 352–354

with subsystems, 341, 347–350

deployment, subsystems based on, 345

deployment diagram

artifacts in, 336–338

constructing, 333–335

uses of, 14, 15, 320, 390–391

derived attributes

definition of, 55–56

inheritance and, 103

design class diagram, 228–232

design pattern. See patterns

design phase

package diagram for, 390

sequence diagrams for, 202

subsystems for, 342

designers, 17

design-time boundary objects, 199

«destroy» stereotype, 195

destructor operation, 85, 97

developers. See implementors

development. See software and system development

device class, 389

«device» stereotype, 334

devices as actors, 135–136

DevX Web site, 374

diagrams. See also shapes and symbols in UML diagrams; specific diagrams

abstract classes represented in, 107

actors represented in, 137–138, 139–141

aggregation represented in, 83–84, 86

alternative categories of, 15

architectural patterns represented in, 355–356

artifacts represented in, 337

association classes represented in, 76

associations represented in, 64, 65, 68–69, 74, 77, 79

choosing using modeling frameworks, 15–16

classes represented in, 52–56, 59–60

collaborations represented in, 250, 355–356

completing in parallel, 368

components represented in, 327

composition represented in, 86–87, 89–92

converting to code, 79

dependencies represented in, 76, 125, 347

diagram of, 12

events represented in, 262, 285, 290–292

generalizations represented in, 94–96

generalized use cases represented in, 167–168

interfaces represented in, 327

level of detail in, 364–365

lifelines represented in, 190–193

links represented in, 63

list of, 13–15

multiple inheritance represented in, 108

multiple, wrapping into packages, 125–127

multiplicity represented in, 68–69

nodes represented in, 333

number of elements in, 3

objects represented in, 52–56

point of view for, 11

preconditions and postconditions represented in, 186

roles represented in, 71–72

specialization represented in, 97–98

spelling and grammar checking for, 43

states represented in, 262

subsystems represented in, 321

transitions represented in, 290–292

use cases represented in, 139–141, 167–168

uses of, 13–15, 31

using too many or too few, 363–364

diamond

for decision and merge nodes, 215

filled in, for composition, 86–87

hollow, for aggregation, 84, 87–88

direction of argument, 50

discriminator. See generalization sets

do/, for activity in a state, 267

DODAF (Department of Defense’s Architecture Framework), 15

do-forever state, 309

domain class diagram

definition of, 117, 122

uses of, 122, 386–387

domain classes. See also use cases

analysis packages for, 341–342

definition of, 121–122

dynamic, 388

responsibilities of, 390

subsystems for, 323

domain groups, 341–342

domain language, 121

dot

for initial nodes, 215

for initial state, 263

dot operator (.), OCL, 187

double angle brackets (<<>>), for stereotype, 55, 137

double colon (::), between class and operation, 50

do-until state, 309

dynamic diagrams, 15

dynamic domain classes, 388

dynamic modeling. See events; state diagram; states

---