|
|
 |
|
|
|
MCSD Self-Paced Training Kit: Analyzing Requirements and Defining Microsoft® .NET Solution Architectures, Exam 70-300
|
|
|
Author
|
|
Microsoft Corporation
|
|
|
Pages
|
528
|
|
Disk
|
1 Companion CD(s)
|
|
Level
|
All Levels
|
|
Published
|
04/02/2003
|
|
ISBN
|
9780735618947
|
|
Price
|
$69.99
To see this book's discounted price, select a reseller below.
|
|
|
|
|
|
|
|
|
Index
A
accessibility aids, 264-65
accounts, service, 340, 346-47
achievable characteristic, 93
active shadowing, 40-41
activity diagrams, UML, 221, 228
actors. See also customers; users
catalog, 55, 90
defining interactions between systems and, 71
identifying, 70
acyclic ring constraints, ORM, 68
administrative features, 371-74
data migration, 373
licensing specifications, 374
monitoring, 371-73
ADO.NET security, 337-38
Adventure Works Cycles case study
application requirements, 31-33
business problems, 25-31
business tasks, 31
change management decisions, 104-5
class model and component model diagram, 247
component and data topology, 231
conceptual model, 156
conceptual model diagram, 164
data types, 293-94
database schema, 287-88, 314
deriving use cases from interviews, 79
draft requirements document, 54, 79
engineering department problems, 31
human resources department problems, 27-28
information systems department problems, 29
interviews, 51-52, 78
logical object model, 196-97
network topology, 230
production department problems, 30
project structure document, 104-5
purchasing department problems, 28-29
refining use cases and requirements, 163
sales department problems, 26-27
scenario, 25, 114-16
sequence diagrams, 196, 209
services matrix, 209
solution concept, 100
system administration department problems, 30
test plan and technical specification, 382-84
threat modeling and mitigation, 349
usage scenarios, 75-76, 80, 149-51
use case diagram, 52-53
user interface prototype, 269-73, 279-80
vision/scope document, 103, 114-17
Web site requirements, 32-33
World Wide Importers acquisition department problems, 28
aggregation relationships, 189-90, 191
alpha code tests, 400
analysis, information. See information analysis
analysis, risk, 8, 111. See also risk management process, MSF
analysis step, conceptual design, 143-56
categorizing requirements, 146-48
conceptual design and, 141. See also conceptual design
conceptual model, 152-56
deliverables, 144
refining use cases diagrams, 148-51, 163
restating requirements, 144-45
tasks, 143-44
viewing conceptual model diagram, 164
analysis step, logical design, 175, 180-93
attributes, identifying, 188-89
candidate business objects, identifying, 184-86
creating services matrix and sequence diagram, 209
logical design and, 175, 184. See also logical design
objects from use cases, identifying, 208
refining list of candidate technologies, 180-84
relationships, identifying, 189-93
services, identifying, 186-87
analysis step, physical design, 225-31
creating preliminary deployment models, 229-31
refining UML models, 225-29
antisymmetric ring constraints, ORM, 68
appearance, user interface, 259-60
appendixes, functional specification, 137
applications. See also projects; solutions
architectures, 153-55
builds, 14, 20, 399, 404
case studies. See Adventure Works Cycles case study; Web e-commerce site example
failure and reliability, 363, 372
features, 10-11, 365
information, 38-39
interoperability, 366-67
monitoring, 371-73
optimizing, 298
performance. See performance
prototype, 20. See also prototyping
servers, 239
state. See state
stress testing, 21, 299, 400
architecture
application, 153-55
enterprise, 38, 49-50, 181-82
solution, 18
artifacts, 41, 46, 131
ASP.NET. See Microsoft ASP.NET
assess step, readiness management, 9
assistance, user, 263-65
association relationships, 189-90, 191
assumptions
constraints vs., 77. See also constraints; requirements
functional specification, 136
project scope and, 98
asymmetric ring constraints, ORM, 68
asynchronous control, 183, 205, 243, 359
atomicity, ORM, 64
attitudes, user, 44
attributes
example, 189
identifying, 184, 188-89
logical data model, 198
physical data model, 289-91
auditing, 182, 347-48
authentication. See also authorization
ASP.NET, 335
role-based security and, 333-34
strategies, 341
technology and, 182
for user process components, 346
for Web-based user interface components, 344-45
for Windows-based user interface components, 346
authenticity, code, 331
authorization. See also authentication
for business components, 343
choosing identities, 340
for data access components, 343-44
identifying resources for, 340
identity flow, 341, 342
role-based security and, 333-34
strategies, 339-42
technology and, 182
for user interface components, 342-43
for user process components, 343
automated testing, 404
availability, 360-62
definition, 360-61
planning levels of, 361
requirements, 147
techniques for, 361-62
B
backup
plan, 413
services, 152
baseline deliverables, 129
baseline deployment model, 221
behavioral view, UML, 59
beta code tests, 400
boundary, system, 71-72
brainstorming, 160, 224, 325
buddy tester principle, 398
budget. See costs
buffer overrun, 321
bug convergence milestone, 22, 393-94
bugs
categorizing, 401-2
prioritizing, 421-22
tracking, 21, 378, 403-4
builds, 14, 20, 399, 404
business
candidate technology considerations, 180-81
context and design, 234
contingency plans, 111, 413
draft solution concepts for, 100
goals, 15, 17, 101
information, 38
objects, 184-86. See also objects
problems for case study, 25-31
requirements, 17, 147-48
rules. See business rules
services, 152-53
solutions. See Microsoft Solutions Framework
sponsor role, 7
tasks for case study, 31
business process reengineering experts, 157-60
business rules
catalog, 55-56, 90
database features for implementing, 311-12
identifying, 310-11
programmatic features for implementing, 311-13
C
cache architecture, 155
caller impersonation, 347
candidate business objects, 184-86. See also objects
candidate requirements, 138. See also requirements
candidate technologies, 176, 180-84
business considerations, 180-81
enterprise architecture considerations, 181-82
logical design and, 176. See also logical design
technology considerations, 182-84
candidates, release, 22, 395. See also releases
capacity testing, 21
cardinality, 199
case study. See Adventure Works Cycles case study
casual code review, 404
categorization, bug, 401-2
change control systems, 404
change management decisions, project structure document, 104-5, 109
change step, readiness management, 9
check-in tests, 399
ciphertext, 332
classes. See also components; objects
class model, 247
Class-Responsibility-Collaboration (CRC) cards, 194-95
relationships and, 190
UML class diagrams, 59, 221, 226-27
clients
client-side checks, 309
environments, 267-69
state management, 233
client/server architecture, 154
closeout activities, 419-20
clustered indexes, 300
code
alpha and beta tests, 400
developing phase and, 20
reviews, 404
secrets, 321
signing, 331
source, 21, 22
type-safe, 330
code-access security, 332-33
cohesion, 234-35, 240, 242
coincidental cohesion, 235
collaboration diagrams, UML, 60
colors, user interface, 259
columns
logical data model, 198, 199
physical data model, 291-95
COM+ services, 335-36
Common Language Specification (CLS), 367
communication, cross-boundary, 299
communication decisions, project structure document, 107-8
communicational cohesion, 235
commutative processes, 359
compatibility tests, 400
components. See also classes; objects
authentication strategies, 344-47
authorization strategies, 339-44
component model diagram, 247
component specifications, 221
core, vs. site specific, 414
deploying core, 23, 414-15
deploying site-specific, 415-18
distributing preliminary, 236-38
implementing data validation in, 313
packaging, 235-36
solution core, 20
specifying interfaces, 244-45
testing, 21
topology, 221, 231
UML component diagrams, 59, 221, 229
user interface, 255, 256-58. See also user interface design
user process, 275-78. See also user process component design
validating and refining, 239-40
composite keys, 294
composition relationships, 189-91
comprehensive code review, 404
conceptual design, 123-70
analysis step, 143-56. See also analysis step, conceptual design
communicating requirements through modeling, 139
developing requirements, 138
example, 163-64
functional specification and, 131-37. See also functional specification
goals, 140
logical design and, 173, 175, 177. See also logical design
MSF Process Model and, 139-40. See also Process Model, MSF
optimization step, 157-62. See also optimization step, conceptual design
planning phase and, 18, 127-28, 139-40, 171-72. See also planning phase
refining requirements, 76
research step, 142
steps, 128, 141-42
summary, 134
conceptual model, 152-56
application architectures, 153-55
diagram, 164
example, 156
services, 152-53
validating, 161-62
conceptual schema design procedure (CSDP), ORM, 62-68
configuration
settings deliverable, 21
tests, 399
connected vs. connectionless modes, 242-43
constraints
assumptions vs., 77. See also assumptions
identifying physical, 223
ORM. See constraints, ORM
performance, 365
project scope and, 98
resolving conflicts between requirements and, 224. See also requirements
constraints, ORM, 62, 64-68
entity subtype, 67
mandatory role, 65
ring, 67-68
set, 66
uniqueness, 64-65
value, 66
context, business, 234
context-sensitive Help, 264
contingency plans, 111, 413
control
in logical design, 205-7
models, 205-6
risk, 8, 111
user interface, 207, 257
cookies, 233
core components, 20, 414-15
core components deployed milestone, 23
core team organized milestone, 16
costs
as constraint, 98
interoperability and, 366
product, 180-81
project team and, 89
redesign, 160
coupling, 235, 240, 242
coverage testing, 398
cryptographic hashing, 332
cultures, 367-70
current state. See also state
assessing, 15
business rule, 56
enterprise architecture, 49-50, 181-82
logical object model, 203-4
usage scenarios, 73-76
custom identity, 340
customers. See also actors; users
functional specification and, 133
pilot and, 405, 407
project structure document and, 106-7
roles, 7
satisfaction data, 24, 419
sign-off, 409, 413, 418, 420
D
daily builds, 14, 20, 399, 404
data
access. See data access
databases. See databases
design. See data layer design
format checking, 308
integrity, 300, 307-10
interoperability, 366
migration plan, 373
models. See logical data models; physical data models
services, 152-53, 313
signing, 331-32
storage, 182, 334, 362. See also data store design
topology, 221, 231
types, 292-94, 308, 311
validation. See data validation
data access
indexes and, 300
optimizing, 298-306
technology and, 182
data layer design, 285-318
auditing strategies, 348
authorization strategies, 343-44
best practices for optimizing data access, 298-99
business rules, identifying, 310-11
business rules in databases, implementing, 311-13
creating data schema, 314
data integrity, 307-10
data integrity requirements, identifying, 309-10
data store design, 286-97
data validation, implementing, 307-13
data validation in components, implementing, 313
database schemas, 286-89, 314
entities and attributes, identifying, 289-91
indexing data, 300
normalizing data, 301-6
optimizing data access, 298-306
partitioning data, 300-301
planning phase and, 285. See also planning phase
relationships, implementing, 295-97
tables and columns, identifying, 291-95
data store design, 286-97
database schemas, 286-89
identifying entities and attributes, 289-91
identifying tables and columns, 291-95
implementing relationships, 295-97
data validation, 307-13
business rules, 310-13
data integrity, 307-10
implementing in components, 313
methods, 308-9
database schemas, 286-89. See also data store design
creating, 314
defining, 287-88
physical design deliverables, 221
types of physical data models, 288-89
databases. See also data
business rules and features of, 311-12
database management systems (DBMSs), 288-89
database model, 246
optimizing, 299-306
schemas. See database schemas
servers, 239
testing, 21
decisions, project structure document, 106-9
decryption, 332
default values, 260, 311
define step, readiness management, 8-9
deliverables. See also documents
conceptual design analysis step, 144
conceptual design optimization step, 157
deploying phase, 24
developing phase, 21
envisioning phase, 17, 90
physical design, 218, 220-21
physical design rationalization step, 232
physical design research step, 223
planning phase, 19, 129-30
stabilizing phase, 22, 392-93
user interface design, 274
denial of service, 325
denormalization, 305-6
dependencies, component, 205, 229
dependency relationships, 189, 191
deploying phase, 410-20
closeout activities, 419-20
configuration settings deliverable, 21
core components vs. site-specific components, 414
customer sign-off, 413, 418, 420
deploying core components, 414-15
deployment models. See deployment models
deployment plan, 379-80, 413
deployment scenarios, 411
documentation, 412-13
milestones and deliverables, 5, 23-24, 410
MSF Process Model and, 4-5. See also Process Model, MSF
pilot and, 405, 407
project team roles and responsibilities, 410-11
quiet period, 418
site deployment, 415-18
staging and production environments, 412
tasks, 23
transferring projects to operations and support, 418-19
UML deployment diagrams, 59, 412
Deploying Phase, The, 260
deployment complete milestone, 5, 23, 24, 410
deployment models
baseline, 221
creating, 238-39
creating preliminary, 229-31
validating and refining, 239-40
deployment stable milestone, 23-24
derivation rules, ORM, 62
design
data layer. See data layer design
distribution and packaging strategy issues, 234
goals, 102
issues. See design issues
presentation layer. See presentation layer design
programming model issues, 242-44
redesigning processes, 158-60
security. See security design
stages of planning phase, 18, 127-28, 171-72. See also conceptual design; logical design; physical design
design issues, 356-70
availability, 360-62
globalization and localization, 367-70
interoperability, 365-67
performance, 364-65
reliability, 362-64
scalability, 356-60
developing phase, 20-21
deliverables, 21
development plan, 375-77
development tools, 183-84
milestones, 5, 20-21
MSF Process Model, 4-5. See also Process Model, MSF
project team and customer roles and responsibilities, 106-7
tasks, 20
development and test environments set up milestone, 19
development environment, 18, 19, 375, 404
development role, 6-7, 89, 129, 397
diagrams
activity, 221, 228
component, 221, 229
component model, 247
conceptual model, 164
deployment, 412
sequence, 195-96, 209, 221, 227-28
UML, 59-60. See also Unified Modeling Language
use case, 52-53, 72, 96, 148-51
directory servers, 239
disabilities, accessibility aids and, 264-65
disaster recovery plan, 413
disciplines, MSF, 7-10
project management process, 9-10
readiness management process, 8-9
risk management process, 7-8. See also risk management process, MSF
distribution
preliminary components, 236-38
programming model and, 243
strategies, 221, 233-34
documentation
internal project team, 55-56, 90
repository, 24
technical specification, 382
tests, 400
document-based user interfaces, 267
documents. See also deliverables
draft requirements. See draft requirements documents
living, 14
project deliverable, 22
project final, 24
domain integrity, 307
downtime, 361-62
draft requirements documents, 51-54
developing, from initial information gathering, 79
example, 54
example interview, 51-52
example use case diagram, 52-53
E
e-commerce Web site. See Web e-commerce site example
elementary facts, ORM, 61
elevation of privilege, 325
encapsulation, high-level, 206
encryption, 331-32
end user, 7. See also users
engineering department problems, case study, 31
enterprise architecture
candidate technology considerations, 181-82
information, 38, 49-50
Enterprise Services security, 335-36
entities
as actors, 70
logical data model, 198
ORM, 63, 64
ORM primitive types, 64
ORM subtype constraints, 67
physical data model, 289-91
entity integrity, 307-8
entity relationship (ER) diagrams, 287-88
environment view, UML, 59
environments
client, 267-69
development and testing, 18, 19, 375, 404
staging and production, 412
test, 373
envisioning phase, 85-121
conceptual design and, 139
deliverables, 17, 90
forming project teams, 89
milestones, 5, 16
moving to planning phase from, 126-27
MSF Process Model and, 4-5, 15-17, 86-87. See also Process Model, MSF
project structure document, 104-9
project team roles and responsibilities, 88-89
purpose, 86-88
refining requirements, 76
risk management process, 110-13. See also risk assessment document
tasks, 15-16
vision/scope document, 91-103, 114-17. See also vision/scope document
error detection, 372
error handling services, 152, 243
error logging, 371, 381
estimates
project scope and, 99
project structure document and, 105
evaluate step, readiness management, 9
evaluating redesigned processes, 160
event handling, 261
event logs, 372
events, 195
exceptions, usage scenario, 73
executable files deliverable, 21, 22
existing processes. See current state
experience, 181
experts, 40, 45, 47, 157-60
exposure, risk, 111, 112-13
Extensible Markup Language (XML), 291, 367
external coverage testing, 398
F
facts, ORM, 61-64
failure, application, 363, 372
feasibility, 180
features
performance and, 365
tradeoffs and, 10-11
files
executable, 21, 22
project, 107
final project documents, 24
final release deliverable, 22
first normal form, 302-3
flat-file databases, 289
focus groups, 43-44
foreign keys, 199, 295
formatting, globalization and localization, 368
FORML (Formal Object-Role Modeling Language), 61, 65-68
Forms authentication, 335
function calls, in-process vs. out-of-process, 242
functional cohesion, 234
functional dependency, ORM, 65
functional specification, 131-37
elements, 134-37
finalized, 21
goals, 132-33
planning phase and, 17-19, 123, 129, 215. See also planning phase
purpose, 131-32
risks of not creating, 133-34
functional specification complete milestone, 19
functional tests, 399
future state. See also state
enterprise considerations, 181-82
optimizing processes for, 157-60
usage scenarios, 74
G
gathering information. See information gathering
generalization relationships, 190-91
globalization
best practices, 369-70
issues, 368-69
localization vs., 367-68
glossary, 56, 90, 263
goals
business goals, 15, 17, 101
conceptual design, 140
design goals, 102
developing example, 117
functional specification, 132-33
performance, 364-65
physical design, 219-20
types of, 101-2
user profile, 94
golden release milestone, 22, 396
granularity, designing for, 234
groups, focus, 43-44
H
handheld computers, 266-67
hardware
core vs. site-specific, 414
solutions, 411
testing, 404
hashing, cryptographic, 332
Help, 260-61, 263-64
help desk, 45, 380
Help file tests, 400
hidden requirements, 77
hierarchical databases, 289
high cohesion, 240
high-fidelity design, 262-63
high-level encapsulation, 206
high-level use cases and usage scenarios, 50
history, project, 135
horizontal partitioning, 301
HTML (Hypertext Markup Language), 266, 335
human resources department problems, case study, 27-28
I
identification, risk, 8, 111
identities
drawbacks of, 321
flow of, 341, 342
resource access, 340
spoofing, 324, 333
IIS authentication, 335, 341, 345
impact, risk, 112
impersonation, 341, 347
implementation step, physical design, 241-46
database model, 246
programming model, 241-44
specifying component interfaces, 244-45
user interface model, 245
implementation technologies, 242
implementation view, UML, 59
Improving Performance with Object Pooling, 359
independent code review, 404
indexed sequential access method (ISAM), 289
indexing data, 300
individual object verification, 203
information, 37-83
analyzing, 49-56. See also information analysis
application, 38-39
business, 38
categories, 38-40
deriving draft requirements, 79
deriving use cases from interviews, 79
developing usage scenarios, 80
gathering, 38-48. See also information gathering
modeling notations, 57-68. See also modeling
operations, 39
preparing for interviews, 78
sources, 46-47
synthesizing, 144
technology, 39-40
use cases and usage scenarios, 69-77. See also usage scenarios; use cases
information analysis, 49-56. See also information
draft requirements documents, 51-54, 79
enterprise architecture information, 49-50
high-level use cases and usage scenarios, 50. See also usage scenarios; use cases
internal project team documentation, 55-56
information disclosure, 325
information gathering, 38-48. See also information
artifacts, 41, 46
categories of information, 38-40
developing draft requirements from initial, 79
focus groups, 43-44
interviewing, 42-43
people and, 47
pilots and, 407-8
preparing for interviews, 78
prototyping, 45
shadowing, 40-42
sources of information, 46-47
strategies, 47-48
surveys, 44
systems and, 46-47
user instruction, 44-45
Information Modeling and Relational Databases: From Conceptual Analysis to Logical Design, 62
information sources, 46-47
artifacts, 46
people, 47
systems, 46-47
information systems department problems, case study, 29
infrastructure testing, 21
input validation, 260
installation
functional specification summary, 136
scripts, 21
site deployment, 417
instances, ORM, 62
instruction, user, 44-45
integration
functional specifications requirements summary, 136
testing, 21
integrity
code, 331
data, 300, 307-10
transactional, 205
interchangeable processes, 359
interdependencies, object, 205
Interface Definition Language (IDL), 244
interfaces, component, 190, 244-45, 381
interim milestones. See also milestones
developing phase, 20-21
envisioning phase, 16
planning phase, 19
stabilizing phase, 393-96
internal builds complete milestone, 20
Internet connections, 321
interoperability, 365-67
designing for, 366-67
reasons for, 366
interviews
deriving draft requirements document from, 51-52
deriving use cases from, 52-53, 79
as information gathering technique, 42-43
preparing for, 78
intransitive ring constraints, ORM, 68
intuitive design, user interface, 259
inventory, objects and services, 226
IP spoofing, 324
irreflexive ring constraints, ORM, 67
isolated storage, 334
iteration, 12-14
daily builds, 14
living documents, 14
versioned releases, 13-14
K
key performance indicators, 397
keys, relational database, 199, 294-95, 312
knowledge, project team and, 89
knowledge base, 24, 419
L
language issues, globalization and localization, 368, 369-70
languages, programming, 183, 244-45, 266, 335
layered architecture, 154
layered-client-cache-stateless-cache-server architecture, 155, 218
layers, service, 235-36
learning, risk, 8, 111
least privilege principle, 322
legal requirements summary, 137
level of privilege, 333
licensing specifications, 374
lifetimes, object, 195-96
living documents, 14
load
performance and, 365
stress tests, 21, 299, 400
localization
best practices, 369-70
globalization vs., 367-68
issues, 368-69
location transparency, 357-58
log handling plan, 413
logbooks, 24
logging
auditing, 182, 347-48
error, 371, 381
event, 372
logical boundary objects, 226
logical control objects, 226
logical data models, 176, 198-200
defining columns, 199
defining relationships, 199-200
defining tables, 198
identifying entities and attributes, 198
logical design, 171-213
analysis step, 175, 180-93. See also analysis step, logical design
benefits, 177
creating services matrix and sequence diagram, 209
establishing control, 205-7
functional specification summary, 134-35
high-level user interface design, 200-201
logical data model, 198-200
logical object model, 196-97
modeling relationships, 194-96
MSF Process Model and, 173-75. See also Process Model, MSF
optimization step, 175, 202-7
outputs, 176-77, 194-201
physical design vs., 219. See also physical design
planning phase and, 18, 127-28, 171-72
project team roles and responsibilities, 178-79
purpose, 176
refining objects, 202
refining requirements, 76, 98
tasks, 175
verifying existing logical object model, 203-4
logical entity objects, 226
logical object models, 176, 196-97, 203-4, 381
logistical decisions, project structure document, 108
loose coupling, 235, 240
low-fidelity design, 262-63
M
maintenance, data validation and, 313
major milestones, 16. See also milestones
manageability
designing for, 234
requirements, 147
management interoperability, 367
mandatory role constraints, ORM, 65
many-to-many relationships, 297
master plan complete milestone, 19
master project plan, 18, 19, 129
master project schedule, 19, 129
master project schedule complete milestone, 19
master risk assessment document, updated, 129
matrix, project tradeoff, 11-12
maturity, 181
meaningful sample population, ORM, 64
measurable characteristic, 93
menus, 260-61, 369
messaging services, 152, 183
methods, 257
metrics, performance, 364-65
Microsoft ASP.NET
as development tool, 184
security, 335, 341, 345
Web-based user interface, 255, 266
Microsoft BizTalk Server, 239
Microsoft Host Integration Server, 239
Microsoft .NET Framework. See .NET Framework
Microsoft Solution Accelerator for the Internet Storefront, 112
Microsoft Solutions Framework (MSF), 1-14
disciplines, 7-10
iteration in projects, 12-14
Process Model, 3-5. See also Process Model, MSF
process models and, 2-3
Team Model, 5-7. See also project teams; roles, project team
tradeoff management, 10-12. See also tradeoff management
Microsoft SQL Server security, 337-38, 348
Microsoft Visio, 37, 57, 60, 61
Microsoft Visual Basic .NET, 183
Microsoft Windows. See Windows
Microsoft Windows Forms, 255, 265
migration plan, 373
milestone review deliverable, 22
milestones
deploying phase, 23-24
developing phase, 20-21
envisioning phase, 16
interim vs. major, 16. See also interim milestones
MSF Process Model, 4-5
planning phase, 19, 129-30
stabilizing phase, 22, 393-96, 409
mitigation
risk, 17, 111
threat, 323, 328-29
mobile device user interfaces, 266-67
modeling, 57-68
benefits of, 57
class models, 247
conceptual design and, 139
conceptual model. See conceptual model
control models, 205-6
database models, 246
deployment models, 238-39
drawbacks of traditional security models, 321
logical data models, 176, 198-200
logical object models, 176, 196-97, 203-4, 381
Object Role Modeling, 57, 61-68
physical data models, 288-89
preliminary deployment model, 221, 229-31
process models, 2-3. See also Process Model, MSF
programming model, 221, 241-44
relationships, 194-96
threat models, 323-28
Unified Modeling Language, 57-61. See also Unified Modeling Language
usage scenarios and use cases, 124. See also usage scenarios; use cases
user interface models, 245, 265-67
Model-View-Controller (MVC) pattern, 257
modules, 180
monitoring plan, 371-73
MSF. See Microsoft Solutions Framework
multiple-user control model, 206
multiplicity, 199
mutual exclusivity, ORM, 64
N
names, strong, 331
navigation, user interface, 260, 263
.NET Framework
globalization and localization namespaces, 367
interoperability, 367
programming model, 183
.NET Framework security features. See also security design
ADO.NET and SQL Server, 337-38
ASP.NET, 335
code signing, 331
code-access security, 332-33
encryption and data signing, 331-32
Enterprise Services, 335-36
isolated storage, 334
.NET remoting, 337
.NET technologies and, 334-38
role-based security, 333-34
type safety verification, 330-31
Web services, 336
.NET remoting security, 337
network
environment, 267-69
interoperability, 366
topology, 221, 230
network load balancing (NLB), 362
next steps definition, 24
nonclustered indexes, 300
normalizing data, 301-6
benefits, 301-2
denormalization, 305-6
first normal form, 302-3
second normal form, 303-4
third normal form, 304-5
notations, modeling. See modeling
notifications, 372
O
Object Role Modeling (ORM), 61-68
adding ring constraints, 67-68
adding value constraints, set-comparison constraints, and subtype constraints, 66-67
analyzing and transforming external information into elementary facts, 62-63
applying mandatory role constraints, 65
applying population checks to fact types, 64
applying uniqueness constraints, 64-65
conceptual schema design procedure, 62
features, 61-62
identifying primitive entity types, 64
object-oriented database management systems (ODBMSs), 289
objects. See also classes; components
auditing strategies, 348
authorization strategies, 343
candidate business, 184-86
class diagrams, 226
controlling, 206
example, 185-86
identifying, 185
identifying, from use cases, 208
interdependencies, 205
inventory, 226
logical design analysis and, 184
object models. See logical object models; physical data models
ORM object types, 63, 64
refining, 202
scalability and, 359
state, 242
UML object diagrams, 59
usage scenario, 73
verifying, for logical object models, 203
Official Guidelines for User Interface Developers and Designers, 259
one-to-many relationships, 296-97
one-to-one relationships, 295-96
online help, 263-64
operating systems, 184, 411
operations
information, 39
information systems, 24
procedures completion, 23
requirements, 17, 147
transferring projects to, 24, 418-19
operations role, 7, 410-11
optimization, data access, 298-306
application optimization, 298
best practices, 298-99
cross-boundary communications, 299
database optimization, 299
indexing data, 300
normalizing data, 301-6
partitioning data, 300-310
stress testing applications, 299
transactions and, 299
optimization step, conceptual design, 157-62
conceptual design and, 141. See also conceptual design
evaluating redesigned processes, 160
optimizing processes for future state, 157-60
validating conceptual model, 161-62
optimization step, logical design, 175, 202-7
establishing control, 205-7
refining objects, 202
verifying existing logical object model, 203-4
original caller identity, 340
ownership, risk, 111
P
packaging
components, 235-36
strategies, 221, 233-34
parallel deployment, 415, 416
parallel testing, 400-401
partitioning
data, 300-301
scalability and, 360
services, 238
passive shadowing, 40
Passport authentication, 335
passwords, weak, 320
people, as information sources, 47. See also customers; users
performance
designing for, 234
goals and metrics, 364-65
key performance indicators, 397
monitoring, 372
normalization and, 302, 306
project team, 89
support elements, 21, 22
system performance plan, 413
tests, 21, 400
user instruction and, 45
phases, MSF Process Model. See Process Model, MSF
physical data models, 288-89
physical design, 215-51
analysis step, 225-31
class model, creating, 247
cohesion and coupling, 234-35
component model diagram, creating, 247
database model, 246
deliverables, 220-21, 232
deployment model, creating, 238-39
distributing preliminary components, 236-38
distribution and packaging strategies, creating, 233-34
functional specification summary, 135
goals, 219-20
implementation step, 241-46
logical design and, 175, 177, 199, 200, 219. See also logical design
MSF Process Model and, 216-19. See also Process Model, MSF
packaging components, 235-36
planning phase and, 18, 127-28, 171-72. See also planning phase
preliminary deployment model, creating, 229-31
presentation layer design and, 200, 253. See also presentation layer design
programming model, 241-44
project team roles and responsibilities, 220
purpose, 218
rationalization step, 232-40
refining UML models, 225-29
research step, 222-24
scope, 219
specifying component interfaces, 244-45
steps, 221-22
user interface model, 245
validating and refining distribution and packaging, 239-40
pilots, 405-8
evaluating results, 407-8
implementing, 407
outputs, 408
pilot plan, 378-79, 406-7
stabilizing phase and, 21, 392. See also stabilizing phase
steps, 405-6
plaintext, 332
planning, risk, 8, 111. See also risk management process, MSF
planning phase, 17-19
administrative features planning, 371-74
conceptual design and, 139-40
data layer design. See data layer design
data migration plan, 373
deploying phase deployment plan, 379-80
design issues. See design issues
design stages, 18, 127-28, 171-72. See also conceptual design; logical design; physical design
design tasks, 18
developing phase development plan, 375-77
functional specification, 131-37. See also functional specification
licensing specifications, 374
milestones and deliverables, 5, 19, 129-30
monitoring plan, 371-73
moving from envisioning phase to, 126-27
MSF Process Model and, 4-5, 125-26. See also Process Model, MSF
planning for future phases, 375-80
presentation layer design. See presentation layer design
project team and customer roles and responsibilities, 106, 128-29
purpose, 127
reviewing test plan and technical specification, 383-84
security design. See security design
stabilizing phase plans, 377-79
tasks, 17-18
technical specification document, 381-82
plans
backup and disaster recovery, 413
data migration, 373
deploying phase, 412-13
deployment, 379-80, 413
development, 375-77
monitoring, 371-73
pilot, 378-79, 406-7
project, 18-19, 129
risk mitigation and contingency, 19, 111, 413
rollback, 373
security, 412
site usage, 412
system performance, 413
test, 377-78, 383, 412
training, 24
political issues, globalization and localization, 370
pooling, object, 359
population, ORM, 62
population checks, ORM, 64
portal servers, 239
post-implementation reviews, 107
predicates, ORM, 63
prefix testing, 398
preliminary components, distributing, 236-38
preliminary deployment model, 221, 229-31. See also deployment models
component and data topology, 231
network topology, 230
preliminary risk assessment, 17
preparing for interviews, 78
presentation layer design, 253-84
creating user interface prototype, 279-80
elements of presentation layer, 255-56
inputs, 256
MSF Process Model and, 253-54. See also Process Model, MSF
physical design and, 245, 253
separating user processes from user interface, 276-77
user interface design. See user interface design
user process components design, 275-78
primary keys, 199, 294, 307-8
primitive entity types, ORM, 64
prioritization
bugs, 395, 402, 403, 421-22
risk, 111
tradeoff triangle and, 97
privilege
elevation of, 325
least, 322
level of, 333
probability, risk, 111, 112
problem statements, 15, 17, 92, 117
procedural cohesion, 235
procedures and processes, 24
Process Model, MSF, 3-5. See also Microsoft Solutions Framework
case study, 25-33. See also Adventure Works Cycles case study
as combined waterfall and spiral model, 3-4
conceptual design, 139-40. See also conceptual design
data layer design. See data layer design
deliverables. See deliverables
deploying phase, 23-24. See also deploying phase
developing phase, 20-21. See also developing phase
envisioning phase, 15-17. See also envisioning phase
information gathering and analysis. See information
iteration in projects, 12-14
logical design. See logical design
milestones and, 4-5. See also milestones
MSF Team Model, 5-7. See also project teams; roles, project team
phases, 4-5, 15-24
phases and UML views, 60-61
physical design. See physical design
planning phase, 17-19. See also planning phase
presentation layer design. See presentation layer design
security design and phases, 323-24. See also security design
stabilizing phase, 21-22. See also stabilizing phase
tradeoff management, 10-12
process models, 2-3. See also Process Model, MSF
processes
identity and, 340
optimizing, 157-60
scalability and, 359
separating user, from user interfaces, 276-77. See also user process component design
system, information, and, 46-47
product cost, 180-81
product management role, 6-7, 88, 129
production department problems, case study, 30
production environment, 412
profiles. See user profiles
program management role, 6-7, 10, 89, 105, 112, 128, 133
programming model, 241-44
design considerations, 242-44
physical design deliverable, 221
purpose, 241-42
progress assessment decisions, project structure document, 109
progress tracking, 9
project management process, MSF, 9-10
project plans approved milestone, 5, 19, 129, 220
project structure document, 104-9
change management decisions section, 109
communication decisions section, 107-8
elements, 105-6
envisioning phase and, 15, 17, 90
example change management decisions section, 104-5
logistical decisions section, 108
program management role and, 105
progress assessment decisions section, 109
project team and customer roles and responsibilities, 105, 106-7
project teams
forming, 15, 89
internal documentation, 55-56, 90
milestone, 16, 17
MSF Team Model roles, 5-7. See also roles, project team
project stakeholder members, 7
project structure document and, 104, 105
target future state and, 157
projects. See also applications; solutions
documents deliverable, 22, 24
estimates. See estimates
files, 107
goals. See goals
history, 135
iteration, 12-14
project plans, 18, 19, 129
review, 23, 419-20
schedules. See schedules
scope. See scope
sponsor role, 7
structure. See project structure document
teams. See project teams
transfer to operations and support, 418-19
proof-of-concept application complete milestone, 20
properties. See attributes
prototyping
applications, 20
information gathering and, 45
low-fidelity design vs., 263
user interfaces, 269-73
validating conceptual model, 162
purchasing department problems, case study, 28-29
pyramid, scalability, 358
Q
quality, 11
questions
actors, 70
attributes, 188
change management decisions, 109
communication decisions, 107-8, 204
information gathering, 48
interview, 43
logical decisions, 108
optimizing processes, 159
performance, 364
progress assessment decisions, 109
shadowing, 41-42
system boundary, 71
user interface design, 258-59
queuing, 362
quiet period, 418
R
range checking, 308
rationalization step, physical design, 232-40
cohesion and coupling, 234-35
deliverables, 232
deployment model, 238-39
distributing preliminary components, 236-38
distribution and packaging strategies, 233-34
packaging components, 235-36
validating and refining distribution and packaging, 239-40
readiness management process, MSF, 8-9
realization relationships, 190-91
recoverability requirements, 147
redesigning processes, 158-60
references, functional specification, 137
referential integrity, 308
regression tests, 21, 399
relational databases, 289. See also databases
relationships, 189-93
Class-Responsibility-Collaboration (CRC) cards, 194
examples, 192-93
identifying, in use cases, 192
logical data model, 199-200
many-to-many, 297
modeling, 194-96
one-to-many, 296-97
one-to-one, 295-96
ORM, 65
relational database, 295-97
sequence diagrams, 195-96, 209
types of, 189-91
release candidates milestone, 22, 395
release management role, 6-7, 89, 129, 133, 379
release readiness approved milestone, 5, 22, 409
releases. See also applications; solutions
stabilizing phase, 22, 396
versioned, 13-14, 97-98, 132
relevant characteristic, 93
reliability, 362-64
application architecture, 155
application failure reasons and, 363
designing for, 363-64
requirements, 147
removal requirements summary, 136
repeatability, bug, 401-2
reporting. See also documents
deploying phase, 24
risk, 111
test, 22, 378
transferring systems, 419
repository, documentation, 24
repudiation, 325
requirements
analysis, 163
case study, 31-33
categorizing, 146-48
communicating, through modeling, 139. See also usage scenarios; use cases
constraints and assumptions, 77. See also assumptions; constraints
data integrity, 309-10
defining, 16
developing candidate, in conceptual design, 138
draft requirements documents, 51-54, 79
functional specifications and, 132, 136
hidden, 77
identifying physical, 223
logical design and, 173-74
planning phase and, 17
refining, 76-77, 96-97, 163
resolving conflicts between constraints and, 224
restating, 144-45
user, 158-60
validating logical object models against, 203
wants vs., 76
research step, conceptual design, 141, 142. See also conceptual design
research step, physical design, 222-24
deliverables, 223
identifying requirements and constraints, 223
resolving conflicts between requirements and constraints, 224
resources
monitoring, 372
scalability and, 359
security and, 340
tradeoffs and, 10-11
responsibilities. See roles, project team
return on investment, 181
reuse, designing for, 234, 257
reviews
post-implementation, 108
project, 23, 419-20
rich clients, 267-69
ring constraints, ORM, 67-68
risk assessment document
calculating risks, 112
contents, 111
creating top 10 list, 112-13
updated master, 129
risk management process, MSF
envisioning phase and, 16, 17, 90
functional specification summary, 137
high-risk features, 14
risk assessment document, 111-13, 129
risk categorization process, 401-4. See also bugs
risk management plan, 19
risks of not creating functional specification, 133-34
steps, 7-8, 110-11
role constraints, ORM mandatory, 65
role playing technique
validating conceptual model, 162
validating logical object model, 203-4
role-based security, 333-34, 336, 340, 343
roles, project team. See also project teams
deploying phase, 379, 417, 419
envisioning phase, 88-89
logical design, 178-79
MSF Team Model, 5-7
physical design, 220
planning phase, 128-29
project management process, 10
project stakeholders, 7
project structure document and, 105, 106-7
stabilizing phase, 378, 396, 397
rollback plan, 373
rolling upgrades, 361
rows, table, 291
rules, business. See business rules, catalog
rules, ORM derivation, 62
S
sales department problems, case study, 26-27
scalability, 356-60
application architectures, 154-55
common approaches, 357-58
data validation in components, 313
designing for, 234, 358-60
requirements, 147
scaling up and scaling out, 357-58
schedules
deployment, 380
initial, 92
master project, 19, 129
planning phase, 18-19
project structure document, 105
risk planning, 111
testing, 378
tradeoffs and, 10-11
scope
assumptions and constraints, role of, 98
benefits of defining, 99
conceptual design, 140
defining, 16, 17, 95-99
deployment, 380
estimates, role of, 99
milestone, 5, 20-21
physical design, 219
refining requirements, 96-97
revising, 99
tradeoff triangle and priorities, 10, 97. See also tradeoff management
use cases and, 95-96
versioning and, role of, 97-98
scope complete milestone, 5, 20-21
screen utilization, user interface, 259
scripts, 21, 312-13
second normal form, 303-4
secrets in code, 321
security
client environments, 269
considerations, 182
design. See security design
drawbacks of traditional security models, 321
functional specification summary, 136
operations requirements, 147
programming model, 243
project team clearance, 89
security plan, 412
servers, 239
services, 142
testing, 21
vulnerabilities, 320-21
security design, 319-53
applying mitigation technologies, 349
auditing strategies, 347-48
authentication strategies for data access components, 346-47
authentication strategies for user interface components, 344-46
authorization and authentication strategies, 339-42
authorization strategies for business components, 343
authorization strategies for data access components, 343-44
authorization strategies for user interface components, 342-43
identifying potential threats, 349
mitigation techniques, 328-29
MSF Process Model and, 323-24. See also Process Model, MSF
.NET Framework security features, 330-38. See also .NET Framework security features
planning application security, 323-29
principles for security strategies, 322
security vulnerabilities, 320-21
STRIDE threat model, 324-25
threat model creation, 325-27
threat model responses, 327-28
threat modeling and mitigation, 349
sequence diagrams, UML, 60, 195-96, 209, 221, 227-28
sequential cohesion, 234
serial deployment, 415, 416
servers, 239, 277, 309
service accounts, 340, 346-47
service level agreement (SLA), 418
services
attributes and, 189
common, 226
example, 187
identifying, 184, 186-87
interaction standards, 182
inventory, 226
layers and packaging and distribution, 235-38
levels and quiet period, 418
matrix, 209
types of, 152-53
session state, 233. See also state
set constraints, ORM, 66
sets, ORM, 62
severity
bug, 401-2
risk, 111
shadowing, 40-42
signing
code, 331
data, 331-32
sign-off, customer, 409, 413, 418, 420
single-user control model, 206
site deployment, 415-18
installing, 417
preparing for, 417
process, 415-16
site-specific components and, 414
stabilizing, 418
training during, 417-18
site deployments complete milestone, 23
site usage plan, 413
skills, project team, 89, 183
SMART characteristics, vision statement, 93
smart keys, 294
social engineering, 320
software. See also applications; solutions
misconfigured, 320
UML and, 58
solution concepts
creating, 99-101
creating business-oriented draft, 100
developing, 16, 17
elements of, 100-101
solutions. See also applications; projects
components, 20
concepts. See solution concepts
design, 18
development. See Process Model, MSF
pilot. See pilots
releases, 13-14, 22, 97-98, 132, 396
scenarios, 411
testing, 21
Solutions Framework. See Microsoft Solutions Framework
source code, 21, 22. See also code
sources, information. See information sources
specific characteristic, 93
spiral process model, 2-3, 4
sponsors, project and business, 7
spoofing identity, 324, 333
SQL (Structured Query Language)
injection attacks, 321
query strings, 233
relational databases and, 289
tables, 291
SQL Server security, 337-38, 348
stabilizing phase, 392-409
categorizing and tracking bugs, 401-4
closing with release readiness approved milestone, 409
code reviews and testing environment construction, 404
conducting pilots, 405-8
coverage and usage testing, 398
deliverables, 22, 392-93
interim milestones, 393-96
milestones, 5, 22
MSF Process Model and, 4-5, 21-22. See also Process Model, MSF
pilot plan, 378-79
prioritizing bugs, 421-22
project team roles and responsibilities, 396
tasks, 21
test plan, 377-78
test tracking and reporting, 22
testing best practices, 397-98
testing terms, 399-401
staging environment, 18, 412
stakeholders, project, 7, 47. See also customers; users
standards and processes, functional specification, 135
state
current. See current state
future. See future state
management, 233
object, 188
stateful vs. stateless objects, 242
stateless architecture, 154-55
UML state diagrams, 60, 205
user process components and, 275-76
status displays, 264
storage, data, 182, 334, 362. See also data store design
stored procedures, 312, 348
strategies
distribution and packaging, 233-34
information gathering, 47-48
security, 322
stress tests, 21, 299, 400
STRIDE threat model, 322, 324-25, 329
string-related issues, globalization and localization, 368
strong names, 331
structural view, UML, 59
structure. See project structure document
Structured Query Language. See SQL
subordinate use cases, 148-49
subtype constraints, ORM, 67
success criteria
solution concept, 100
testing, 397
support
information systems, 24
performance, 22
pilot, 406
transferring projects to, 24, 418-19
supportability
considerations, 181
functional specification summary, 136
requirements, 147
surveys, 44, 419
symmetric ring constraints, ORM, 68
synchronous control, 205, 243, 359
system
crashes, 401
defining interactions between actors and, 71
determining boundaries of, 71-72
identifying, 69
as information source, 46-47
performance plan, 45, 413
requirements, 17, 146
services, 152-53, 182-83
system administration department problems, case study, 30
T
tables
logical data model, 198
normalizing, 301-6
physical data model, 291-95
relationships and, 295-97
tampering, 325
target future state, 157-58. See also future state
Team Model, MSF, 5-7. See also project teams; roles, project team
technical specification document, 184, 381-82, 384
technology
candidate, 180-84
information, 39-40
logical design and, 176
technology validation complete milestone, 19
temporal cohesion, 235
terms
glossary, 56, 90, 263
ORM, 62-63
testing, 399-401
testing
best practices, 397-98
categorizing bugs, 401-2
code reviews, 404
coverage, 398
environment, 18, 373, 375, 404
performance goals and, 365
results and tools deliverable, 22
stabilization phase and, 21, 392, 397-404. See also stabilizing phase
stress testing applications, 299
success criteria, 397
terms, 399-401
test plan, 377-78, 383, 412
test specifications and test cases, 21
test tracking and reporting, 22
tracking bugs, 403-4
usage, 398
zero-defect mindset, 398
testing role, 6-7, 89, 129, 397
thin clients, 267-69
third normal form, 304-5
threading model, 243
threat models, 323-28
creating, 325-27
mitigation techniques, 328-29
responding to threats, 327-28
STRIDE, 324-25
tight coupling, 235
time-based characteristic, 93
toolbars, 260-61
tools
development, 183-84, 376
migration, 373
monitoring, 373
ToolTips, 264
top 10 lists of risks, 112-13
topology, 221, 230-31
component and data, 231
network, 230
tracking
bugs, 378, 403-4
progress, 9
risk, 8, 111
test, 22
tradeoff management, 10-12
project scope and, 10, 97
project tradeoff matrix, 11-12
tradeoff triangle, 10-11, 97
training
development team, 376
readiness management, 9
during site deployment, 417-18
training plan, 24, 413
user instruction and, 45
transactional integrity, 205
transactional services, 183
transactions, optimization and, 299
trend analysis, 372
triangle, tradeoff, 10-11, 97
triggers, 111, 312
type safety verification, 330-31
types, data, 292-94, 308, 311
U
UML. See Unified Modeling Language
UML Distilled: A Brief Guide to the Standard Object Modeling Language, 132
unencrypted data transfer, 321
Unicode, 369
Unified Modeling Language (UML), 57-61
activity diagrams, 228
class diagrams, 226-27
component diagrams, 229
diagrams, 59-60
features, 58
functional specification and, 131-32
objects and services inventory, 226
refining models, 225-29
relationships, 189-93
sequence diagrams, 227-28
views, 58-59
views and MSF Process Model phases, 60-61
Unified Modeling Language User Guide, The, 58
uniqueness constraints, ORM, 64-65
unit tests, 399
universe of discourse (UoD), 61
upgrades, rolling, 361
usability testing, 21
usage scenarios. See also use cases
analyzing high-level, 50
benefits, 74
creating, 74-76
current state, 73-76
developing example, 80
features, 72-73
functional specification summary, 136
future state, 74
objects and, 184
planning phase, 17-18
refining requirements from, 76-77
for subordinate use cases, 149-51
validating, 151
walkthrough and role playing, 203-4
usage testing, 398
use case diagrams, UML, 52-53, 59, 72, 96, 148-51
Use Case Driven Object Modeling with UML: A Practical Approach, 58, 132
use cases. See also usage scenarios
actors, identifying, 70
analyzing high-level, 50
creating, 69-72
creating subordinate, 148-49
defining interactions between actors and systems, 71
deriving, from interviews, 52-53, 79
determining system boundary, 71-72
diagrams, 52-53, 59, 72, 96, 148-51
functional specification summary, 136
logical design and, 180
objects, identifying, 208
planning phase, 18
project scope and, 95-96
refining, 148-51, 163
refining requirements from, 76-77, 96-97, 163
relationships, identifying, 192
systems, identifying, 69
usage scenarios for subordinate, 149-51
validating, 151
user experience role, 6-7, 89, 129
user interface design, 255-74
auditing strategies, 347
authentication strategies, 344-46
authorization strategies, 342-43
client environments, 267-69
components, 256-57
control, 207
creating initial, 262-63
deliverables, 274
features, 259-61
functions of user interface components, 257-58
globalization and localization issues, 369, 370
guidelines, 258-59
high-level, 176, 200-201
models, 245, 265-67
presentation layer and, 255-56. See also presentation layer design
prototypes, 269-73, 279-80
providing user assistance, 263-65
separating user processes from user interfaces, 276-77. See also user process component design
validating, 273-74
user process component design, 275-78
auditing strategies, 347
authentication strategies, 346-47
authorization strategies, 343
guidelines, 277-78
presentation layer and, 255. See also presentation layer design
separating user processes from user interfaces, 276-77
user process component functions, 275-76
user profiles
creating, 94-95, 101
envisioning phase, 16-17
planning phase and, 17
users. See also customers
acceptance testing, 21
as actors. See actors
attitudes, 44
experience, 181
as information sources, 47
instruction, 44-45
profiles. See user profiles
requirements, 17, 146. See also requirements
UML user view, 59
user interfaces. See presentation layer design; user interface design
user services, 152-53, 245
V
validation. See also verification
conceptual model, 161-62
data, 307-13
distribution and packaging, 239-40
input, 260
logical object model, 203-4
objects and relationships, 194
operations, 419
requirements, 145
use cases and usage scenarios, 151
user interface design, 273-74
vision/scope document, 102-3
values
default, 260, 311
ORM, 63, 64
ORM constraints, 66
verification. See also validation
build verification tests, 399
individual object, 203
type safety, 330-31
versioned releases, 13-14, 97-98, 132
vertical partitioning, 301
views
UML, 58-59, 60-61
user interface, 257
visibility, bug, 401-2
Visio, 37, 57, 60, 61
vision statements
characteristics, 93
envisioning phase and, 16, 17
examples, 93-94, 117
vision/scope approved milestone, 5, 15, 16, 86, 102
vision/scope created milestone, 16
vision/scope document, 91-103
developing example, 114-17
envisioning phase and, 16, 17, 90
features and contents, 91-92
functional specification summary, 135
problem statement, 92
project goals, 101-2
project scope, 95-99
solution concept, 99-101
user profiles, 94-95
validating, 102-3
vision statement, 93-94
Visual Basic .NET, 183
vulnerabilities, security, 320-21
W
walk through technique
validating conceptual model, 162
validating logical object model, 203-4
wants, requirements vs., 76. See also requirements
waterfall process model, 2-3, 4
weak passwords, 320
weaknesses, security, 320-21
Web e-commerce site example
goals, 101-2
prioritizing bugs, 421-22
risk exposure, 113
vision statements, 93-94
Web Forms, 255
Web services security, 336
Web site requirements, case study, 32-33
Web-based state management, 233
Web-based user interfaces, 266, 344-45
Wide World Importers acquisition department problems, case study, 28
Windows
Distributed interNet Applications (DNA) architecture, 155
user interfaces, 265-66, 346
Windows authentication, 335
Windows XP Remote Desktop and Windows Terminal Services, 266
Windows Forms, 255, 265
wizards, 264
workflow, 258
Writing Effective Use Cases, 139
Writing Secure Code, 322, 329
X
XML (Extensible Markup Language), 291, 367
Z
zero-bug bounce (ZBB) milestone, 22, 395
zero-defect mindset, 398
Last Updated: March 13, 2003
|
