Doc - Communication

[yesbabyrun]

• Document the package according to the following structure:

  • Summary: general explanation of the functionality, logic, and any specific concepts
  • Classes: tables listing the classes of the package (property, type, description)
  • Actions: action controllers specific to the package
  • UML: UML ERD diagrams with any comments

• add UML as images (png high res)

• 1 person responsible per package (mark yourself as responsible)

• init/demo: use the documentation to verify demo data per package