Tumwater High School Athletics Android Application - WordPress@UP

fullfattruckMobile - Wireless

Dec 10, 2013 (3 years and 10 months ago)

101 views

Tumwater High School Athletics Android
Application

Requirements & Functional Specifications

Team Members: Kevin Conley, Sam Golloway, & Jena Graham (Team Lead)

University: University of Portland

School: Shiley School of Engineering

Course: CS

480

Faculty Advisor: Steven Vegdahl

Industry Advisor: Dave Shanley

Client: THS Atheltic Departement

Date: Fall 2013





THS ATHLETICS ANDROID APPLICATION



2

Table of Contents

Revision History

................................
................................
................................
..........

5

Introduction

................................
................................
................................
...............

6

Requirements

................................
................................
................................
.............

8

General Specifications:

................................
................................
................................
................................
...........

8

Specification 1: Android Mobile Device Equipped with Working Touchscreen

.............................

9

Specification 2: Data Plan or Wireless Internet Access

................................
................................
.............

9

Specification 3: General User Requirements Met

................................
................................
.........................

9

Specification 4: Access to RSS Feed Calendar w
ith Updated Information

................................
.......

9

Client
-
Driven Specifications:

................................
................................
................................
.............................

10

Specification 5: Robust Application

................................
................................
................................
.................

10

Specification 6: Today’s Events

................................
................................
................................
..........................

10

Specification 7: Schedules

................................
................................
................................
................................
.....

11

Specification 8: Rosters

................................
................................
................................
................................
..........

11

Specification 9: Contacts for Coaches and Athletic Administrators

................................
..................

11

Specification 10: Maps to
Venues

................................
................................
................................
......................

11

Specification 11: Highlights

................................
................................
................................
................................
.

11

Specification 12: News Lin
ks

................................
................................
................................
...............................

12

Specification 13: Gallery

................................
................................
................................
................................
.........

12

Specification 14: Documents

................................
................................
................................
...............................

12

Specification 15: Sponsors

................................
................................
................................
................................
....

12

Specification 16: Website Link

................................
................................
................................
............................

12

Specification 17: About THS Athletics

................................
................................
................................
.............

12

Specification 18: Adve
rtising Capabilities

................................
................................
................................
.....

12

Technical Specifications:

................................
................................
................................
................................
....

13

Specification 19:

Access to The Olympian RSS News Feed Links with Search Capabilities

....

13

Specification 20: Access to TSD Photo Streams

................................
................................
..........................

13

Specification 21: Access to Google Maps API

................................
................................
...............................

14

Specification 22: Access to YouTube Mobile Links

................................
................................
....................

14

Specification 23: Contacts for Coaches and Athletic Administrators

................................
...............

14

Specification 24: Ability to Download Application from Google Play Store

................................
..

14

Use Cases
................................
................................
................................
..................

15

Use Case 1:

................................
................................
................................
................................
................................

15

Use Case 2:

................................
................................
................................
................................
................................

15

Use Case 3:

................................
................................
................................
................................
................................

16

User Interface

................................
................................
................................
...........

17

Home Screen:

................................
................................
................................
................................
...........................

17

Today’s Events:

................................
................................
................................
................................
.......................

17

Schedules:

................................
................................
................................
................................
................................
.

18

Rosters:

................................
................................
................................
................................
................................
......

19

Contacts:

................................
................................
................................
................................
................................
....

20

Maps:

................................
................................
................................
................................
................................
...........

21

Highlights:

................................
................................
................................
................................
................................
.

22

News:

................................
................................
................................
................................
................................
..........

23

Gallery:

................................
................................
................................
................................
................................
.......

24

Sponsor:

................................
................................
................................
................................
................................
.....

25

THS ATHLETICS ANDROID APPLICATION



3

About:

................................
................................
................................
................................
................................
.........

26

Development Process

................................
................................
...............................

28

Milestones

................................
................................
................................
................

30

Milestone 1: Functional Specification Draft Submitted for
Review

................................
.................

31

Milestone 2: Functional Speciation Updates

................................
................................
.............................

31

Milestone 3:

Functional Specification Approved

................................
................................
.....................

31

Milestone 4: “Hello World”

................................
................................
................................
...............................

32

M
ilestone 5: Top 3 Concerns

................................
................................
................................
............................

32

Milestone 6: October Program Reviews Submitted for Review

................................
........................

32

Milestone 7: Design Document Draft Submitted for Review

................................
..............................

32

Milestone 8: Framework Demo

................................
................................
................................
.......................

32

Milestone 9: Design Document Approved

................................
................................
................................
..

32

Milestone 10: Home Screen Demo

................................
................................
................................
.................

32

Milestone 11: November Program Reviews Submitted for Review

................................
................

33

Milestone 12: First Working Icon Demo

................................
................................
................................
.....

33

Milestone 13: Revaluatio
n of Scale Review

................................
................................
...............................

33

Milestone 14: January Program Review Submitted for Review

................................
........................

33

Milestone 15: New Icon(s) Demo

................................
................................
................................
...................

33

Milestone 16: Above Icon(s) Final Approval

................................
................................
.............................

33

Milestone 17: February Program Review Submitted for Approval

................................
.................

33

Milestone 18: New Icon(s) Demo

................................
................................
................................
...................

34

Milestone 19: Above Icon(s) Final Approval

................................
................................
.............................

34

Milestone 20: Client Review Meeting

................................
................................
................................
...........

34

Milestone 21: Final Report Draft Submitted f
or Approval

................................
................................
..

34

Milestone 22: Fix Bug/Issues Raised By Client

................................
................................
........................

34

Mil
estone 23: Final Report Final Draft

................................
................................
................................
........

34

Milestone 24: Founders Day

................................
................................
................................
............................

35

Milestone 25: Post Mortem Presentation Submitted for Review

................................
.....................

35

Preliminary Budget

................................
................................
................................
...

36

Facilities

................................
................................
................................
...................

37

Risks

................................
................................
................................
.........................

38

Risk 1: Team members face
external deadlines
................................
................................
.......................

38

Risk 2: Learning Curve for Android development

................................
................................
..................

38

Risk 3: File Sharing Difficulties

................................
................................
................................
.......................

39

Risk 4: RSS Feed Inputs

................................
................................
................................
................................
......

39

Risk 5: Evergreen Conference Athletics does not Allow Access

................................
........................

39

Constraints

................................
................................
................................
...............

40

Technical

................................
................................
................................
................................
................................
...

40

Economic

................................
................................
................................
................................
................................
...

40

Environmental

................................
................................
................................
................................
........................

40

Social

................................
................................
................................
................................
................................
...........

40

Political

................................
................................
................................
................................
................................
......

40

Professional
................................
................................
................................
................................
..............................

40

Ethical

