1 / 28

FINAL PRESENTATION Gregory LaFlash Patrick O’Loughlin Zachary Snell Joshua Howell Kira Jones

THAT ONE SPECIAL SHOT. FINAL PRESENTATION Gregory LaFlash Patrick O’Loughlin Zachary Snell Joshua Howell Kira Jones Hao Sun. TOSS • www.toss.myphotos.cc. CONTENTS. Project Description and Requirements Design Alternatives System Design Team Management and Teamwork Project Concerns

wprado
Download Presentation

FINAL PRESENTATION Gregory LaFlash Patrick O’Loughlin Zachary Snell Joshua Howell Kira Jones

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. THAT ONE SPECIAL SHOT FINAL PRESENTATION Gregory LaFlash Patrick O’Loughlin Zachary Snell Joshua Howell Kira Jones Hao Sun TOSS • www.toss.myphotos.cc

  2. CONTENTS • Project Description and Requirements • Design Alternatives • System Design • Team Management and Teamwork • Project Concerns • Final Project • Evaluation Results 2 / 28 TOSS • www.toss.myphotos.cc

  3. VIDEO 3 / 28 TOSS • www.toss.myphotos.cc

  4. PROBLEM BACKGROUND • At any large gathering attendees will want to take and share photos. • With the proliferation of smartphones, taking photos has never been easier. Sharing photos, however, remains cumbersome. 4 / 28 TOSS • www.toss.myphotos.cc

  5. NEEDS STATEMENT • There was a need for a system to facilitate the convenient sharing of photos taken at an event through a crowd-sourced photo database. • Our system provides options for: • Storage • Privacy • Security • Price 5 / 28 TOSS • www.toss.myphotos.cc

  6. GOAL • TOSS: a system which provides various means of storage, privacy, and security for event photos. • Our system allows event hosts to create TOSS events in which guests will be able to upload and download photos taken in real time to and from the hosts’ preferred storage service. 6 / 28 TOSS • www.toss.myphotos.cc

  7. REQUIREMENTS • TOSS works in real time, even during high usage. • TOSS is free. The only cost of our system is the cost of the Virtual Server from NFOServers which is $52.45 for 6 months. This cost can be mitigated either through donations or advertisements. • TOSS is convenient. 7 / 28 TOSS • www.toss.myphotos.cc

  8. DESIGN ALTERNATIVES • Stand-alone web application • Lack of mobility/convenience for uploading photos • Stand-alone mobile application • Lacks storage space/convenience for downloading photos • Solution: Use both web and mobile applications • Mobile Devices: Android or iPhone 8 / 28 TOSS • www.toss.myphotos.cc

  9. SYSTEM LEVEL DESCRIPTION 9 / 28 TOSS • www.toss.myphotos.cc

  10. ANDROID APPLICATION • Hosts and guests can enter an event code to take and edit photos. • The application then sends the photo to the Photo Service for processing. • Implementation details: • Android version 4.0 and above • Spring API for performing REST calls • SimpleXML for serializing app data • ZXing Barcode scanner to read QR codes • Aviary API 10 / 28 TOSS • www.toss.myphotos.cc

  11. PHOTO SERVICE • Photo Service processes photos sent from the Android application. Processing includes validating event codes and checking for banned devices. Then it sends photo information to the API Abstraction Layer. • Implementation details: • Java, Jersey (REST), and Grizzly (Server) 11 / 28 TOSS • www.toss.myphotos.cc

  12. API ABSTRACTION LAYER • API Abstraction Layer is responsible for any interaction with storage APIs (Dropbox, FTP) by the Web Service or Photo Service. • Implementation details: • Java • Sockets • Threads 12 / 28 TOSS • www.toss.myphotos.cc

  13. WEB SERVICE • Hosts: register, add storage services, and create and manage events. • Guests: upload and download event photos using an event ID and event password. No need to register! • Implementation details: • Python • Django Web Framework • Nginx for content management • Gunicorn for web engine • Bootstrap, HTML, CSS, Javascript 13 / 28 TOSS • www.toss.myphotos.cc

  14. DATABASE • Database is responsible for storing all information concerning user accounts, user API access, events, and photos. • Implementation details: • Mysql 14 / 28 TOSS • www.toss.myphotos.cc

  15. TEAM MANAGEMENT • Zachary • Web Service: Event Creation, Email Uploading • Database • Kira • Web Service: Accounts, Event Management, Photo Uploading / Downloading • Hao • Website Branding • Gregory • Project Leader • Android Application • Patrick • Photo Service • API Abstraction Layer: Service Communications • Joshua • API Abstraction Layer: Storage Service APIs 15 / 28 TOSS • www.toss.myphotos.cc

  16. TEAM WORK • Equal responsibilities and division of labor. • We used Google Groups and Bitbucket which allowed members to have a good grasp on the project progression. • We coordinated to handle system component communication. • We were able to help each other solve problems. • We stepped in when tasks were slow in progression. 16 / 28 TOSS • www.toss.myphotos.cc

  17. HEALTH AND SAFETY CONCERNS • Privacy Concerns for event attendees. • Optional event wide tagging. • Possible safety impact on the event host’s storage account. • Allow for the banning of malicious users based on device ID. • Require password protected photo viewing. 17 / 28 TOSS • www.toss.myphotos.cc

  18. SOCIAL, POLITICAL AND ETHICAL CONCERNS • TOSS is intended to be a beneficial application to allow event attendees the ability to connect and share through photos. • Event attendees already consent to having their photos taken as part of attending the event. 18 / 28 TOSS • www.toss.myphotos.cc

  19. MANUFACTURABILITY, SUSTAINABILITY AND ECONOMICS • Manufacturability: None • Sustainability: • The cost of the server can be sustained by donations or advertisements. • APIs can change and need to be kept up to date. • Economics: • Only cost is the server. • We could monetize the system with advertisements, or premium accounts. 19 / 28 TOSS • www.toss.myphotos.cc

  20. BUDGET 20 / 28 TOSS • www.toss.myphotos.cc

  21. FINAL PRODUCT - WEBSITE 21 / 28 TOSS • www.toss.myphotos.cc

  22. FINAL PRODUCT - WEBSITE 22 / 28 TOSS • www.toss.myphotos.cc

  23. FINAL PRODUCT - ANDROID APP 23 / 28 TOSS • www.toss.myphotos.cc

  24. EVALUATION RESULTS • TOSS was tested at AggieCon. • Gathered participants. • Found basic UI bugs that were easily fixable. • The server never crashed and always uploaded photos. 24 / 28 TOSS • www.toss.myphotos.cc

  25. EVALUATION RESULTS • Uploading and downloading photos between Python and Java works well. • 100 photos - 31 sec • 500 photos - 2 min 31 sec • 750 photos - 3 min 22 sec • Website and Android app went through several UI improvements based on team and AggieCon feedback. • Android app tested with every possible event settings combination. 25 / 28 TOSS • www.toss.myphotos.cc

  26. EVALUATION RESULTS 26 / 28 TOSS • www.toss.myphotos.cc

  27. OVERVIEW • Project Description and Requirements • Design Alternatives • System Design • Team Management and Teamwork • Project Concerns • Final Project • Evaluation Results 27 / 28 TOSS • www.toss.myphotos.cc

  28. THAT ONE SPECIAL SHOT QUESTIONS? TOSS • www.toss.myphotos.cc

More Related