Hi all, If we take the segment table in the db , it should also have the seat id column. What I am thinking is,for each seat id for a segment, it will have a different row in segment table but I am not sure if it will be the best design. Any comments? Thanks, Murat
Are you talking about DB design matching the Class structure? In my opinion, segment repeating in the DB for each seat is not a good idea. In class design you can have a collection holding the seat reference and DB has a seperate table with seats and their segment Ids. This is what how I was thinking.
a better way to solve this problem is to model this in OBJECTS. remember you are going to be evaluated in how you resolve and design the domain model in class diagrams (objects not tables) .... 44 points ....
... Object-oriented document editors typically use objects to represent embedded elements like tables and figures. However, they stop short of using an object for each character in the document, even though doing so would promote flexibility at the finest levels in the application.
William Butler Yeats: All life is a preparation for something that probably will never happen. Unless you make it happen.
Thanks for your answers. I fully aggree with you. But I am considering to use Entity beans which directly corresponds to tables. (Am I wrong?) Ofcourse,my high level class diagram will not include those entities but I was wondering how will it look like in a detailed class diagram. Thanks again, Murat
Won't you please? Please won't you be my neighbor? - Fred Rogers. Tiny ad:
a bit of art, as a gift, that will fit in a stocking