Software Requirement Specification Document

1. Introduction
This document aims at defining overall software requirements for the automatic car parking system named PARK A LOT. Efforts have been made to define the requirements exhaustively and accurately. The final product will be having only features/functionalities mentioned in this document and any assumptions for additional feature/functionality should not be made by any of the parties involved in developing/testing/implementing/using this product. In case it is required to have some additional features, a formal change request will need to be raised and subsequently a new release of this document and/or product will be produced.

a) Purpose
This specification describes the capabilities that will be provided by the software application PARK A LOT. It also states the various required constraints by which the system will abide. The intended audiences for this document are the development team, testing team and the end user of this product.

b) Scope
The software product PARK A LOT will be a web based application that will be used managing an automatic car parking garage. This application will manage information of the Registered and Unregistered customers, also the pricing details for different types of customers. This application will also maintain the usage history. There are two types of parking available viz. Reserved and Walk In. the system will also generate the billing slips for the customers. The application will greatly simplify and speed up the parking and management of garage.

c) Definitions Acronyms and Abbreviations

Cancelled Reservation - a reservation that has been cancelled, either by the customer at least thirty minutes prior to the start date time of the reservation or by the expiration of the grace period.

Customer ID - the email address a customer uses to register with the online Park-A-Lot system. Elevator Camera - an image capturing camera capable of utilizing image recognition to determine the license plate number on a vehicle inside the parking garage elevator. Elevator Display - an LCD screen located inside the parking garage elevator for displaying information. Elevator Keypad - a 102/105-key keyboard located inside the parking garage elevator for inputting information. Exit Camera - same as elevator camera, and capable of using image recognition on license plates of vehicles exiting the garage. Extended Reservation - A reservation that has been extended past the original end time. Grace Period - the amount of time a customer is allowed to be late to check in for a reservation before the reservation is cancelled. Missed Reservation - when a customer fails to arrive before the grace period is over. No-Show Penalty - A fee a customer is assessed if he or she fails to fulfill a reservation before the expiration of the grace period. No Vacancy - The parking garage is full and is not walk-in parking at this time. Overstay - when a customer fails to depart at the scheduled time. Penalty Rate - the rate a customer who overstays his or her reservation is charged for that overage time, 1.5 times the hourly rate. Rain Check Credit - it is a credit given to the customer when he or she arrives at the parking garage and no spots are available to park in. Reservation - an arrangement to park in a parking garage for a fixed amount of time at a certain fee per hour. Recurring Reservation - a reservation, made in advance with a variable grace period that occurs on some regularly repeating schedule. Reservation Parking - when a customer parks at the garage to fulfill a preexisting reservation (either recurring or confirmed). Spot Sensors - sonar sensors capable of determining whether a parking spot inside the garage is occupied with a car or not. Walk In Parking - when a customer parks on-the-spot at a parking garage without a preexisting reservation.

d) References
Park A Lot Website: For information about the garage capacity, timings, and prices. IEEE Recommended Practice for Software Requirements Specifications- IEEE Std. 830-1993.

e) Overview
The rest of this document describes the various system requirements, interfaces, features, and functionalities in detail.

2. Overall Description
Parking of vehicles is one of the most suffered problems nowadays. PARK A LOT is an automated garage that solves the above discussed problem efficiently. In this automatic parking garage the customers have to leave their car at entry elevator and then the software allots that vehicle a parking spot. Vehicles details are stored along with its parking spot number in the software database. Now the car is shifted to the spot allotted to it with the help of the electronically controlled elevator. When the customer need his vehicle back he/she just has to give vehicles license plate no. and vehicle is brought to the exit elevator automatically and a bill is generated according to the time for which the parking was used, type of parking, type of customer etc. A customer can either be Registered or Unregistered. The Registered customers are offered several privileges like reservation of parking, facility of monthly billing etc. but the unregistered customer can only park his/her vehicle as Walk-In parking.

a) Product Description
This application will be a Web Based Application, self contained and an independent software product. i. User Interfaces Login Screen A screen for entering the UserId, Password and Type of User will be provided. Access to further screens will depend on Type of User. Registration Screen This screen is for the unregistered customers. It will capture all the information about the customer (name Ph. No., Vehicle No. Vehicle Type, Address, E-mail Id etc.) There will be screen that displays the current situation of the garage i.e. how many and which spots are occupied and which are not. There will be a screen that will show all the information about the registered customers. This screen is accessible only to the Administrator. There will be screen for the registered customers to reserve a parking. It will capture the date, time of start, and time of end of parking. It will also calculate the amount for that reservation.

