Anyway here it goes: which book(s) would you recommend me to improve my
knowledge of the OO modelling and design? This book has to help me write
a code which will not turn into a mess after few years

Responding to Jovic...

Anyway here it goes: which book(s) would you recommend me to improve
my knowledge of the OO modelling and design? This book has to help me
write a code which will not turn into a mess after few years :)

See the "Books" category of my blog.

Large Scale C++ Software Design - I was looking for something like this,
but you said that this book is little dated.

The list of books I am considering is:
http://www.amazon.de/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882/ref=sr_1_1?ie=UTF8&s=books-intl-de&qid=1253178002&sr=8-1

http://www.amazon.de/Large-Scale-Software-Addison-Wesley-Professional-Computing/dp/0201633620/ref=sr_1_1?ie=UTF8&s=books-intl-de&qid=1253178053&sr=8-1

http://www.amazon.de/Pragmatic-Programmer-Journeyman-Master/dp/020161622X/ref=pd_sim_eb_5_img

http://www.amazon.de/Refactoring-Patterns-Joshua-Kerievsky/dp/0321213351/ref=pd_ys_home_shvl?ie=UTF8&coliid=I2I92K7J7E26ZK&colid=34F3YXYHZ5QMY

http://www.amazon.de/Driven-Development-Example-Addison-Wesley-Signature/dp/0321146530/ref=sr_1_1?ie=UTF8&s=books-intl-de&qid=1253178335&sr=1-1

http://www.amazon.de/Working-Effectively-Legacy-Robert-Martin/dp/0131177052/ref=pd_bxgy_eb_img_b

http://www.amazon.de/xUnit-Test-Patterns-Refactoring-Signature/dp/0131495054/ref=sr_1_1?ie=UTF8&s=books-intl-de&qid=1253178355&sr=1-1

Responding to Jovic...

Large Scale C++ Software Design - I was looking for something like
this, but you said that this book is little dated.

The OOP-based Agile movement has since institutionalized the idea of
refactoring working code to make it more maintainable. So books like
Fowler's "Refactoring" will have more up-to-date techniques. But the
basic ideas that Lakos presents are still quite valid and he has one of
the better discussions of what coupling is about. He is also one of the
few authors I've seen who provides hard data on what the potential costs
of dependency management are.

Bear in mind that Lakos is not primarily focused on OOA/D per se. He is
primarily focused on tactical design in C++ to get around physical
coupling problems in the 3GLs. Most of his examples start with a basic
design and then discuss how to make it more maintainable in C++. So he
doesn't spend a lot of time one how one got the initial design in the
first place. IOW, don't expect a lot of discussion about things like
problem space abstraction because it is a very code-focused book.

Can you recommend me a book that discuss how to do a proper initial A/D
of a large system?

xUnit Test Patterns is sort of required reading if you want to have a
conversation with a TDD junkie, otherwise they'll start shouting
buzzwords and jargon at you that will make you feel stupid. Plus, the
jargon used is actually fairly nice. The only downside to this book
is it doesn't explain how to avoid writing certain tests, or simply
fewer tests, via simply doing better design.

Large Scale C++ Software Design is probably the best book in the
bunch.

If you want a good book on modeling in general, more general than just
OO, and more math-based, I recommend Software Abstractions by Daniel
Jackson of MIT.