Index_P

---

P

package diagram

definition of, 125–127

uses of, 14, 320, 390

packages

definition of, 125–127

subsystems compared to, 340

for system design, 339–343

for use cases, 146

visibility of, 57

«page» stereotype, 338

par operator, 211

«parallel» stereotype, 334

parameters. See arguments

parentheses (()), enclosing operation arguments, 51

partition names, in activity diagram, 224, 226

patterns

applying to a specific application, 252–254

composite structure diagrams for, 250–252

defining, 249–250

definition of, 29, 31

developing, 247–248

framework compared to, 31, 255

showing object interaction in, 254

for systems, 354–357

Web site about, 250

people. See actors; customers; stakeholders; users

performance

high degree of coupling for, 350

as system design requirement, 317

persistence

analysis packages based on, 342

of objects, choosing, 318

Petri net, activity diagrams compared to, 216

physical architecture, modeling, 333–338

physical models, 327

PIM (Platform-Independent Model), MDA and, 16

pipe-filter architectural pattern, 357

Platform-Independent Model. See PIM

Platform-Specific Model. See PSM

plus sign (+), for public visibility, 57

point of view for diagrams, 11

polymorphism, 27–28

Popkin, System Architect tool, 380–381

Popkin’s UML Resource Center Web site, 374

ports, 331

postconditions

for activities, 219

for text-based behavioral specification, 184–187

for transitions in protocol state machines diagram, 310

for use-case specification, 154

pound sign (#), for protected visibility, 57

precise UML group Web site, 373

preconditions

for activities, 219

for text-based behavioral specification, 184–187

for transitions in protocol state machines diagram, 310

for use-case specification, 154

presentation subsystem, 322, 355

primary actors, 139, 141

Principle of Least Surprise, 28

private operations, 182

private visibility, 57–58, 182, 340

procedural messages, 196

process modeling, activity diagrams for, 216

«process» stereotype, 331

programs. See software and system development; tools for UML modeling

project-oriented class diagrams, 119–127

property. See attributes

protected visibility, 57, 340

protocol state machines diagram

constructing, 310–312

definition of, 308–310

uses of, 14

«provided interface» stereotype, 328–329

proxy actors, 134–136, 138

pseudocode, for algorithms, 188

pseudostates

with concurrent substates, 305–308

definition of, 300–302

PSM (Platform-Specific Model), MDA and, 16

public operations, 181–182

public visibility, 57–58, 182, 340

pUML Web site, 373

---