If I create a conceptual class diagram such that each class captures \'name\' and \'attributes\' but not \'operations\', have I not basically created what would be otherwise
IMO In Simple terms
Class diagram depicts the details of how will the system work.
ER diagram depicts how the system persists 'state' as a blue print.
Goal: Detail out state and behavior of the components(classes) of the system. Design 'efficient', flexile system(less coupling and more cohesion) using Solid principles.
Goal: Design a blue print of how to 'efficiently' persist the state of the system. Consider what kind of queries will be made (read vs write), are there any joins required consequently figure out the columns for indexing Use Normalization, ACID properties.
PS: notice the both the diagram tries to efficiently do thing in their on respect.