1. Update 2 Sarah Mercier

2. Summary Current status ▫Implemented features ▫Known bugs ▫Changes from original plan Prototype demo ▫Before/after ▫GAE/Play!/Siena  How it works with example Plan for next semester ▫Remaining features ▫Bug fixes ▫Timeline

3. Current status Implemented features ▫Login with email address ▫User-specific content  User role dictates content and permissions ▫Employee, Client, Project administration ▫Time  Logging  Copy day Known bugs ▫Editing time entries: wrong week selected ▫Clearing of database upon deployment of new/updated version ▫Closed projects listed in billing for all users ▫Doesn’t check user email is actually allowed to access TT

4. Current status Changes from original plan ▫MVC framework ▫Siena plugin to make datastore easier to work with ▫Android app?  Discovered most people at work don’t have Android phones  Possibly mobile version of site, if time allows

5. Before/after

6. GAE/Play!/Siena framework How it works

7. Demo!

8. Plan for next semester Remaining features ▫Time submission/approval ▫Notifications ▫Report generation  Client summaries  Project manager summaries  Executive summaries ▫Exportation of data ▫Mail/Google Talk modules ▫Branding

9. Plan for next semester Bug fixes ▫Fix wrong time selected ▫Fix datastore wipe upon deployment  Possibly default values populate database upon deployment ▫Fix closed project listing  Check for property when getting list of projects ▫Fix user detection  If can populate database with users upon deployment, should be easy to do

10. Plan for next semester Timeline ▫December/Beginning Spring 2011  Bug fixes  Time submission/approval  Notifications ▫End of February  Report generation and summaries  Data export ▫End of March  Google Mail/Talk Modules ▫End of April  Branding ▫End of Semester  Mobile version of application (possibly)

11. Questions?