Guidelines, code review

• Why

  • High quality code and structure across modules
  • Code writing education
  • Code simularity

• What

  • Package structure, class design and naming conventions
  • Code in general, program flow and documentation

• Who

  • Each module-responsible in R&D reviews code written by other programmers, and feedback are given back to them

• How

  • Names of selected classes are given from one resp. to another for review

• When

  • Every 14 days

Notes: