Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Umple Case Study : Second-Hand Car Sale Website #995

Closed
Jaorji opened this issue Feb 13, 2017 · 6 comments
Closed

Umple Case Study : Second-Hand Car Sale Website #995

Jaorji opened this issue Feb 13, 2017 · 6 comments
Assignees
Labels
examples Related to examples in UmpleOnline or the user manual Priority-VLow This is likely a cosmetic issue or a long-range low-impact wishlist item

Comments

@Jaorji
Copy link
Contributor

Jaorji commented Feb 13, 2017

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.

@Nava2
Copy link
Contributor

Nava2 commented Feb 13, 2017

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!

@Jaorji
Copy link
Contributor Author

Jaorji commented Feb 13, 2017

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

@Jaorji Jaorji self-assigned this Feb 13, 2017
@Nava2
Copy link
Contributor

Nava2 commented Feb 13, 2017

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.

@vahdat-ab
Copy link
Member

I agree with @Nava2 but I let @Jaorji decide about it. Developing with Spark and SQLITE will be easier than others.

@TimLethbridge
Copy link
Member

This is a suggestion for an Umple Example that is more than just a simple model. As such it would be better to create a separate github repo for it, and when done make a link to it here, then close this issue. If I see nothing happen by mid-2018 this issue should be closed.

@TimLethbridge TimLethbridge added examples Related to examples in UmpleOnline or the user manual Priority-VLow This is likely a cosmetic issue or a long-range low-impact wishlist item labels Nov 20, 2017
@TimLethbridge
Copy link
Member

This was not done by the proposer. Closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
examples Related to examples in UmpleOnline or the user manual Priority-VLow This is likely a cosmetic issue or a long-range low-impact wishlist item
Projects
None yet
Development

No branches or pull requests

4 participants