OK... Now I think I know what the Problem is!
Powdir, or anyone who is reading.
I think my problem with OOP is not the code or design, rather than the approach to the problem. For example the lab I posted earlier. Can anyone describe the thought process as to which objects will be needed, what will be a child object, why we need a base classs ...etc...
I have searched for an article or something to describe the reasoning when learning how to approach OOD and I have found nothing more than definitions of Classes, Methods, Blah, Blah, Blah.
Any comments would be greatly appreciated.
SHOOK
1 Attachment(s)
Well ... I get most of it.
Here it is boys and girls.
Between readon the useless info on the net and my class, along with the information provided on this forum I have finally have a grasp on this whole OOP concept.
However, I am still trying to finish my assignment. I think I have created the classes correctly. I have tried to create everything according to the UML diagramm, but I am not certain how to create the Paragraph Class or the Document Class, I think I have to use Arraylists but I am not sure how the methods within the Classes.
I am not too worried about the Main Module apart from how to use the Document and the Paragraph Class
I have attached the following files:
-The Lab Description (Diagram Included)
-My prof's demo, that is not complete
-My program up to date.
If someone could take a look and let me know If I am going in the right direction, or offer some advice it would be greatly appreciated.
Thanks All.
Shook
:confused: