Where do I start designing when using O/R mapping? Objects or database tables?

Question

I'm starting a new database application and I wonder if it would be better to start the design at the objects (with UML) and build the database schema accordingly, or start at the design of the database (with ER) and create the objects accordingly.

What are the pros and cons of either approach?

(I dont think it matters but just in case: I'm planning to use Java and Hibernate)

Answer 1

Depends on whether your application is designed to meet user needs, or to meet the needs of developers.

Start with the user stories, and get the OOP Classes straight. And your users will love you.

Otherwise you end up with an application that turns users into data entry clerks. (You'll have lots of company.)