Car Service Record Management System
Requirements
Based on the functionality that we have discussed in the system introduction and the use cases, we will be setting our requirements. Although the project's focus is only on websites, in the future we might broaden it to include desktop and mobile applications. The functional and nonfunctional requirements for this web application are defined below.
Functional Requirements
FR-1: The system should be able to allow general users, admins, car insurance companies, workshops, and car manufacturer companies to login and sign up.
FR-2: General users should be able to update their personal information.
FR-3: General users should be able to request car information using the car registration number and owner details.
FR-4: General users should be able to accept or reject any request made to their profile, either for car information or personal information, from general users or car insurance companies.
FR-5: The system should allow workshops to create, update, or delete maintenance records created by them.
FR-6: The system should be able to provide car manufacturers with all the car service records related to their brand and model.
FR-7: The system should be able to generate a PDF of the report so that it can be viewed offline.
FR-8: Admins should have the ability to register, authorize, or revoke the access of any kind of user.
FR-9: The system should be able to notify users about the upcoming service date of their cars.
FR-10: The system should allow insurance companies to request a general user for all their car and personal information.
Non-Functional Requirements
NFR-1: The system must be scalable in order to support an expanding user base.
NFR-2: Multiple users looking for information about the same car should be supported by the system.
NFR-3: Different browsers should be able to access the website.
NFR-4: To enable quick access, the system should store the data in the cloud.
NFR-5: To provide a quick website load time, numerous servers spread across various locations are required.
NFR-6: To ensure that no data is lost, there should be a data backup.
NFR-7: The appropriate actions should be taken to guarantee the security of data servers.
NFR-8: Each page of a website should load in under two seconds.
NFR-9: The website should be accessible 99.9% of the time.
Stakeholder Analysis
| Stakeholders | User Characteristics |
|---|---|
| User(Car Buyer) | Background
: familiar with mobile and web-based applications; familiar with computers and smartphones Expectations : Users can see the details of the car he/she wants to buy, like its history of maintenance, owner history, and all the records that are associated with that car. Preferences: The user should be able to use the system on desktop and be able to enter the details of the system from a keyboard. The website can also be run on mobile so that users can use it on their mobiles. They can see all the details and history associated with the car they have searched for. They can download the pdf of the report so that it can be viewed offline and the user can compare the report with what they got from the owner. |
| Insurance companies | Background :
comfortable with both mobile and web-based applications, and conversant with computers and smartphones. Expectations: Companies can see the details of the car like the maintenance history, how many parts are duplicated, and all the other details that can help the company get the right amount of insurance premium that they can charge the user. Preferences : They should be able to use the system on desktop and be able to enter the details of a car from a keyboard. The website can also be run on mobile so that users can use it using their mobile. They can see all the details of the car that they searched for and also in good format, so it is easy to read. They can extract and download the data in such a format that it is easy for the analyst to analyse the insurance premium they can charge. |
| Repair shops | Background :
comfortable with both mobile and web-based applications and is conversant with computers and smartphones. Expectations : The repair shop owner can see the data associated with that car and also update the data of the car by using the system so that the data is correct. Preferences : They should be able to use the system on a desktop and be able to enter the details of a car from a keyboard. The website can also be run on mobile so that users can use it on the go. can see the data associated with the car and also update the data with what they have repaired or changed with ease. |
| Automobile Manufaturing Companies | Background :
comfortable with both mobile and web-based applications and being conversant with computers and smartphones. Expectations : Automobile manufacturing employees should be able to enter the information about a car model and then be able to see the details regarding the parts that are being worn out the most. Preferences : They should be able to use the system on desktop and can enter the details of a car from a keyboard. The website should also be able to run on mobile so that they can use it while on the go. can see the data associated with the car of a particular model in order to get the details about its parts. |