Repository navigation
Home
Morning:
Daniel gets into his car and notices the fuel gauge is low. “Didn’t I just fill up last week?” he wonders. He can’t remember how much he spent or how long his last tank lasted. “It would be nice to track my fuel costs,” he thinks.
Late Morning:
While driving to work, Daniel hears a strange noise from the engine. “When was the last time I got an oil change?” he asks himself. He flips through old receipts in the glovebox but can’t find the answer.
Lunch:
At lunch, Daniel talks to a friend about car expenses. “I track my maintenance schedule,” his friend says. “It helps me avoid unexpected repairs.” Daniel realizes that his car is due for a tire rotation soon but has no system to remind him.
Afternoon:
Later in the day, Daniel receives a notification from his insurance company about renewal. “I should probably check if my last inspection is still valid,” he thinks, unsure of when he last had it done.
Evening:
As Daniel winds down for the day, he thinks about how much he relies on his car but feels unprepared when it comes to maintenance and expenses. “If I had a tool to log fuel usage, track service dates, and remind me about maintenance, I’d feel more in control,” he resolves.
A user is able to log fuel usage, track service dates, and receive reminders about service dates
-
UC1: A user can log their fuel usage
-
UC2: A user can view fuel usage
-
UC3: A user can log a service event
-
UC4: A user can view service history
-
UC5: A user can schedule a service reminder
-
UC6: A user can view their reminder history
-
UC7: A user can receive a service reminder
- NFR1: Should be easy to use
- NFR2: Should be fast to use
- C1: Project will be built in dotnet 8
- C2: Project will use a console UI