1 / 7

Thunder Bay Shipwrecks High Fidelity Walkthrough

Thunder Bay Shipwrecks High Fidelity Walkthrough. CS4760 Group #3 – Spring 2014 Kyle Kralapp , Justin Ploe , Tyler Adam, Maegan Sobel , Briana Bettin , Brandon Martinez, James Kanka April 4 th , 2014. About Thunder Bay. Scientist: Tane Casserly , Maritime Archaeologist

kiefer
Download Presentation

Thunder Bay Shipwrecks High Fidelity Walkthrough

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. Thunder Bay ShipwrecksHigh Fidelity Walkthrough CS4760 Group #3 – Spring 2014 Kyle Kralapp, Justin Ploe, Tyler Adam, Maegan Sobel, Briana Bettin, Brandon Martinez, James Kanka April 4th, 2014

  2. About Thunder Bay • Scientist: TaneCasserly, Maritime Archaeologist • National Oceanic and Atmospheric Administration • Thunder Bay National Marine Sanctuary • The Thunder Bay Website:www.thunderbay.noaa.gov • Our development website: http://www.csl.mtu.edu/classes/cs4760/www/projects/group3/www/

  3. The Thunder Bay App System • Android SDK application • Google Maps API for shipwreck points • SQL Database of shipwreck information • Primary Functions: Map View, Help View, Search View, Search Results, Individual Wreck Details View

  4. Environments & Types of Users • Research purposes • Planning a trip • General information/curiosity • While visiting the area • Hobbyists

  5. Usability Goals • Ease of use • Intuitive • Informative • Captivating – users want to use it

  6. Notable Prototype Design Changes • Map icons are planned to be shapes according to ship type, assuming map API and development time allow for this • The button bar along the top is now tabs • Likewise, the tabs now open a full tabbed view, rather than a partial dropdown within the existing view • The shipwrecks are being stored as query-able database lines, rather than objects • Branding of our logo and app name has been added to a title bar; a splash screen for app startup is pending • The name of the “home” tab has been changed to “map”

  7. Potential Development Concerns • Google Maps API not “playing nice” in application - Details like highlighting an individual wreck on the full map from its page as planned; or changing the pin icon styles, may need rethinking if there are issues. • Database interaction and correct population of data- New implementation of shipwreck data, originally were going to be individual objects; this redesign of the application may pose some hurdles as we finish up.

More Related