Functional Specifications - University of Portland

stuckwarmersΚινητά – Ασύρματες Τεχνολογίες

14 Δεκ 2013 (πριν από 3 χρόνια και 4 μέρες)

235 εμφανίσεις

UNIVERSITY OF PORTLA
ND

SCHOOL OF ENGINEERIN
G

CONTACT: JORDAN FRYE
R

University of Portland

School of Engineering

Phone 503 943 7314

5000 N. Willamette Blvd.

Fax 503 943 7316

Portland, OR 97203
-
5798


Requirements and
Functional
Specifications

Project
Android

Pilot Nation

Team Members
:

Jordan Fryer

(Fall Team Lead)

Andrew Olivier

(Spring Team Lead)

Karen Echon

Jacob Hahn

Industry Representatives:

Jason Favors

Ben Foran

Faculty Advisors:

Steve Vegdahl

Other Contributers:

Tricia Miller

FUNCTIONAL
SPECIFICATIONS

REV. 0.1

PAGE
II

TEAM STELLAR SEA LIO
NS


UNIVERSITY OF PORTLA
ND

SCHOOL OF ENGINEERIN
G

CONTACT: JORDAN FRYE
R

.

.

.

.

.

.

.

.

.


Revision History

Rev.

Date

Author

Reason for Changes

0.1

16
September
2010

Jordan
Fryer

Template and requirements

0.2

16
September

2010

Jacob Hahn

Added development process,
assumptions, and risks

0.3

17
September

2010

Karen Echon

Added user cases and resources

0.4

18
September

2010

Jordan Fryer

Added the introduction and revised
all sections

0.5

19
September
2010

Karen Echon, Jacob
Hahn

Added ethics section, updated
resources, diagram, and comments

0.6

19
September

2010

Andrew Olivier

Added design overview and
hardware components

0.7

21
September

2010

Jordan Fryer

Extensive editing of all sections

0.8

23
September
2010

Andrew Olivier

Improved system architecture
overview and added edit suggestions

0.9

24
September

2010

Jordan Fryer

Finalized document and submitted
to faculty advisor for

review

0.91

28 September 2010

Jordan Fryer

Made revisions based on faculty
feedback

0.92

4 October 2010

All Team Members

Made revisions based on additional
faculty feedback

0.95

5 Octover 2010

All Team Members

Approved by faculty


FUNCTIONAL
SPECIFICATIONS

REV. 0.1

PAGE
III

TEAM STELLAR SEA LIO
NS


UNIVERSITY OF PORTLA
ND

SCHOOL OF ENGINEERIN
G

CONTACT: JORDAN FRYE
R

.

.

.

.

.

.

.

.

.


Table of Contents

Introduction

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

9

Requirements

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

11

Overview

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

11

General Specificatio
ns

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

12

Android Mobile Device Platform

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

12

Online Capabilities

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

13

User Specifications

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

13

GUI for Activities

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

13

Purple Pride News Activity

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

16

Ca
lendar and Events Activity

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

16

Activities Can Be Toggled ON or OFF

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

16

User Message Board Activity

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

16

Promotional Events Activity

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

17

Help Documentation

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

17

Contact and Info

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

17

Developer Specifications

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

18

Template API

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

18

Access to Online Information

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

19

Patch Release Capability

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

19

Server Storage Access

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

20

High Level Design

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

21

Overview of System Architecture

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

21

Component Details

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

22

Central Menu and Activity Organizer


User

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

22

FUNCTIONAL
SPECIFICATIONS

REV. 0.1

PAGE
IV

TEAM STELLAR SEA LIO
NS


UNIVERSITY OF PORTLA
ND

SCHOOL OF ENGINEERIN
G

CONTACT: JORDAN FRYE
R

.

.

.

.

.

.

.

.

.


Activities


User

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

22

Online Capabilities

User

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

23

Template API
-

Developer

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

23

Patch
Release
-

Developer

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

23

Server Data Hosting
-

Developer

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

23

Use Cases

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

23

Use Case 1: End User Presses the Power Button

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

23

Use Case 2: End User Downloads the Android Pilot Nation Application
............

24

Use Case 3: End User Launches the Android Pilot Nation Application for the First
Time
................................
................................
................................
...........................

25

Use Case 4: End User Launches the Android Pilot Nation Application

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

26

Use Case 5: End User Closes the Android Pilot Nation Application

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

27

Use Case 6: End User Scr
olls Up/Down on a Page in the Pilot Android Nation
Application

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

28

Use Case 7: End User Navigates into an Activity

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

28

Use Case 8: End User Toggles an Activity On/Off

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

29

Use Case 9: End User Adjusts
Calendar and Events

Activity Settings

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

30

Use Case 10: Write a Message on the Message Board Activity

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

31

Use Case 11:
End

User Acc
esses the Purple Pride News Activity

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

32

Use Case 12:
End

User Follows a Link on Purple Pride News Activity

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

33

Use Case 13:
End

User Sees Current Scores Using the Purple Pride News
Activity

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

34

Use Case 13:
End

User Presses “Needs Help”

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

35

Use Case 14:
End

User Wants More Information about Android Pilot Nation

...

36

Use Case 15:
End

User Sees the Most Recent Upcoming Event Using the
Calendar and Events

Activity

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

37

FUNCTIONAL
SPECIFICATIONS

REV. 0.1

PAGE
V

TEAM STELLAR SEA LIO
NS


UNIVERSITY OF PORTLA
ND

SCHOOL OF ENGINEERIN
G

CONTACT: JORDAN FRYE
R

.

.

.

.

.

.

.

.

.


Use Case 16:
End

User Brings Up the Google Ca
lendar via the Calendar and
Events Activity
................................
................................
................................
..........

38

Use Case 17: Developer Releases an Update for Android Pilot Nation Application
39

Development Process

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

41

General Approach

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

41

Assumptions

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

42

Ethical Considerations

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

43

Business Assessment

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

43

Mileston
es

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

44

1
-

Functional Specification Version 0.95

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

44

2
-

Functional Specification Approved

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

44

3
-

Design Document First Draft

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

44

4
-

Final Budget Set

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

45

5
-

Design Document Version 0.95

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

45

6
-

Design Document Approved

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

45

7
-

Final Report First Draft

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

45

8
-

Final Report Version 0.95

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

45

9
-

Final Report Approved

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

45

10
-

Project Presentation

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

45

Risks

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

46

Team’s Courses Hamper Progress

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

46

IT does not Provide Access to Information on Website

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

46

A Server is not Made Available

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

47

Learning Curve for Developing on Android is Higher than Expected

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

47

Android Emulator is not Compatible with Our Machines

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

47

FUNCTIONAL
SPECIFICATIONS

REV. 0.1

PAGE
VI

TEAM STELLAR SEA LIO
NS


UNIVERSITY OF PORTLA
ND

SCHOOL OF ENGINEERIN
G

CONTACT: JORDAN FRYE
R

.

.

