Search This Blog


4 May 2009

Occams razor & Specification

William was right.  We need to keep things simple.

Requirements documents have 2 purposes;
  1. Explain what capability is required 
  2. Describe the contraints that need to be adhered to
Whatever you can do to trim your documentation?  What are you saying that is unnecessary?  How can you use less words (and images) to deliver a clearer message?

Simplicity is the method.  Clarity is the goal.

Jonathan and Albert also agree.

Picture by alles-schlumpf, CC @ Flickr