................................
................................
................................
................................
................................
.........

41

Legal

................................
................................
................................
................................
................................
............

41

Health and Safety

................................
................................
................................
................................
...................

41

THS ATHLETICS ANDROID APPLICATION



4

Security

................................
................................
................................
................................
................................
......

41

Manufacturability

................................
................................
................................
................................
..................

41

Sustainability

................................
................................
................................
................................
...........................

41

Standards

................................
................................
................................
................................
................................
..

42

Codes

................................
................................
................................
................................
................................
...........

42

Conclusion

................................
................................
................................
................

43

Bibliography

................................
................................
................................
.............

44

Glossary

................................
................................
................................
....................

45

GUI:

................................
................................
................................
................................
................................
..............

45

IDE:

................................
................................
................................
................................
................................
..............

45

RSS:

................................
................................
................................
................................
................................
..............

45

SDK:

................................
................................
................................
................................
................................
.............

45





THS ATHLETICS ANDROID APPLICATION



5

Revision History

Version Number

Date

Changes

0.1

September 10, 2013

Initial Draft Completed

0.
95

September 19, 2013

First Revision Set Completed

0.
96

September 27, 2013

Second Revision Set Completed

1.0

October 10, 2013

Final Revision Set Completed




THS ATHLETICS ANDROID APPLICATION



6

Introduction


With over 900,000 mobile applications currently for sale on the Apple App Store,
this
project will certainly not be revolutionary on a global scale, however, as the first
app in Tumwater High School history, it wil
l be innovative to
the
client. The app wi
ll
focus on the athletic department of Tumwater High School and will be utilized
to

communicate a variety of information including schedules, stats, and rosters to
student athletes, their parents, and high school administrators. Figure 1 shows a
basic moc
k
-
up of the home screen of the THS Athletic App.



Figure 1: THS Athletic App Home Screen Mock
-
Up


The absence of a current app for the athletic program

at Tumwater High School

serves as the motivation for undertaking this project.
The
team was approa
ched by
the client who wanted the ability to continue providing relevant information to the
student athletes in a form that was convenient to them. As the majority of student
THS ATHLETICS ANDROID APPLICATION



7

athletes use a smartphone as their mobile device, an app could provide an avenue

of
communica
tion that is currently lacking.


Android platform
was selected as a target platform

for a variety of reasons.
Currently holding the
larger
52.4% of the smartphone market share (
Solsman
),
Android devices are ubiquitous. The developers of the
project also have technical
experience with Java, the coding language in which Android applications are
developed, and the team faculty advisor has a greater knowledge base for Android
development

than for the iPhone
. Android applications can be developed

on any
machine type, unlike the next most influential platform

Appl
e

which can only be
developed on a Mac. Android is also powerful in its own right; a mobile operating
system that was developed

by Google can offer a wealth of support tools.
In fact,
“G
oogle has also released a device emulator so that programming and testing can be
done without access to a physical Android mobile device. In addition, tools for
debugging, memory, and performance profiling are included in a plugin for the
Eclipse integrate
d development environment” (
Managed Mayhem
, 15).


Application content will be generally simple in nature. The client has requested
there be icons and content for the following possible items: Today’s Events,
Schedules, Rosters, Athletic Coaches and Adm
inistrators Contacts, Maps to Venues,
Highlights, News Links, Gallery, Documents, and About. For the purpose of this
project,
the
team will ensure the first five items are addressed and progress to the
other items as time and success allows.


This
functional specification both define
s

and
clarifies
the
technical and functional
requirements necessary to create the THS Athletic Application.
The document starts
by describing the requirements for the application from the perspective of the
client, gene
ral requirement specifications, and technical specifications.
It then

outline
s

three possible use cases
,

the

user
interface
specifications,
the

development
process, milestones throughout the course of the project, preliminary budget
information, facilitie
s necessary to create the project, possible risks that the project
may face, and the

constraints
that may arise
.



THS ATHLETICS ANDROID APPLICATION



8

Requirements

As
shown
in Figure 2, the user will interact with the THS Athletic Application via
their
Android

Mobile Device. Once install
ed on the device, the user

will
interact
with the application via
the keyboard and touchscreen surfaces. If the application
requires information from an external RSS Feed Calendar or other Internet servers,
it will request the information and transport it
back into the application.


Figure 2: Block Diagram of App

In the following specifications,
it is

assume
d that

the first three requirements are
met when the application is run on a device. The priority rating allows
the

developers to gain all necessar
y information from the client while still maintaining
realistic
expectations

for the scope of the project.
S
pecifications with a priority
number above 8

and above

to be met by
completion
of the project
. A
dditional
specifications
will be
accomplished in or
der of priority
, with the overall goal of
meet
ing

all client ideal wishes.

General Specifications:

The general specifications
, as shown in Table 1,

that must be met by external
sources to minimally allow the THS Athletic Application to function.




THS ATHLETICS ANDROID APPLICATION



9

Table
1
: General Specifications


Specification Number

Priority Rating

Requirement
Specification

1

10

Android Mobile Device
Equipped

with
Working

Touchscreen

2

10

Data Plan or Wireless
Internet Access

3

10

General User
Requirements Met

4

10

Access to
RSS Feed
Calendar with Updated
Information


Specification 1: Android Mobile Device Equipped with Working Touchscreen

In ord
er for the application to work,
the

design assumes the user is operating an
Android Mobile device with access to the Goog
le Play Store. Much of the application
functionality also comes from gestures made by the user’s fingers on
the
device

s
touchscreen. Thus, for basic functionality
the

application also requires a working
touchscreen.

Specification 2: Data Plan or Wire
less Internet Access

The THS Athletics Application assumes that the Android device onto which the
application will be installed has access to data either via a wireless data plan or
wireless
Internet

access. Access will be necessary both to initially down
load the
application and receive pertinent updates on content as the application focuses on
continually changing content.

Specification 3: General User Requirements Met

The final assumption is that a user is generally able to operate a mobile device.
While the GUI design will attempt to make all interactions with the device as
intuitive as possible, mobile devices

have a
tendency

to be difficult for some users to
understand.
A

basic
comfort

with the mobile device

and the ability of the user to
operate a touch screen has been assumed
.
If time permits,
special modifications will
be made to the design to compensate for color blindness or other sight problems

as
will it be considered in the initial GUI design
.

Spec
ification 4:
Access to
RSS Feed Calendar with Updated Information

A
ccess
will be required
to an RSS Feed Calendar
with
the THS Athletic department
public schedules. This information is currently housed at a site managed by the
Evergreen Conference
,

and
is in RSS Feed form. While
modification permissions
would not
be
require
d
,
the project
would require read permissions for the calendar
to embed information within the THS Athletic Application.


THS ATHLETICS ANDROID APPLICATION



10

Client
-
Driven Specifications:

After gathering the client’s

ideal application content,
the

developers are able to rank
priorities
. These rankings will help with keeping the project within appropriate
scope.

The following
specifications

shown in Table 2

focus mainly on application
content.


Table
2
:
Client
-
Driv
en

Specifications


Specification Number

Priority Rating

Requirement
Specification

5

10

Robust Application

6

7

Today’s Events

7

10

Schedules

8

8

Rosters

9

9

Contacts for Coaches and
Athletic Administrators

10

6

Maps to Venues

11

4

Highlights

12

4

News Links

13

4

Gallery

14

6

Documents

15

8

Sponsors

16

7

Website Link

17

5

About THS Athletics

18

8

Advertising Capabilities


Specification 5: Robust Application

With a school population of approximately 1,200
and a studen
t athlete participation
rate of 50%
(
600

student
athletes
)

this application will need to be robust enough to
handle a fair amount of use. The number of potential users grows when one
considers the family and friends of the student
athletes

in addition to
general
community usage. The application should
allow for unlimited downloads via the
Google Play Store and should be able to support use from a moderate number of
users without crashing.


Specification 6: Today’s Events

Through the access given to the

athletic events calendar, this icon content will
contain a particular subsection of the calendar events

the events for the particular
day. This tab will
list all sports on a single screen and will not feature the ability to
view a single sport. This ic
on content

should display the events in a list format for
quick access.

THS ATHLETICS ANDROID APPLICATION



11

Specification 7: Schedules

This icon’s
content

will contain the full schedules, i.e. the full array of calendar
events from the RSS Feed
athletic

calendar. The application will fea
ture a drop
down menu (see User Interface section for example)
that allows the user to select
viewing the schedules for “All” sections or an individual section. The sections will
correspond to individual sports with specifications made between male and fe
male
teams (i.e. Football, Volleyball, Boys Tennis, Girls Tennis). The user will be able to
select the event that they want to open a screen with more detailed information
including any notes that appeared on the calendar entry and location information.

Specification 8: Rosters

Similarly to the

organization of the

Schedules content, the Roster icon’s content will
display the full array of student athletes currently participating at THS. This
information is currently held in a database maintained by the

Evergreen Conference,
however, the client is open to suggestions as to how the developers need to access
this information. The application will again, feature a drop down menu that will
also

allow

the user to see the athletes for “All”
sports or feature
a single sport

(i.e.
see all the Baseball players)
. The user will be able to select the athlete to display a
limited amount of additional information including some performance statistics and
basic player information. This additional knowledge will come
from the same
database.

Specification 9: Contacts for Coaches and Athletic Administrators

Content featured under the Contacts icon will be a list of coaches and
athletic

administrators. The page will feature a search bar at the top to allow users to
s
earch for
a

contact by name or
by

simply scroll
ing
. Selecting the name of the
contact can access the internal page that will feature contact information including
phone number and/or e
-
mail addresses.

Specification 10: Maps to Venues

The client has req
uested the local high schools

and thus frequent event venues

be
presented in the application for user knowledge. As Google is the parent of Android
and the development team is working with Google Maps in other courses it would
be a
powerful
additional fea
ture to include the Google Map of each location and let
Google Maps handle directions to take this stress off the developers.

Specification 11: Highlights

A previously existing YouTube video account featuring videos of Tumwater High
School athletes is a
lready in existence. The Highlights icon would take the user to a
mobile version of the YouTube account and the videos created by that account

a
capability that is already supported by YouTube if you simply access YouTube in a
mobile browser. In terms of

development, this page would essentially be an
embedded link.

THS ATHLETICS ANDROID APPLICATION



12

Specification 12: News Links

The Olympian is the local newspaper and hosts all of its news articles in a format
that allows for an RSS Feed to be easily set up based on a search term. The client
has asked that news articles on THS be gathered for easy access for the user.

Specifica
tion 13: Gallery

A previously existing
Flickr

photo stream featuring images of Tumwater High School
athletes is already in existence. After being granted permissions to access this
stream, the Gallery icon would take the user to a mobile version of the
Fl
ickr

stream

a capability that is already supported by
Flickr
. In terms of development, this page
would
essentially

be an
embedded

link.

Specification 14: Documents

The content behind the Documents icon would serve as a gathering place for
important d
ocuments. The client has requested PDF versions of documents such as
the athletic code, medical releases, and travel releases

to

be stored in a location that
is easy for the student athletics and their guardians to access. These would be static
documents

that would be linked to a URL where they are already stored on the
Tumwater High School Athletics website.

Specification 15: Sponsors

This icon’s content would provide a list of companies with their company logo.
Please see Specification 18 for additi
onal details concerning why this was a
requested item within the application.
As this would be a new sales point for the
alethic program, the sponsor’s information is not currently stored in any external
data structure. Developers and client could agree
upon where the application
retrieves this information.

Specification 16: Website Link

By selecting this icon, the user will be taken to the THS Athletics website:
http://www.tumwater.k12.wa.us/site/Default.aspx?PageType=1&SiteID=9&Chann
elID=103&DirectoryType=6
. Should there be any required information tha
t is
not
featured in the application,

the client would like direct and easy access to the
website. The developers will not worry about making this website mobile friendly

the icon will simply serve as an embedded link.

Specification 17
: About THS Athle
tics

As the name implies, the About icon page will feature basic information regarding
the THS Athletic Department including general phone numbers and e
-
mail
addresses. Although much of this information is included in the Contacts section,
this will allow

the user easy access to the information should they need basic
questions answered.

Specification

18
: Advertising Capabilities

Via the
Sponsors

content page, possible static images on the home screen, and the
embedded

sponsor logo in the
navigation

bro
wser

the client has requested
advertising

capabilities be available
in the application.

THS ATHLETICS ANDROID APPLICATION



13


A public high school, two years ago funding cuts by the state legislator forced the
implementation of a Pay
-
To
-
Play fee that
charges

every student athlete a fee to
p
articipate in each sport they choose to play
. This can cause financial hardships and
hinder some student athletes’ ability to
participate

so the athletic department offers
a limited number of scholarships for the fee. These scholarships are currently
fun
ded from a variety of sources, including ads by local business in the programs of
events. By providing a sponsorship opportunity in a technological form for the
school the application would be able to aid in the funding of more scholarships
while also giv
ing local businesses a chance to support the youth of their community.


Technical Specifications:

The specifications that must be met for the application to be a functional product
can be seen in Table 3.


Table 3: Technical Specifications


Specification Number

Priority Rating

Requirement
Specification

1
9

7

Access to The Olympian
RSS News Feed Links with
Search Capabilities

20

7

Access to TSD Photo
Streams

21

7

Access to Google Maps API

