Quote:
Original post by kingIZZZY
This question most probably relates to chapter 6-11 thread, but ill post here cuz it also concerns this project.
Im having a hard time learning and remembering the steps of Object Oriented analysis/design. Since i am currently not really planning out for myself some big project, whatever i read in chapter 11 sounds all the same in all phases: "Just get it straight what is this thing in the real world, and how do we need it to interact with users, and make it that way". whatever, I just cant get chapter 11 in my head.
Therefore, if finnishing the analysis phase is part of project 1, then im in trouble. And, uh, if OO Analysis/Design is part of being a C++ programmer (duh), then im in REAL trouble...
Any suggestions?
I know what you mean. I've done a few games in c++ and OO design never really made sense to me. All 4 of my games were done procedurally. I tried this exercise to work on my design and it was like BOOM! everything about OO started to click.
My advice is to not get wrapped up in making sure everything is OO. Use OO when it helps you, and if it's becoming a hindrance, don't use it. After using the language for a while it will begin to make more sense.
The important thing is to never let any one thing about coding keep you from doing it. It's better to write bad code that you understand then to sit on your hands until your design is flawless. The more you code the more your design will improve and the more you will understand things that you don't get right away.