DOC PREVIEW
WVU CS 430 - SOFTWARE REQUIREMENTS SPECIFICATION

This preview shows page 1-2-3-4-5-6 out of 18 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 18 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 18 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 18 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 18 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 18 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 18 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 18 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

SOFTWARE REQUIREMENTS SPECIFICATIONRFID Parking GarageAnthony NicholsMatthew Nichols1.0 IntroductionFinding parking spaces for automobiles and motorcycles can a problematic venture due tolimited 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 inwhich 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 easeof use and increased security of parking areas is needed1.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.- To determine the adaptability of an RFID parking system with different situations- To determine the feasibility and cost effectiveness of an RFID parking system that provides efficiency and ease of use.- Improve security over convention RFID parking systems by adding a keypad1.2 Statement of scopeA description of the software is presented. Major inputs, processing functionality and outputs are described without regard to implementation detail. 1.3 Software contextIn order to resolve 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 Frequency Identification (RFID) cards and readers could be taken advantage of in order to streamline the entry and exit process. The cards would be tied to customer accounts to which money could be transferred using a web interface. This new process would grant users virtually immediate entry and exit from the parking structure, while the garage owner would seamlessly receive correct payment. The process would begin by the user requesting an account through the web interface. This web interface will need to be easy to understand and navigate. After creating an account and receiving their unique 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 vehicle passes the RFID reader at a garage entrance, their card would be read in order to retrieve account information.If the account balance was above the required minimum, the vehicle would be granted access. When leaving the garage, the RFID reader at the exit would read the user’s RFID card and remove an appropriate amount of money from the connected account. This process of entry and exit can be streamlined to avoid the lines associated with the current parking garage procedure. The system would be able to count the number of vehicles in the structure at any one time, and therefore, know the amount of free parking spaces, if any existed.1.4 Major constraints- 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 maintain functionality when used repetitively by elementary school aged children.- 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.- The system must not expose the user to electrical shock.2.0 Usage scenario 2.1 User profiles- Administrators – these individuals oversee the parking garage and all of itsaspect. 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-casesAlthough 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.2.3 Special usage considerationsNo special usage considerations needed.3.0 Data Model and Description 3.1 Data DescriptionThe objective of the RFID Parking Garage System is to allow users of the system a fast and convenient way in which to park their vehicles. The system will provideusers with an RFID card and a graphical user interface from which to interact withthe system. The RFID card is used at parking lots with this system to swipe their card and gain immediate access to a parking space. The user interface will allow users to check account information and additionally make payments to their account. The level zero functionality of the RFID Parking Garage System is illustrated in Figure 1. A summarized description of the level zero functionality follows in a table. 3.1.1 Data objects- RFID Card Swipe – input from the user to the system- Password Entry – input from the user to the system by a keypad- Red/Green Light – indicator for the user of the system that notifies the user if they have access- Admin/User Login –


View Full Document

WVU CS 430 - SOFTWARE REQUIREMENTS SPECIFICATION

Documents in this Course
Lecture

Lecture

28 pages

Design

Design

27 pages

Load more
Download SOFTWARE REQUIREMENTS SPECIFICATION
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view SOFTWARE REQUIREMENTS SPECIFICATION and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view SOFTWARE REQUIREMENTS SPECIFICATION 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?