I am terribly sorry if this sounds a little ‘off topic’. 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?
I am terribly sorry if this sounds a little ‘off topic’. 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 [/quote]
Hi,
I am new in modeling and actualy I finishing university. But maybe my answer will help you. With my knowledge I know that ERD (Entity Ralationship diagram) what you use to design database (structure of tables) and class diagram are two diferent diagrams. In class diagram you describe classes in your system which got object (one or many). These classes haven’t got to work with your database and they also don’t have to be your entity.
For example class could be a Form that will be showen to give or take information from user. Or it could calculate something.
Lukas
PS: If I am wrong please let me know… I will be glad to learn something new
