1 / 20

TrackSys

TrackSys. Final Project Presentation and Demonstration. Modus Pwnens Design. Gordon Celesta – Project Manager Jordan Ell – Designer / Programmer Triet Huynh – Designer / Programmer Brian Richter – Designer / Programmer Braden Simpson – Lead Programmer. Overview. Project Description 

mikkel
Download Presentation

TrackSys

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TrackSys Final ProjectPresentation and Demonstration

  2. Modus Pwnens Design • Gordon Celesta – Project Manager • Jordan Ell – Designer / Programmer • Triet Huynh – Designer / Programmer • Brian Richter – Designer / Programmer • Braden Simpson – Lead Programmer

  3. Overview • Project Description  • Use Cases • Prototypes • Demonstration • Development • Design Patterns • Technical Implementation • Reflections • Recommendations • Summary • Client Feedback • Questions

  4. Problem Description • Run3 owns an Indoor arena, with eight tracks, located in Sooke • Athletic clubs search for and book track time for runners training to qualify for the Canadian Olympic Team at the 2012 Olympics in London • A Club representative applies for registration with Run3 and sign a waiver before making their first booking • The club representative views their future and past bookings • The arena manager adjusts Club bookings and fees, when necessary • The arena manager bills each club on a monthly basis for the number of hours used • The clubs pay the monthly fee to continue making bookings • The arena manager views – at a glance – the availability of tracks for the week. • The manager checks the track history and schedules maintenance when required • The manager sends contacts the Clubs when tracks are being maintained.

  5. Club Use Cases • Club applies for registration • Club checks track availability • Club books track • Club cancels booking • Club pays monthly fee • Club requests history

  6. Manager Use Cases • Manager searches for club • Manager charges additional fee • Manager bills Club • Manager views track schedules • Manager books track for maintenance • Manager views track history • Manager sends email notification to Club(s)

  7. Prototypes • Registration • Track Booking

  8. Demonstration

  9. Development - Unified Process • Inception Phase • Domain, Use cases • Requirements • Client Meeting 1 • Elaboration Phase • Low fidelity prototypes • Client Meeting II • Construction Phase • Rapid Implementation • Transition Phase • Testing

  10. Development - Network Graph https://github.com/bradens/TrackSys/network

  11. Design Patterns • Singleton • Manager • Database Boundary Classes • Object Pool • Database Boundary Classes • Observer • Servlet Handler • Model View Controller

  12. Technical Implementation • Server Side Architecture • Codehaus Jetty • Embeddable javax.servletContainer • Lightweight, Standards compliant • Great eclipse integration • Google Gson • Easy to serialize java objects into json data to send to the client. • MySQL • Client Side • jQuery & jQueryUI • Easy to use, rapid development results.  Great AJAX functionality, giant community and documentation. • HTML/CSS • styling and content • Eclipse • Integrated plugins (github, jetty, Aptana Studio)

  13. Recommendations • Additional meetings • Lab for the class • Start project earlier • More time for coding and a more iterative process for the implementation phase in stages.

  14. Reflections • Team dynamic • "Jelled" at Felicitas • Skype • Google Docs • Email • Group study rooms

  15. Summary • Use case driven development • Unified Process • Four primary use cases • Club applies for registration • Club books track • Club pays monthly fee • Club requests history

  16. Client Feedback

  17. Reflections • Very detailed handwritten mockups • Team used Use-Cases as basis (gave us an easy understanding of their work) • Professionalism (Business card) • Proper agenda, team lead us comfortably through the meetings

  18. Questions

More Related