Text To PDF - 02102023 - 180438
Text To PDF - 02102023 - 180438
4. *Work Order Management*: Utilize a system to create, track, and manage work
orders for various vehicle services and repairs.
5. *CRM (Customer Relationship Management) System*: Use a CRM system to
maintain a database of customer information, preferences, and interactions to
provide personalized service.
Customize and integrate these tools according to the specific needs and scale of
your automobile service station for a comprehensive management solution
Source code
Output
Successfully Connected
Table created
Automobile
1.Service
2.Source
3.Selling
4.Exit
Enter The Choice-
Choice 1:output
Successfully connected
Table created
Automobile
1.service
2.source
3.selling
4.exit
Enter The Choice- 1
Enter the serial number: 1
Enter the customer name: Ashraf
Enter the customer details: Student
Enter the customer address: Samadh Senior Secondary school,Tiruchiapalli
Enter the pincode: 620020
Enter the puramt: 657868700
Enter the discount: 16330
Successfully created
Try for second choice
Choice 2:output
Successfully Connected
Table created
Automobile
1.service
2.source
3.selling
4.exit
Enter The Choice- 2
Username: Ashraf
Password: 2023
SELECT*FROM WHERE
Username=”Ashraf”
Choice 3:output
Successfully Connected
Table created
Automobile
1.service
2.source
3.selling
4.exit
Enter The Choice- 3
Mycursor.execute(“SELECT*FROM customer_details”)
Limitations
The provided system, while functional for basic operations, has several limitations:
1. *Simplicity*: The system is kept simple for explanatory purposes and lacks
advanced features and error handling needed for a real-world application.
2. *No Database Integration*: The system doesn't integrate with a database for
persistent data storage. In a real application, data would be stored in a database for
reliability and scalability.
3. *Lack of User Interface*: The system operates through code, and there's no user-
friendly interface for customers or staff to interact with.
4. *Limited Exception Handling*: Error handling and exception management are
minimal, and the system may not handle unexpected inputs or errors robustly.
5. *No Security Measures*: The system doesn't implement security measures like
authentication, authorization, or encryption, which are essential for protecting
sensitive customer and business data.
6. *Fixed Service Types*: The service types (e.g., "Oil Change") are hard-coded. A
real system would allow for dynamic addition and modification of service types.
8. *Single Instance Execution*: The code is designed to run in a single instance, not
accommodating a concurrent and distributed environment.
10. *No Reporting or Analytics*: The system doesn't provide analytics or reporting
capabilities for business insights and decision-making.
11. *No Testing Framework*: There's no provision for automated testing, making it
harder to ensure the system's reliability and correctness as it evolves.
12. *Static Data*: Data, such as inventory items and customers, are hardcoded in
the example. A real system would fetch and update this data dynamically.
The requirements for the Automobile Service Management System are derived from
the objectives and are defined to ensure the system's functionality, usability, and
performance. These requirements serve as a guideline for the development
process, acting as a foundation for creating a successful software solution for
managing automobile service centres.
2. *Customer Management*:
- Ability to capture and store customer information, including contact details,
service history, and preferences.
3. *Vehicle Information*:
- Capability to record and manage vehicle details, such as make, model, year, and
VIN (Vehicle Identification Number).
5. *Inventory Management*:
- Ability to monitor and manage inventory levels of automotive parts, oils, and
other supplies, including tracking stock, orders, and deliveries.