TrackSys

TrackSysFinal ProjectPresentation and DemonstrationGood afternoon Run Cubed and guestsWe are Modus Pwnens Design and are here to present to you TrackSys, our software solution for your organization.1Modus Pwnens DesignGordon Celesta Project ManagerJordan Ell Designer / ProgrammerTriet Huynh Designer / ProgrammerBrian Richter Designer / ProgrammerBraden Simpson Lead ProgrammerOur group consists of myself, Gordon Celesta project managerJordan Ell 2OverviewProject DescriptionUse CasesPrototypesDemonstrationDevelopmentDesign Patterns

Technical ImplementationReflectionsRecommendationsSummaryClient FeedbackQuestions

We will be speaking about theProject Description

Then we will hand the presentation over to our clients Run cubed for a few minutesAt the end we will answer some questions3Problem DescriptionRun3 owns an Indoor arena, with eight tracks, located in SookeAthletic clubs search for and book track time for runners training to qualify for the Canadian Olympic Team at the 2012 Olympics in LondonA Club representative applies for registration with Run3 and sign a waiver before making their first bookingThe club representative views their future and past bookingsThe arena manager adjusts Club bookings and fees, when necessaryThe arena manager bills each club on a monthly basis for the number of hours usedThe clubs pay the monthly fee to continue making bookingsThe arena manager views at a glance the availability of tracks for the week.The manager checks the track history and schedules maintenance when requiredThe manager sends contacts the Clubs when tracks are being maintained.Heres a brief overview of the problem description4Club Use CasesClub applies for registrationClub checks track availabilityClub books trackClub cancels booking Club pays monthly feeClub requests historyFrom the project description and first meeting with the clients, these are the use cases we identified for the clubs; with the four main use cases in bold5Manager Use CasesManager searches for clubManager charges additional feeManager bills ClubManager views track schedulesManager books track for maintenance Manager views track historyManager sends email notification to Club(s)These are the use cases we identified for the arena manager6PrototypesRegistrationTrack Booking

During our meeting with our clients we presented low fidelity prototypes as part of storyboardsThe following slides are examples of two prototypes used7

This hand-drawn prototype was part of the Club Applies for Registration use case and storyboard

8

This one was part of the Club Books Track use case and storyboardWe also used pictives to demonstrate some of the functionalityIn future versions of TrackSys we hope to incorporate a pop-up booking dialogue as seen here.

9DemonstrationI now pass the presentation over to Brian, who will guide us through a demonstration of TrackSys10Development - Unified ProcessInception PhaseDomain, Use casesRequirementsClient Meeting 1Elaboration PhaseLow fidelity prototypesClient Meeting IIConstruction PhaseRapid ImplementationTransition PhaseTestingDevelopment - Network Graphhttps://github.com/bradens/TrackSys/network

Design PatternsSingletonManagerDatabase Boundary ClassesObject PoolDatabase Boundary ClassesObserverServlet HandlerModel View ControllerOn this project we implemented 4 design patterns. The singleton design pattern was applied to the manager controller class, as well as the database boundary classes. We then used the object pool pattern to limit database connections to one per boundary class. This drastically improves performance and reliability. Then we have the Observer design pattern used on the servlet handlers. This waits for ajax requests to the servlet and directs the data flow to the correct view. Finally through the use of entity, view and controller classes we used the model view controller architecture.13Technical ImplementationServer Side ArchitectureCodehaus JettyEmbeddable javax.servletContainerLightweight, Standards compliantGreat eclipse integrationGoogle GsonEasy to serialize java objects into json data to send to the client.MySQLClient SidejQuery & jQueryUIEasy to use, rapid development results. Great AJAX functionality, giant community and documentation.HTML/CSSstyling and contentEclipseIntegrated plugins (github, jetty, Aptana Studio)For TrackSys, we built a Client Server rich web application. For the server side architecture, we used jetty which is ____. We also used Google Gson to easily serialize ____, and finally MySQL for our database. For the client side, we used Jquery and Jquery UI because they are ____. Along with HTML and css for styling and content of course. As for our IDE, we used eclipse with plugins for (git, jetty, and aptana studio (which is a web development plugin)14RecommendationsAdditional meetingsLab for the classStart project earlierMore time for coding and a more iterative process for the implementation phase in stages.ReflectionsTeam dynamic"Jelled" at FelicitasSkypeGoogle DocsEmailGroup study roomsSummaryUse case driven developmentUnified ProcessFour primary use casesClub applies for registrationClub books trackClub pays monthly feeClub requests historyOn behalf of Modus Pwnens Design, thank you for attending this presentationWe now pass this presentation over to Run3 to provide client feedback17Client FeedbackLEAVE AT THIS SLIDE WHILE CLIENT GROUP JOINS US AT THE FRONT18Reflections 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

QuestionsThat concludes our presentationWe now have five minutes for questions starting with our clients and then our guests20