Upload
noe
View
45
Download
3
Embed Size (px)
DESCRIPTION
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. - PowerPoint PPT Presentation
Citation preview
Franchise Management System
Ryan Audet, T.J. Lindsey, Samer Mansour
Franchise Management SystemA 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.
TechnologyJSP front endJava Oracle databaseBIRT Reporting
Reason: We’ve all used JSP and Java, seemed reasonable to use it, less of a learning curve
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.
Why Java?FreeWorks on many
platforms and operating systems
Good for web based and network applications
We all know it!
Why Oracle?Technology we are
all familiar withGood experience for
industryEasily provided by
the school.Allows us to have
one database rather than many while developing.
Why BIRT?Easy set up and deploy in tomcat. Reports are easy to design.
Development ToolsNet BeansSQL DeveloperSSHTortoise SVN and
Assembla
Problems FacedTunnelling to Oracle using VistaSolution: Don’t use Vista.Google Maps APIProblems: 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.
Successes AchievedGetting our environment set up Its always the hardest partMail ServletCustomizabilityDesignDatabase set up and making tables
Progress – Milestone 1Requirements DocumentOutline all major requirementsAdd new requirements to expand projectOutline possible additional requirements if time permitsCreate Use-Cases for some requirements
Progress – Milestone 2Architecture and Design DocumentsArchitecture ModelObject Model Inheritance Model
Proof of ConceptsEmailGoogle MapsCustomization
Progress – How are we doing?Less code done than expectedBetter design, understandingGot over most of the technical hurdlesShould be easier from here on out
FutureAdd a lot of basic functionalityAdd more customizabilityImplement BIRTJust keep building
Future – Expected Issues60-454 sucks already, we can see that getting
in the way.
Questions?