2
2

7

Access to YouTube Mobile
Links

2
3

10

Contacts for Coaches and
Athletic Administrators

24

10

Ability to Download
Application from Google
Play Store



Specification
19
: Access to The Olympian RSS News Feed Links with Search
Capabilities

Developers need the ability to access the RSS News Feeds from The Olympian. The
Olympian allows free access to their feeds with read
-
only
permissions that

would be
suitable

for this project. However, the application code will need the functionality to
ac
cess this information and display it in an application
friendly

format.

Specification
20
: Access to TSD Photo Streams

Developers

need the
ability to

access the TSD Photo Stea
ms of the images of THS
Athletes. Flickr already has the functionality to disp
lay their photo streams in a
THS ATHLETICS ANDROID APPLICATION



14

mobile friendly format so the code of the application would need to embed the link
to the mobile version of the photo stream.

Specification
21
: Access to Google Maps API

The Google Maps API is included in the Android developer

toolkit, however, the
code of the application would need the functionality to communicate properly with
Google Maps to produce the maps and directional services for each athletic venue.

Sp
ecification
22
: Access to YouTube Mobile Links

Developers need t
he ability to access the THS Athletics YouTube account listing.
YouTube already has the functionality to display their videos and video lists in a
mobile friendly format so the code of the application would need to embed the link
to the mobile version.

Sp
ecification
23
: Contacts for Coaches and Athletic Administrators

The client and developers will need to work together to produce a database where
this information is stored that can be read into the application and altered by the
client after the finish
ed product

has been released

and
support is
no longer
being
provid
ed
.

As this would be a new feature for the alethic program, the contact
information is not currently stored in any external dat
abase
. Developers and client
could agree upon where the application retrieves this information.

Specification 24: Ability to Download Application from Google Play Store

By following all the Google developer protocol, the application should pass all
necessar
y requirements to allow it to be downloaded from the Google Play Store
onto Android mobile devices.



THS ATHLETICS ANDROID APPLICATION



15

Use Cases


Use Case 1:

Scenario:
User Initially Downloads the THS Athletics Application

Context:
After powering on their
Android

based mobile device,
the user would
need to ensure they had access to data via cell tower or wireless network. The user
then
navigates

to the Google Play Store via their phon
e interface and searches for
“THS Athletics”. The user will select the app logo from the search resul
ts and select
“Download”. After confirming the download, the user will need to wait for the
download to complete and choose to open the THS Athletics app in which case the
user will be brought to the
home screen of the Application
.

People Involved:

End

a
pplication user

Devices Involved:

Android Device. The device must either be connected to a
wireless network via a wireless chip or have a data plan available for its use.

Possible Issue 1:

The phone does not have enough storage available to download
the

application
.

Viable Solution 1:
On
the development
end,
the
team

must do
their
best to

ensure

that the

size of the app
is
realistic.
It must also be

en
sure
d that

the Google Play
store

will
alert

the user that there is not enough space before the downloa
d begins.

Possible Issue 2:

Once the download is confirmed and is in progress, the download
could get interrupted due to an interruption in service or loss of power to the
Android device.

Viable Solution 2:

Again,
it should be

to
confirm

with the Google Play store that a
possible corruption in the file due to errors while downloading are handled by the
store as part of hosting the application.

Use Case 2:

Scenario:
User is “flipping” through possible
icons for selection while on the home

screen

Context:
The Android device is currently in use and the THS Athletics Application is
open. The user is interacting with the app by flicking through the possible icons for
selection on the bottom of the home page. The user must be able to accomplish this
by placin
g their finger anywhere on the touchscreen of the device and dragging their
finger to the right or left.

People Involved:

Smartphone and application user

Devices Involved:

Android Device. The device must either be connected to a
wireless network via a

wireless chip or have a data plan available for its use.

Possible Issue 1:

The user places their finger on an area of the screen that
is not
connected to the move action.

Viable Solution 1:
The GUI design of the application must be intuitive enough th
at
the user can easily see how to access the additional functionality on the second
piece of the home screen and the application must sense actions in a realistically
large area to respond to user input that may not be perfectly precise.

Possible Issue 2
:

The Android device being utilized by the user is not equipped
with a touchscreen or the touchscreen is broken.


THS ATHLETICS ANDROID APPLICATION



16

Viable Solution 2:

It must be made
clear in
the
documentation that a touchscreen
or similar capabilities are required to utilize the appl
ication.

Use Case 3:

Scenario:
User Wants to Access Contact Information

Context:
The Android device is currently in use and the THS Athletics Application is
open. The user is interacting with the app

and wishes to know the contact
information for the

head football coach at Tumwater High School. The user would
then select the “Contact” icon and be taken to a list of coaching and administrative
contacts where they could either utilize the search bar or scroll through the
possibilities. The
user would
then select the appropriate contact and be taken to the
information page on the person.

People Involved:

Smartphone and application user

Devices Involved:

Android Device. The device must either be connected to a
wireless network via a wireless chip or

have a data plan available for its use.

Possible Issue 1:

The user is unable to
determine

which icon takes them to the
desired information.

Viable Solution 1:
Again, this comes down to GUI design. The application should
not have too many icons so as
not to confuse the user.
The

team will also need to
work with the client to determine the best titles for each icon.



THS ATHLETICS ANDROID APPLICATION



17

User Interface


The THS Athletic App will have a variety of
GUI’s,

as there must be a GUI for each
icon of content from the home screen of the application. The following images are
simply mock
-
ups and the development team reserves the right to produce a product
that looks different than imaged below.

Home Screen:

The
home screen has swipe
-
able icons to move from the initial set of six icons to a
second set of icons for more functionality

as shown in Figures 3 and 4
.



Figure
3
: Home Screen 1 Mock
-
Up



Figure
4
: Home Screen 2 Mock
-
Up

Today’s Events:

Quiet explanatory, this icon will feature access to the embedded RSS calendar for the
events

for that day

as shown in Figures 5 and 6
.



Figure
5
: Today’s Events Icon
Screen Mock
-
Up



Figure
6
: Today’s Events Icon
Internal Screen Mock
-
Up

Schedules:

This content will display upcoming events, listed in
chronological order

as shown in
Figure 7
. There will also be a drop
-
down tab to narrow the events by sport

shown
in Figure 8
.



Figure
7
:
Schedule Icon Screen
Mock
-
Up



Figure
8
: Schedule Icon Drop Down
Screen Mock
-
Up

Rosters:

This content will display student athletes, listed in alphabetical order

shown in
Figure 9
. There will also be a drop
-
down tab to narrow the athletes by sport.


THS ATHLETICS ANDROID APPLICATION



20


Figure
9
: Roster Icon Screen Mock
-
Up

Contacts:

