Index_S

S

Sabotage, protection against, 120

Sales table data example, 370

SAP accounting and warehouse inventory integration, 121

Scalability, 104, 152-155, 348

for anticipated growth, 86

approaches to, 152-153

defined, 152

guidelines for designing for, 153-155

validating, 372

Scalability requirements, 116

Scaling out, explained, 153

Scaling up, explained, 152-153

Schedules, functional specifications and, 146

Scheduling an evening batch process, 436

Schema (database), 213, 220-238, 286. See also ORM diagrams

Schema diagram, 213

Scope creep, 64, 442

Scope of a solution, defining, 64-65

Screen design and layout, usability of, 275

Screen shots, representative, 307

Screens

artistic rendering of potential, 307

designing, 356

hierarchical chart of, 264

usability of, 275

Script accessibility, 115

Search operations, use of indexes in, 369

Second normal form (2NF), 218

Secure access, strategies for, 187-191

Security, 301-304, 350

and application type, 349

application and Windows, 352

creating specifications for, 349-355

defined, 301

firewalls for, 9

levels of, 302

vs. privacy, 305

transaction servers for, 271

validating, 372

Security administration, 191

Security administrators, documentation for, 394

Security breaches (hacks), 303

Security context (component), 353

Security context of the Principal object, 187

Security context (user), 303, 353

Security documentation, 351, 394

Security documents, 394

Security event log (Windows), 341

Security goals, establishing, 350-351

Security login, as a feature, 103

Security mechanisms, preventing defeat of, 121

Security policy, 353

Security principal, 351

Security principles, 184-185

Security requirement objectives, 117-118

Security requirements, 117-121

Security strategy, selecting, 184-185

Security technologies, 301

Security tradeoffs, 302

SecurityException object, 189

Semi-isolated model (of web application development), 435-436

Sensitive data

categories of, 120

and importance of logs, 339

protecting, 305

security and, 302

Sequence or activity diagrams (UML), 296

Serialize method, 300

Server failure, 349

Server farm, 362

Servers

in client/server model, 268

clustered, 273

distributed geographically, 270

Server-side state management, 170-171

Service account, 190

Service applications within .NET, types of, 357

Service delivery with reduced downtime and risks, 149

Service levels (for users), 194

Service monitoring and control, 191

Service providers and customers, agreements between, 191

Services

and application architecture, 151

defined, 151, 308

designing, 357-358

simple or complex, 151

Windows vs. web, 308-309

Session ID, 311

Session object, 360

Session state, 310-311, 359

keeping in memory, 310

maintaining in ASP.NET, 360

saving outside of memory, 311

stored external to the application, 360

stored on the server side, 359

storing (.NET and ASP.NET), 359-361

Setup Project template (Visual Studio .NET), 22

Severity of worst-case scenario, 302

SGML (Standard Generalized Markup Language), 273

Shadowing (observing users), 102

Shared checkout mode (Visual SourceSafe), 434

Ship date, projected, 442

Shipping application, error handling in, 122

Side-by-side assembly, 193

Side-by-side execution, 182-183, 358

explained, 9

types of, 183

Side-by-side versioning, 172

Signed data, 186

Signing code with a strong name, 186

Signing data, explained, 186

Simple key, defined, 315

Simplicity, of user interface, 418

Simultaneous users, planning for many, 116

Single point of failure, 120

Single-tier application architecture, 266-268

developer maintenance of, 366

examples of, 267

reasons to choose, 268

reasons to develop, 267

Site map, 264, 275

Skeleton code, 296

Skills, availability of, 62-63

SkipVerification security permission, 354

SLAs (service-level agreements), 191

Smart cards, 351

Smart clients (.NET), 6

Smart comment editing, 398, 415

