EA baseline architecture, defining, 51-56
EA document, 50
EA (Enterprise architecture), 49, 300
developing, 49-58
integrating the solution into, 300
making a commitment to, 58
EA model, 50
business view elements, 51-52
impact on software design, 58
EA technical view architectures, 55-56
EAI (enterprise application integration), 346
ECMA International, 29
ECMA standards, 29
E-commerce web site, n-tier architecture for, 270
Elementary fact (in ORM), 221
diagram based on, 229
identifying, 221-224
E-mail, delivering to browsers, 13
E-mail system
n-tier architecture for, 270
Web-based, 310
Employment agency case study, 84-100
business process, 85
business requirements, 101-103
creating job seeker accounts, 93
database diagram for, 318
existing IT environment, 85
facts about candidates, 222
facts about jobs, 223
interviews with key personnel, 86
job seekers database, 85
job submission data flow diagram, 110
logical database design for, 316-318
matching jobs and candidates, 221
ORM model for, 220-238
parts of the business, 221
potential application objects, 288-289
requirements, 101-114
system renovation, 85
use case diagram for, 88-93
years of experience and skill level, 235
Encapsulation, defined, 291
Encoding methods for systems and data (regional), 113
Encrypting and decrypting data, 186
Enter Outlining Mode When Files Open (Visual Basic), 414
Enterprise
business view of, 50
technology view of, 50
Enterprise application, 437
Enterprise architecture. See EA
Enterprise deployment, 173
Enterprise Developer Edition (Visual Studio .NET), 24
Enterprise Ready Server (ERS), Apache, 30
Enterprise Services server application, 190
Enterprise technical architecture, 55
Enterprise templates, 22, 436-441
items in, 436-437
policy file in, 438-441
primary goals of, 437
Enterprise-level systems, n-tier architecture for, 270
Enterprise-wide business diagrams (Visio), 26
Entities, establishing relationships among, 252
Environmental risk, 67
Envisioning phase documents, analysis of, 147
Envisioning phase (MSF), 44-82, 84
deliverables for, 99
documents created, 69
ending milestone of, 99
requirements gathered, 99
ER diagrams, exporting ORM diagrams as, 238
ER (entity relationship) modeling, 212-215
vs. ORM, 214-215
zero-or-one-to-many relationship, 232
Ergonomics, in user interface design, 265
Error details displayed, types of users and, 344-345
Error handling, 122-123, 299-300
creating specifications for, 343-345
strategies for, 163-164
Error handling component, 345
Error handling methods, 344
Error icon (Event Viewer), 343
Error logs, 162, 298
Error message example (unhandled), 345
Errors
vs. exceptions, 163
how long it takes to fix, 116
intentional, 120
reported by exceptions, 300
ERwin database-modeling tool, 27
European Computer Manufacturers Association, 29
Event handler names, conventions for, 409
Event handling, bubbling of, 164
Event logs. See Logging; Logs
Event Properties dialog box (Windows), 342
Event severities, types of, 343
Event steps (use case), 111
Event Viewer (Windows), 341-342
event details in, 342
icons for event severities, 343
EventArgs suffix, 409
Event-based system, 291
EventLog component, 341
Events in a system, identifying potential, 289
Events that trigger actions, identifying, 291
Evidence-based security, 304
EWTA (Enterprise-wide technical architecture), 56
Exam preparation, 464-470
Exam 700-300 objective mapping document, 463-470
Exam 700-300 objectives, 464-470
creating a conceptual design, 467
creating a logical design, 467-468
creating a physical design, 468-470
creating standards and processes, 470
developing specifications, 466-467
envisioning the solution, 464
gathering and analyzing business requirements, 464-465
Exam simulation, 460
Excel, licensing, 363
Exceptions
vs. errors, 163
explained, 299
handling, 299-300
and level of monitoring, 163
passing back to previous objects, 299
for reporting errors, 300
Exclusive checkout mode (Visual SourceSafe), 434
EXE (binary executable) files, 267
Execution plans for application queries, 369
Expectations from the application, 156
Expected outcome (use case), 112
Experts in business activities, identifying, 102-103
Extends object (use case), 87, 92
Extensibility, 348
requirements, 104
validating, 372
External builds, 430
External dependencies, identifying, 103
External entities (data flow diagrams), 105
External entity, explained, 260
External uniqueness constraint, 315
External uniqueness (of facts), 232