Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
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)
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.)