Much of this information is internal documentation. Care has not been made to make links work and make the documentation conprehensible for outsiders.
  • - Technical Reviews —

Rules for Design/Code Reviews

Typically used at our weekly developer/designer meetings.

  1. Each person who is to present a design or piece of code

(however preliminary), comes to the meeting with at most

3 printed pages (text, drawing, source code, whatever), with
a copy for everyone else.
  1. The author very quickly explains what the design/code segment

is about and what type of feedback is expected.

  1. Each member of the group reads and annotates the document

for 10 minutes.

  1. The document is discussed for 20 minutes.
  1. The author retrieves all the annotated versions.

External Resources for Inspiration

  1. Code Review in the Berlin Project: Contains a helpful set of guidelines.
  • - Design Languages —

The Unified Modeling Language (UML) - a standard notation for software architectures

  1. Rational - main site
  2. Cetus Links - large link collection