Code Complete: A Practical Handbook of Software Construction, Second Edition - page 313
| < Free Open Study > |
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] backup plans 2nd bad data, testing for barricades assertions, relation to class-level input data conversions interfaces as boundaries operating room analogy purpose of base classes abstract overridable routines [See classes, base] abstraction aspect of coupling, too tight Liskov Substitution Principle overridable vs. non-overridable routines protected data routines overridden to do nothing single classes from Basic [See also Visual Basic] basis testing, structured 2nd BCD (binary coded decimal) type BDUF (big design up front) beauty big design up front (BDUF) big-bang integration binary searches binding compile time heuristic design with in code just in time key point load time run time black-box testing blank lines for formatting 2nd blocks braces writing rule comments on conditionals, clarifying defined emulated pure layout style pure, layout style single statements Book Paradigm boolean expressions 0, comparisons to [See boolean variables, expressions with; control structures, boolean expressions in; expressions, boolean] 0s and 1s as values breaking into partial tests C languages syntax checklist for constants in comparisons decision tables, moving to DeMorgan's Theorems, applying evaluation guidelines functions, moving to identifiers for if statements, implicit comparisons Java syntax 2nd layout guidelines logical identities negatives in numeric, structuring parentheses for clarifying pointers, comparisons with positive form recommended refactoring short circuit evaluation simplifying zero, comparisons to boolean functions creating from expressions if statements, used in boolean tests breaking into partial tests [See comparisons, boolean] hiding with routines simplifying zero, comparisons to boolean variables 0s and 1s as values [See boolean expressions, variables in; data types, boolean] C, creating data type checklist documentation with enumerated types as alternative identifiers for naming simplifying tests with zeros and ones as values boss readiness test on prerequisites bottom-up approach to design bottom-up integration boundary analysis braces block layout with styles compared break statements C++ caution about guidelines labeled multiple in one loop nested-if simplification with while loops with bridge failure, Tacoma Narrows Bridge pattern brute-force debugging buffer overruns build tools [See also compilers] building metaphor building vs. buying builds, daily business rules architecture prerequisites change, identifying areas of good practices table for subsystem design buying components 2nd |
| < Free Open Study > |
Similar products
Similar products
- What is Sarbanes-Oxley[q]
Transmission gate or operation - C# in a Nutshell
Memberfilter c# - Programming WCF Services
Transactionscoperequired - DB2 Developers Guide
Vendor+for+db2+training - Real World Microsoft Access Database Protection and Security
Ms access 97 vba link tables using unc - Building the Perfect PC
Ensuring the grounding tab clears the ethernet port