Building Maintainable Software, Java Edition

Index

Symbols

• 11-check, Write Short Units of Code

A

• Abstract Factory design pattern, Abstract Factory Design Pattern-Abstract Factory Design Pattern
• acceptance tests
  • automation of, Objection: We Still Need Manual Testing
  • characteristics, How to Apply the Guideline
• adaptive maintenance, The Four Types of Software Maintenance
• analysis
  • and component balance, A Good Component Balance Eases Finding and Analyzing Code
  • and duplication, Duplicated Code Is Harder to Analyze
• architecture components, balance of (see component balance)
• automation of tests (see test automation)

B

• backups, code duplication and, Duplicates of Entire Files Should Be Allowed as Backups
• balance of components (see component balance)
• bank account numbers, checksum for, Write Short Units of Code
• benchmarking, Rating Maintainability
• Boy Scout rules
  • and improvement of modified code, Leave No Trace
  • defined, Objection: Why Should We Invest in Unit Tests When the Current Coverage Is Low?
  • for preventing code smells, How to Apply the Guideline-Rule 7: Leave No Badly Handled Exception Behind
  • with large codebases, Remember That Every Commit Counts
• branch coverage, Write Simple Units of Code
• branch points
  • defined, Write Simple Units of Code
  • limiting number of, How to Apply the Guideline
• business impact of maintainability, Maintainability Has Significant Business Impact
• business logic, manual testing and, Objection: We Still Need Manual Testing

C

• calls, Motivation
• chains, conditional, Dealing with Conditional Chains-Dealing with Conditional Chains
• change
  • and ...