When we design a MIS Application,which is right?
1.Design the database table first,then design the data object
2.Design the data object according to business logic,then use some O/R Mapping tools to generate the databse table
3.design the databse table and data object in the same time

I'm not MIS, more back-end web dev and this is just personal experience, but:
data object first. If your a back-end guy you want your code working in a simple form, then want to build it out.
front end can request change of database, you just want your code working as the first step before you waste a heap of time therefore you "stub out" your code (including the dataobject) then flesh it out, make the database, complete everything. It's a personal opinion, but there you go.

In my opinion, Hibernate should be used where the database is normalized
 and proper indexing is in place, so as to use really interesting
functions of Hibernate.

Thanks,

http://question2answer.googlepages.com/

:)

There are three model to develop a Hibernate application listed by "Hibernate in Action":
[1] Top down
?) Start with an existing business logic, its implementation in Java.
?) Create mapping metadata (in xml files, etc.)
?) We can let Hibernate's "hbm2ddl" to generate the db schema.

[2] Bottom up
?) begin with an existing db schema and data model.
?) Use the reverse_engineering tools to generate XML mapping files.
with "hbm2hbmxml" for example. With "hbm2java", a skeleton fro a Java persistence layer is generated.
?) Expected some manually work.

[3] Middle out -- recommend only for seasoned Hibernate expert
?) Begin with handwritten Hibernate XML mapping files.
?) Then generate the db schema with "hbm2ddl" and Java classes with "hbm2java". The Hibernate XML mapping files are constantly updated during the development, and other artifacts are generated from this master definition.

[4] Meet in the middle -- the most difficult scenario
?) Combining existing Java classes and existing db schema.

A beginner to hibernate, hope can help a bit.