Index_U


U

UDDI, 14-15

Umbrella approach to integration testing, 423

UML Actor Properties dialog box, 90

UML Association Properties dialog box, 91

UML class diagrams, 26, 286

UML diagrams, 26, 52-54, 250

UML documents, 250. See also Use cases

UML Shape Display Options dialog box, 92

UML specification, core diagrams in, 295

UML state diagram, 52-54

UML State Properties dialog box, 53

UML templates, 26

UML Transition Properties dialog box, 54

UML (Unified Modeling Language), 52, 145

in application design, 295-296

benefits of, 296

official web site for, 295

standard notation for, 296

UML Use Case dialog box, 91

UML version 2.0, 295

Unary facts, 223, 228

Unauthorized access, corruption via, 119-120

UNC (universal naming convention) share, 433

Unclustered index, 369

Underscores, conventions for using, 409

Unhandled error message example, 345

Unicode character-encoding standard, 166-167

Unique keys, managing, 370

UNIQUEIDENTIFIER data type (SQL Server), 313

Uniqueness constraints (ORM diagram), 231-233

Unit test for components, 422

Unix, .NET for, 30

Unix servers, on the Internet, 8

Unmanaged code, defined, 19. See also COM components

Unmanaged programming, 358

Unstructured programming, 4

UP (Unified Process), 49

Updates to database rows, asynchronous process for, 308

Upgrade deployment issues, 365

Upgrade path, designing, 365-366

Upgrades

reasons for, 193

strategies for, 193

while applications are running, 366

Usability, defined, 275

Usability experts, 275

Usability issues, categories of, 275

Usability testing, 274-275

Usage, profiling expected, 158-159

Usage scenarios (use case), 112

for subordinate use cases, 150

types of, 112

validating against artifacts, 150

validating logical design against, 321

Use case diagrams

creating, 88-93

refining, 150

types of, 112

Use case objects, 87-89

Use case process, building, 93-94

Use cases, 87-93

creating subordinate, 150

elements of, 111

explained, 111, 250

identifying, 111-113

keywords for, 87-88

for testing the application, 296

usage scenarios for subordinate, 150

and user documentation, 392

validating against artifacts, 150

validating against user responses, 150

validating logical design against, 321

Use External (IIS version-control) option, 436

User categories, 95

User characteristics, 263-264

User in control, concept of, 416-417

User controls, .NET and, 12

User data, temporary storage for, 359

User display configuration, support for, 357

User documentation, 391-393

formats, 392

XML tags in, 397-408

User expectations, performance and, 160

User experience

defined, 416

usability and, 275

User ID and password, 351, 353

User IDs, managing, 303

User IDs and timestamps, 298

User instruction, 102

User interface design, soft kills required for, 265

User interface designers, 265

User interface standards, 390-391, 416-421

User interface (UI)

aesthetics of, 418

avoiding use of modes in, 416

canceling a process, 419

careful organization of, 418

checklist for good, 419-420

color schemes, 418

conceptual design, 262-265

consistency in, 417

with customizable icons, 417

directness in design of, 417

effective feedback in, 419

effectiveness and efficiency of, 275

familiar and predictable, 417

with forgiveness built in, 418

with interactive discovery, 418

issues of localized applications, 168

logical design, 306-307

multilingual, 167

password fields with asterisks, 305

personalizable, 416

simplicity of, 418

text-based, 306

that provides the state of a process, 419

that provides warnings to users, 418

using familiar metaphors in, 417

using visual clues in, 417

for web services, 306

User list, to receive targeted e-mails, 86

User login and logout, auditing, 298

User navigation, designing, 356

User profiles, 95

creating, 95

defined, 263

gathering, 263-264

information in, 95-96

problems when retrieving, 299

User requests, long-running, 359

User requirements, 149

assessing, 111-114

breaking down into tasks, 290

common understanding of, 145

comparing logical design with, 320

conceptual design compared with, 274

extracting verbs from, 289-290

validating physical design against, 371

User responses, validating use cases against, 150

User responsibilities and interactions, 95

User session data, storing, 361

User sessions

explained, 310, 359

managing, 310

User stories. See Use cases

User support plan, creating, 194

User training, 149

limiting need for, 421

security and, 353

User usability, 149

User use case, 112

Users

categories of, 263

client installation for untrained, 117

communicating with, 391

in control, 416-417

expectations and needs of, 95

presenting UI design to for approval, 306

promising very high availability to, 348

security context for, 303

shadowing, 102

types of, 95

understanding potential, 263

verifying with role-based security, 189




MCSD Analyzing Requirements and Defining. NET Solutions Architectures Study Guide (Exam 70-300)
MCSD Analyzing Requirements and Defining .NET Solutions Architectures Study Guide (Exam 70-300 (Certification Press)
ISBN: 0072125861
EAN: 2147483647
Year: 2003
Pages: 94

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net