.

.

.

.

.

.

.


Resources

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

48

Personnel
................................
................................
................................
..........................

48

Preliminary Budget

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

48

Android Phone

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

48

Printing

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

48

Equipment

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

48

Conclusions

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

49

Glossary

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

50

References

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

51


FUNCTIONAL
SPECIFICATIONS

REV. 0.1

PAGE
VII

TEAM STELLAR SEA LIO
NS


UNIVERSITY OF PORTLA
ND

SCHOOL OF ENGINEERIN
G

CONTACT: JORDAN FRYE
R

.

.

.

.

.

.

.

.

.


List of Figures

Figure 1
-

Android Pilot Nation Mock Up

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

9

Figure 2
-

Block Diagram of the Product

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

11

Figure 3


Distribution of Android Platforms

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

12

Figure 4


Home View GUI Mock Up

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

14

Figure 5


Purple Pride News GUI Mock Up
................................
................................
.............

15

Figure 6


Calendar and Events Activity GUI Mock Up

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

15

Figure 7
-

System Architecture

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

21

Figure 8
-

Waterfall Development Model

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

41



FUNCTIONAL
SPECIFICATIONS

REV. 0.1

PAGE
VIII

TEAM STELLAR SEA LIO
NS


UNIVERSITY OF PORTLA
ND

SCHOOL OF ENGINEERIN
G

CONTACT: JORDAN FRYE
R

.

.

.

.

.

.

.

.

.


List of Tables

Table 1
-

General Requirement Specification

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

12

Table 2
-

User Requirement S
pecification

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

13

Table 3
-

Developer Requirement Specification
................................
................................
.........

18

Table 4
-

Milestones

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

44

Table 5
-

Project Risks and Contingencies

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

46

Table 6
-

Preliminary Budget

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

48


FUNCTIONAL
SPECIFICATIONS

REV. 0.1

PAGE
9

TEAM STELLAR SEA LIO
NS


UNIVERSITY OF PORTLA
ND

SCHOOL OF ENGINEERIN
G

CONTACT: JORDAN FRYE
R

.

.

.

.

.

.

.

.

.


Introduction

Android Pilot Nation is an Android application whose
all
-
around purpose is to create a mobile
community for the University of Portland athletics fans. The functionality of Android Pilot
Nation is twofold: to provide news and updates pertaining to relevant

athletic events and to
provide a basic template API to allow future developers to add functionality.

Figure
1

displays a basic
mock
-
up of the end product of Android
Pilot Nation.


Figure
1
-

Android Pilot Nation Mock
Up

The motivation for undertaking the development of Android Pilot Nation originates from the
absence of a mobile device application for University of Portland

athletics program
.

Purple
Pride is the official fan club of the University of Portland Pilot athletics. Purple Pride’s
mission is to increase student involvement in Pilot Athletics, create a fun and exciting
atmosphere, provide opportunities to meet new people through an i
nterest in athletics, and
represent the University of Portland with integrity and sportsmanship.
1

Android Pilot Nation
has

the same goal to connect University of Portland athletic fans in a new and exciting way.

Android is a mobile operating system devel
oped by Google and is based upon the Linux
kernel. According to the National Purchas
e

Diary, a leading market research company,
Android operating system smartphones ranked first among all smartphone operating systems
sold in 2010.
2

This played a large fac
tor in
the
decision to choose the Android operating
system to develop a mobile phone application for promoting Purple Pride. In addition,
Android is a good
development
platform. Android applications are written in Java, a language
in which the

team has c
onsiderable
programming
experience programming. Google 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 in
tegrated development environment.

Lastly,
the marketplace for the Android mobile device is very large and allows new developers to
easily release their
products
.

Android Pilot Nation is being developed with exte
nsibility in mind.
Its

main feature is a core
platform that allows for additional components, named
Activ
ities, to be added. The core
FUNCTIONAL
SPECIFICATIONS

REV. 0.1

PAGE
10

TEAM STELLAR SEA LIO
NS


UNIVERSITY OF PORTLA
ND

SCHOOL OF ENGINEERIN
G

CONTACT: JORDAN FRYE
R

.

.

.

.

.

.

.

.

.


platform functions to sort these
Activ
ities, facilitate their needs, and provide a method for the
application end user t
o remove

or disable

unwanted
Activ
ities. A general template API will
help assist future developers in creating and integrating new
Activ
ities into Android Pilot
Nation. The template forces any developers that come after
Team Stellar Sea Lions to adhere
t
o a standard in order to help promote extensibility even with completely new functionality.

Upon initial release, Android Pilot Nation will have two basic
Activ
ities that will demonstrate
the use of the template API and the functionality of the core platfo
rm. The two
Activ
ities are
the Purple Pride News
Activ
ity and the
Calendar and Events

Activ
ity.
The Purple Pride News
Activ
ity
will retrieve information from the
Purple Pride website so that the user can stay
updated with current news and events. It will feature real time scores of current home games
and provide player and coach statistics. The
Calendar and Events

Activ
ity
will notify

the user
when games are goin
g to occur. The user
will
subscribe to the University of Portland sports
in
which
they are interested
,

and
will be

notified prior to any event from those sports. The
Calendar and Events

Activ
ity
will

integrate

with the basic calendar application on the A
ndr
oid
operating system and
will
record

upcoming eve
nts for the user
,
reschedul
ing

if
a
date or time
is changed.

The purpose of this functional specification document is to clarify and define the Android
Pilot Nation application for the benefit of
the
facu
lty advisor
, industry representatives, client,
team

members, and potential future developers. This document outlines the basic
functionalities and assumptions of Android Pilot Nation and illustrates the design process and
milestones set to complete this p
roject. The remainder of this document overview
s

the
Android Pilot Nation’s requirements, components, use cases, development process, ethical
considerations, business assessment, milestones, risks, and resources.

FUNCTIONAL
SPECIFICATIONS

REV. 0.1

PAGE
11

TEAM STELLAR SEA LIO
NS


UNIVERSITY OF PORTLA
ND

SCHOOL OF ENGINEERIN
G

CONTACT: JORDAN FRYE
R

.

.

.

.

.

.

.

.

.


Requirements

Overview

Team Stellar Sea Lions plans to create an application for the Android mobile device for the
University of Portland’s official fan club of Pilot athletics. Project Android Pilot Nation
brings the excitement of the Portland Pilots sports into the palm
s

of t
he fans.
Unlike most
projects, however, Android Pilot Nation does not just appeal to one end user.
The project
is
being

developed with the intent to create a developer
-
friendly environment for future
programmers to easily add functionality to the initial release.

The

focus

is therefore

on
meeting the requirements of two groups, the developers and the end user.

Android Pil
ot Nation requires
an Android mobile device to use the application. This restricts
the user from using a Windows hand
-
held device
,

an
Iphone

or iOS device, or any other
device that does not run Android as its primary OS
.
The user interacts with the Andro
id Pilot
Nation application through the Android mobile device.
The

