Daily build process steps, 430
Daily builds, 430
DAO (Data Access Objects), .NET and, 12
Data, multiple routes to, 156
Data about to expire, calling a function when, 361
Data access types, with external applications, 346
Data archiving, strategies for, 192-193
Data block (localization), 167
Data changes, history of, 339
Data encoding methods (regional), 113
Data encryption, 354-355
Data entry application, 287
hierarchical diagram, 265
saving a record in, 307
Data exchange between applications, 165, 347
Data exchange standards, 165
Data Flow Connectors, in VEA DFDs, 262
Data flow diagrams. See DFDs
Data flow object (Gane-Sarson model), 106-107, 109
Data Flow object (Visio application), 107, 109
Data flow requirements, 121-123
Data flows (in data flow diagrams), 105
Data format, for sharing with clients, 86
Data integrity, in relational database, 169
Data interoperability, 165
Data layer (application), 269
Data migration
considerations for, 364
defined, 364
strategies for, 183-184
Data migration script
log file in, 365
running several times, 365
Data migration specifications
creating, 364-365
purpose of, 364
Data model
building, 312-319
creating the physical design for, 368-370
Data privacy
creating the logical design for, 305
vs. data safety, 305
strategies to ensure, 186-191
Data purging, 193
Data requirements
conceptual model of, 220-238
defining, 104-105
Data safety, vs. data privacy, 305
Data sharing, transaction servers for, 271
Data storage, strategies for, 168-169
Data storage architecture, 272-274
Data storage needs, 192
Data store object (Gane-Sarson model), 106
Data stores
in data flow diagrams, 105
defined, 260
in VEA DFDs, 262
Data tier, 85-86
Data types, 105
language-specific, 10
.NET built-in, 17
Database changes, logged details of, 340
Database connection, error handling for, 344
Database design, 212-248, 312-319
converting conceptual to logical, 315
creating logical, 316-318
three phases of, 213-214
validating logical, 319-322
Database design model (physical), creating, 368-370
Database diagram for employment agency example, 318
Database errors, identifying potential, 299
Database modeling concepts, 315
Database Project template (Visual Studio .NET), 22
Database schema, 213, 286. See also ORM diagrams
Database schema design, 220-238
Database server, use of indexes, 369
Database table
horizontally partitioned, 370
primary key for, 312
stored on multiple database servers, 370
Database table constraints, 313-314
Database transactions. See Transactions
Databases
benefits of well-designed, 312
keys and constraints, 312-314
sorting by primary key, 313
splitting over many machines, 270
Data-oriented applications, 287, 295
Data-oriented system
identifying objects in, 288-289
nouns as potential objects in, 288
Datasets (.NET), 18
Date object (calendar application), 292-293
Date the software will release, 442
Date and time considerations, 301
Dates (locale-aware), 114
DBA analysis of performance bottlenecks, 370
DBA (database administrator), 370
DBMS (database management system), 214
DBMS physical data model, 168-169
DCOM (Distributed COM), 6-8, 269
complex deployment model for, 8
vs. .NET, 8-10, 16
DDE (Dynamic Data Exchange), .NET and, 12
DDL (Data Description Language) scripts, 26
Debug build vs. release build, 429
Debug logs, 298
Debug process (local host projects), 433
Debug process (remote host projects), 433
Debugger (Visual Studio .NET), 28
Debugging after deployment, designing for, 366
Decipher, 186
Decision point (go or no go), 62
Decisions that must be made by the system, 254
Declarative role-based security, 189
Declarative security check, 189
Default build configurations, 430
Default constraint (database table), 314
DEFAULTSETTINGS node in policy file, 440
Definition and flow of data, charting, 104
Deliverables, 195
Deliverables for the envisioning phase, 99
Denormalized database, 218
Department managers, as stakeholders, 98
Dependencies
critical, 149
identifying, 103
Dependent assemblies, located and loaded, 175
Dependent tasks, performance bottlenecks of, 307
Deployability, validating, 372
Deploying an application, 144
Deploying an upgrade, issues of, 365
Deployment, 144
defined, 361
for mission-critical applications, 367
strategies for, 172-173
Deployment builds, 430
Deployment documents, 394
Deployment guide (Microsoft TechNet), 362
Deployment model
defined, 361
developing, 361-366
Deployment path, 117
Deployment phases for .NET applications, 173
Deployment plan, 170-172
Deployment requirements, 117
Deployment scenarios, 173
Deployment scripts, 394
Deployment specifications, creating, 362-363
Deployment strategy, selecting, 170-173
Design, validating, 425
Design documents, envisioning and planning phases, 46
Design flaws, detecting, 425
Design goals
defining, 104
examples of, 104
of extensibility requirement, 104
Design review, 425-429
Destruction, protection against, 120
Developer documentation, 391, 394-395
Developer response documents, 395-403
Developers (.NET)
assigning tasks and responsibilities to, 395
web site for, 6
who jump right into coding, 250
Developing an enterprise architecture, 49-58
Developing for Windows DNA infrastructure, 7
Development, approach to, 47
Development database, pre-populating for testing, 365
Development documentation, reviewing, 425-429
Development environment verification, 161
Development environment (Visual Studio .NET), 23-26
Development models for web applications, 434-436
Development phase, builds during, 430
Development phase for example project, 65
Development plan, 161-162
Development process, 47, 161
Development process phases, 47
Development strategies, 144, 161-170
Development tasks, defining, 151
DFDs (data flow diagrams), 252, 257-262, 347
comparing with conceptual database design, 274
creating, 105-110
creating in VEA, 261-262
data flow, 260
databases and data stores, 260
defining inputs and outputs, 258
explained, 105
external entities, 260
high-level, 258-259
input and output, 258-259
items typically depicted in, 259
levels of granularity, 258
low-level, 259
notation objects, 105
notations for drawing, 259
processes, 259
rules for creating, 261
treating the system as modularized, 259
Yourdon & Coad methodology for, 259-260
Dialect considerations, 301
Differential backup, 192
Digital certificates, 351
Digital signature, 304
Direct users, 95
Directory structure, enterprise template for, 437
Disabilities, accessibility for, 98-99, 114-125, 372-373
Disaster recovery plans, 349
Disciplines (MSF), 45, 47-48
Disconnected recordsets, 18
Distributable applications, using COM to create, 7-8
Distributed processing, transaction servers for, 271
Distributed web and n-tier applications, 6-7
Distributing the load across multiple servers, 153
Distributing traffic across servers, 157
Distribution methods for applications, 173
Distribution phase (deployment), 173
Diverse deployment, 164
DLLs (dynamic link libraries), 10, 173, 267
DNA paradigm, 7
Document reviews, 390
Documentation, 395-403
as a communication tool, 391
as a manual, 392-393
as screen shots and instructions, 392
design review, 425-429
and discovering new issues, 391
vs. face-to-face discussions, 391
logical design documents, 287
purpose of, 391
to support maintenance, 366
time and resources applied to, 391
UML for, 296
Documentation documents, types of, 391
Documentation standards, 390-408
DOS, 21, 306
DOS box, 21
DOS (denial of service) attack, 352
Download speed of HTML and ASP pages, 85
Downloads, incremental, 173
Downtime
acceptable amount of, 156
minimum average of time without, 116-117
Duffy, Scott, 16, 49, 219, 275, 296, 349
Duplication of data, reducing, 219