How ahirraoshubham/auto-spare-parts-management-system works
Project Type and Purpose
• This is a standalone, desktop‐based Java application (“Auto Spare Part Management System”) built on Java 1.6+ with a Microsoft Access (.accdb) backend.
• It provides CRUD and reporting functionality for spare parts, customers, staff, orders, quotations, and billing.
File Structure
• Top‐level Java classes (Bill.java, Customer.java, Order.java, etc.) indicate domain entities and GUIs (Home.java, Login.java, Welcome.java).
• Resources/Auto spare.accdb is the database file.
• Run.bat, Delete class files.bat and Readme.txt/README.md are deployment and documentation artifacts.
Extract Insights from the README
• Confirms a Windows‐only Java+Access stack.
• Describes modules: stock management, billing, customer & staff records, distributor ordering.
• No mention of a web or service layer—pure desktop.
a. Main Components
• Presentation Layer (Java Swing UIs): Login, Home, ViewQuotation, Reports, etc.
• Business Logic Layer (Service Classes): CustomerDetails.java, Variables.java, Reports.java, BillReport.java, OrderReport.java.
• Data Access Layer (DAO): classes or methods inside domain classes that use JDBC-ODBC bridge to connect to Auto spare.accdb.
• Database (Microsoft Access .accdb file)
• External Tools (BAT scripts for launch and cleanup)
• Reporting Engine (built‐in Java reporting code, e.g., BillReport, OrderReport)
b. Relationships and Data Flow
1. User interacts with a Swing form (e.g., Login.java → Home.java → Order.java).
2. Forms call Business Logic methods to validate input, enforce rules.
3. Business Logic invokes Data Access methods to perform SQL CRUD on the Access DB.
4. Results flow back up: DAOs → Services → UIs.
5. Reports components read from the DB, transform data into printable bills, reports.
6. Batch scripts wrap application start and optional cleanup.
c. Architectural Patterns & Principles
• Layered (Presentation → Business → Data Access → Database)
• MVC‐style separation (Forms = View, service classes = Controller/Model)
• Single Database file acts as central datastore (no microservices)
d. Key Technologies & Frameworks
• Java 1.6+ (Swing/AWT)
• JDBC‐ODBC bridge or UCanAccess driver
• Microsoft Access (.accdb)
• Windows Batch (.bat) for orchestration
Detailed Elements to Capture
• The single Access database file as a shared resource.
• Reporting modules as a subcomponent of the Business Logic layer.
• Batch files as entry/exit points.