Software Requirements

Document

Parkean Android Application

Version 1.0

















Requirements Document
CPS 4951 and Tech 4513
1. Systems Context & Scope

1.1 Description and Scope of the System
ParKean is an Android application created for students and faculty at Kean University
to have an easier parking experience. This system will have users log in, ask the user
to choose a parking lot, and will display how many parking spots are available. The
system will accomplish this by having the user input when they have parked their
vehicle.
This Android application will affect Kean University operations only. It will involve
active parking lots at Kean University Main Campus, East Campus, and STEM
Campus. The expected user for the application will be new and continuing students at
Kean University as well as staff members.
The software being used for development is the Android development kit which is a
plug-in to the Eclipse IDE.

1.2 System Partitioning (Identify Major Parts and Subsystems)
Major Parts: Android Operating System
Subsystems: Google API and SQLite Database
1.3 Product Boundary
All functions must stay within the platform boundaries.
All data must be easily available to view.
Since our audience is particularly limited to mobile devices in a parking lot,
all data must be easily viewable on all android smartphone devices.
1.4 Use Case List (Develop UML Diagram)


2. Functional and Data Requirements

2.1 Functional Requirements
The functional requirements are shown in the flow chart below:


2.2 Data Requirements
This application will be heavily dependent on user input. Once a user inputs that they are
parked, it will store which parking lot they are parked in. At a specific time every night, the
application will clear the data in particular parking lots to refresh for the next day. Data will
also be stored during the sign up and login process. Once a user creates a username and
password it will be stored in the database.
3. Look, Feel, and User Requirements
3.1 User Interface Requirements
All screens will have a top toolbar and the rest of the screen below. The top toolbar
will contain a back button and the name of the application.
User Tasks Sign In:
o Select Sign Up if you do not have a username or password. Input username
and password into text box if user has already signed up.
o Click sign in button once user has inputted username and password.
User Tasks Main Screen:
o Once signed in user will select Parking or Parked.
o Once user selects parking they will be sent to a screen with the option to look
at a map integrated with google APIs and Kean Parking Lots or go directly to
a list of the parking lots.
o In the list of parking lots there will be an amount of estimated spots available
in each lot.
o This would then direct to you to the page if you chose parked.
o On the parked page there is an ETA to ask what time they will be leaving their
spot.
3.2 Ease of Use Requirements
To make this application run with functionality there are requirements divided into the
following sections:
Reporting Requirements
Security Requirements
User Interface Requirements
Technology and Database Architecture Requirements
Support Requirements
3.3 Ease of Learning Requirements
In order to gain a large audience at Kean University we decided to make this app
extremely easy to learn. It is very simplistic due to the very efficient and fast paced
environment in Kean University parking lots.
4. PERFORMANCE REQUIREMENTS

4.1 Speed Requirements
8.2 kb/s in and 2.3 kb/s out with a response time of 112 ms
4.2 Safety Critical Requirements
Systems doesnt require any safety critical requirements
4.3 Precision Requirements
System calculates how many open parking spots are available by taking the number of
spots in the particular section and subtracting the spots that are taken. The spots that
are take is determined by the Google API of that section and how many users logged in
saying they are in that spot.
4.4 Reliability and Availability Requirements
The system will be available at all times as long as it is connected to Wi-Fi or a
telecommunication system.
4.5 Capacity and Scalability Requirements
The systems will be able to handle multiple updates to the database and store
information such as user names and passwords. The system will work across multiple
android operating systems.
5. OPERATIONAL REQUIREMENTS

5.1 Expected Technological Environment Requirements
The application will run on multiple Android operating systems
5.2 Partner Applications & Interfaces Requirements
The application will use Google API to obtain users location
5.3 Supportability Requirements
The application will be able to support multiple users on multiple Android devices
5.4 Maintainability and Portability Requirements
The developers will be able to delete any stale or unwanted data in the application. The
application will be on mobile devices and will be able to be accessed as long as theirs
Wi-Fi or a telecommunication system.
6. Security Requirements
6.1 System Confidentiality Requirements
All data used is open to the public and free to access.
Any user who feels violated by the application may have their data
removed from the system at their request.
6.2 Data Integrity Requirements
Data may not be modified, altered, or deleted with authorization from the
developer.
Any unauthorized change of data comes up as a red flag in the system.
In order to protect data, the system will be capable of performing data
integrity checks.
6.3 Audit Requirements
Due to lack of personal information required there is not a high level of security on this
application. The database and log in information will be safe and secure. In the attempt
there is a security breach or data becomes corrupt, we will be able to clear all of the data
and start fresh. This will only affect the applications accuracy of parking spots available
until the following day.

7. LEGAL REQUIREMENTS
The application will be copyrighted

8. STANDARDS REQUIREMENTS
The application will have a log in so that users can log into their personal accounts. It will use
Google API to get the users location so that it can store it and display it. It will display to the
users what parking spots are available by subtracting the spots that are taken which was
determined by the locations from the Google API.
9. Off-The-Shelf Solutions Requirements
9.1 COTS System Solutions Requirements
Our System will be built from scratch using the Eclipse IDE software. We will be using
Google APIs to create the mapping in our application.
9.2 Ready-Made Components Requirements
There is an open-source community in the android developer market. Although our
application will be made from scratch, the open-source community may be referenced.