Difference between revisions of "Swim Sheets"

From ESE205 Wiki
Jump to navigation Jump to search
Line 85: Line 85:
  
 
==Results==
 
==Results==
 +
 +
'''Final App Layout'''
 +
 +
'''Demo Poster'''
 +
 +
'''Comparison to Objectives'''
 +
* Database
 +
* Connection between Database and App
 +
* Demo
 +
* User Interface
 +
* Results Display
 +
 +
'''Critical Decisions'''
 +
 +
'''Source Code'''
 +
  
  
 
[[Category:Projects]]
 
[[Category:Projects]]
 
[[Category:Fall 2017 Projects]]
 
[[Category:Fall 2017 Projects]]

Revision as of 03:12, 4 November 2017

Overview

A common problem at swim meets is the backup that occurs from timers having to record the times for each swim on paper. The times then have to be manually entered in case one of the touchpads in the water does not register the swimmers touch, resulting in a false time. The objective of our project is to create an IPhone app to assist with swim meets. We want timers at swim meets to be able to input the time they recorded for the swimmer, based on the event number, lane number, and heat number, into the app instead of writing it on paper. This will allow the times recorded to go directly into the database instead of having to be manually entered at the conclusion of each swim event.

Here is a link to the weekly log that will contain updates on our progress for the project: https://classes.engineering.wustl.edu/ese205/core/index.php?title=Swim_Sheets_Log

Team Members

Hailey Jenkins
Rebecca Bruce

Objectives

We want the IPhone app’s interface to prompt the user for the event number, heat number, and lane number. The app should then return the swimmer’s name based off the psych sheet for the overall meet. The user can then double check the accuracy of the name and override it if necessary. Once the swim is complete, a time will be entered and stored in an excel spreadsheet that could then be inputted into a swim database at a later time.


The main goals of this app are to:
1. Create a database that takes in the psych sheet and can report the swimmers name.

2. Prompt the user for event number, heat number, and lane number

3. Display data in an organized manner for overall meet results and analysis.

4. The database should take in an input of data, consisting of rosters, events, heat, and lane. These should be imported into the database from a .txt file that can be used by various teams to import into the database.

5. Results will be generated and be viewable from the database for the coaches use. These results can also be exported into a spreadsheet for viewing.

6. The data for each race will be received from inputs from the app, not an external source.

Challenges

Learn how to create a public IP address to update the times.

Learn how to create a database and PHP files.

Learn how to use Apple’s IDE to create the application.

Learn how to import the data from a document.

Learn how to use the iCloud server.

Learn how to override errors in the input process.

Gantt Chart

Gantt Chart UpDate.png












Budget

Blue Host: $3.95 per month for 3 months

ERD

An ERD is a way to model data that "graphically illustrates an information system's entities and the relationships between those entities". To generate this, we organized our data tables into separate entities on the graphs. We then put connections between the ID's that matched up in order to show how the different data tables interact with each other. ERD.png

https://www.techopedia.com/definition/1200/entity-relationship-diagram-erd


Draft of App Layout

Design and Solutions

Design Components

Interface

Server and Database

Results

Final App Layout

Demo Poster

Comparison to Objectives

  • Database
  • Connection between Database and App
  • Demo
  • User Interface
  • Results Display

Critical Decisions

Source Code