1 / 11

THS Athletic Android Application

THS Athletic Android Application. Jena, Kevin, and Sam. Codename: “Utopia Street”. Team Members: Sam, Jena, and Kevin Faculty Advisor: Dr. Vegdahl Industry Advisor: Dave Shanley ( CrowdCompass ) Client: Tumwater Athletics Department. Team Roles. Sam: Head Design Coordinator

dima
Download Presentation

THS Athletic Android Application

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. THS Athletic Android Application Jena, Kevin, and Sam

  2. Codename: “Utopia Street” • Team Members: • Sam, Jena, and Kevin • Faculty Advisor: Dr. Vegdahl • Industry Advisor: Dave Shanley(CrowdCompass) • Client: Tumwater Athletics Department

  3. Team Roles • Sam: • Head Design Coordinator • Website Manager • Mexican Cuisine Expert • Kevin: • Logician Coordinator • Head Fermented Beverage Consumer • Quality Assurance Lead • Jena: • Lead Technical Analyst • Technical Writing Specialist • App “Prettiness” Assurance

  4. Design Description • Who: Tumwater students, parents, supporters… • Available for free download online • What: Android App for THS Athletics • Schedules, rosters, contact information, statistics, etc. • Why: Communication between athletes, parents and supporters • Currently lacking the time, resources, and skills to create an application on their own

  5. Block Diagram

  6. Design Challenges • Data Conversion/Processing • How is the raw data inputted? • How can we quickly interpret it? • Android Emulator • Slow, cumbersome, intangible, etc.

  7. Important Decisions • Android vs. iOS • Layout/GUI Design

  8. Risks • Data Conversion • Decide how to handle info ahead of time • Support and Longevity • Provide enough information for maintenance • Handling Moving Parts • What if the website is down? • What if phone loses internet connection?

  9. Major Milestones

  10. Conclusion • Design Description • Design Challenges • Important Decisions • Risks • Milestones

  11. Image Locations • http://gerrycanavan.files.wordpress.com/2012/08/utopia.jpeg • http://imgur.com/LmAwa • http://xkcd.com • http://theandroidmaster.blogspot.com/2013/05/android-vsios.html • http://www.zoliblog.com/wordpress/wp-content/uploads/2010/04/86284.strip_.gif • http://uncensored-words.blogspot.com/2012/01/risk.html

More Related