The document describes an automated parking system project that aims to maximize parking utilization. It discusses reserving spots online, detecting vehicles with license plate readers, directing cars to empty spots, and processing payments. Functional requirements include registering customers, making reservations, identifying vehicles, and handling both registered and walk-in customers. Non-functional requirements address authorization, data validation, performance, and maintenance. Risks, effort estimation, testing procedures, and future enhancements are also outlined.

1. PARKING GARAGE AUTOMATION
Aparna Adiraju - 84193
Prashanthi Gogineni - 82259
Rakesh Reddy - 84808
Avdesh Kumar - 84201
Dimple Badiani - 81049
Raghavendra - 84807

2. INTRODUCTION
•In this project we are trying to automate the parking
system of a parking lot. We assume that there is a
parking lot where still we have people who go over to
keep a check of the empty spots or there are some
sensors which keep a track of the total number of
vacant or occupied spots.

3. CONCEPT DEFINITION
• Our aim it to go a step further and try to automate
this process itself. We will try to create a system
with which customers can reserve their parking spot
online. With this system we can have various
sections where if it is a already registered customer
we have a separate section for them.
• The system would try to maximize the parking
structure. Where we can manage the parking for a
specific time to accommodate all the customers.

4. Metrics for automated parking system
Customer Experience - Reducing the time customers spend on
parking.
a) The Gift of Time
b) 30 Seconds is the New Minute
Street Operations - Optimizing parking space utilization and revenue.
a) Optimizing Parking Management
b) Meter Operations
c)Manage Limited Neighborhood Parking.

5. Support and Analytics - Reducing cost by boosting productivity.
a) Productive Parking Programs
b) Manage On-Street Parking Congestion
c)Demand Management
Compliance - Creating flexibility of payments for maximizing collections.
a)Creating Compliance
b)Directed Enforcement
c)Parking Enforcement Officer Support

6. FUNCTIONAL REQUIREMENTS
• New customers will have to be able to register with automated park so
that they can make future reservations.
• If a registered customer wants to make a monthly contract he will be
given a list of months to choose from. Based on the month he selects
and the availability of spots the database will reserve a guaranteed
spot for the user.
• Once the presence of a car in the lift is detected, the license plate reader
has to read the plate number and check to see if a
contract/reservation has been made with that number.
• If a reserved/contract customer’s plate number is not recognized the user
will be asked to input his log in details and this will be used to
access the user’s account and provide service accordingly.

7. • If an unregistered customer arrives to park in the garage he will be
treated as a walk-in customer.
• Once the system determines which floor to transport the car to, the
elevator has to lift the car to that deck.
• Once a user leaves a spot the spot should become available
immediately and not be unavailable till the car exits the garage.
• If an unregistered customer wants to leave the garage the
operator(security guard) has to be notified. The operator has to
help the customer pay his bill in order to be able to exit the garage.

8. • If a user extends the duration of reservation before the end of
thereserved time period, the database should be checked to see
theavailability of spots.
• If a reserved customer doesn’t arrive within the grace period
thereservation has to be cancelled but the user will be charged for the
fullreserved period.
• When a registered customer wants to make a reservation for
aparticular time period then he’ll be given a list of dates and
times to pick from.
• Once the presence of a car in the lift is detected, the license platereader
has to read the plate number and check to see if
acontract/reservation has been made with that number.

9. • If a reserved/contract customer’s plate number is not recognized the user will be
asked to input his log in details and this will be used to access the user’s
account and provide service accordingly.
• Once a user leaves a spot the spot should become available immediately and
not be unavailable till the car exits the garage. The operator has to help the
customer pay his bill in order to be able to exit the garage.
• If a reserved customer doesn’t arrive within the grace period thereservation
has to be cancelled but the user will be charged for the fullreserved period.The exit
gate has to open for registered customer once the licenseplate reader at the exit
reads the plate number.
• The gate that leads to the ground floor should open to permit walk-incustomers to
enter the ground floor. This should be done after anavailable spot has been
detected and the user agrees to the walk-interms and conditions.

10. NON-FUNCTIONAL REQUIREMENTS
• Automated park should only permit authorized users to access/edit acustomer’s
profile. Customers should not be able to alter their amountowed in any way other
than posting a payment.
• Only a valid email address and credit card number should be accepted.
• Only those customers with an account profile in good standing shouldbe allowed
to make a reservation.
• A customer utilizing the elevator should have access to their floorwithin 3 minutes
from the entry console.
• Automated park should incorporate self-check features to getmalfunctioning
hardware serviced/replaced to minimize any reductionof service.

11. USE CASE SUMMARY

13. USE CASE - PARKING
• This use case shows when the customer arrives at the gate and want to
park.
• If the customer has already registered then the camera at the entrance will
read the registration number, check for the requirements for the
registration and bring the car to the assigned floor.
• If the customer is not registered the system will search for the vacant
parking spots, inform the customer and he can pay and reserve that spot
before parking.

14. CLASS DIAGRAM

15. STATE DIAGRAM

16. SEQUENCE DIAGRAM

17. DEPLOYMENT DIAGRAM

19. RISK ASSESSMENT :
There exists various types of riks that may arise while
building a project.
Financial risk:
The risks arising from the actions of transactions like
vendors,customers and counterparties in derivative
transactions
Environment Risk:
Crime/location, Accedent/Health and
Safety,Fire/disaster, depreciation.

20. Privacy and Information Risk:
The collection,use,disclosure of personel information
for research purposes that belongs to a group may
be harmed.
Business Corporate Risk:
Loss of income,loss of
service/Dowtown, Reputation/History/Management
risk,Insider fraud/Employee dishonesty,Loss of key
staff.

21. Different ways for Identifying
• Analysis of system
• feedback and communication
• scenario building
• Audits
• Brainstorming
• SWOT analysis
• Experience Judgement

22. PROJECT EFFORT ESTIMATION

24. –Johnny Appleseed
“Type a quote here.”

25. TESTING
The purpose of this Automated Parking Information System operational test is to determine the ability of the
automated, real-time parking information and guidance system to:
• Provide efficient and user-friendly access to parking at the garage.
• Improve management and utilization of the underutilized parking resources at the garage.
There are two types of testing
1. manual
2. automation
Manual testing is costly and time consuming, because every test case comprises building up a park scenario with real
cars and manual driving of each maneuver.
Furthermore, performing a test in this way is difficult to reproduce, because the details of the test execution vary. In
contrast, automated tests can perform a great number of test cases with less effort. Therefore automated functional tests
performed in a controlled simulation environment in addition to manual tests could form an important quality assurance
measure.

26. Evolutionary functional testing provides a way to automate
functional tests as a complete process. Instead of selecting the
test cases manually, a search for interesting test cases is
performed
automatically. This is done by translating the test case selection
into an optimization problem. This requires the solution of two
problems. First, how to generate the test data and second how
to
evaluate the test result

27. • ACCEPTANCE TEST CASES:
Log in - test passes if correct email
and password is entered
Vehicle Check - test passes if the
license plate matches with the
reservation details
Registration - test passes if user
enters a valid email id and other
details for creating account

28. FUTURE WORK
• For further modifying the system few of the following can be done.
• Advertising for online reservations where information about the surroundings near the
parking lot can be given to the customer and the garage owner can sell the advertising space
to the merchants by promise to notify the customers of their deals and offers.
• Integration of multiple parking lots can be done where the information can be shared by the
administrator to facilitate the parking and convenient for the customer.
• Use of new and advanced sensors to track the vehicles.

29. THANK YOU