application communicates
with
University of Portland servers based on the requests of the user. The block diagram illustrated
in
Figure
2

shows a general overview of the different parts of the system and how they interact
with
one
other.


Figure
2

-

Block Diagram of
the

Product

As shown
in

Figure
2
, the user interacts with the Android mobile device through manipulation
of the Android’s touch screen and keyboard.
The input from the user

interacts w
ith the
Android Pilot Nation’s
Activ
ities and will either cause it to display information onto the touch
screen or request information from the University of Portland servers.


The
following
sections
focus on

the requirements of

the Android Pilot Nation

ap
plication.
The priority of each requirement is given on a numeric scale. A priority level of 1 requires
that the specification be met upon the initial release of the Android Pilot Nation application. A
priority level of 2 requires that the specification

is not required upon initial release, but has
functionality that would improve the Android Pilot Nation application if time permits
implementation. A priority level of 3 is additional functionality that will most likely not be
Android
mobile device


keyboard

FUNCTIONAL
SPECIFICATIONS

REV. 0.1

PAGE
12

TEAM STELLAR SEA LIO
NS


UNIVERSITY OF PORTLA
ND

SCHOOL OF ENGINEERIN
G

CONTACT: JORDAN FRYE
R

.

.

.

.

.

.

.

.

.


implemented upon initial re
lease, but may be primary and secondary goals of future updates to
the Android Pilot Nation application.

Each of these levels

of priority is appended to the
section letter (G for general, U for user, and D for developer) and a unique number in order to
re
ference that specific functionality. For example, G0.1 refers to the general requirement of an
Android Mobile Device and illustrates that it has a priority level of 1.

General

Specifications

The
general

specifications of the Android Pilot Nation are the g
eneral requirements for the
Android Pilot Nation application to work overall
.
Table
1

displays the
general
specifications
of Android Pilot Nation.

Table
1

-

General

Requirement

Specification

Priority
Number

Requirement

Specification

G0
.1

Android Mobile D
evice

Platform
with Touch Screen

G
1.1

Online
Capabilities


Android Mobile Device

Platform

Android Pilot Nation requires an Android mobile
device in order for the user to
benefit from the application

and
requires
that developers either have an emulator or a
physical Android to develop on. The Android mobile device must meet certain
hardware specifications in order for Android Pilot Nation to

work properly.
Figure
3

below
displays the distribution of Android platforms used during two weeks of testing
ending on September
1,
2010, as displayed on the Androi
d developer’s website.
3


Figure
3



Distribution of Android Platforms

As seen in

Figure
3
, a majority of Android mobile device owners use an Android
platform that is of version 2.1 and higher. Android Pilot Nation will require the user
and developer to use an Android with a
p
la
tform level equa
l to or greater than Android
2.1
. Since Android Pilot Nation will not be released until April, 2011, backward
Platform

API Level

Distribution

Android 1.5

3

12.0%

Android 1.6

4

17.5%

Android 2.1

7

41.7%

Android 2.2

8

28.7%

FUNCTIONAL
SPECIFICATIONS

REV. 0.1

PAGE
13

TEAM STELLAR SEA LIO
NS


UNIVERSITY OF PORTLA
ND

SCHOOL OF ENGINEERIN
G

CONTACT: JORDAN FRYE
R

.

.

.

.

.

.

.

.

.


compatibility will not be a large issue as more people upgrade to higher level
platforms and
as
new platforms are released.

All
Android platforms are forward
compatible.


Online Capabilities

Android Pilot Nation requires that the Android mobile device has online capabilities in
order for the user to access current information about Purple Pride.
If the Android
mobile device does
not have online capabilities, end users cannot download the
application from the online Android marketplace.
Developers

also

require that the
Android mobile device has online capabilities so that their
Activ
ities for

the
application can access any informa
tion that may be needed from online resources.

User

Specifications

The user specifications are the requirements specified by the end users of Android Pilot
Nation.
Table
2

displays the user specifications that are required.

Table
2

-

User Requirement Specification

Priority Number

Requirement

Specification

U0.1

GUI for Activities

U
1
.1

Purple Pride News
Activity

U2
.1

Calendar and Events

Activity

U3
.1

Activities
C
an
B
e Toggled ON or OFF

U4
.
3

User Message Board

Activity

U5
.2

Promotional Events Activity

U6.1

Help Documentation

U7.1

Contact and Info


G
UI for Activities

Android Pilot Nation is expected to have a graphical user interface that allows the user
to interact with the
Activ
ities o
f Android Pilot Nation and display

visually the purpose
of an
Activ
ity and how their interactions affect it. Graphical user interface
s are
difficult to design properly due to the specific desires of each individual user and the
difficulty in defining intuitive and aesthetically pleasing

designs
. Nonetheless,
Android Pilot Nation requires that users have a graphical sense of how Android

Pilot
Nation is organized and how
to

interact with it.
Figure
4
,
Figure
5
, and
Figure
6

FUNCTIONAL
SPECIFICATIONS

REV. 0.1

PAGE
14

TEAM STELLAR SEA LIO
NS


UNIVERSITY OF PORTLA
ND

SCHOOL OF ENGINEERIN
G

CONTACT: JORDAN FRYE
R

.

.

.

.

.

.

.

.

.


display

basic
mock
-
up
s

of
the
elements composing

Android Pilot Na
tion’s GUI. The
main point of the
s
e

figure
s

is to not show what the GUI will look like, but the different
functionality that is needed and an example of how that could be displayed.


Figure
4



Home View

GUI

Mock Up

Figure
4

displays a
n

example of what the main page may look like when the user starts
up the Android Pilot Nation application. As displayed in the figure, it may display
some type of image that is closely associated with a
home or front page for a majority
of mobile device users. This may or may not be accompanied by some sort of
greeting welcoming back the user to Android Pilot Nation. T
he part of the GUI that
the user interacts with to change Activities is the
Central Me
nu and Activity
Organizer. In this example GUI, it has taken the form as a tab
-
like heading at the top
of Android Pilot Nation. The Central Menu and Activity Organizer’s main goal is to

display the A
ctivities that the user has toggled on (more details in

requirement U3
.1
below) and illustrate which A
ctivity has the current active view. In this case
,

the
Android Pilot Nation’s home is the current active view. The home should have some
type of link for help on using Android Pilot Nation and a link giving
a general
explanation of what the Android Pilot Nation
application
is.

FUNCTIONAL
SPECIFICATIONS

REV. 0.1

PAGE
15

TEAM STELLAR SEA LIO
NS


UNIVERSITY OF PORTLA
ND

SCHOOL OF ENGINEERIN
G

CONTACT: JORDAN FRYE
R

.

.

.

.

.

.

.

.

.



Figure
5



Purple Pride News GUI Mock Up

Figure
5

displays a
n

example of what the Purple Pride News Activity (more details in
requirement U1.1 below) may look like. This GUI is required to give a readable
layout of the information associated with Purple Pride. The page may be broken up
into different sections that