Containing the e
-
mail and phone n
umbers of both coaches and athletic
administrators, this page will offer the ability to search for a specific contact or
scroll through to find the desired contact

as shown in Figures 10 and 11
.



Figure
10
: Contacts Icon Screen
Mock
-
Up



Figure
11
: Contacts Icon Internal
Screen Mock
-
Up

Maps:

L
inks to external Google Maps that allow the user to select which local hig
h school
they wish to travel
to

and then be connected with the Google Map

as shown in
Figures 12 and 13
. T
his will require additional API functionality for Google Maps.



Figure
12
: Maps to Venues Icon
Screen Mock
-
Up



Figure
13
: Maps to Venues Internal
Screen Mock
-
Up

Highlights:

This page will feature a l
ink to external YouTube mobile
site that is housed within
the

application framework (i.e. it would be just like going to a website)
.
A
ccess
ing

the YouTube API
should not be necessary
because the content will be a link to an
external source

not embedded wi
thin the application
. The mock
-
up image
, Figure
14,

is displaying a mobile YouTube site for ESPN search.



THS ATHLETICS ANDROID APPLICATION



23


Figure
14
: Highlights Icon Screen Mock
-
Up


News:

Link to external RSS Feed for the local newspaper

The Olympian

with search
functionality for Tumwater High School enabled. This runs the risk we will display
news stories on the high school in general within
the

athletic focused app but that
does not
appe
ar to be of great concern. The mock
-
up
, Figure 15,

shows an RSS Feed
for Yahoo Sports News.


THS ATHLETICS ANDROID APPLICATION



24


Figure
15
: News Link Icon Screen Mock
-
Up

Gallery:


Displays pictures from the Tumwater Athletic Flickr Feed. Again,
the

team
should
not
need access to the
Flickr API because the content will be a link to an external
source

not embedded within the application. The mock
-
up image
, Figure 16,

is
displaying a simply Flickr RSS Feed Creation Search for the term “sports”.




THS ATHLETICS ANDROID APPLICATION



25


Figure
16
: Gallery Icon Screen Moc
k
-
Up

Sponsor:

The sponsor tab will allow for some
revenue
for THS Athletic program through
which sponsors can be listed under this icon tab. The GUI is nearly identical to the
Contacts icon page, with companies replacing individuals

as shown in Figure 17
.


THS ATHLETICS ANDROID APPLICATION



26


Figure
17
: Sponsor Icon Screen Mock
-
Up

About:

The About icon screen lists the relevant contact information for the Tumwater High
School Athletic Department

as shown in Figure 18
.


THS ATHLETICS ANDROID APPLICATION



27


Figure
18
: About Icon Screen Mock
-
Up




THS ATHLETICS ANDROID APPLICATION



28

Development Process


The compartmentalized nature of this application lends itself to a development
process that is based on iterative and incremental development and implantation.
The THS Athletic Application will use an approach similar to the Agile Software
Development mod
el. As illustrated in Figure
19
, the Agile Software Development
model allows the developers to focus on a single feature for a short period of time
and move that single feature (i.e. the Contact section of the application) through the
development cycle be
fore starting over with a new feature to implement
. Simply
put, the main idea of Agile Programming “program one feature at a time, always
preparing a full release at the end of each feature” (
Crenshaw
, 54
).



Figure
19
: Agile Software Development


The

first step of this process is to refer to the function and design specification
documents

to understand exact
ly

what the feature is to
accomplish
, the information
it is to contain, and how this information will be brought into the application.
Next,
the
specifics of the architecture and design of the feature will be determined and the
developers move on to implementing the feature. Again, the development phase in
an Agile Software Development model allows for an iterative and incremental
approach that al
lows the developers to get small pieces of the system working fully
at a time before moving on to the next. After the small feature appears to be
functioning, the feature can be brought to other team members, faculty advisors,
and the client for feedback.


By utilizing the Agile Software Development Model the THS Athletic Application
becomes slightly more flexible for both the developers and the client. As cited by a
few of the Agile Manifesto’s the project will “welcome changing requirements, even
late i
n
development
. Agile processes harness change for the customer’s competitive
advantage” (
Crenshaw
, 66) as long as the changes are within reason. This method
THS ATHLETICS ANDROID APPLICATION



29

will also be beneficial for the programmers moral as another manifesto states that
“working softw
are is the primary measure of progress” (
Crenshaw
, 67) and this
method allows the team to have something a new feature to demo
nstrate

to both the
client and faculty advisor about once a month.


Due to the fact the THS Athletic Application requires a core

framework to function
and before the developers can begin adding features in the process described above,
the

team will have to modify the traditional Agile Software Development Model
slightly to allow for the idea that a large milestone will be required
before features
can be added. After the framework
has been completed
,
the

team can revert to the
more
accepted Agile
methodologies, however, before the framework is completed
the team
will follow many identical internal steps but the timeline will be exte
nded
from weekly measures to monthly ones.
. The monthly milestones will represent
entire icon functionality while there will be weekly sub milestones within each
content development milestone.



THS ATHLETICS ANDROID APPLICATION



30

Milestones


The milestones of the THS Athletics Application development team are listed below
in Table
5
.


Table
5
: Milestones


Number

Description

Deadline

Major or Minor

1

Functional
Specification D
raft
Submitted for
Review

September 15,
2013

Major

2

Functional
Specification
Updates

September 22,
2013

Minor

3

Functional
Specification
Approved

October 4, 2013

Minor

4

“Hello World”

佣瑯t敲‶,′013

M慪潲

5

Top 3 Concerns

October 11, 2013

Minor

Fall Break Week

6

October Program
Reviews

Submitted

for Review

October 22, 2013

Minor

7

Design Document
Draft Submitted for
Review

October 27, 2013

Major

8

Framework Demo

November 3, 2013

Major

9

Design Document
Approved

November 10,
2013

Minor

10

Home Screen Demo

November 22,
2013

Major

1
1

November Program
Reviews Submitted
for Review

November 27,
2013

Minor

Thanksgiving Break

1
2

First Working Icon
Demo

December 8, 2013

Major

1
3

Revaluation of
Scale Review

December 15,
2013

Minor

Winter Vacation

1
4

January Program
Review Submitted
for Review

January 19,

2014

Minor

1
5

New Icon(s) Demo

January 26, 2014

Major

THS ATHLETICS ANDROID APPLICATION



31

1
6

Above Icon(s) Final
Approval

February 2, 2014

Minor

1
7

February Program
Review Submitted
for Approval

February 26, 2014

Minor

18

New Icon(s) Demo

February 22, 2014

Major

19

Above Icon(s) Final
Approval

February 28, 2014

Minor

20

Client Review
Meeting

March 2, 2014

Minor

21

Final Report Draft
Submitted for
Approval

March 7, 2014

Major

Spring Break

22

Fix Bug/Issues
Raised by Client

March 19, 2014

Minor

23

Final Report Final
Draft

March 30,
201
4

Minor

24

Founders Day
Preparation

April 3, 2014

Major

2
5

Founders Day

April 8, 201
4

Major

2
6

Post Mortem
Presentation
Submitted for
Review

April 15, 201
4

Minor



Milestone 1: Functional Specification Draft Submitted for Review

The Functional Specification for the THS Athletic Application is expected to be
“content finished” and ready for the first faculty review. This allows ample time for
several revisions before the next milestone. This milestone will be considered a
success

if a copy of the functional specifications with all sections written is
submitted to Dr. Vegdahl in electronic format before the midnight on September 15,
2013.

Milestone 2: Functional Speciation Updates

After this review, the document will progress to

version 0.95 and be ready to submit
to
the

senior design instructor. This milestone will be considered a success if a
faculty advisor approved copy is submitted on time to Dr. Albright.

Milestone 3: Functional Specification Approved

The functional spe
cification document will be considered approved once the faculty
advisor, senior design
instructor, industry advisor, and client have
reviewed
the
document. It will then become version 1.0. This milestone will be considered a
THS ATHLETICS ANDROID APPLICATION



32

success if the document is a
ble to garner approval from the above parties by
midnight on
October 4, 2013.


Milestone 4: “Hello World”

After installing all necessary software, receiving the Android test device, and
becoming

familiar
with the
large amount
of information required to run a simple
test application
the
team will attempt the classic “Hello World” application via the
Android similar. If
textual output is

produce
d

on

the screen of the simulator
,

the
milestone will be considered a success.

Miles
tone 5: Top 3 Concerns

The team will spend some development hours in an effort to achieve the future
Home Screen Milestone
. Throughout this time the team should gain
better idea
for
what

elements of the project are going to present the largest challenge
(i.e. GUI,
external information, etc.). Each team member will submit a Basecamp message
outlining his or her three biggest concerns moving forward with development. It
will be a success if all team
members

submit the message by midnight.

Milestone 6:
October Program Reviews Submitted for Review

A draft that the team considers final of their October Review will be submitted to
the

faculty advisor for review and suggestions before the presentation in lecture. This
milestone will be considered a success
if the presentation is submitted electronically
to
the

faculty advisor by noon.

Milestone 7: Design Document Draft Submitted for Review

The Design Document for the THS Athletic Application is expected to be “content
finished” and ready for the first fac
ulty review. This allows ample time for several
revisions before the next milestone. This milestone will be considered a success if a
copy of the design document with all sections written is submitted to Dr. Vegdahl in
electronic format before the midnig
ht.

Milestone 8
:
Framework Demo

The application framework should be done by this milestone. The
precise

definition
of the framework will be clarified with the design document
;
the framework is not
expected to be perfect with this milestone but rather be
far enough along to be
demoed.

Milestone 9: Design Document Approved

The design document will be considered approved once the faculty advisor, senior
design instructor,

and

industry advisor

have
review
the document. It will then
become version 1.0. Th
is milestone will be considered a success if the document is
able to garner approval from the above parties by midnight.

Milestone 10: Home Screen Demo

As the first major
code
-
intensive milestone, the home screen demo will showcase an
application that op
ens to the home screen and has GUI elements and icons in place.
The home screen should be “swipeable” to move to the next set of icons and
THS ATHLETICS ANDROID APPLICATION



33

selection of each icon should result in the application moving to that particular piece
of content. At this point,
each content page can simply be a blank application
file/page. This milestone will be considered a success if the above functionality is
achieved on the Android simulator.

Milestone 1
1
: November Program Reviews Submitted for Review

A draft that the team considers final of their
November

Review will be submitted to
the

faculty advisor for review and suggestions before the presentation in lecture.
This milestone will be considered a success if the presentation is submitted
electronica
lly to
the

faculty advisor by noon.

Milestone 1
2
: First Working Icon Demo

This milestone will showcase the Scheduling tab completed. The content will be
reflecting information stored in an external calendar and will include some sort of
separation between the different sport schedules. This milestone will be considered
a succe
ss if the above functionality is achieved on the Android simulator.

Milestone 1
3
: Revaluation of Scale Review

At this point, all team members should have a better idea of the scope and difficulty
level each icon worth of content contains and will evalua
te how many of the
original

ideal specifications can be met within
the

time
frame
. This milestone will be
considered a success if all team members submit a Basecamp message with their
evaluation, what icons should be completed, what icons should be elimin
ated (if
any), and the reasoning behind elimination.

Milestone 1
4
:


January Program Review Submitted for Review

A draft that the team considers final of their January Review will be submitted to
the

faculty advisor for review and suggestions before the p
resentation in lecture. This
milestone will be considered a success if the presentation is submitted electronically
to
the

faculty advisor by noon.

Milestone 1
5
: New Icon(s) Demo

This milestone should feature 1/3 of the agreed upon icons completed and
ready for
a soft demo. The functionality should be as outlined in the technical specification
and content should come from external sources. This milestone will be considered a
success if a demo of the above features can be performed.

Milestone 1
6
: Ab
ove Icon(s) Final Approval

After taking into account faculty and industry advisors suggestions, the new
functionality will be demoed to the client. If the client is presented with a stable
version of the feature via the Android simulator the milestone wil
l be considered a
success.

Milestone 1
7
: February Program Review Submitted for Approval

A draft that the team considers final of their February Review will be submitted to
the

faculty advisor for review and suggestions before the presentation in lecture
.
THS ATHLETICS ANDROID APPLICATION



34

This milestone will be considered a success if the presentation is submitted
electronically to
the

faculty advisor by noon.

Milestone
18
: New Icon(s) Demo

This milestone should feature 1/3 of the agreed upon icons completed and ready for
a soft demo.

The functionality should be as outlined in the technical specification
and content should come from external sources. This milestone will be considered a
success if a demo of the above features can be performed.

Milestone
19
: Above Icon(s) Final Appr
oval

After taking into account faculty and industry advisors suggestions, the new
functionality will be demoed to the client. If the client is presented with a stable
version of the feature via the Android simulator the milestone will be considered a
succ
ess.

Milestone 20: Client Review Meeting

While the team has done internal evaluations on the progress, developers now meet
with the client to determine which content icons are essential to the overall success
of the project and must be completed. This
milestone will be considered a success if
a meeting occurs with the client by the specified date.

Milestone 2
1
: Final Report Draft Submitted for Approval

The
Final Report

Document for the THS Athletic Application is expected to be
“content finished” and ready for the first faculty review. This allows ample time for
several revisions before the next milestone. This milestone will be considered a
success if a copy of the
f
inal report

document with all sections written is submitted
to Dr. Vegdahl in electronic format before the midnight.

Milestone 22: Fix Bug/Issues Raised By Client

After the client has had the opportunity to do some load testing and to test the
applicatio
n in the manners it will actually be used, the client will submit to the
development team a bug report and the team will evaluate which they feel are actual
bugs and which are perhaps design clarifications. The team will fix bugs and resolve
issues.

Mile
stone 2
3
: Final Report Final Draft

The final report document will be considered approved once the faculty advisor,
senior design instructor, industry advisor, and client have approved the document.
It will then become version 1.0. This milestone will be

considered a success if the
document is able to garner approval from the above parties by midnight.

Milestone 24: Founders Day Preparation

This milestone encompasses the preparation of all content and presentations that
must be ready for Founders Day.
The team will have their presentation approved by
the faculty advisors. The team will also schedule a dry run presentation at least five
days before Founders Day to practice the presentation with the faculty advisor and
THS ATHLETICS ANDROID APPLICATION



35

industry advisor in attendance. Th
is milestone will be considered a success if the
presentation is approved by the faculty advisor.

Milestone 2
5 Founders

Day

This milestone encompasses all content and presentations that must be ready for
Founders Day. It will be
considered a success if
we have a working product to demo
and all team members make it to the presentation!


Milestone 2
6
: Post Mortem Presentation Submitted for Review

A draft that the team considers final of their Post Mortem Review will be submitted
to
the

faculty advisor for

review and suggestions before the presentation in lecture
and to the junior class. This milestone will be considered a success if the
presentation is submitted electronically to
the

faculty advisor by noon.


THS ATHLETICS ANDROID APPLICATION



36

Preliminary Budget

The initial estimate of
the costs associated with the THS Athletic Application can be
seen itemized in Table
6
.


Table
6
: Preliminary Budget


Material
Description

Number Requested

Rate per Item

Total Amount per
Material

Android Mobile
Device

1

$250

$250

Publication Costs

1

$35

$35

Printing Costs

300

$0.05

$15


Total Requested: $300


Android Mobile Device:

The Android mobile device will be utilized for testing
purposes and allows all members of the team to test on an actual device, even if they
do not have an Android based smartphone.


Publication Costs:

The THS Athletic Application will be available for
free download
on the Google Play Store, however,
the client
will be required to pay a one time fee
of $35 to publish the application to the store.
(
Android SDK
,
Launch Checklist
)


Printing Costs:

Any documents that need to be reviewed in hard
-
copy form o
r any
design mock
-
ups that may need to be printed will be paid for with this budget line
item.




THS ATHLETICS ANDROID APPLICATION



37

Facilities

As the THS Athletic Application is mainly software based the project will require
little in terms of facilities from the Shiley School of Engine
ering.
The

developers
request access to the Senior Development Room. The team will also need access to a
machine loaded with the Eclipse IDE (Eclipse) and permission to install the Android
SDK.


The Android SDK will allow developers access to the “API
libraries and developer
tools necessary to build, test, and debug apps
for Android” (
Launch Cheklist
,
Android SDK
). This package will ensure
that the team
are using the latest version
Eclipse and will provide Android SDK Tools, Android Platform
-
tools, the

latest
Android platform, and the latest Android system image for the emulator.



THS ATHLETICS ANDROID APPLICATION



38

Risks

The THS Athletic Application development process could face several risks and
issues as are summarized in Table
7
.


Table
7
: Possible Project Risks


Risk

Severity

Likelihood

Team members face
external deadlines from
other course work
and/or life events

Low

High

Learning curve for
Android development
and new environments
proves to be
steep

Moderate

Moderate

File sharing between
Mac and PC is difficult

Low

Low

RSS

Feed inputs for the
calendar are not
cooperative with the
Android specifications

High

Moderate

Evergreen Conference
Athletics will not allow
access to Calendars

High

Low


Risk 1: Team members face external deadlines

As all team members are seniors, the

external deadlines from other courses are
expected to be heavy. With all team members having similar schedules, an exam in
another course could shift focus from the project. Team members
may also need

to
leave town for personal or professional reasons,
such as interviews. To compensate
for course work,
the

milestones have been planned with other course major projects
and exams in mind.
The team
have also attempted to set early internal deadlines to
make missing one less detrimental for the actual miles
tone. To compensate for
external events, when individual team members become busy or leave town, the
responsibilities can be redistributed to other team members.

Risk 2: Learning Curve for Android development

As with any new program and development env
ironment, there will be a great deal
of new information to learn about
regarding
both the Android development process
and the environments in which
the
application

will be
running
. While
this is
expected
to be an only moderately occurring risk, starting
t
o get familiar

early via
test programs (“Hello World” for example) will allow us to identify where
difficulties may occur and then do
the
best

job possible

to ask questions of advisors
and guide
-
books early.

THS ATHLETICS ANDROID APPLICATION



39

Risk 3: File Sharing Difficulties

Two team me
mbers work on personal PC’s. One team member and the faculty
advisor work on Mac’s. This could prove difficult to share some files if the operating
system alter the files in any way to run on each particular machine

if a program
runs differently on a Mac

then it does a PC
. To compensate for this risk, we will
share
the

first
“Hello World”
test program

between the machines to ensure smooth
transfers. If there proves to be an issue, we can use an external
file hosting and
version
-
tracking

site to keep all

the “machine
-
unspecific” files and then only fully
compile them on
individual machines.


Risk 4: RSS Feed Inputs

There is a moderate risk that the client’s RSS Feed Calendar will not
align

nicely into
an
Android

development environment. If this were to be the case, it would be
detrimental

as the priority functionality of the app is to display
athletic

events via
such a calendar. Should this risk come to
fruition
, we have spoken with the client
about gathering their information in different formats. We could create
a

RSS Feed
Calendar, which the client could update,

and those updates could then
propagate

into
the
app
-
this solution simply gives us more control ove
r the specifics of the RSS
Feed.

Risk 5: Evergreen Conference Athletics
does not
Allow Access

There is a low likelihood that the external company that manages the

calendars for
all high schools

in Tumwater High School’s Athletic Conference

the Evergreen

Conference

will not allow
the
team access to the databases where statistic
information is stored. Although they have allowed development teams for other
schools access in the past

one team was granted access as recently as last year

there is a small chan
ce that such access will not be given. To compensate for this,
the team
will work through
the

client for access and begin the request process early
to allow for any difficulties that may arise.





THS ATHLETICS ANDROID APPLICATION



40

Constraints


Technical

In terms of just technical impac
ts,
the

application is hardly revolutionary in the f
ield
of computing
. However, as the first school in the athletic conference to have an
application
the

project may inspire similar undertakings by the local high school
athletic programs
who

may use
the

