test objects design

Grady Booch announces the major update to RUP’s best practices and points to this article from which I extracted Anti-patterns mentioned:

Process Anti-patterns: Precise plans/estimates, track against static plan management style. More process is better. Always use the same degree of process throughout the lifecycle.

Scope Anti-patterns: Achieve precise and thorough requirements before any project work begins. Requirements focus the drive toward a custom solution.
Teamwork Anti-patterns: Nurture heroic individuals and arm them with power tools.

Development Approach Anti-pattern: Plan the whole lifecycle in detail, track variances against plan. Detailed plans are better plans. Assess status by reviewing specifications

Communication Anti-pattern: Go directly from vague high-level requirements to custom-crafted code.

Software Quality Anti-pattern: Postpone integration testing until all code has been completed and unit-tested. Peer-review all artifacts, rather than also driving partial implementation and testing, to discover issues.