References

• XP Simple design rules
  1. Runs all the tests.
  2. Contains no duplication (OnceAndOnlyOnce)
  3. Expresses all the ideas you want to express.
     • Do not put the implementation of unrelated ideas in the same method.
     • Classes should organize ideas in a readily understandable way.
     • Use appropriate names so you don't have to explain method, member or class names with additional documentation
     • Methods and classes should be implemented so they can be understood totally from their public interfaces. This not only allows for up-front testing, but decreases coupling.
  4. Minimizes classes and methods. This is actually redundant, but is a reminder that we are trying to make this simple and concise.

• Other XP design principles
  • OnceAndOnlyOnce,
  • YouArentGonnaNeedIt,
  • DoTheSimplestThingThatCouldPossiblyWork)

• Bob Martin's Design Principles,
• Craig Larman's GRASP patterns,