1 / 16

Franchise Management System

Franchise Management System. Ryan Audet, T.J. Lindsey, Samer Mansour. Franchise Management System. A powerful tool for managing your franchise ! A multi-level tool that provides functionality for all levels of your business . Including owner, managers, employees and customers.

noe
Download Presentation

Franchise Management System

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. Franchise Management System Ryan Audet, T.J. Lindsey, Samer Mansour

  2. Franchise Management System • A powerful tool for managing your franchise! • A multi-level tool that provides functionality for all levels of your business. • Including owner, managers, employees and customers. • Tool provides management support for individual franchise stores as well as your franchise as a whole. • Framework provides easy creation of online store for your franchise with customizability and order tracking. • Flexible tool is designed to be used by any franchise.

  3. Technology • JSP front end • Java • Oracle database • BIRT Reporting • Reason: We’ve all used JSP and Java, seemed reasonable to use it, less of a learning curve

  4. Why JSP? • Common technology all group members were familiar with. • Allow for application to be deployable in a non-web environment with a different front-end. • Experience relevant to industry.

  5. Why Java? • Free • Works on many platforms and operating systems • Good for web based and network applications • We all know it!

  6. Why Oracle? • Technology we are all familiar with • Good experience for industry • Easily provided by the school. • Allows us to have one database rather than many while developing.

  7. Why BIRT? • Easy set up and deploy in tomcat. • Reports are easy to design.

  8. Development Tools • Net Beans • SQL Developer • SSH • Tortoise SVN and Assembla

  9. Problems Faced • Tunnelling to Oracle using Vista • Solution: Don’t use Vista. • Google Maps API • Problems: Bloated, Requires live website. • Solution: Do not use API. Allow managers to add links to google maps but no other map functionality. • School’s servers were down constantly.

  10. Successes Achieved • Getting our environment set up • Its always the hardest part • Mail Servlet • Customizability • Design • Database set up and making tables

  11. Progress – Milestone 1 • Requirements Document • Outline all major requirements • Add new requirements to expand project • Outline possible additional requirements if time permits • Create Use-Cases for some requirements

  12. Progress – Milestone 2 • Architecture and Design Documents • Architecture Model • Object Model • Inheritance Model • Proof of Concepts • Email • Google Maps • Customization

  13. Progress – How are we doing? • Less code done than expected • Better design, understanding • Got over most of the technical hurdles • Should be easier from here on out

  14. Future • Add a lot of basic functionality • Add more customizability • Implement BIRT • Just keep building

  15. Future – Expected Issues • 60-454 sucks already, we can see that getting in the way.

  16. Questions?

More Related