Parking Simulation
System
Semester Project Documentation
Software Engineering (SEN-102)
Submitted By
Name Student ID
SYED ARQAM HUSSAIN BAI-24F-651
M. SAAD COHAN BAI-24F-632
M. SAQIB BAI-24F-634
ZEESHAN MIRZA BAI-24F-642
Submitted to
Mr. Faiz Ahmed
Abstract:
Urbanization and the rapid increase in vehicle ownership have made parking management a critical
challenge in cities. Drivers often face difficulty in finding parking spaces, resulting in traffic congestion, fuel
wastage, and frustration. Traditional parking systems rely on manual supervision and static signboards,
which lack real-time visibility and analytical capabilities.
The Parking Simulation System is a software-based solution that digitally models parking operations such as
vehicle entry and exit, parking slot allocation, occupancy tracking, and parking fee calculation. The system
also introduces an advanced QR-code-based payment mechanism to simulate cashless parking. This project
follows standard software engineering practices and is intended for simulation, analysis, and evaluation of
parking strategies without the need for physical sensors or hardware.
Introduction:
Parking management plays a vital role in urban infrastructure planning. Inefficient parking systems increase
congestion, reduce productivity, and negatively impact the environment. Traditional systems are not flexible
and do not provide analytical insights for administrators.
The Parking Simulation System addresses these issues by providing a digital platform that simulates parking
behavior and allows administrators to study usage patterns, peak hours, and pricing strategies. This project
demonstrates how software solutions can improve parking efficiency and support data-driven decision-
making.
Communication Phase:
The communication phase focuses on understanding the problem domain, identifying stakeholders, and
gathering requirements.
Project Objective:
To digitally simulate parking lot operations
To efficiently allocate parking spaces
To monitor parking duration using simulation time
To calculate parking charges automatically
To support QR-code-based payment handling
To provide analytical reports for administrators
Stakeholders:
Stakeholder Description
Parking User Parks vehicle and make payment
Administrator Manage slots, pricing and reports
Organization Uses insight for planning
Requirement Gathering:
Requirements were gathered using:
Interviews with parking users and administrators
Observation of existing parking systems
Analysis of parking issues in urban areas
Business Requirement Document:
The BRD defines the high-level needs.
Business Goals:
Reduce parking congestion
Improve space utilization
Enable cashless parking
Minimize manual intervention
Support planning and analytics
Business Problems:
Time wasted searching for parking
Inefficient space usage
Manual payment delays
Lack of parking usage data
Business Requirements:
The system shall manage parking slot availability digitally.
The system shall simulate vehicle entry and exit processes.
The system shall calculate parking fees based on duration.
The system shall support QR-based payment simulation.
The system shall generate detailed parking and revenue reports.
Business Rules:
Parking slots are allocated on a first-come-first-serve basis.
Pricing rules are defined by the administrator.
Payment must be completed before vehicle exit.
A parking slot is released only after successful payment.
Each vehicle is assigned only one slot at a time.
Business Constraints:
No physical sensor required.
Low cost solution.
Functional Specific Document:
The FSD explains how the system fulfills business requirements.
User Functional Requirements:
View available parking slots
Park vehicle in allocated slot
View parking duration and charges
Scan QR code for payment
Receive payment confirmation
Admin Functional Requirements:
Configure parking slots
Define pricing rules
Monitor occupancy
Generate reports
Manage payment records
System Functional Requirements:
Automatic slot allocation
Simulation time tracking
Parking fee calculation
QR code generation
Payment status update
Slot release after exit
Non-Functional Requirements
Performance: Fast response
Security: Data protection
Scalability: Supports expansion
Usability: User-friendly interface
Project Scope
The project scope defines the boundaries of the Parking Simulation System by clearly identifying what is
included in the system and what is excluded.
In-Scope
Simulation of parking operations
Slot allocation and occupancy management
Time-based parking fee calculation
QR-code based payment simulation
Administrative monitoring and reporting
Data analysis for parking usage
Out-Of-Scope
Installation of physical sensors
Real-time integration with live payment gateways or banks
Time-based parking fee calculation
PLANNING
Model Planning:
The Parking Simulation System operates by digitally modeling the complete lifecycle of a vehicle inside a
parking facility. The system uses simulation logic, predefined rules, and a centralized database to manage
parking slots, track time, calculate charges, and process QR-based payments.
Parking Slot Database:
In the first step, when a vehicle arrives at the parking facility, the user enters vehicle details such as vehicle
number and type into the system. The system records the entry time using a simulation clock and sends a
request to check parking availability. Then the system checks the Parking Slot Database to determine the
availability of free parking spaces. If a slot is available, the system selects an appropriate slot based on
predefined allocation rules such as first-come-first-serve or vehicle type. If no slot is available, the system
notifies the user that the parking area is full. After that, once a free slot is identified, the system allocates the
slot to the vehicle and updates the parking status to “Occupied.” The allocated slot number is displayed to
the user, and the parking session is created in the system database.
a) Simulation Clock:
In the second step, after slot allocation, the system continuously tracks the parking duration using simulation
time. The entry time is stored, and the parking duration is calculated when the vehicle exits. This tracking
helps in accurate fee calculation and usage analysis. When the user decides to leave the parking facility, an
exit request is made. The system retrieves the corresponding parking session details, including entry time
and allocated slot.
b) Payment Module:
In the third step, the system calculates the parking fee based on; Total parking duration, pricing rules defined
by the administrator, time-based or hourly rates, the calculated amount is displayed to the user. After fee
calculation, the system generates a unique QR code for the parking transaction. The QR code contains
encoded details such as parking session ID, vehicle number, and payable amount. The user scans the QR
code using a mobile payment application. In this project, the payment process is simulated. Once the QR
code is scanned, the system updates the payment status as “Paid” in the database. After successful payment,
the system marks the parking session as completed. The allocated parking slot is released and updated as
“Available” for the next vehicle. At last, all parking and payment data is stored in the database. The
administrator can view reports such as; parking occupancy, peak hours, total revenue (simulated), slot
utilization.
Development Methodology:
The development of the Parking Simulation System follows the Waterfall Model, a structured and
sequential software development approach. This model was selected because the system requirements are
clearly defined at the beginning and the project follows a step-by-step flow, where each phase is completed
before moving to the next. This approach ensures better control, documentation, and clarity throughout the
development process.
In the Requirement Analysis phase, all functional and non-functional requirements of the system were
gathered and finalized. This included understanding vehicle entry and exit flow, parking slot allocation rules,
simulation time tracking, fee calculation logic, and QR-based payment simulation. Clear requirements
helped in defining the project scope and avoiding changes at later stages.
The System Design phase focused on creating the overall architecture of the Parking Simulation System.
During this phase, the database structure for parking slots, vehicle records, and transactions was designed.
The simulation clock mechanism and slot allocation logic were also planned to ensure smooth system
operation.
Next, the Implementation phase involved developing the core modules of the system. This included vehicle
entry handling, parking slot allocation, time tracking, fee calculation, and QR code generation for payment
simulation. Each module was developed according to the predefined design specifications.
After implementation, the system entered the Testing phase, where individual modules were tested using
unit testing, followed by integration testing to ensure proper interaction between components. Various
scenarios such as full parking conditions, incorrect inputs, and extended parking durations were tested to
identify and fix errors.
Finally, the Deployment and Maintenance phase ensures that the system operates smoothly in a simulated
environment. Any issues identified after testing are corrected, and system performance is monitored.
Although the current system uses simulated payments, the design allows future enhancements such as real
payment gateway integration.
By following the Waterfall Model, the project maintains a logical development flow, proper documentation,
and reduced risk of errors, making it suitable for an academic software project like the Parking Simulation
System.
Schedule Planning:
Objective: To define a clear timeline and milestones for the development, testing and deployment of the
Parking Simulation System.
Project Timeline & Phases:
Phase Duration Description
Requirement Analysis: 1 week Gather system requirements,
define scope, and finalize
assumptions.
System Modeling & 2 weeks The phase involves designing
Database Setup architecture, create parking slot
database, and set up simulation
clock.
Simulation Logic 3 weeks It involves implementing
Development vehicle lifecycle simulation
such as vehicle entry, slot
allocation, time tracking.
QR Payment Simulation 1 week It involves developing QR code
Integration generation and integrating
simulated payment process.
Testing & Debugging 2 weeks It involves performing unit
tests, integration tests, and
resolve issues.
hour analysis.
Reporting & Analysis Module 1 week Create dashboards for occupancy,
revenue, and peak hour analysis.
Milestones:
Week 1: Requirements finalized.
Week 3: Database and system model ready.
Week 6: Core simulation logic completed.
Week 7: Payment module integrated.
Week 9: Testing completed.
Week 10: Reporting module delivered.
Dependencies:
Database setup must be completed before simulation logic development.
Payment module integration depends on fee calculation logic.
Risk Planning:
Objective:
To identify potential risks during the development and operation of the Parking Simulation System and
define mitigation strategies to minimize their impact.
1. Technical Risks
Risk Impact Mitigation Strategy
Database failure or High Implement regular backups and redundancy
corruption mechanisms.
QR code generation errors Medium Validate QR encoding and test with multiple
scenarios.
Simulation clock High Use reliable time libraries and perform unit testing.
malfunction
2. Operational Risks
Risk Impact Mitigation Strategy
Incorrect fee calculation High Thoroughly test pricing rules and implement
validation checks.
Slot allocation conflicts Medium Apply locking mechanisms and concurrency
control in database.
System downtime during High Optimize performance and conduct load testing.
peak hours
3. External Risks
Risk Impact Mitigation Strategy
Payment gateway integration issues Medium Start with simulated environment and
(future real payments) plan for API fallback.
Hardware failure in parking facility Low Ensure system can run on cloud or
backup servers.
4. Risk Monitoring
Maintain a Risk Register to track identified risks.
Conduct weekly reviews during development.
Use alerts and logs for real-time monitoring in production.
Quality Planning:
1. Quality Objectives
Accurate time tracking for parking duration.
Correct fee calculation based on pricing rules.
Reliable QR code generation and payment status update.
Smooth user experience with clear notifications and minimal delays.
2. Quality Standards
ISO/IEC 25010 Software Quality Model (Performance, Reliability, Usability).
Response time for slot allocation: ≤ 2 seconds.
Fee calculation accuracy: 100% correctness in all test cases.
QR code readability: 100% success rate in simulated environment.
3. Testing Strategy
Unit Testing:
Validate individual modules (entry, allocation, payment).
Integration Testing:
Ensure seamless interaction between modules.
System Testing:
Test full lifecycle from entry to exit.
Performance Testing:
Simulate peak load conditions to check system stability.
User Acceptance Testing (UAT):
Verify usability and functionality from an end-user perspective.
4. Quality Assurance Activities
Code reviews for all modules.
Automated test scripts for fee calculation and time tracking.
Continuous monitoring of logs for errors and anomalies.
Weekly quality audits during development phase.
5. Metrics for Quality
Defect Density: Number of defects per module.
Response Time: Average time for slot allocation and payment processing.
Accuracy Rate: Percentage of correct fee calculations.
User Satisfaction: Feedback score from test users.
Modeling
Unified Modeling Language
(UML) Diagram:
This UML Use Case Diagram shows how the User (Driver) and Admin interact with the Parking
Simulation System. It highlights the main system functions such as parking, payment, and
administration, along with «include» relationships that represent dependent processes like fee
calculation and QR code generation.
Data Flow Diagram
(DF) Diagram:
Symbol /
Name / Entity Description
ID
External entity who enters vehicle details, receives slot
User Driver
allocation, and makes QR-based payment
External entity who configures parking slots, sets pricing rules,
Admin Parking Administrator
and views reports
Parking Simulation
System Main process that manages parking, payment, and reporting
System
Arrow 1 Vehicle entry details Data sent by User to the System when entering the parking
Slot allocation &
Arrow 2 System response to User with allocated slot and parking status
parking status
Arrow 3 Payment confirmation Data sent by User to System after making payment
Slot & pricing Data sent by Admin to System to manage parking slots and
Arrow 4
configuration pricing rules
Arrow 5 Reports & analytics Data sent by System to Admin showing reports and analytics
Data Flow Diagram (DFD LEVEL 1)
Data
Data Store
Store Description Related Processes
Name
ID
Stores detailed information about parking slots, Vehicle Entry & Slot
Parking Slot including slot ID, slot status (available or Allocation, Payment
D1
Database occupied), and slot configuration defined by the Processing, Reporting &
admin. Analysis
Maintains records of active and completed Vehicle Entry & Slot
Parking
parking sessions such as vehicle number, Allocation, Parking Time
D2 Session
allocated slot, entry time, exit time, and total Tracking, Reporting &
Database
parking duration. Analysis
Contains payment-related data including Fee Calculation & QR
Payment calculated parking fee, payment status, Generation, Payment
D3
Database transaction ID, QR payment details, and Processing, Reporting &
payment timestamps. Analysis