3. Functional Requirements - Ash City

idleheadedceleryMobile - Wireless

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

67 views



Page
i


Requirements Specification

for

Ash City Mobile Application

Version 1.0

Prepared by Sophia Santamaria








Page
ii

Table of Contents

Table of Contents

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

ii

Revision History

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

iii

1.

Introduction

................................
................................
................................
..............................
1

1.1

Purpose

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

1

1.2

Intended Audience and Reading Suggestions

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

1

1.3

Project Scope

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

1

2.

Overall Description

................................
................................
................................
..................
1

2.1

Product Features

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

1

2.2

Operating Environment

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

1

2.3

Design and Implementation Constraints

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

2

2.4

Assumptions and Dependencies

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

2

3.

Functional Requirements

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

Error! Bookmark not defined.

3.1

Session Management
-

Standard:

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

2

3.3

Session Management
-

Search:

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

3

3.4

Session Management


Sub Navigation:

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

3

4.

External Interface Requirements

................................
................................
...........................
3

4.1

User Interface

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

3

4.2

Hardware Interfaces

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

4

4.3

Software Interfaces

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

4

4
.4

Communications Interfaces

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

4

5.

Other Nonfunctional Requirements

................................
................................
.......................
5

5.1

Performance Requirements

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

5

5.2

Safety Requirements

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

5

5.3

Securi
ty Requirements

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

5

5.4

Software Quality Attributes

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

5

6.

Other Requirements

................................
................................
................................
................
5

Appendix A: Issues List

................................
................................
................................
.................
5





Page
iii

Revision History

Name

Date

Rea
son For Changes

Version

Sophia
Santamaria

January 9,
2013

Initial Draft

1.0

Charles Wu

January 9,
2013

Editing, format, updating missing content

1.1









Page
1


1.

Introduction

1.1

Purpose

The purpose of this document is to define
the requirements for creating a
downloadable mobile
application for

iPhone and
Android application for the

Ash City Catalogue
. This document will
outline all of the necessary information to start development.

1.2

Intended Audience and Reading Suggestions

The intended audience for this docum
ent is

Ash City V.P.s
and the
sales team
. Throughout the
rest of this document it the project will be broken up into sections for: Project Description, System
Features, External Interface Requirements, and Non Functional Requirements.
There is also a
glos
sary of common terms found throughout the document.

1.3

Project Scope

This project is to take the existing
online catalogue
and convert them to
a mobile application
. The
benefits of this project are to be able to use a mobile device to make the

product

catalo
gue more
assessable.
The goal is to make it as easy as possible to
view and order

with anyone using the
application.
This will allow for users
to view and purchase Ash City collections on the go
.


The software being used for development is the
Apple and
Android development kit
s, Xcode and
Android
SDK. The project is being managed by a server running
INSERT SOFTWAR
E
.

2.

Overall Description

2.1

Product Features

This program will allow users to be able to review and order Ash City Collections from their mobile
phon
e
. Any phone that supports Android
2.2

or higher

or iO
S 5 or higher will be able to install the
applications and run the application from their phone. This app will allow users to have a
seamless experience as if they were doing so on their pc through th
eir web browser.

2.2

Operating Environment

The software will run on the Android operating system version 2.2 or higher and iOS

5 or higher.
All devices that support this version of
the Android operating system will be able to run the
application. The applicat
ion is developed Android SDK and Xcode respectively. The

intent of this
application is to utilize the images and ordering functions on a mobile device but with the
functionality and interface designed for mobile phone. The application should be integrated

with
the existing catalogue and ordering database for easy updates.



Page
2


2.3

Design and Implementation Constraints

The software must run on the Android operating system. The mobile phone has existing
hardware/software constraints. The database used by the softwar
e needs to be the same one that
is used by the existing catalogue and ordering database. The software must also use the language
supported by the Android development environment, java plus the Android SDK.


F
or the iPhone app, as with the Android, hardwa
re and software restraints are limited to the
iPhone 3S and newer, running iOS 5 or newer.

2.4

Assumptions and Dependencies

The system is dependent upon the

server. Customers will have to download the Ash City
application from Google Play or the App Store.

3.

Fu
nctional Requirements

3.1

Session Management
-

Standard
:

FR
-
1: After installing the Application from iTunes or the App store the user will be asked to login.


FR
-
2: Upon successful login, the user can select from the following catalogue options:




Spring 2
013



Winter 2013


FR
-
3:
Based on the selection the product categories will be listed:




Outerwear



Soft Shell



Fleece



Knits



Wovens



Active Wear



Safety



Accessories



Team Wear



e.c.o
.

Collection



FR
-
4
:
Once a category is selected the produ
ct thumbnail images will appear for selection.


FR
-
5: A user can then select the product and view the details.


FR
-
6: The detail page will contain all the same features and information as the website.


FR
-
7: From the here the user can either proceed to ca
ll a rep for an order or proceed to the online
checkout process.




Page
3


3.3

Session Management
-

Search
:

FR
-
1:
After installing the Application from iTunes or the App store the user will be asked to login.


FR
-
2: Upon successful login, the user can select from the f
ollowing cat
alogue options or use the
search function indicated by the search icon in the top right hand corner of the application.


FR
-
3: Once the icon is selected two open text field will be available to the user to search for the
product name
-

by produ
ct ID/SKU or by keyword.


FR
-
4: Following a successful query the search feature will query the application database to
display the search results. Following an unsuccessful query the search feature will display
an error message that no matches were found.


FR
-
6: A user can select the desired product from the results and proceed to the product details.


FR
-
7: From the here the user can either proceed to call a rep for an order or proceed to the online
checkout process



3.4

Session Management


Sub Na
vigation
:

FR
-
1: After installing the Application from iTunes or the App store the user will be asked to login.


FR
-
2:
Upon successful login, the user can select from the following cat
alogue options, search or
use the sub navigation to find the fo
llowing items:





Catalogue



Videos



Contact

Us


FR
-
3: Should a user select to download the catalogue PDF it will be viewed on their mobile device.


FR
-
4: Should a user select videos, the 360 video

list will display. Upon selecting a video it will play
on their device.


FR
-
6: Should a user select Contact Us, the call feature will open on their mobile device.



4.

External Interface Requirements

4.1

User Interface

UI
-
1:
All users shall be able to zoom into
images using the standard gestures on mobile devices
.


UI
-
2: All Users will be able to view the next product by swiping left to right
.




Page
4


UI
-
3: All users should be able to go back to the product category page via the back button in the

top
corner
.


UI
-
4:
Al
l users should be able to search by keyword or product ID
.


UI
-
5: All users should be able to navigate using the sub navigation icons to access the Catalogue
PDF, 360 videos
,

and to contact a rep
representative



4.2

Hardware Interfaces

This will be an iPhone
and an Android phone application, and as such, will be designed to
interface with the hardware present on the iPhone and Android phones. In theory the application
will be able to run by other devices that can emulate the Android, but this will not be a
co
nsideration during design.


As this is a mobile device, it will be using the cellular network or WiFi to connect to the Internet,
which will allow it to communicate with the database servers. This means that it will be using the
infrastructure, be it wi
reless communication points or physical lines, of the network in order to
perform properly. There will have to be some sort of error checking for if the network is down or
inaccessible.

4.3

Software Interfaces

This product will be connecting remotely to a MyS
QL database that is already set up and is the
same one that the Ash City website connects to. This allows for use by users of both computers
and the phone. The operating system the software runs on will be the operating system the
Android or iPhone runs
on, which comes with a software framework that will be utilized, including
many prepackaged components to do things like create menus, hookup buttons, and other
common functions expected of a mobile device. The only communication will be between the
phone

and the server housing the database, which will be sending queries or updates and
receiving the information back. The logic associated with the website will be duplicated on the
phone, so there will be little in the way of a server side component perform
ing logic.

4.4

Communications Interfaces

This will be an iPhone and Android application, but may still link to web pages that are not
necessary to duplicate. As described above, this will be communicating with a database server,
and so will be making use of t
he Android network and HTTPS in order to communicate. There is
no email or messaging currently, but this may change. The primary forms of communication will
be database transactions or requests. The system will need to be able to integrate with the
INTE
RNAL

system in order for users to log in.



Page
5


5.

Other Nonfunctional Requirements

5.1

Performance Requirements

The primary performance requirement is speed of the network. The application itself will only have
minimal logic and so there should be little to no issue
s with the computation required by the phone
itself.

5.2

Safety Requirements

There are no safety requirements with this application, other than any normal hazards of a mobile
device. The only hazard is a user using the device when they should not be, such a
s while driving.

5.3

Security Requirements

The application must be able to link up with the
INTERNAL

system in order for users to properly
log in and be identified. This information must be kept secure.


5.4

Software Quality Attributes

The primary attribute of
this application will be usability given the large amounts of data and
information that will be presented on such a small screen, as well as the user’s ability to input data
into the device in a reasonable manner that should not be that much more difficult

than if they
were at an actual computer.


As usability is hard to quantify, substantial user testing will be needed and feedback gathered in
order to determine if the application can generally be considered usable. Because this application
will be on a
phone, portability is also important. We don’t want it to take up so much space or be
too slow causing the user’s to not be able to fit it on the device.


6.

Other Requirements


Appendix A: Issues List

Bug_Tracker.xls


This will be a list of the outstanding

bugs that are left at the end of the project.