d
esign and technical implementations as a
model.

Economic

As
the

application contains an icon page with content that is concerning
sponsorship of the application,
the

project does have the opportunity to make a
positive financial impact on the THS Athletic
Department. A public high school, two
years ago funding cuts by the state legislator forced the implementation of a Pay
-
To
-
Play
fee that
changes every student athlete a fee to participate in each sport they
choose to play. This can cause financial hardsh
ips and hinder some student athletes’
ability to
participate

so the athletic department offers a limited number of
scholarships for the fee. These scholarships are currently funded from a variety of
sources, including ads by local business in the programs of events. By providing a
sponsorship opportunity in a tech
nological form for the school
the team is

aiding
in
the funding of more scholarships while also giving local businesses a chance to
support the youth of their community.


Environmental

As
the

project does not result in the physical construction of any dev
ice, building,
etc.
, there are

no environmental concerns to consider;
this topic does not apply
.

Social

The

project could have
a significant, positive

impact on the social aspects of the
Tumwater community
,

as the student athletes could witness a rise in

their
supporters as more people attend the sporting events due to the fact it is easier to
access schedules and directional information. As many could testify, athletics have
the ability to bond individuals and this application could simply get them in t
he
same location for this to happen.

Political

As
the

project does not have any political or influential content of which to consider
the team
have no political constraints;
this topic does not apply
.

Professional

The areas of professional implications

financial profits, future developer
inspirations, or sustainability

are covered in other sections leaving no areas of
concern that are exclusively professional;
this topic does not apply
.


THS ATHLETICS ANDROID APPLICATION



41

Ethical

The THS
Athletic
Application will be interacting with the Evergreen Conference
Calendar and must take the appropriate measures to ensure that
the

application
does not change or damage the original version of the calendar. When using
someone

else’s
, or some other
company’s
, data and data systems
the team
must
ethically ensure that
they
are being good stewards of their property.

Legal

The majority of the students featured on the application Roster section are under 18
years of age.
The team
must be mindful of this fact
wh
en

generating content for the
application and ensure that appropriate permissions have been granted. The client
via their student athlete release forms will handle this aspect of the application.

Health and Safety

Although not truly personal information
,
the application
will be featuring the name
and statistics of student
athletes; this
will be available for both outsiders and their
student peers. It may seem
extreme

but
the application
must be
mindful

of a
student athlete who
is not
performing

well and

the mental
implications

that may
come from this statistic information being published for their peers to view.
The
team
also want
s

to be concerned with the safety of the student
athletes

in terms of
putting their name publically in
the

application. This

concern, however, can be
mitigated

by the idea that most students have Facebook or other social media
accounts so the information is
probably

already public.

Security

The

application
need
not be particularly secure, however, it must have basic
security
aspects that would protect the end user from malicious developers utilizing
the

application as an access point to the end user’s device.

Manufacturability

As
the

project does not result in the physical construction of any device, building,
etc.
the team
has
no manufacturing concerns of which to consider;
this topic does
not apply
.

Sustainability

Sustainability is a
major

concern

throughout the course of development and design
on the THS Athletic Application as
the
team will generally not be available to update
after handing the final project to
the

client.

This results in the need to have very
well documented code for other developers to update at a later date. The
application should also gather the content from
external sources (i.e. the RSS Feed
Calendar, etc.) that will continue to be updated and
the

application can simply
propagate these updates. This will result in an application that is nearly self
-
sufficient in terms of content update.


THS ATHLETICS ANDROID APPLICATION



42

Standards

The

tea
m must do
its

very best to utilize good coding standards and produce solid,
clean, and reliable code for the application. Should the interest be sparked with
other high schools in the area to create a similar application,
an AP Computer
Science class woul
d probably create the other applications
.
The developers
must be
good stewards and teachers through example by giving these new developers
quality code from which to base their own product upon.

Codes

As
the
project does not result in the physical
const
ruction

of any device, building,
etc.
the team has
no codes of which

to consider;
this topic does not apply
.




THS ATHLETICS ANDROID APPLICATION



43

Conclusion


The Tumwater High School Athletics Application seeks to provide a revolutionary
product to a client who has requested a new way to

communicate with student
athletes and the greater community. End users will be able to view today’s events,
see a more comprehensive schedule of events, locate contact information and team
rosters, access venue information, connect to external forms of m
edia, and retrieve
important documents from within the Android based application.


The

team is utilizing a language
with which they

are already
familiar.

Additionally,
it

will be able to use the free Android SDK and Android mobile device to simulate
testing of the application.
This will allow instant feedback for how the application
will function on the actual device of use.


The portion of the THS Athletic Application is likely to come from the large number
of external sources that must cooperate with
the
project code in order for the
application to function properly. The main concern is the RSS Feed Calendars as the
schedule
s provide the backbone of content to the application and must be
dynamically updateable after
the developers
have finished the project development.


As an application that has the potential to be used by thousands every day,
the
development team has the
opportunity to provide an exciting resource and spark
the interest for possible similar projects via
the
THS Athletic Android Application.






THS ATHLETICS ANDROID APPLICATION



44

Bibliography

"Athletics Directory."
Tumwater High School
. Tumwater School District, 2013. Web.
10 Sept. 2013.


Crenshaw, Tayna.
Software Process
. Portland, OR: Tayna Crenshaw, 28 Aug. 2013.
PDF.

"Eclipse
-

The Eclipse Foundation Open Source Community Website."
Eclipse RSS
.
N.p., 2013. Web. 10 Sept. 2013.

"Get the Android SDK."
Android SDK
. N.p., n.d. Web. 10 Se
pt. 2013.

"Launch Checklist."
Android Developers
. N.p., n.d. Web. 10 Sept. 2013.

"Managed Mayhem."
Managed Mayhem RSS
. Jim Rising Software Dev Projects, 06
May 2009. Web. 10 Sept. 2013.

Solsman, Joan E. "Smartphone Market Share Consolidates at Top, Stud
y Shows."
CNET News
. CBS Interactive, 28 June 2013. Web. 10 Sept. 2013.









THS ATHLETICS ANDROID APPLICATION



45

Glossary


GUI
:

An acronym for Graphical User Interface, a GUI is a way for humans to interact with
the application through a use of windows, icons, and menus.

IDE:

An acronym for Integrated Development Environment, an IDE comprises a base
workspace and extensible plug
-
ins to be utilized as a general software development
environment.

RSS:

An acronym for Rich Site Summary, an RSS feed uses standard web feed formats

to
publish frequently updated information. In this project, that is calendar and event
information.

SDK:

An acronym for Software Development Kit, a SDK is a set of developmental tools
that allow a developer to create an application. The SDK typicall
y includes certain
software packages, software frameworks, development materials, and testing
modules.