Index_T

T

Tab Size and Indent Size settings, 413-414

Table names, conventions for, 410-411

Tables, accessible, 115

Tape storage, 272

Target environment, 50

Target architecture, 50

Task List items, enterprise template for, 437

Task modules, testing, 422

Tasks, maximum time to complete, 116

Team model key concepts, 46

Team model (MSF), 45-46

Team model roles (MSF), 45-46, 62

Team performance

being busy vs. producing results, 444-445

evaluating, 444

Team (project)

meeting due dates, 442

skills of, 48

structuring of, 45

Technical architecture

analyzing current, 57

defining, 266-274

defining current, 50

Technical and business architectures, aligning, 57-58

Technical drawing software (Visio), 26

Technical factors of physical design model, 338-339

Technical feasibility

in a case study, 63

explained, 62

Technical requirements, fulfilling, 338

Technical specifications

for logging, 339

transforming functional specifications into, 151-196

Technical specifications document, 144, 151-152

Technical support (from LearnKey), 461

Technical support personnel, documentation for, 394

Technical view of baseline architecture, 51, 55-56

Technology

as a risk category, 67

current use of, 49

degree to which it fulfills metrics, 124

identification of major, 124

organization’s view of, 49

Technology inventory, 123

Technology validation, 121-125

Technology view of an enterprise, 50

Templates (Visual Studio .NET project), 20-22

Terminology, usability of, 275

Ternary facts, 223, 232

Terrorism, protection against, 120

Test cases, 145, 424

Test code, avoiding duplication of, 424

Test data migration scripts, 365

Test environment, verifying, 161

Test harnesses, 112, 422

Test plan

creating, 194-195, 425

key sections of, 194-195

Test scenarios, 145

Testing

builds during, 430

of deployment process, 394

financial savings of good, 421

pre-populating databases for, 365

purpose of, 421

requirements for, 421

use cases for, 296

using POC for quick tests, 322

Testing fixtures/harnesses, 112, 422

Testing personnel, deployment documents for, 394

Testing standards, 390, 421-424

Testing stubs, creating, 422

Text Editor defaults, setting, 413

Text Editor (Visual Studio IDE), 412-413

Text-based user interface, 306

Theft, protection against, 120

Thin clients, 268

Third normal form, 218

Threads (application), 308

Threat model, 185

Three-tier application architecture, 266, 269-271

developer maintenance of, 367

of a web application without .NET, 13

Tiers

defined, 266

using fewest number of, 266

Time estimates, 145

Time saved by the implementing the solution, 445

Timed exam simulation, 460

Timeline document, 99

Timeouts, for database transactions, 307

TOOLBOXCONSTRAINT, in policy file, 440

Top-down approach to integration testing, 422-423

Top-level namespaces, 17

Top-level screens

for data entry application, 265

examples of, 264

identifying likely, 264

ToString() method and properties, 405

Total cost of ownership, 193

Total risk, measurement of, 68-69

Total risk calculation, 68-69

Tracking of issues, 432

Trade secrets, 120

Training needs, analyzing, 95-96

Training plan creation guidelines, 196

Training (of users), 95-96, 149, 196

Transaction logs (SQL Server 2000), 192-193

Transaction records, security and, 302

Transaction server environment, 270-271

Transaction servers, benefits of, 271

Transaction throughput, 159

Transactions

with built-in timeouts, 307

locking, 154

monitoring, 271

Triggers element (use case), 111

T-SQL (Transact SQL), 411

Two-tier application architecture, 266, 268-269

availability factors, 348

consuming of web services, 309

developer maintenance of, 367

flexibility of, 269

managing user sessions, 310

reasons not to choose, 269

reasons to choose, 268

web applications with, 268

Type library, 18

Type-safe code, 354

Type-safety validation in .NET, bypassing, 354