SOFTWARE REQUIREMENTS SPECIFICATION

RFID Parking Garage

Anthony Nichols
Matthew Nichols
1.0 Introduction
Finding parking spaces for automobiles and motorcycles can a problematic enture due to
limited space and time! while the selling of parking spaces is potential lucratie endeaor"
#urrently! most large parking garages! including airport parking! use a ticketing system in
which users get a time$stamped ticket when entering the structure and pay a time relatie
fee when e%iting" &he transmission of these disposable tickets is a time inefficient
process susceptible to error" &hese tickets can easily be lost! and with the lost tickets! the
entire process disoriented" &he manual payment process can also be time consuming
when traffic is at a high rate"
An RFID parking system would improe this by allowing the user to interact with the
parking area with an RFID card at the entrance and e%it of the parking area" An RFID
parking system would also allow the user to keep an account on which the system would
keep track of financial transactions" &his would reduce the amount of time the user must
interact with the system and increase the security of the user" A new system to allow ease
of use and increased security of parking areas is needed
1.1 Goals and objectives
&o proide indiiduals who re'uire a parking area with a system that is
efficient and easy to use"
&o proide indiiduals with a system that accounts for the length of each
isit and proides them with an account on which that can pay for the
isit"
&o determine the adaptability of an RFID parking system with different
situations
&o determine the feasibility and cost effectieness of an RFID parking
system that proides efficiency and ease of use"
Improe security oer conention RFID parking systems by adding a
keypad
1.2 Statement of scope
A description of the software is presented" Ma(or inputs! processing functionality
and outputs are described without regard to implementation detail"
1.3 Software context
In order to resole the issue! we must change the way that both that customers
access the parking garage and how money is transferred between the building
owner and the customer" A simple and accessible technology like Radio
Fre'uency Identification )RFID* cards and readers could be taken adantage of in
order to streamline the entry and e%it process" &he cards would be tied to
customer accounts to which money could be transferred using a web interface"
&his new process would grant users irtually immediate entry and e%it from the
parking structure! while the garage owner would seamlessly receie correct
payment" &he process would begin by the user re'uesting an account through the
web interface" &his web interface will need to be easy to understand and naigate"
After creating an account and receiing their uni'ue RFID card in the mail! the
user could add money to their account to be used as payment in the parking
garage)s* connected to the system" As a user ehicle passes the RFID reader at a
garage entrance! their card would be read in order to retriee account information"
If the account balance was aboe the re'uired minimum! the ehicle would be
granted access" +hen leaing the garage! the RFID reader at the e%it would read
the user,s RFID card and remoe an appropriate amount of money from the
connected account" &his process of entry and e%it can be streamlined to aoid the
lines associated with the current parking garage procedure" &he system would be
able to count the number of ehicles in the structure at any one time! and
therefore! know the amount of free parking spaces! if any e%isted"
1.4 Major constraints
&he system deelopment cost for the initial prototype should not e%ceed
-.//"
&he final sales cost should be competitie with other typing products and
speciali0ed numeric keypad deices that are on the market at the time of sale"
&he system should be designed for operation in the home! office! or
classroom"
&he system should withstand periodic cleaning with a damp cloth and mild
detergent"
&he system should not contain materials that are ha0ardous to the user"
&he system should maintain functionality when used repetitiely by
elementary school aged children"
&he system should not interfere with the operation of the personal computer
to which it is attached"
&he system must comply with Part 12! entitled 3Radio Fre'uency Deices3
of &itle .4 of the #ode of Federal Regulations"
&he system keypad should be ergonomic in design so that the occurrence of
repetitie stress in(uries is minimi0ed"
&he system must not e%pose the user to electrical shock"
2.0 sa!e scenario
2.1 ser profiles
Administrators 5 these indiiduals oersee the parking garage and all of its
aspect" &hey are responsible for maintaining prices! user issues such as
payment problems! login issues! and general parking garage problems"
6sers 5 these indiiduals are the ones who use the parking garage system"
2.2 se"cases
Although the RFID Parking Garage is a relatiely comple% system! its direct
interaction with the user is relatiely simple" &he primary actors in this system
are users! administrators! and the database" 6sers utili0e this system to gain
access to the parking garage and to access7change their account information"
Administrators use the system to manage accounts and add users" &he database
contains all information about users and decides whether a user is cleared for
entrance or not"

2.3 Special usa!e considerations
No special usage considerations needed"
3.0 #ata Model and #escription
3.1 #ata #escription
&he ob(ectie of the RFID Parking Garage 8ystem is to allow users of the system
a fast and conenient way in which to park their ehicles" &he system will proide
users with an RFID card and a graphical user interface from which to interact with
the system" &he RFID card is used at parking lots with this system to swipe their
card and gain immediate access to a parking space" &he user interface will allow
users to check account information and additionally make payments to their
account" &he leel 0ero functionality of the RFID Parking Garage 8ystem is
illustrated in Figure 1" A summari0ed description of the leel 0ero functionality
follows in a table"
3.1.1 #ata objects
RFID #ard 8wipe 5 input from the user to the system
Password 9ntry 5 input from the user to the system by a keypad
Red7Green :ight 5 indicator for the user of the system that notifies the
user if they hae access
Admin76ser :ogin 5 An Admin or user logs into the web interface
Data Re'uest 5 A data re'uest made by the admin or user of the system on
the web interface
Data Response 5 Data that is sent to the admin or user of the system
3.1.2 $elations%ips
Relationships among data ob(ects are described using an 9RD$ like form" No
attempt is made to proide detail at this stage"
3.1.3 &omplete data model
3.1.3.1 'evel 0
Parking Garage
System
RFID Card Swipe
and Password Entry
Red/Green Light
Admin/User Login
Data Response
Data Reqest
3.1.3.2 'evel 1
3.1.4 #ata dictionar(
Admin $ Administrator
RFID 5 Radio fre'uency Identification
R; $ Re'uest
4.0 )unctional Model and #escription
4.1 ser Interface *+eb,
4.1.1 -rocessin! narrative *-S-.&,
&he user interface will be accessible ia the web and will allow the user to
iew their account information! including usage data! person information!
and money remaining in the account" 6sers will also be able to add money
to their account"
4.1.2 )unction flow dia!ram
4.1.3 Inputs and /utputs
Inputs
&ransaction information
Information re'uest
:ogin information
6pdated information
<utputs
Data Response
4.1.4 )unctionalit(
Allows a user of the parking garage to log in! check their usage
information! add money to their account! and change their account
information"
4.1.0 -erformance Issues
&he system could run slower if the serer is under pressure which could
cause delays in updating account information"
4.1.1 #esi!n &onstraints
N7A"
4.2 2dmin Interface *+eb,
4.2.1 -rocessin! narrative *-S-.&,
&he administrator interface will be accessible ia the web and will allow
administrators to add accounts to the database and update the account
information"
4.2.2 )unction flow dia!ram
4.2.3 Inputs and /utputs
Inputs
New account information
6pdated account information
6pdated parking price
:ogin information
<utputs
Data Response
4.2.4 )unctionalit(
Allows the administrators to add new users to the system and update user
information"
4.2.0 -erformance Issues
&he system could run slower if the serer is under pressure which could
cause delays in updating account information"
4.2.1 #esi!n &onstraints
N7A"
4.3 $)I# $eader"#atabase Interface
4.3.1 -rocessin! narrative *-S-.&,
&he RFID Reader$Database Interface will be the main way of
communication for the RFID card holder to communicate to the database
for access into the parking garage"
4.3.2 )unction flow dia!ram
4.3.3 Inputs and /utputs
Inputs
Account holder information contained on the RFID card
Account holder,s =$2 digit password
<utputs
Access7Denial to the parking garage
4.3.4 )unctionalit(
&he RFID Reader$Database Interface allows for communication from the
user to the database" If the user has an account and criteria for access are
met then they are granted access into the garage"
4.3.0 -erformance Issues
Interface from outside sources may possibly cause delays in the re'uest
for access to the garage"
4.3.1 #esi!n &onstraints
&he RFID card must be in close pro%imity for the RFID reader to pick up
the signal and relay the information the database"
4.4 #atabase S(stem
4.4.1 -rocessin! narrative *-S-.&,
&he database system will hold all of the information of eery user,s
account registered for the parking garage" &he Administrator Interface will
communicate to the database system if they need to modify a users
account"
4.4.2 )unction flow dia!ram
4.4.3 Inputs and /utputs
Inputs
Information re'uest
6pdated account information
New account information
:ogin information
&ransaction information
Account holders =$2 digit password
<utputs
Data response
4.4.4 )unctionalit(
&he database stores all information for the parking garage system
including login information for users and administrators"
4.4.0 -erformance Issues
<ther applications that are running on the same serer as the database
could potentially cause delays with re'uests"
4.4.1 #esi!n &onstraints
&he database design should be simple and easy for modification in the
future if changes are needed or re'uested"
4.0 Software Interface #escription
4.0.1 .xternal mac%ine interfaces
+e are currently not planning to make an interface to an e%ternal machine
not contained within our pro(ect as this time"
4.0.2 .xternal s(stem interfaces
+e are currently not planning to make a system interface for a machine
not contained within our pro(ect at this time"
4.0.3 3uman interface
&he web interface will be the human interface for our pro(ect" &he web
interface will allow users to monitor their account by adding funds!
changing passwords! check history logs )payment and parking*! and make
payments if necessary"
4.1 &ontrol flow description
&he control flow is presented in section 2"> of the document which will gie an
outline of what our system will be e%pected to proide upon completion"
0.0 4e%avioral Model and #escription
0.1 #escription for software be%avior
0.1.1 .vents
6ser attempts to access the parking garage ia RFID card
6ser logs into the web interface
Admin logs into the web interface
Admin changes users account information in the system
Admin creates7remoes an account
0.1.2 States
Garage Access Re'uest
6ser +eb Access
Admin +eb Access
Idle
0.2 State 5ransition #ia!rams

1.0 $estrictions6 'imitations6 and &onstraints
&he system deelopment cost for the initial prototype should not e%ceed -.//"
&he final sales cost should be competitie with other typing products and speciali0ed
numeric keypad deices that are on the market at the time of sale"
&he system should be designed for operation in the home! office! or classroom"
&he system should withstand periodic cleaning with a damp cloth and mild detergent"
&he system should not contain materials that are ha0ardous to the user"
&he system should maintain functionality when used repetitiely by elementary
school aged children"
&he system should not interfere with the operation of the personal computer to which
it is attached"
&he system must comply with Part 12! entitled 3Radio Fre'uency Deices3 of &itle
.4 of the #ode of Federal Regulations"
&he system keypad should be ergonomic in design so that the occurrence of repetitie
stress in(uries is minimi0ed"
&he system must not e%pose the user to electrical shock"
7.0 8alidation &riteria
7.1 &lasses of tests
General &est 5 6ser of the simple attempts to access the parking garage
ia an RFID card or keypad
Admin &est 5 An Administrator attempts to login to the system and
perform arious tasks" )add7remoe users! modify user accounts! 'uery
database! etc"*
+eb interface &est $ A user attempts to login the web interface and
modify there account"
7.2 .xpected software response
General &est 5 8ystem should indicate to the user whether or not they
hae access and then either grant or deny access to the user
Admin &est 5 6ser information should be modified in the database
+eb interface &est 5 6sers account should be modified according the
changes that were made" &he new data will be stored in the database"
7.3 -erformance bounds
N7A