the user can click on to see more relevant information or
may just display the latest news from the Purple Pride organization. Links can be
clicked if the user desires more information.

The

current score is displayed at the top
of the GUI

if a home game

is ongoing
.


Figure
6



Calendar and Events

Activity GUI

Mock Up

Figure
6

displays a
n

example of what the
Calendar and Events

Activity (more details
in requirement U2.1 below) may look like. The main function of the
Calendar and
Events

Activity is to
integrate wit
h the user’s calendar
and notify them
about
FUNCTIONAL
SPECIFICATIONS

REV. 0.1

PAGE
16

TEAM STELLAR SEA LIO
NS


UNIVERSITY OF PORTLA
ND

SCHOOL OF ENGINEERIN
G

CONTACT: JORDAN FRYE
R

.

.

.

.

.

.

.

.

.


upcoming events. The GUI, therefore, is not as important to this
Activ
ity as other
Activ
ities such as the Purple Pride News Activity.
Basic information of

the next
upcoming event
will be on display.

This inclu
des the time and date and location of the
event.


Al
l A
ctivities will be required to have a GUI from the developers.
Requirement D0.1
under the following section entitled Developer Specifications gives more details.

Purple Pride
News Activity

Upon initial

release,
Android Pilot Nation
will
contain functionality that allows the
user to access current news from Purple Pride.
It is expected to display current events
found on the Purple Pride website, along with real time scores of current on
-
going
games.
It will contain important statistics about the players and information about the
coaches.

Calendar and Events

Activity

The second default
Activ
ity expected to ship with Android Pilot Nation upon release
is an
Activ
ity that notifies the user of upcoming g
ames. This
Activ
ity will
integrate

with the standard calendar on the Android phone

by requesting read and write
privileges. When successfully interfaced, it can

notify the user
of an upcoming game
.
The user will be able to customize when

and how frequen
t
ly

they are notified by this
Activ
ity

in a settings selection screen found by pressing the default settings button
found on every Android mobile device
.
If event times or dates change, the
Calendar
and Events

Activity will update the calendar.


Activiti
es Can Be Toggled ON or OFF

Users can personalize the functionality of Android Pilot Nation through a user
interface by toggling on or off specific
Activ
ities. For example, if a user desired to not
be

notified b
y the
Calendar and Events

Activity, they cou
ld toggle it off so they only
receive updates from the Purple Pride News Activity. When more
Activ
ities are
added to Android Pilot Nation from future developers, this functionality will be
beneficial to ens
ure the user only receives the A
ctivity functiona
lity they desire.

The
ability to toggle on and off
Activ
ities can be found on the home page by pressing the
standard Android mobile device settings button.

User Message Board

Activity

The
User Message B
oard

Activity

would allow users to send messages to
o
ne an
other
through a message board style interface.
This A
ctivity has a very low priority level
and will not be implemented by the initial developers due to the issues around
regulating a message board.

Despite this fact, the template API will support th
e
functionality of the User Message Board Activity.


FUNCTIONAL
SPECIFICATIONS

REV. 0.1

PAGE
17

TEAM STELLAR SEA LIO
NS


UNIVERSITY OF PORTLA
ND

SCHOOL OF ENGINEERIN
G

CONTACT: JORDAN FRYE
R

.

.

.

.

.

.

.

.

.


Promotional Events Activity

Though not at a
level
-
1 priority, the Promotional Events Activity is an important
requirement suggested by the client of Team Stellar Sea Lions. The Promotional
Events Activi
ty would expand upon the functionality of the
Calendar and Events

Activity, allowing an authorized person to send messages
for
promotional events
associated with Pilots sporting events. For example, users may be sent a message
when notified about an upcom
ing men’s soccer game that, being members of Android
Pilot Nation, they are eligible for a free hot dog and medium soda
at the concession
stand. This A
ctivity requires that an administrative figure send out promotional events
through the University of Por
tland servers or
through the w
ebsite and that the Android
Pilot Nation application receives this message and displays it to the user.

Help Documentation

In case the user does not find the use of Android Pilot Nation intuitive, there must be
some way for
them to receive help. This will be in the form of a help icon on the
Home page of Android Pilot Nation. This help documentation will most likely be
brief
,
with no ability to search through the document.

Contact and Info

Android Pilot Nation

has

contact
information for
Team Stellar Sea Lions

and any
future developers who have created Activities after initial release
.


This will be in the
form of an info icon on the Home page of Android Pilot Nation.

Information about
what Android Pilot Nation is will al
so be with this contact information.








FUNCTIONAL
SPECIFICATIONS

REV. 0.1

PAGE
18

TEAM STELLAR SEA LIO
NS


UNIVERSITY OF PORTLA
ND

SCHOOL OF ENGINEERIN
G

CONTACT: JORDAN FRYE
R

.

.

.

.

.

.

.

.

.


Developer Specifications

The developer specifications are the requirements of future developers who plan to work on
Android Pilot Nation and bring additional functionality through new
Activities
.

Table
3

lists
the developer requirements.

Table
3

-

Developer Requirement Specification

Priority Number

Requirement

Specification

D0
.1

Templa
te
API

D1
.1

Access to Online Information

D
2
.2

Patch Release Capability

D3
.
3

Server Storage Access


Template API

Android Pilot Nation’s main goal is to release a template that

will

allow future
developers to easily create new
Activities
to add to the
application

s functionality. A
template API
will provide

a set of tools that

will

allow new
A
ctivities to
connect
seamlessly with the original
Activities
found in the initial release and with future
Activities
.

There is no assumption on the type of
Activities
that could be
added
. The
refore

the
template must accommodat
e

any type of
Activity
. Activities could range from games
featuring Wally, uploaded pictures, a list of insults for the current opposing team, or a
Purple Pride themed alarm clock. Du
e to the unknown nature of future developer’s
intents, the template for Android Pilot Nation must be flexible

enough to allow
variety,

yet rigid enough to disallow abuse or bugs to interfere with other
Activity’s
purposes.

The tools provided by the API mus
t be documented to further allow easy integration
of future
Activities
into Android Pilot Nation. Developers of new
Activities
will
implement required methods specified in detail by API documentation so that any
Activity
can be easily integrated.

Though t
he specifics are

not yet known, the template API would need the following
fu
nctionality for future
developer
s

to implement:

On Creation Method

A method is needed for the developer’s
Activity
that sets up the creation of
any variables and creates the UI for that
Activity
when the user transitions to
FUNCTIONAL
SPECIFICATIONS

REV. 0.1

PAGE
19

TEAM STELLAR SEA LIO
NS


UNIVERSITY OF PORTLA
ND

SCHOOL OF ENGINEERIN
G

CONTACT: JORDAN FRYE
R

.

.

.

.

.

.

.

.

.


that Activity
as the active view. This is for loading any resources needed and
constructing any objects needed
to run

the
Activity
.

On Destruction

Method

A method is needed for the developer’s
Activity
that deconstructs

it

and
releases any resources for that
Activity
when the user transitions to a differen
t
Activity
as the active view.

Settings Selected Method

A method is needed for when the user wi
shes to change any settings the
developer may have for their
Activity
. When the user pushes the s
tandard
settings button on the

Android mobile device, this method
will
be called. The
developer does not have to implement this method, since they may have n
o
settings for their
Activity
.

User Listening Method
s

The core functionality of the template API will be running a listener for user
input and call the appropriate methods for the current
Activity
in active view.
For example, if a user
is
running the Purp
le Pride News Activity and
clicks
on
the screen in order to follow a link, the listening method for touch screen
presses will be called and the correct overridden method in the Purple Pride
News Activity code would handle
the
input and make a decision on w
hat
action to take.

Update Method

A general method for any updating
or
refreshing of the
A
ctivity is needed. For
example, a
n A
ctivity
may need to refresh the current score
. The update
method works on refreshing any information or running any timers neede
d for
the
A
ctivity in
active view. This
differs

from user input such that user input
methods wait to run code until user input is
received
. This update method runs
at intervals specified by the developer.

Access to Online Information

Developers require t
hat their
Activ
ities have access to online information pertaining to
Purple Pride. If any data is stored
for the developer

on a University of Portland server,
there must be a method to call to retrieve the needed data for their
Activity
. It is not a
level 1 priority, however, to allow future developers to change any data on the server.

Patch Release Capability

Developers require some capability to release their
Activity
and any future patches of
their
Activity
to the user. The
A
ndroid marketplace all
ows updates of programs to be
FUNCTIONAL
SPECIFICATIONS

REV. 0.1

PAGE
20

TEAM STELLAR SEA LIO
NS


UNIVERSITY OF PORTLA
ND

SCHOOL OF ENGINEERIN
G

CONTACT: JORDAN FRYE
R

.

.

.

.

.

.

.

.

.


downloaded. Future developers need a way to veri
fy that they have a new
Activity
ready
to be
download
ed

or updated so that users will be notified via the marketplace.

Server Storage Access

Developers may require from Android
Pilot Nation access to a server at University of
Portland to store information. This server would need to communicate with the
Activ
ity requesting to store information and would be required to go through
University of Portland protocols for handling infor
mation.


FUNCTIONAL
SPECIFICATIONS

REV. 0.1

PAGE
21

TEAM STELLAR SEA LIO
NS


UNIVERSITY OF PORTLA
ND

SCHOOL OF ENGINEERIN
G

CONTACT: JORDAN FRYE
R

.

.

.

.

.

.

.

.

.


High Level Design

Android Pilot Nation is built around two users, the end user and the developer. In order to
service both of these user bases, the high level design will be
divided

into components that
deal specifically
each of these groups
.

For

the end user, Android Pilot Nation is a tool on their Android
mobile
device that acts as a
gateway to Purple Pride related information. Therefore, the layout from the user

s perspective
is simple; the user uses their Android device to run the Android Pilo
t Nation application.
Then
,

by

interacting with the application
and the
Activ
ities
, they can consume data related to
Purple Pride that is hosted by the University Of Portland’s servers.

This data is displayed in a
graphical manner on their Android mobile
device (details found in requirement U0.1).

For the developer, an API will be provided that will allow them to integrate their Android
Pilot Nation Activity with the main Android Pilot Nation interface
, the Central Menu and
Activity
Organizer.

Overview of
System Architecture

Figure
7

depicts how Android Pilot Nation will interface with the end user.




Outbound
data

Inbound
data

Display/
Speakers


End User

Android Device

Android
Pilot
Nation

University of
Portland Server

Central Menu
and
Activity Or
ganizer

Purple
Pride News
Activity

Calendar and
Events
Activity

Other

Activities

User
I
nput

Android API
Abstraction Layer

Help
Activity

Figure
7

-

System Architecture

FUNCTIONAL
SPECIFICATIONS

REV. 0.1

PAGE
22

TEAM STELLAR SEA LIO
NS


UNIVERSITY OF PORTLA
ND

SCHOOL OF ENGINEERIN
G

CONTACT: JORDAN FRYE
R

.

.

.

.

.

.

.

.

.


As
shown

in

Figure
7
, the end user communicates with Android Pilot Nation through their
Android Device.
The Android Pilot Nation application will then receive this input through the
Android API abstraction layer.

Next, that input will be used by the application to fulfill the
user’s request.

If the user is running the application for the first time,
the
input will
be sent to

the Central
Menu and Activity Organizer. The input will then presumably be used to run an

A
ctivity with
Android Pilot Nation. Once a particular Activity is running, input will be directed to the
A
ctivity through the main Android Pilot Nation application, until the Activity is stopped or
focus is changed to another Activity or back to the Centr
al Menu and Activity Organizer.

Should an Activity be looking for input, it will rely on the main Android Pilot Nation
application to interface with the Android API abstraction layer. For instance, when the Purple
Pride News Activity wants information fro
m the University of Portland server, it will contact
the Android Pilot Nation application which will then handle communications with the
Android API abstraction layer to send the outgoing message to the University’s servers. Then
the Android Device will re
ceive the inbound message from the University’s servers and will
hand it off to the Android Pilot Nation application through the Android API abstraction layer.
Android Pilot Nation will then give the information to the Purple Pride News Activity.

The Acti
vity may create output for the end user and will display that information in a way
similar to contacting the University of Portland server, except this time instead of forwarding
the data to a server, the Android Pilot Nation application will use the Andro
id API abstraction
layer to handle the display.

Component Details

Central Menu and Activity Organizer


User

The Central Menu and Activity Organiz
er is the main way that the
user will be able to
select an A
ctivity to run from a list of available
Activ
ities
. The Central Menu and
Activity Organizer will have a default screen that will appear every time the user starts
Android Pilot Nation. This screen will include a user

interface for navigating the
user’s
Activ
ities. The Central Menu and Activity Organizer w
ill allow the user to
more easily access their
Activ
ities. This screen acts the initial intermediary between
the main Android Nation application and the Activities the user may select from.

Activities


User

Android Pilot Nation will allow for a number of

Activ
ities to be used by the user.
These
Activ
ities will include at a minimum those listed in the user Requirements
Section.
U
sers will select
Activ
ities to be displayed on their screen through the Central
Menu and Activity Organizer. The user will then b
e able to interact with that Activity
to the extent that it supports interaction. The user will initially select an Activity to
come into focus through the Central Menu and Activity Organizer. Once in focus the
main Android Pilot Nation application will di
rectly forward input to the Activity. The
FUNCTIONAL
SPECIFICATIONS

REV. 0.1

PAGE
23

TEAM STELLAR SEA LIO
NS


UNIVERSITY OF PORTLA
ND

SCHOOL OF ENGINEERIN
G

CONTACT: JORDAN FRYE
R

.

.

.

.

.

.

.

.

.


Activity will always forward its own output to the main Android Pilot Nation
application.

Online Capabilities

User

S
ome
of the
Activ
ities will retrieve data from the Internet an
d display that data for the
user in
a format more suitable for consumption than the web browser included on the
Android device. The main Android Pilot Nation Application will be
responsible for

handling outbound information from the Activities and the Android API abstraction
layer, and will
also be in
responsible for

handling inbound information from outside
sources given to it through the Android API abstraction layer and then forwarding that
information to the Activity it is for.

Template API
-

Developer

Android Pilot Nation will supply an
API for the functionality that it adds to the base
Android 2.1 platform. This documentation will be in a format similar to that found on
the Android developer website and will include both documentation and examples to
aid future developers with adding add
itional functionality to Android Pilot Nation.

Patch Release
-

Developer

Android Pilot Nation will allow for future developers to release patches that enhance
existing parts of the program or add additional features to it.

Server Data Hosting
-

Developer

Data that is hosted by the University of Portland will be accessed by Android Pilot
Nation. This data will be hosted for the duration of Android Pilot Nation’s life cycle.
Some data will be hosted specifically for Android Pilot Nation, but some of the data

may be already hosted for current web pages.

Use Cases

The use cases specified below are possible interactions an end user can have with Android
Pilot Nation.

Use Case 1:
End
User Presses the Power Button

Primary Actor:

End
User


Goal in context:

Turn the Android
mobile device

on


Preconditions:

The Android
mobile device

is plugged in or has battery
power. The phone is currently turned off.

Android Pilot Nation has already
been configured and the user has toggled on
Activ
ities that run in the
ba
ckground.

FUNCTIONAL
SPECIFICATIONS

REV. 0.1

PAGE
24

TEAM STELLAR SEA LIO
NS


UNIVERSITY OF PORTLA
ND

SCHOOL OF ENGINEERIN
G

CONTACT: JORDAN FRYE
R

.

.

.

.

.

.

.

.

.



Trigger:

The
end
user wishes to use the Android
mobile device
.


Scenario:

1.

The
end
user presses the Power button
.

2.

The individual components receive power from the power supply.

3.

A loading screen appears
indicating that

the phone is loading the sy
stem.

4.

The Android home screen appears and is ready to be used.

5.

Android Pilot Nation launches background processes for the
on
-
toggled
Activ
ities.


Exceptions:

1.

The
end
user is unable to locate the Power button.

2.

The Android
mobile device in use may have
faulty
hardware
.

3.

The operating system on the Android
mobile device

may contain a bug
that will not allow the phone to turn on.


Priority:

High priority.


When available:

Current release.


Frequency of use:

Every time
the end

user needs to use the Android d
evice.


Channel to primary actor:

Direct physical manipulation of the device.


Open issues:
None.


Use Case 2
:
End
User Downloads the Android Pilot Nation Application

Primary Actor:

End
User


Goal in context:

Download the Android Pilot N
ation a
pplication


Preconditions:

The Android
mobile device

is turned on and ready for use.
The Android
mobile device

has a data plan attached to its service or is
connected to the wireless internet.


Trigger:

The

end

user wishes to dow
nload the Android Pilot Nation
a
pplica
tion.


Scenario:

1.

The user navigates into the Android Store
a
pplication.

2.

The user locates the search bar and
selects

it using his/her finger.

3.

The cursor on the search bar will blink and the user will then type in
“Android Pilot Nation” into the search bar.

4.

The Android Store
a
pplication will load the contents of the search.

FUNCTIONAL
SPECIFICATIONS

REV. 0.1

PAGE
25

TEAM STELLAR SEA LIO
NS


UNIVERSITY OF PORTLA
ND

SCHOOL OF ENGINEERIN
G

CONTACT: JORDAN FRYE
R

.

.

.

.

.

.

.

.

.


5.

The
end
user will click on the Android Pilot Nation icon in the search
results.

6.

The phone will ask for verification of the download and the
end
user will
click “Yes.”

7.

The Android Pilot Nat
ion application will download and the
end
user
will be brought back into the Android Store
a
pplication once done.


Exceptions:

1.

The phone turns off

during

the download due to a weak battery.

2.

The phone lose
s

internet or data service that disrupt
s

the downloa
d of
the application.

3.

The Android
mobile device in use may have
faulty
hardware
.


Priority:

High priority.


When available:

Current release.


Frequency of use:

Once

per device
.


Channel to primary actor:

Application
.


Open issues:
None.


Use Case
3:
End
User Launches the Android Pilot Nation Application for the First
Time

Primary Actor:

End
User


Goal in context:

Open the Android Pilot Nation a
pplication

after first
download


Preconditions:

The Android
device

is turned on and ready for use. The
Android
device

has a data plan attached to its service or is connected to the
wireless internet. The Android Pilot Nation
a
pplication has been downloaded.
The
end
user is in the home screen of the Android
mobile device
.

The
end
user has not
previously
launched An
droid Pilot Nation.


Trigger:

The
end
user wishes to use the Android Pilot Nation
a
pplication

for
the first time
.


Scenario:

1.

The

end

user locates the Android Pilot Nation icon in the list of
applications that has been downloaded.

2.

The
end
user clicks on the

Android Pilot Nation application.

3.

The Android Pilot Nation home screen will appear.

FUNCTIONAL
SPECIFICATIONS

REV. 0.1

PAGE
26

TEAM STELLAR SEA LIO
NS


UNIVERSITY OF PORTLA
ND

SCHOOL OF ENGINEERIN
G

CONTACT: JORDAN FRYE
R

.

.

.

.

.

.

.

.

.


4.

Android Pilot Nation will give a brief introduction to the new
end
user
and allow them to choose what
Activ
ities to toggle on.


Exceptions:

1.

The
device

turns off in the mid
dle
of configuration
due to a weak
battery.

2.

The Android mobile device in use may have faulty hardware.

3.

The user has an incompatible Android operating system platform level.



Priority:

High priority.


When available:

Current release.


Frequency of use:

First
time a
n end

user
uses

the application.


Channel to primary actor:

Application
.


Open issues:
None.


Use Case
4
:
End
User
Launches
the Android Pilot Nation Application

Primary Actor:

End
User


Goal in context:

Open the Android Pilot Nation
a
pplication


Preconditions:

The Android
mobile device

is turned on and ready for use.
The Android
device

has a data plan attached to its service or is connected to
the wireless internet. The Android Pilot Nation
a
pplication has been
downloaded

and configured
. The user is in the home screen of the Android
device
.


Trigger:

The user wishes t
o use the Android Pilot Nation a
pplication.


Scenario:

1.

The user locates the Android Pilot Nation icon in the list of applications

that has been downloaded.

2.

The user clicks

on the Android Pilot Nation application.

3.

The Android Pilot Nation home screen will appear.


Exceptions:

1.

The Android
mobile device in use may have
faulty
hardware
.


Priority:

