Knowledge Base, they said. Bah! It's just a hole where we dump all ideas in and bury them!

Monday, July 18, 2005

Loose Coupling

  • Change causes less pain.
  • Dependencies are known, that they can be managed.
  • Change is not too expensive and time consuming.
  • Change on both (all) sides can be managed independently of each other.
  • Impacts are known and anticipated.

  • Can I modify the software to provide the changed functionality?
  • Can I modify some parts of the software without having to change all parts? How local can I keep the changes?
  • Can I deploy the changes?
  • Can I deploy the changes without taking the system down?
  • Can I deploy parts of the changes without breaking the system?
  • Can I allow users to determine the update schedule so critical business functions are not impacted by the update?

0 Comments:

Post a Comment

<< Home