1.0 Introduction
Finding parking spaces for automobiles and motorcycles can a problematic venture due to
limited space and time, while the selling of parking spaces is potential lucrative endeavor.
Currently, 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 relative
fee when exiting. The transmission of these disposable tickets is a time inefficient
process susceptible to error. These tickets can easily be lost, and with the lost tickets, the
entire process disoriented. The manual payment process can also be time consuming
when traffic is at a high rate.
An RFID parking system would improve this by allowing the user to interact with the
parking area with an RFID card at the entrance and exit 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. This 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
To provide individuals who require a parking area with a system that is
efficient and easy to use.
To provide individuals with a system that accounts for the length of each
visit and provides them with an account on which that can pay for the
visit.
The system development cost for the initial prototype should not exceed
$400.
The final sales cost should be competitive with other typing products and
specialized numeric keypad devices that are on the market at the time of sale.
The system should withstand periodic cleaning with a damp cloth and mild
detergent.
The system should not contain materials that are hazardous to the user.
The system should not interfere with the operation of the personal computer
to which it is attached.
The system must comply with Part 15, entitled "Radio Frequency Devices"
of Title 47 of the Code of Federal Regulations.
Administrators these individuals oversee the parking garage and all of its
aspect. They are responsible for maintaining prices, user issues such as
payment problems, login issues, and general parking garage problems.
Users these individuals are the ones who use the parking garage system.
2.2 Use-cases
Although the RFID Parking Garage is a relatively complex system, its direct
interaction with the user is relatively simple. The primary actors in this system
are users, administrators, and the database. Users utilize this system to gain
access to the parking garage and to access/change their account information.
Administrators use the system to manage accounts and add users. The database
contains all information about users and decides whether a user is cleared for
entrance or not.
Red/Green Light indicator for the user of the system that notifies the
user if they have access
Data Request A data request made by the admin or user of the system on
the web interface
Data Response Data that is sent to the admin or user of the system
3.1.2 Relationships
Relationships among data objects are described using an ERD- like form. No
attempt is made to provide detail at this stage.
3.1.3 Complete data model
3.1.3.1 Level 0
Parking Garage
System
Admin/User Login
Data Request
Data Response
3.1.3.2 Level 1
Admin - Administrator
RFID Radio frequency Identification
RQ - Request
Transaction information
Information request
Login information
Updated information
Outputs
Data Response
4.1.4 Functionality
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.5 Performance Issues
The system could run slower if the server is under pressure which could
cause delays in updating account information.
4.1.6 Design Constraints
N/A.
4.2 Admin Interface (Web)
4.2.1 Processing narrative (PSPEC)
The administrator interface will be accessible via the web and will allow
administrators to add accounts to the database and update the account
information.
4.2.2 Function flow diagram
Login information
Outputs
Data Response
4.2.4 Functionality
Allows the administrators to add new users to the system and update user
information.
4.2.5 Performance Issues
The system could run slower if the server is under pressure which could
cause delays in updating account information.
4.2.6 Design Constraints
N/A.
4.3 RFID Reader-Database Interface
4.3.1 Processing narrative (PSPEC)
The 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 Function flow diagram
Outputs
4.3.4 Functionality
The 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.5 Performance Issues
Interface from outside sources may possibly cause delays in the request
for access to the garage.
Information request
Updated account information
Login information
Transaction information
Outputs
Data response
4.4.4 Functionality
The database stores all information for the parking garage system
including login information for users and administrators.
4.4.5 Performance Issues
Other applications that are running on the same server as the database
could potentially cause delays with requests.
4.4.6 Design Constraints
The database design should be simple and easy for modification in the
future if changes are needed or requested.
4.5 Software Interface Description
4.5.1 External machine interfaces
We are currently not planning to make an interface to an external machine
not contained within our project as this time.
4.5.2 External system interfaces
We are currently not planning to make a system interface for a machine
not contained within our project at this time.
4.5.3 Human interface
The web interface will be the human interface for our project. The 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.6 Control flow description
The control flow is presented in section 5.2 of the document which will give an
outline of what our system will be expected to provide upon completion.
5.1.2 States
Idle
The system development cost for the initial prototype should not exceed $400.
The final sales cost should be competitive with other typing products and specialized
numeric keypad devices that are on the market at the time of sale.
The system should be designed for operation in the home, office, or classroom.
The system should withstand periodic cleaning with a damp cloth and mild detergent.
The system should not contain materials that are hazardous to the user.
The system should not interfere with the operation of the personal computer to which
it is attached.
The system must comply with Part 15, entitled "Radio Frequency Devices" of Title 47
of the Code of Federal Regulations.
The system keypad should be ergonomic in design so that the occurrence of repetitive
stress injuries is minimized.
General Test User of the simple attempts to access the parking garage
via an RFID card or keypad
Admin Test An Administrator attempts to login to the system and
perform various tasks. (add/remove users, modify user accounts, query
database, etc.)
Web interface Test - A user attempts to login the web interface and modify
there account.
General Test System should indicate to the user whether or not they have
access and then either grant or deny access to the user
Admin Test User information should be modified in the database
Web interface Test Users account should be modified according the
changes that were made. The new data will be stored in the database.