disadvantages of using an ERD instead of a class diagram when using Object Oriented Programing

Question

hello everyone can someone pls help me on this one?i need to know what are the disadvantages
of using an Entity Relationship Diagram instead of a class diagram when using OOP? thanks everyone.

Answer 1

Accept the post as Answer, if resolved !

Answer 2

How come my post got accepted as Answer?

Answer 3

thanks again Vulpes,your great.

Answer 4

Wikipedia have a decent article on ERDs (http://en.wikipedia.org/wiki/Entity-relationship_model).

Also, whilst it's a bit rambling at times, I found this link (http://members3.jcom.home.ne.jp/daruma_kyo/en/aboutooa/classD_ERD_classExtraction.html) which brings out the differences between class diagrams and ERDs.

Answer 5

thanks vulpes you are great,i wonder if you could suggest were i could read further on this.thanks

Answer 6

Entity Relationship Diagrams are more limited in scope than class diagrams. If you were trying to use them as an alternative to the latter, then:

1. They wouldn't deal with how your classes interacted with each other.

2. They wouldn't deal with how the data in your classes could be manipulated.

For these reasons, ERDs are usually confined to modelling relational databases rather than whole applications.