I am also new to Hibernate and this tutorial helped me. I also agree with above comment(MetaZone)

Can you please comment on this?

Here are my steps:
Define your object model and its relationships — inheritance, associations and parent/child with their cardinality (1-M, 1-1, etc.) and their direction (bi, uni).
Identify those domain model objects that need to be persisted in a database and implement the database tables using the standard ways objects and their different relationships are mapped to db tables
Define the hibernate mapping files for mapping the domain model to the database tables.
Define your DAO classes with methods for saving, deleting, getting. updating the domain model objects; the methods will use hibernate in their implementation.

The first 2 steps are independent of Hibernate (however, by reading hibernate documentation, it can greatly help with the understanding of defining your object model and then what the standard ways are to map an object model to a database).

An important part of this is to make sure that you understand what the domain model is and what the other objects in your application are. The domain object model is the common ‘vocabulary’ between the non-domain model objects that are used by other layers — e.g. when the GUI calls a method on a business logic object, the parameters and return values of the business logic method are domain model objects; if that business logic class needs to call a DAO class, the parameters and return values of the DAO class are domain model objects. Therefore, the main dependency between layers is the domain model; each layer is responsible for any mapping from and to the domain model objects. Implicit in this is that you’re developing a layered architecture where your non-domain model objects are categorized into layers of abstraction that only provide the functionality that the layer specifies (e.g. the DAO layer classes only perform database access; they have no business logic, no logic to access external systems, etc.)