SE File
SE File
SE File
Problem Statement :
Hiring a cab or getting a car ride for far-across travel places has
always been a massive issue in Indian society. If abandoned in the
middle of the road, you have the option to walk to your destination.
But, it will be physically draining. How would you feel if your taxi driver
suddenly renegotiates the fare and when you say no the driver leaves
you grounded in the middle of nowhere? Traumatic experience right?
There are people who generally don’t prefer to travel in public transport
like busses, trains due to the crowd , safety issues and many more
genuine reasons , also if you are not a resident in a particular city then
Ola cab is the best option for travelling .
Solution:
The car aggregator company connects and partners with drivers and
taxi drivers to bring a modern change with the help of technology.
Entities: -
1. Customer
2. Driver
3. Cab
4. Bill
Attributes: -
1. Customer (Cust_id, Cust_name, Cust_phone, pickup_location , drop_location)
2. Driver(D_id , D_name , D_phone )
3. Cab(cab_no , cab_image , cab_model)
4. Bill (Bill_no, Bill_date, Bill_amt,Bill_tax)
Primary Keys: -
1. Cab: - Cab_No
2. Customer: - Cust_id
3. Bill: - Bill_no
4. Driver : D_id
Foreign Keys: -
1. Cab : Cab_id
2. Driver : D_id
Primary Actors: -
1. Admin
2. Customer
3. Driver
Relationships: -
1. Extend: -
Dependency of one use case on another use case.
Here, VIP booking and normal booking extends booking
2. Generalization: -
Generalization is shown in Bill Payment where there are 3 options: -
Pay With Cash
Pay With UPI
External Entities–
1. Customer
2. Admin
3. Driver
Process -
1. Car Booking Management System
Data Flow-:
2. Customer Orders Car
3. The Car Order is sent to Admin
4. Admin checks for available drivers nearby
5. Driver accepts booking
6. Invoice is sent to customer
External Entities–:
1. Customer
2. Admin
3. Driver
Process–:
1. Manage Customer Information
2. Manage Car Information
3. Monitor Car Details
4. Manage Transactions
5. Manage Driver Information
Data Store – :
1. Customer Database
2. Car Database
3. Transaction Database
4. Driver Database
Process-:
1. Display Customer Information
2. Validates/ Process Customer Information
Data Store-:
1. Customer Info
Process-:
1. Display Cab Information
2. Validates/ Process Cab Information
Data Store-:
1. Cab Info
Data Flow-:
2. Access Cab Information
3. Retrieve Cab Info
4. Enter/ Update / Delete Cab Info
Process-:
3. Display Driver Information
4. Validates/ Process Driver Information
Data Store-:
5. Driver Info
Data Flow-:
6. Access Driver Information
7. Retrieve Driver Info
8. Enter / Update / Delete Driver Info
Join Operation: -
Display Details, Cab Booking and Send Invoice are joined together into Logout action state.
Department: -
The departments are: -
1. Admin
2. Customer
3. Finance
Fork Operation: -
The login action state is further divided into: -
1. Admin Login
2. Customer Login
3. Driver Login
The System Dashboard is divided into: -
1. View / Search Cab
2. Order Cab
Actor: -
The Actor here is Admin.
Lifeline: -
1. Sign Up
2. Login Process
3. Order Taxi
4. Ola Service
5. Database
Messages: -
EN20CS301220 KISHKIN JOSHI
a) Call Messages: -
1. Registration
2. Customer Registration
3. Click login ()
4. Verify Username and Password
5. Search Cab
6. Cab Details
7. Process for Forgot Password
8. Operation
9. Reserve Car
10. Operation
11. Cab Information
12. Operation
13. Request Logout
b) Return Messages: -
1. Acknowledgement of Registration
2. Confirm
3. Acknowledgement of Login
4. Login Failed
5. Acknowledgement
6. View Cab Details
7. Acknowledgement for Forgot Password
8. Acknowledgement
9. Successfully Booked Cab
10. Acknowledgement
11. View of Details
12. Successfully Logout
Classes & their Attributes of Car Showroom Management System Class Diagram: -
Classes & their Operations(Methods) of Car Showroom Management System Class Diagram:-
1. Login: - validate()
2. Customer: - login(), send_order(), receive_order(), search_car(), cancel()
3. Driver - login(), maintain(), view_report(), generate_bill()
4. Cab: - view_cab(), update_cab(), register_cab(), cancel_cab()
5. Cab_booking: - select_cab(), book_cab()
6. Inventory: - search(), check()
7. Bill: - view_bill(), pay_bill(), cancel_pay()
Components: -
1. Car
2. Customer
3. Employee
4. Car_Booking
5. Inventory
6. Sales
7. Security
8. Persistence
9. Database
Interface: - System Admin
EN20CS301220 KISHKIN JOSHI
Features Of Car Showroom Management System Component Diagram: -
1. Model the components of Car Showroom Management System.
2. Model the database schema.
3. Model the executables of an application.
4. Model the system’s source code.