I am working on a new personal project, a webapp to show info on airlines, airplanes and their manufacturers.
Use cases are pretty obvious:
- search for airlines by place of origin
- search for aircrafts
- search for the fleet of a specific airline
I made a EER diagram of the database and i would love some feedback. I'd like to add that this is something i make myself (kind of a portfolio project, am unemployed right now) so i try to keep it quite 'simple'.
The correct name of the diagram is Entity-Relationship and the correct acronym is 'ER'.
Aside, the airlines ER diagram problem is a common assignment in either undergraduate or graudate database courses. I had this assignment at the gradudate level many moons ago... you might want to change the subject to something not so common, just a suggestion.
Joined: Jan 29, 2009
Duly noted ;-) I'll keep it in mind.
And I never went to grad school, so i wouldn't know about it. Although you do make a good point. But the thing is, if i change the subject, i do risk having a lot of trouble finding data. And I don't have the time to gather lots of content like that. Implementation will already take up a lot of time (Spring, Hibernate etc).
thanks for the input though
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com