Skip to content
caracciolo edited this page Aug 31, 2015 · 1 revision

1. Code: Release

At this point of the project you deliver your shippable product to the customer. The release must be of quality.

Make sure that:

  • **Tag the release in the repository with `v2.0`**.
    
  • You addressed comments in the previously received reviews. 
    
  • Documentation for the domain model exists and is helpful, concise, correct.
    
  • The documentation is up-to-date.
    
  • You have a sufficiently wide set of test cases. 
    
  • The code should be easy to read, understand and maintain. This includes a consistent coding style and meaningful naming.
    
  • The repository is clean, that is, there are no unnecessary files, such as logs, notes, etc.
    
  • If needed, provide demo data and accounts to test the application (user/pwd: ese/ese).
    
  • Fix known bugs.
    
  • If a feature is half-backed, remove it altogether.  
    
  • The website should run in chrome and firefox.
    

2. Presentation

Each team will present his own product:

  • You have 10 min to talk. Not more.
  • One or multiple members can present.
  • Use your own computer. It needs VGA connectivity for the beamer.

Some tips:

  • describe your application doing a demo. Show the most useful features of your application by reproducing typical user scenarios.
  • conclude mentioning what you learned and the biggest challenges you encountered during the project
Clone this wiki locally