Smart Comment Editing setting (C#), 415

Smart indenting (Visual Basic), 413

SMS (Microsoft Systems Management Server), 362-363

SOAP messages, 14, 355

SOAP (Simple Object Access Protocol), 9, 14-15, 309, 355

Software (see also Applications) consolidating or removing outdated, 445

constructed vs. developed, 44

too much variety in current, 57

Software assurance plans, creating, 425

Software design

EA model impact on, 58

in the .NET environment, 5

in object-oriented environment, 5

primary goal of, 4

Software design practices, 4

Software design skills, 4-5

Software design templates (Visio), 26

Software design tools (Visual Studio .NET), 23-28

Software development, use of the term, 44

Software development process phases, 47

Software inspection, 425

Software quality, goal of, 442

Software walkthrough, 425

Solution

analyzing the feasibility of, 62-63

aspects of, 59

current state and, 125

defining the scope of, 64-65

developing, 59-61

identifying features of, 103

impact of on IT environment, 125

integrating into the enterprise, 300

licensing, 183

modularizing logically, 145

visualizing, 43-82

Solution build configuration, 430

Solution concept, defined, 59

Solutions Framework. See MSF

Source attribute (of requirements), 100

Source code. See Code

Source code control. See Visual SourceSafe

Sp prefix (in TSQL), 411

SQL clauses, on separate lines, 411

SQL DTS (Data Transformation Services), 184

SQL scripts, 214

SQL Server 2000, 214, 273

IDENTITY data type, 313

naming conventions, 411

transaction logs, 192-193

UNIQUEIDENTIFIER data type, 313

SQL Server version code-named Yukon, 29

SQL statements, case of, 411

SQL (Structured Query Language), 26, 214, 411

SSL encryption, 305

SSL (Secure Sockets Layer), 155, 305

Staffing needs, 96, 116

Stakeholders

communicating with, 391

identifying key, 97-98

Standalone application architecture, 266

Standalone applications, 266-267

Standard battery of test cases, 424

Standards

for coding, 408-416

developing, 389-456

establishing, 390-424

exam objectives, 470

explained, 390

in functional specifications, 146-147

for interfacing and exchanging data, 104

for new developers and teams of developers, 424

types of, 390

Starting files, enterprise template for, 437

State maintenance, transaction servers for, 271

State management

client-side or server-side, 170

criteria for choosing, 169

designing, 358-361

logical design for, 310-311

strategies for, 169-170

State Server mode, Session object in, 360

Statechart diagrams (UML), 296

Stateless components, 154

Statement of purpose (for requirements), 100

Status logs, 298

Stencils (Visio application), 107

Stock quotes application, as a web service, 309

Storage management, 191

STRIDE principles, 185

String-related issues of localized applications, 167

Striped sets of hard drives, 272

Striping (RAID), 157

Strong-name code signing, 186

Strong-named assemblies, 175-178

Structural diagrams (UML), 295

Stubs, on client machines, 8

Study Guide, obtaining as a PDF, 460-461

Style guides or templates (web site content), 420

Style sheets, for color control and accessibility, 114-115

Subordinate use cases, usage scenarios for, 150

Subtasks

breaking component task into, 290

matching with data, 290

Subtyping constraints (ORM diagram), 236

Subtyping (ORM diagram), 236-237

Success Audit icon (Event Viewer), 343

Summary document (functional specifications), 144-145

Support plan, creating, 194

Support processes (business processes), 94

Support staff, as stakeholders, 98

Surveys, 102

Survivability requirements, 120

Switch statement, case statement indenting for, 415

Symmetric cryptography, 186

Synchronous architecture, 307

Synchronous processes, bottlenecks and, 153

Synthesizing of information, 148-150

System administration, 191

System boundary (use case), 87

System entities, identifying, 251

System errors

defined, 344

identifying potential, 299

System event log (Windows), 340-341

System integration, data flow requirements for, 121-123

System maintenance security requirement, 121

System namespace, 17

System pathways, 252

System requirements, 149

System resources managed by the system, 10

System use case, 112

System.Console namespace, 306

System.Data namespace, 18

System.Diagnostics namespace, 341

System.Drawing namespace, 12

System-extended stored procedures (SQL), naming, 411

System.Forms.HelpProvider namespace, 392

System-generated ID, 118

System-handled error message, 345

System-level privileges, 303

System.Security.Cryptography namespace, 355

System-stored procedures (SQL), naming, 411

System.Threading namespace, 308

System.Web namespace, 18

System.Web.Caching namespace, 360

System.Web.UI namespace, 306

System.Windows.Forms namespace, 306

System.XML namespace, 12, 18