Index_C

C

C programming language, 13

C# comments

code blocks, 396

inline, 396

C# programming language, 29, 269, 304

code for compiling an assembly, 397

for loop, 416

formatting options, 415

C# project templates, 398

C# specification (ECMA standard 334), 29

C++ programming language, 304

code formatting, 412

memory handling, 10

Cabinet (.cab) files, 173, 362

Cache duration and location, setting, 360

Cache object, 360-361

Caching pages or fragments (ASP.NET), 360

Calculator application, 267, 287, 297

Calendar application, 292-294

Callback function, defined, 308

Camel casing, for variable names, 409

Case statement, indenting for switch statement, 415

Cash register application, 258

Categories and potential sources of risk, 67

Categorization attribute (of requirements), 100

CCW (COM callable wrapper), 11

CD-ROM (included with this Study Guide), 459-461

CEO interview, 86, 136

CGI application languages, 13

CGI (Common Gateway Interface), 13

Change, in process review, 94

Change management, 64, 194, 432-436

Change management processes, 64, 194

Character-encoding standard, 166-167

Checklists (code review), 427-429

Chief Technology Officer interview, 86, 137

Child objects, 292, 294

Cipher, 186

Ciphertext, 186

Class diagrams (UML), 26, 286, 295-296

Class libraries, 8, 22

Class names, 17

Class naming conventions, 409

Class properties, identifying, 294

Classes (.NET Framework), 12, 17, 306, 357

defined, 291

identifying for an application, 291

CLI (Common Language Infrastructure), 29

Client, defined, 268

Client application, interaction with components, 358

Client billing application example, 293-294, 315

Client certificate, 304

Client installation, 117

Client workstation, 267

Client/server application architecture, 266, 268-269

Client/server vs. n-tier architecture, 269

Client-side state management options, 170

Closed-book exam simulation, 460

CLR applications, 173

CLR assemblies, features that support, 174

CLR (Common Language Runtime), 11, 17, 19-20

assembly versioning, 175

benefits to .NET developers, 19

CLS (Common Language Specification), 165

Cluster, explained, 156-157

Cluster software, 156

Clustered index, 369

Clustered servers, 273

Clustering, explained, 156-157

CMS (contact management system), 221

COD (Component Object Model), 6

Code

breaking over several lines, 416

line length of, 415

managing, 432-436

using monotype font for, 415

using one statement per line, 416

white space in, 416

Code access security (.NET), 187, 354

Code block (localization), 167

Code Comment Web Report, 398

Code commenting techniques, 395-396

Code comments, 391

avoiding lines of asterisks in, 396

cleanup of before development, 396

for complex sections of code, 396

for explaining intent, 396

keeping up-to-date, 395

line length of, 415

placing before each method, 395

in response documents, 395-396

uniform style for, 396

using white space in, 396

for variable declarations, 396

Code download (distribution method), 173

Code formatting

block style, 411

indentation, 412

opening and closing braces, 411

purpose of, 411

slanted style, 412

Code formatting conventions, 411-416

Code maintainability, 409

Code review, 390, 425-429

assumptions, 427

findings of, 427

list of defects, 426

reporting phase, 427

style guidelines, 428

Code review checklists, 427-429

Completeness section, 427

Correctness section, 427

Multiple Views section, 428

Rules of Construction section, 428

Style section, 428

Code signing, 186

Coding practices, 390

Coding standards, 408-416

Coexistence strategies, 172

Cognitive disability, requirements for, 114

Coherent environment (user interface), 418

Collaborative development models, 434-436

Collection data type, 360

Color blindness, accessibility for, 114, 372

Color scheme for the system, CSS for, 115

Color schemes, in user interface, 418

Column mappings, in data migration, 364

Column names, data-type neutral, 411

COM compatibility with .NET, 11

COM component metadata, 18

COM (Component Object Model), 7, 11

COM components, 18, 269

custom designed, 13

turning into web services, 10

COM objects, 308

COM programming model, 6

COM versioning vs. .NET versioning, 9

COM+, 6-7, 269, 271

COM+ application, adding .NET Framework components to, 10

COM+ component pooling, 154

COM+ components, application state for, 310

COM/DCOM model, 8

drawbacks of, 7-8

