First of all you should determine if it is at all necessary to architecture your project following OOP principles. From my experience almost all projects complexer than a hitcounter could use some form of OOP.
But since you are having trouble understanding how to properly implement OOP principles in your project i'm inclined to think your problem isn't technical in nature but more organizational.
Do you have a clear view on your project or a written brief/spec? What components are there? What data entities? Are databases involved? Do you need to communicate with external webservices? Over soap or rest? Are your going the MVC way?
The answer to all these questions and alot more will make you think of your project from a higher point of view, from there on work down and you'll easily start seeing how you can implement OOP in your project.
It will take some practice and you will make mistakes and decisions you will regret later but that's all part of the learning process.
Do a search on SO for OOP books and you'll find a treasure of information on all things OOP. Clicketyclick: https://stackoverflow.com/search?q=object+oriented+programming+books
text