High priority.


When available:

Current release.


FUNCTIONAL
SPECIFICATIONS

REV. 0.1

PAGE
27

TEAM STELLAR SEA LIO
NS


UNIVERSITY OF PORTLA
ND

SCHOOL OF ENGINEERIN
G

CONTACT: JORDAN FRYE
R

.

.

.

.

.

.

.

.

.


Frequency of use:

Every time a user wants to use the application.


Channel to primary actor:

Application
.


Open issues:
None.


Use Case
5
:
End
User Closes the Android Pilot Nation Application

Primary Actor:

End
User


Goal in context:

Close the Android Pilot Nation
a
pplicat
ion


Preconditions:

The Android
mobile device

is turned on and ready for use.
The Android
mobile device

has a data plan attached to its service or is
connected to the wireless internet. The Android Pilot Nation
a
pplication has
been downloaded. The user is
currently using one of the
Activ
ities of the
Android Pilot Nation a
pplication.


Trigger:

The
end
user wishes to dismiss the Android Pilot Nation application.


Scenario:

1.

The
end
user presses
Home

button on the

Central Menu and Activity
Organizer
.

2.

The
end
user presses the standard Android settings button.

3.

The
end
user selects

the

Quit

button
.

4.

The

Android

mobile device

brings the
end
user to the Home screen of
the Android
mobile device
.


Exceptions:

1.

The
end
user may not be able to locate the
Home

button

on the
Central
Menu and Activity Organizer
.

2.

The user may not be able to locate the Android settings button or the
quit option.



Priority:

High Priority
.


When Available:
Current Release.


Frequency of use:

Every time the

end

user wants to close the appl
ication.


Channel to primary actor:

Application
.


Open issues:
None.


FUNCTIONAL
SPECIFICATIONS

REV. 0.1

PAGE
28

TEAM STELLAR SEA LIO
NS


UNIVERSITY OF PORTLA
ND

SCHOOL OF ENGINEERIN
G

CONTACT: JORDAN FRYE
R

.

.

.

.

.

.

.

.

.


Use Case
6
:
End
User
Scrolls Up/Down on a Page in the Pilot Android Nation
Application

Primary Actor:

End
User


Goal in context:

To scroll up or down the application.


Preconditions:

The Android
mobile device

is turned on and ready for use.
The Android
mobile device

has a data plan attached to its service or is
connected to the wireless internet. The Android Pilot Nation
a
pplication has
been downloaded. The user is
currently using an
Activ
ity of the Android Pilot
Nation a
pplication.


Trigger:

The
end
user wishes to scroll up or down the application.


Scenario:

1.

The
end
user places their finger on any part of the
Activ
ity

page.

2.

If the
end
user wishes to scroll up the
Activ
ity

page, the
end
user will
drag their finger down. If the
end
user wishes to scroll down the
Activ
ity

page, the
end
user will drag their finger up.

3.

The
end
user may repeat #2 if
the end user
still wishes to scroll
.


Exceptions:

1.

The Android
mobile device in use may have
faulty
hardware
.


Priority:

Optional


When Available:
Current release.


Frequency of use:

Occasional.


Channel to primary actor:

Application
.


Open issues:
None.


Use Case
7
:
End
User Navigates into
an Activity

Primary Actor:

End
User


Goal in context:

Navigate into
an
Activ
ity
.


Preconditions:

The Android
mobile device

is turned on and ready for use.
The Android
mobile device

has a data plan attached to its service or is
connected to the wireless internet. The Android Pilot Nation
a
pplication has
been downloaded. The
end
user
is using an
Activ
ity of the Android Pilot
Nation a
pplication.

FUNCTIONAL
SPECIFICATIONS

REV. 0.1

PAGE
29

TEAM STELLAR SEA LIO
NS


UNIVERSITY OF PORTLA
ND

SCHOOL OF ENGINEERIN
G

CONTACT: JORDAN FRYE
R

.

.

.

.

.

.

.

.

.



Trigger:

The
end
user wishes to navigat
e into another
Activ
ity
.


Scenario:

1.

The
end
user will interact with the
Central Menu and Activity Organizer

of Android Pilot Nation

application
.

2.

The

end

user will use
their

finger to press on a desired
Activ
ity

icon
found on the
Central Menu and Activity O
rganizer
.

3.

If
the
desired
Activ
ity

has been toggled on, Android Pilot Nation will
bring the

end

user to the
Activ
ity page. Otherwise, the
end
user must
locate the Home icon on the Central Menu and Activity Organizer.

a.

The
end
user will then press on the Android standard Settings
button, select Settings, and toggle the
Activ
ity on.

More details can
be found in Use Case 8.

b.

The
end
user will repeat 2.

4.

Android Pilot Nation will then load that
Activ
ity

to

screen.


Exceptions:

1.

The
end
user is unable to locate the
Central Menu and
Activ
ity Organizer
.

2.

The Android
mobile device in use may have
faulty
hardware
.


Priority:

High Priority.


When Available:
Current Release.


Frequency of use:

Occasional.


Channel to primary actor:

Application
.


Open issues:
None.


Use Case
8
:
End

User
Toggles an
Activ
ity On/Off

Primary Actor:

End
User


Goal in context:

To toggle an
Activ
ity on/off


Preconditions:

The Android
mobile device

is turned on and ready for use.
The Android
mobile device

has a data plan attached to its service or is
connected to the wireless internet. The Android Pilot Nation
a
pplication has
been downloaded. The
end
user
is on
an
Activ
ity page

of Android Pilot
Nation.


Trigger:

The
end
user wishes
set an
Activ
ity on/off.


FUNCTIONAL
SPECIFICATIONS

REV. 0.1

PAGE
30

TEAM STELLAR SEA LIO
NS


UNIVERSITY OF PORTLA
ND

SCHOOL OF ENGINEERIN
G

CONTACT: JORDAN FRYE
R

.

.

.

.

.

.

.

.

.


Scenario:

1.

The
end
user will interact with the
Central Menu and
Activ
ity Organizer

of Android Pilot Nation application

and

click on the Home icon.

2.

The
end
user

click
s on the standard Android s
ettings button
.

3.

The
end
user selects the Settings icon that appears, ignoring the
Quit

button.

4.

A list will display which
Activ
ities are toggled on or off
.

5.

The

end

user will go through the list, setting each
Activ
ity

to

on or off,
depending on what the
end
user desires.

6.

The
end
user will then click on the
Done

button at the bottom of

the list
.



Exceptions:

1.

The
end
user is unable to locate the
Central Menu and
Activ
ity Organizer
,
or
the
Settings

button
.

2.

The Android mobile device in use may have faulty hardware.


Priority:

High

Priority.


When Available:
Current Release.


Frequency of use:

Occasional.


Channel to primary actor:

Application


Open issues:
None.


Use Case
9
:
End
User
Adjusts
Calendar and Events

Activ
ity

Setting
s

Primary Actor:

End
User


Goal in context:

