The basic requirement for the case study project shows below:
Show the detail information of Second-hand car: the brand, the product year, the colour, the description, Used year and related dealer information, the number of appointment.Every car owns by a dealer and can have many appointments.
Show the dealer information: the company name, the company location, the company phone, the company e-mail address.Every dealer can own one to more cars and many appointments.
-Registration: The user need register to make an appointment with the dealer. So the user need use their first name, last name, e-mail address, contact number to register.
-Make an appointment: If the user wants to see the car in detail, he should make an appointment with the dealer.It should show the calendar and confirm the appointment information.After confirmation, the system should send an email to this user and related dealer.Every user can make an appointment with zero or more dealers.
For the class relation and UI side, I'll use umple to generate essential java code and use HTML5 to show the UI.
Will use Tomcat as the server and store MySQL database.
Might I suggest using something like Spark instead of Tomcat as it's much less effort to setup and use. Additionally, use plain old SQLITE instead of MySQL for the same reason, it's easy to work with.
If there's other reasons, feel free to ignore these comments. I just saw "proof of concept" and figured I'd offer suggestions!
Thanks for your suggestion.Just because I used Tomcat and MySQL before, so I'm familiar with it. But if you suggest that's much less effort .I'm happy to learn and try. @Nava2
Probably worth the investigation to ease setup for someone else! Plus both of these could easily be hosted somewhere like Heroku.
Definitely not my place to say one way or the other, let @vahdat-ab decide on that one.
I agree with @Nava2 but I let @Jaorji decide about it. Developing with Spark and SQLITE will be easier than others.