Index_R

R

Race condition, explained, 153

RAID (Redundant Array of Independent Disks), 157, 272

RAID 5, 157

RAID 10, 157

RAID 0, 157

Raising an error, explained, 344

Raising an exception, explained, 299

RCW (runtime callable wrapper), 11

RDBMS (relational database management system), 273

RDO (Remote Data Objects), .NET and, 12

Readability of source code, 409

Reader (in code review), 426

Readiness management discipline (MSF), 45, 48

Record locks, reducing, 154

Recorder (in code review), 425-427

Recordsets, disconnected, 18

RecruitmentService.net. See Employment agency case study

Red/green color blindness, accessibility issues of, 114

Redundancy, 218, 349

Redundant accounts, locating, 86

Reference documents (technical specifications), 151

Reference scheme, 225-226

Referential integrity rules, 313

Regional issues (internationalization), 112-113

Registry settings on client machines, 8

Regression test library, 424

Regression testing, 423-424

Regulatory requirements, analyzing, 98

Relational database, 273

Relational database index, 368

Relational model database, 169

Relationships object (use case), 87

Release build, vs. debug build, 429

Release candidate builds, 430

Release configurations, 430

Releases, managing, 432-436

Reliability, 158-159

and availability, 158

requirements, 117

Remote host projects, 433

Reporting, 436

Reporting database, 300

Reporting systems (applications), 287

Reports

analyzing performance of, 370

asynchronous processes for long, 308

Required conditions (use case), 111

Requirement IDs, 100, 149

Requirements, 84

attributes of, 100

categories of, 84

categorizing, 149-150

for employment agency case study, 101-114

gathering from artifacts, 105

general characteristics of, 100

restating of, 148-149

tracking from creation to implementation, 149

transforming into functional specifications, 147-151

types of, 99

well-defined, 148

Requirements documents, 393

Requirements gathering, explained, 84

Requirements-based testing, 421

Resource files (culture-specific), 167

Resource managers, 154

Resource utilization, 159

Resource-based authorization strategy, 190

Resources

acquiring as late as possible, 153

availability of, 62-63

bottlenecks for, 153

estimates for use of, 145

partitioning, 155

Response documents, 395-403

code comments, 395-396

explained, 395

structure of, 395

Response times for users, 159

Restated requirements, 148-149

Restated requirements criteria, 148

Retesting of code, 422

Retinal eye scans, 302

Return on investment, identifying, 445

Revenue

created by implementation of the solution, 445

in process review, 94

Reverse engineering an ORM model, 216

Reverse engineering of Visual Studio projects, 26

Review process, 425

Reviews, types of in design review process, 425

Risk assessment document, 66

Risk management discipline (MSF), 45, 48, 66

Risks

assigning probability and impact values to, 67-68

grouping, 68

identifying, 65-70

listing in order of severity, 68-69

potential sources of, 66-67

for RPM system case study, 69-70

Role descriptions (in ORM), 221

Role-based authorization strategy, 190

Role-based security, 187, 189, 303

Rolling upgrades, 156

Routers, properly configured, 353

Routine names

conventions for, 410

Pascal casing for, 409

RPM (Retailer Promotion Management) system case study, 60-70

RUP (Rational Unified Process), 49, 250