Following documents will also be generated Parking slip that will confirm the identity of owner of the vehicle at the time of exit A parking bill is created for the customer each time the vehicle exits the garage A monthly bill is also created for the registered customers ii. Hardware Interfaces A network based system connected to the internet. Support for printer to print the bills and confirmation slip of reservation. A keypad at the elevator for the customer to enter the license plate no. in case the elevator camera is not working. A Camera at the entry elevator which will capture the vehicles license plate no. at the time of entry. Spot sensors installed at every parking spot which will tell if the spot is occupied. Exit camera which will capture the vehicles license plate no. at the time of exit. iii. Software Interfaces Any windows/Mac/ios/android based operating system Oracle 8i as the DBMS for the database. Java and Embedded C for coding/developing the software. Visual basic 6 for creating the bills. iv. Communication Interfaces None v. Memory Constraints At least 64MB RAM and 2GB space on hard disk will be required for running the application at the garages system. For the customers no memory constraints, only internet connection is required.

b) Product Functions
The system will allow access to only authorized users with specific roles (Administrator, Registered Customer, Unregistered Customer, and Garage Coordinator). Depending upon the users role he/she will be able to access only specific modules of the system.

i. A login facility for enabling only authorized access to the system. ii. User (with role Administrator) will be able to view the information details of all the customers and also edit the pricing rules. iii. User (with role Registered Customer) will be able to edit his personal details, also he will be able make reservations for future parking; he/she is also allowed to pay the monthly bills online. iv. User (with role Unregistered Customer) will be able fill online registration form to become a Registered Customer. v. User (with role Garage Coordinator) will be able to view the screen that shows the current situation of the garage.

c) User Characteristics
i. Educational Level: Should be comfortable with the English Language. ii. Experience: No constraint iii.Technical Expertise: Should be comfortable using general purpose applications on a computer.

3. Specific Requirements
This section contains the software requirements to a level of detail sufficient to enable designers to design the system and testers to test that system.

a) External Interface Requirements

i. User Interfaces The following screens will be provided Login Screen: this will be the first screen that will be displayed. It will allow different users to access different screens based upon the users role. Various fields available on this screen will be UserId alphanumeric of length up to 10 characters. Password alphanumeric of length up to 8 characters. Role will have one of these values (Administrator, Registered Customer, Unregistered Customer, and Garage Coordinator) Registration Screen: this screen is accessible only to the unregistered customers. Using the registration form over this screen one can register with the system to become a registered customer.

 Current Situation screen: this screen is accessible only to the administrator and the garage coordinator. Using this screen the garage coordinator comes to know about the no. of empty and occupied spots of the parking. Reservation Screen: this screen is only accessible to the registered customers. Here the registered customer can reserve a parking for future purposes. Various fields available on this screen will beUserId - alphanumeric of length up to 10 characters. Password - alphanumeric of length up to 8 characters. Reservation Date numeric field of format dd-mm-yyyy. Vehicle Id numeric of length 10 characters. Start Time and End Time ii. Hardware and Software Interfaces As stated above.

b) Performance Requirements
None

c) Design Constraints None d) Software System Attributes

i. Security The application will be password protected. The user will have to enter correct username, password and role to access the application. ii. Maintainability The application will be designed in a maintainable manner. It will be easy to incorporate new requirements in the individual modules. iii. Portability The application will be easily portable on any windows/mac/ios/android based system.

e) Logical Database Requirements

The following information will be placed in the databasei. Customers Details: Name, Ph. No., Address, Email-Id, Vehicles License No. ii. Vehicles Details: License No., Vehicle Name, Vehicle Type iii.Parking Details: License No., Spot No. Allotted, Time of Entry, Time of Exit and Amount Payable. iv. Reservation Details: Customers Name, Customers UserId, Date of Reservation, Start Time and End Time

f) Other requirements
None

User Interface Design and Implementation

1. Login Screen

2. Registration Screen

3. Reservation Screen

4. Current Situation Screen

5. Parking Slip

6. One Time Parking Bill

7. Monthly Bill