Car Service Record Management System
Background
On average, over 6 million passenger car accidents occur in the United States each year, and in
the United States, there are around 239,100 auto repair and maintenance facilities. The data
shows us that consumers in the United States spent a total of 194.9 billion dollars on services
for their motor vehicles in 2021. This data is maintained by numerous third-party vendors and
insurance firms, which may result in inaccurate or fragmented data. Therefore, a central system
All the data that can be readily maintained is required. Our plan is to create a system that
keeps track of auto maintenance, which will be helpful when buying or selling a certain car to
learn more about it and its condition. This technology will assist in keeping track of data
regarding used or accident-damaged vehicles. The idea of this project originated when one of
our teammates had to solve this problem during an interview for a full-time software engineer
Role.
We believe that the issues raised in the real-world scenario will be addressed by this project.
Additionally, we think that there aren't any trustworthy mechanisms in place for keeping track
of car maintenance records, which could affect both the price of a car overall and potential
Buyers.
Without the appropriate architecture, the system is a little too complex to handle, and as more
work proceeds, the complexity will only grow, making it more challenging to add new features,
make adjustments, and optimize the code. The system's performance, scalability, usability, and
manageability will all be directly impacted by the architecture, which will help define the
system's overall integrity. We also need our system to have module-to-module interaction, data
abstraction, and some additional functionality, and in order to do so, it is very important for us
to pick the right architectural style.
(Figure 1) Car Workshop