• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Sequence diagrams, Class diagrams and Database tables.

 
Varnam Aayiram
Ranch Hand
Posts: 88
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Folks...

A use case diagram has been designed. Based on the design and the problem scenario, some classes/objects have been identified. A sequence diagram is than designed, which helps in uncovering even more classes.

Now we come up with a class diagram which contains all the classes identified. We are now read to design our tables for the database. This is my question, is it a must for every single class/object identified to be converted to a table in the database?

regards
JavaLover2008
 
Paul Sturrock
Bartender
Posts: 10336
Eclipse IDE Hibernate Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
"ILove Java" please check your private messages.
 
Javid Jamae
Author
Ranch Hand
Posts: 198
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Most ORM tools provide some way of mapping more than one object to a single table (components or embedding) and one object to more than one table (joining).
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic