You need to know what business rules your database design is supposed to satisfy. The aim of normalization is to help ensure that the business rules (i.e. the set of dependencies you wish to implement) are properly supported by the keys and other integrity constraints in your data model.
Write down the set of functional dependencies before you start and use that as the basis of your normalization exercise.