index_T

Index

[SYMBOL] [A] [B] [C] [D] [E] [F] [G] [H] [I] [J] [K] [L] [M] [N] [O] [P] [Q] [R] [S] [T] [U] [V] [W]

T-shaped integration
table-driven methods
     advantages of
     binary searches with
     case statement approach
     checklist
     code-tuning with
     creating from expressions
     days-in-month example
     defined
     design method
     endpoints of ranges
     flexible-message-format example
     fudging keys for
     indexed access tables 2nd
     insurance rates example
     issues in
     key points
     keys for
     lookup issue
     miscellaneous examples
     object approach
     precomputing calculations
     purpose of
     stair-step access tables
     storage issue
     transforming keys
Tacoma Narrows bridge
takedown code, refactoring
Team Software Process (TSP)
teams
     build groups
     checklist
     development processes used by
     expanding to meet schedules
     managers
     physical environment
     privacy of offices
     process, importance to
     religious issues
     resources on
     size of projects, effects of
     style issues
     time allocations
     variations in performance
technology waves, determining your location in
Template Method pattern
template tools
temporal cohesion
temporary variables
test-data generators
test-first development
testability
     defined
     strategies for
testing
     automated testing
     bad data classes
     black-box testing
     boundary analysis
     bounds checking tools
     cases, creating 2nd 3rd
     characteristics of, troublesome
     checklist
     classes prone to error
     classifications of errors
     clean test limitation
     clerical errors (typos)
     code coverage testing
     component testing
     compound boundaries
     construction defects, proportion of
     coverage of code 2nd
     data flow testing
     data generators for
     data recorder tools
     debuggers
     debugging, compared to
     defined-used data paths
     design concerns
     designs, misunderstanding
     developer-view limitations
     developing tests
     diff tools for
     driver routines
     dummy classes
     dummy files for
     during construction
     ease of fixing defects
     equivalence partitioning
     error checklists for
     error databases
     error guessing
     error presence assumption
     errors in testing itself
     expected defect rate
     first or last recommendation 2nd
     frameworks for 2nd
     goals of
     good data classes
     integration testing
     JUnit for
     key points
     limitations on developer testing
     logging tools for
     logic coverage testing
     maximum normal configurations
     measurement of 2nd
     memory tools
     minimum normal configurations
     mock objects
     nominal case errors
     old data, compatibility with
     optimistic programmers limitation
     outside of construction domain defects
     planning for
     prioritizing coverage
     provability of correctness 2nd
     quality not affected by
     random-data generators
     recommended approach to
     record keeping for
     regression testing 2nd
     requirements
     resources for
     results, uses for
     role in software quality assurance
     routines, black-box testing of
     scaffolding 2nd
     scope of defects
     selecting cases for convenience
     stabilizing errors
     standards, IEEE
     structured basis testing 2nd
     stub objects
     symbolic debuggers
     system perturbers
     system testing
     test case errors
     test-first development
     testability 2nd
     time commitment to
     tools, list of
     unit testing 2nd
     varying cases
     white-box testing 2nd
threading
throwaway code
throwing one away metaphor
time allowances
tool version control
toolbox approach
tools
     checklist
top-down approach to design
top-down integration
transcendental functions 2nd
translator tools
try-finally statements
type casting, avoiding
type creation
    C++ [See data types, creating; data types, user-defined]
     centralization benefit
     checklist
     classes, compared to
     example of
     guidelines for
     information hiding aspect of
     languages with, evaluation of
     modification benefit
     naming conventions
     Pascal example
     portability benefit
     predefined types, avoiding
     purpose of
     reasons for
     redefining predefined
     reliability benefit
     validation benefit
type definitions