To adjust
the Calendar and Events

Activ
ity

setting.


Preconditions:

The Android
mobile device

is turned on and ready for use.
The Android
mobile device

has a data plan attached to its service or is
connected to the wireless internet. The Android Pilot Nation
a
pplica
tion has
been downloaded. The user
is using an
Activ
ity of the Android Pilot Nation
a
pplication.


Trigger:

The
end
user wishes to
change the settings of the Calendar and
Events

Activ
ity
.


Scenario:

1.

The
end
user will interact with the
Central Menu and
Activ
ity Organizer

of Android Pilot Nation application

and click on the Calendar and
Events icon
.

FUNCTIONAL
SPECIFICATIONS

REV. 0.1

PAGE
31

TEAM STELLAR SEA LIO
NS


UNIVERSITY OF PORTLA
ND

SCHOOL OF ENGINEERIN
G

CONTACT: JORDAN FRYE
R

.

.

.

.

.

.

.

.

.


2.

If the
Calendar and Events

Activ
ity has been toggled on, Android Pilot
Nation will bring the user to the
Calendar and Events

Activ
ity page.
Otherwise, the
end
user must locate the
Home

button

on the Central
Menu and
Activ
ity Organizer.

a.

The
end
user will then press on the Android standard Settings button,
select Settings, and toggle Calendar and Events
Activ
ity on.

b.

The user will repeat 1.

3.

The
end
user will select

the standard Android settings button
.

4.

The
end
user will select the
Settings

button
.

5.

The
end
user can interact with a list of settings that appears, choosing
what sports to be notified of and how close to an event to be notified.

6.

T
he
end
user will then click on the
Done

button at the bottom of the
Settings page

when
they

have finished changing the desired settings
.



Exceptions:

1.

The
end
user is unable to locate the
Central Menu and
Activ
ity Organizer
,
the
Settings

button, or the
Done

button
.

2.

T
he Android mobile device in use may have faulty hardware.


Priority:

High

Priority.


When Available:
Current Release.


Frequency of use:

Occasional.


Channel to primary actor:

Application


Open issues:
None.


Use Case
10
:
Write a Message on the Message Board
Activ
ity

Primary Actor:

End
User


Goal in context:

To write a message on the Message Board
Activ
ity.


Preconditions:

The Android
mobile device

is turned on and ready for use.
The Android
mobile device

has a data plan attached to its service or is
connected to the wireless internet. The Android Pilot Nation
a
pplication has
been downloaded. The
end
user
is on an
Activ
ity page of Android Pilot
Nation.


Trigger:

The
end
user

wants

to write a message on the

Message Board
Activ
ity.


FUNCTIONAL
SPECIFICATIONS

REV. 0.1

PAGE
32

TEAM STELLAR SEA LIO
NS


UNIVERSITY OF PORTLA
ND

SCHOOL OF ENGINEERIN
G

CONTACT: JORDAN FRYE
R

.

.

.

.

.

.

.

.

.


Scenario:

1.

The
end
user will interact with the
Central Menu and
Activ
ity Organizer

of Android Pilot Nation

application
.

2.

The
end
user will use his/her finger to press on Message Board
Activ
ity
icon found on the
Central Menu and
Activ
ity Organizer
.

3.

If the Message Board
Activ
ity has been toggled on, Android Pilot
Nation will bring the
end
user to the Message Board
Activ
ity page.
Otherwise, the
end
user must locate the
Home

button

on the Central
Menu and
Activ
ity Organizer.

c.

The
end
user will then press on the Android standard Settings button,
select Settings, and toggle Message Board
Activ
ity on.

d.

The
end
user will repeat
2
.

4.

The Message Board
Activ
ity page will appear with messages previously
posted by
other end
users and a text box which allows the
end
user to
post a message on the board.

5.

The
end
user will click on the text box and the cursor will blink.

6.

The
end
user will type the desired message into the text box and will
press on the
Post

button when
they

have
finished.

7.

Android Pilot Nation will update the server with the message.

8.

The message will appear on the Message Board
Activ
ity.



Exceptions:

1.

The
end

user is unable to locate the
Central Menu and
Activ
ity Organizer,
the Message Board
Activ
ity icon, the text box, or the
Post

button
.

2.

The
Android device loses

internet or data service that disrupt
s

the
update
to the server.

3.

The Android mobile device in use may have faulty hardware.


Priority:

Very Low

Priority.


When Available:
Future

Release.


Frequency of use:

Occasional.


Channel to primary actor:

Application


Open issues:
None.


Use Case
11
:
End

User
Accesses the
Purple Pride

News

Activ
ity

Primary Actor:

End

User


Goal in context:

To
access the
Purple Pride

News
Activ
ity.


Preconditions:

The Android
mobile device

is turned on and ready for use.
The Android
mobile device

has a data plan attached to its service or is
FUNCTIONAL
SPECIFICATIONS

REV. 0.1

PAGE
33

TEAM STELLAR SEA LIO
NS


UNIVERSITY OF PORTLA
ND

SCHOOL OF ENGINEERIN
G

CONTACT: JORDAN FRYE
R

.

.

.

.

.

.

.

.

.


connected to the wireless internet. The Android Pilot Nation
a
pplication has
been downloaded. The user
is on an
Activ
ity page

of Android Pilot Nation.


Trigger:

The

end user

wishes to access the
Purple Pride

News

Activ
ity
.


Scenario:

1.

The
end
user will interact with the
Central Menu and
Activ
ity Organizer

of Android Pilot Nation

application

and click the
Purple Pride

News
Activ
ity icon
.

2.

If the
Purple Pride

News
Activ
ity has been toggled on, Android Pilot
Nation will bring the user to the
Purple Pride

News
Activ
ity page.
Otherwise, the
end
user must locate the Home icon on the Central Menu
and
Activ
ity Organizer.

a.

The
end
user will then press on the Android standard Settings button,
select Settings, and toggle
Purple Pride

News
Activ
ity on.

b.

The
end
user will repeat 1.

2.

Android Pilot Nation will load up the
Purple Pride

News
Activ
ity
screen.



Exceptions:

1.

The
end

user is unable to locate the
Cent
ral Menu and
Activ
ity Organizer
or

the
Purple Pride

News

Activ
ity icon
.

2.

The Android mobile device in use may have faulty hardware.


Priority:

High

Priority.


When Available:
Current Release.


Frequency of use:

Occasional.


Channel to primary actor:

Application


Open issues:
None.


Use Case
12
:
End

User Follows a Link on Purple Pride
News
Activ
ity

Primary Actor:

End

User


Goal in context:

To
follow a link on the Purple Pride News
Activ
ity
.


Preconditions:

The Android
mobile
device

is turned on and ready for use.
The Android
mobile device

has a data plan attached to its service or is
connected to the wireless internet. The Android Pilot Nation
a
pplication has
been downloaded. The
end

user
is on an
Activ
ity page of Android Pilo
t
Nation.