vs. .NET, 8-10

Command-line environment (Mono project), 30

Commands, consistent set of, 417

Commenting web pages, 403-408

Comments (code). See Code comments

Commitment to enterprise architecture, 58

Common processes (business processes), 93

Common utility modules, explained, 423

Communication object (use case), 87, 89-92

Commutative operations, 153-154

Company trade secrets, 302

Competitive processes (business processes), 94

Competitor strengths and weaknesses, 97

Compidot (compositively identified object type), 315-318

Compiled languages, vs. interpreted, 19

Compiled libraries (.dll), 10, 173, 267

Component failure, 349

Component management (.NET), 358

Component pooling, 154, 311

Component review and inspection, 426

Component Services (for Windows 2000), 269-271

Component subtasks, matching with data, 290

Component tasks, breaking into subtasks, 290

Component versions, running multiple, 19

Components, 308, 357

designing, 357-358

designing for interchangeability, 154

handling their own errors, 345

identifying responsibilities of, 289-290

installing on production equipment, 117

interaction with client application, 358

stateless, 154

that share user state data, 359

unit test for, 422

Composite keys, 315, 317

Conceptual application design path, 251

Conceptual components derived from business rules, 251

Conceptual database design, 212, 316

comparing with DFDs, 274

converting to logical design, 315

Conceptual database design model, 316

Conceptual design, 99, 249-284

converting into logical design, 286

deriving a logical design from, 287-295

exam objectives, 467

explained, 252

vs. logical design, 252

user interface, 262-265

validating, 223, 274-275

Conceptual design phase, 213, 251

Conceptual design summary, 146-147

Conceptual model

of business requirements, 251-265

creating, 151, 221-227

of data requirements, 220-238

ORM, 228-230

Conceptual system model, major tasks of, 251

Conceptual user interface design, 264-265

Conceptual-logical-physical design model, 250

Conditional data, flow of, 122

Confidentiality requirements, 120

Configuration files, explicit version policy in, 175

Configure and Assembly screen (Visual Studio .NET), 181

Connection to the database, error handling for, 344

Connection object (use case), 92

Connection pooling (ODBC), 154

Consistency, in user interface, 417

Consistency with user goals, 275

Consistent API, 357

Console applications, 306

explained, 21

presentation layer of, 356

Constants, use of, 410

Constraint object (use case), 87

Constraints

applying, 438-441

database table, 313-314

identifying, 160

including in physical design, 355-356

CONSTRAINTS nodes in policy file, 439

Construction phase (MSF), 60

Consumers of web services, 31, 271

Consuming of web services, 14, 309

Contact object (Outlook Express), 297

Continuous availability (web site), 85

Controlled code sharing, 172

Converting to .NET vs. developing in .NET, 12

Copyright statement (on web site), 421

Core behaviors of an object, 294

Core business requirements, 253

Corruption via unauthorized access, 119-120

Covalent Enterprise Ready Server (ERS), Apache, 30

CPU-intensive tasks, 19

Critical capabilities, availability and, 117

Critical dependencies, 149

Criticality to customer attribute (requirements), 100

Criticality to user attribute (requirements), 100

Cross-device communication, limiting, 155

Cross-platform initiatives, 30

Cross-platform .NET, 29-30

Cross-referencing matrices (conceptual design), 262

CryptoAPI (Microsoft) security functions, 355

Cryptography classes (.NET), 354-355

CSDP (Conceptual Schema Design Procedure), 212, 214, 220-238

final checks of, 238

seven steps of, 220

CSS (cascading style sheets), 115, 420

CTS (Common Type System), 10

Cultural differences (regional), 113, 165-167, 301

Cultural and political issues (global), 113, 165-167, 301

Currencies (locale-aware), 114

Currency (localization requirements), 113

Currency and number considerations, 301

Current state, and proposed solution, 125

Current-state usage scenario, 112

Custom help topics (enterprise template), 437

Custom identity, 191

Custom principals, 352

Custom roles, granting to a user in Windows, 352

Customer contact, in process review, 94

Customer contract, with functional specifications, 145

Customer expectations, functional specifications and, 146

Customer object attributes, 105

Customer requirements, functional specifications and, 146

Customers, client installation for untrained, 117