OOSE

CASE STUDY
D V SHRAVANI
BU21CSEN0500304

INTRODUCTION
A Parking Management System automates the process of managing parking
spaces, making it easy to find, reserve, and pay for parking. It provides real-time
slot availability, allows users to book spots, calculates charges, and sends
reminders. For staff, it offers tools to monitor and manage parking operations.
This system improves user convenience, reduces search times, and enhances
the efficiency of parking facilities.
REQUIREMENTS
Functional Requirements:
1. Need Requirements for Function User Registration and Login: To reserve
parking spaces, users (such as drivers) can register and log in using the
system.
2. Parking Slot Availability: Shows current data on open and occupied
parking spaces. Slot Reservation: Enables users to book a time slot for a
predetermined amount of time. Automated billing creates a bill by
calculating parking fees based on how long a car is parked.
3. Staff Access Control: Enables security guards and parking attendants to
monitor parking conditions, control slots, and confirm reservations.
Notifications: Notifies users when their reservations expire and when it's
time to park.
Non-functional specifications Performance:

1. Usability: All user roles (drivers, attendants, and administrators) may

easily navigate this straightforward and intuitive user interface.
2. Reliability: 500 transactions per hour or more must be handled
consistently and without interruption.
3. Security measures include safe login and data encryption for user
information to guard against unwanted access.
 4. Scalability: The system should be able to grow to accommodate the
management of numerous parking lots in different areas.
Design (UML Models)
Class Diagram:Class diagrams are a type of UML (Unified Modeling Language)
diagram used in software engineering to visually represent the structure and
relationships of classes within a system i.e. used to construct and visualize
object-oriented systems.
Notations
i. Class Name: Top compartment, bold, centered.
ii. Attributes: Middle compartment, shows variables with visibility (+, -), and
data type.
iii. Methods: Bottom compartment, lists functions with visibility, return type,
and parameters.
Relationships

Diagram Example:
Use Case Diagram: Represent key interactions of each actor (e.g., Driver,
Attendant, Admin) with the system and their corresponding use cases.

Diagram Example:
 State Machine : It describe the dynamic behavior of an individual object as a
number of states and transitions between these states.

Notations
Sequence diagram: it is used show the interactions between objects in the
sequential order.

Diagram

Activity Diagram : describes the behavior of a system in terms of activities.

Implementations
By using Visual Paradigm

public class Class {

}
public class admin {

public int adminid;

public int name;
public int contactdetails;

public void manageparkinglot() {

// TODO - implement admin.manageparkinglot
throw new UnsupportedOperationException();
}

public void generatereport() {

// TODO - implement admin.generatereport
throw new UnsupportedOperationException();
}

}
public class user {

private int userID;

public int name;
public int contactdetails;

public void getticket() {

// TODO - implement user.getticket
throw new UnsupportedOperationException();
}

public void payfee() {

// TODO - implement user.payfee
throw new UnsupportedOperationException();
}

public class payment {

private int paymentid;

private int amount;
private int method;

public void processpayment() {

// TODO - implement payment.processpayment
throw new UnsupportedOperationException();
}

}
public class vehicle {

public int vehicleID;

public int type;
public int licenceplate;
 public void park() {
// TODO - implement vehicle.park
throw new UnsupportedOperationException();
}

public void exit() {

// TODO - implement vehicle.exit
throw new UnsupportedOperationException();
}

public void entry() {

// TODO - implement vehicle.entry
throw new UnsupportedOperationException();
}

}
public class parkinglot {

public int lotID;

public int availablespace;
public int location;
public int attribute;

public void addvehicle() {

// TODO - implement parkinglot.addvehicle
throw new UnsupportedOperationException();
}

public void removevehicle() {

// TODO - implement parkinglot.removevehicle
throw new UnsupportedOperationException();
}

}
public class parkingticket {
 public int ticketID;
public int vehicleID;
public int entrytime;
public int exittime;
public int fee;

public void calculatefee() {

// TODO - implement parkingticket.calculatefee
throw new UnsupportedOperationException();
}

Test Cases

User Management Test Case

Test Case: User Registration
Objective: Verify user registration functionality.
Preconditions: User is not already registered in the system.
Inputs: Username, password, email.
Steps:
Navigate to the registration page.
Enter a valid username, password, and email.
Submit the registration form.
Expected Result: User account is created successfully, and a confirmation email
is sent.
2. Parking Slot Management Test Case
Test Case: Add New Parking Slot (Admin Only)
Objective: Verify the ability for an admin to add a new parking slot.
Preconditions: Admin privileges.
Inputs: Parking slot details (e.g., ID, location, availability).
Steps:
Log in with admin credentials.
Navigate to the "Add Parking Slot" page.
Enter parking slot details.
Submit the form.
Expected Result: Parking slot is added successfully, and availability is updated in
the system.
3. Vehicle Management Test Case
Test Case: Register New Vehicle
Objective: Verify vehicle registration functionality.
Preconditions: User is logged in and has a valid account.
Inputs: Vehicle details (License plate, model, owner information).
Steps:
Navigate to "Register Vehicle" page.
Enter vehicle details.
Submit the registration form.
Expected Result: Vehicle registered successfully, and details are saved in the
system.
4. Payment Management Test Case
Test Case: Pay Parking Fee
Objective: Verify parking fee payment processing.
Preconditions: A parking ticket is issued and payment is pending.
Inputs: Ticket ID, payment details (e.g., card number).
Steps:
Go to the "Pay Ticket" page.
Enter ticket ID and payment details.
Submit the payment.
Expected Result: Payment is processed successfully, and a receipt is generated.
5. Parking Ticket Management Test Case
Test Case: Issue Parking Ticket
Objective: Verify parking ticket issuance functionality.
Preconditions: Available parking slot.
Inputs: Vehicle ID.
Steps:
Select an available parking slot.
Enter vehicle ID to issue a ticket.
Expected Result: Parking ticket is issued with details like start time, slot ID, and
vehicle ID.
6. Reports and History Test Case
Test Case: View Parking History
Objective: Verify viewing of a user's past parking history.
Preconditions: User has parking history in the system.
Inputs: User ID.
Steps:
Go to the "Parking History" page.
Enter the User ID.
Submit.
Expected Result: All past parking sessions for the user are displayed.
7. Search and Filter Test Case
Test Case: Search by Vehicle License Plate
Objective: Verify the search functionality by vehicle license plate.
Preconditions: Vehicle with the license plate is registered in the system.
Inputs: License plate.
Steps:
Go to the search page.
Enter the license plate and submit.
Expected Result: Display the vehicle details for the matching license plate.

These cases provide a focused test for each primary component of a Parking
Management System.

Conclusion :

To conclued ,this case study highlights how the Parking Management

System streamlines the parking process, making it more efficient and
user-friendly. By automating essential tasks like booking slots,
processing payments, and tracking vehicle history, the system reduces
the effort for both users and staff. Through detailed functional and
non-functional requirements, UML-based design, and rigorous testing,
the case study demonstrates how a well-planned system can improve
service quality, security, and scalability. Ultimately, it serves as a model
for developing reliable and effective solutions in facility management.