Printable View
I am not sure what to do here, maybe someone can direct me to or help out. I am creating a game and adding a gui interface to it as a lab project for school. My lab instructor has emailed and asked for a "1 page object oriented design" to be turned in to her showing what we're doing.
I have no idea what that means. I am happy to do the work myself, but I don't even know what this is asking me for. I'd ask her myself, but I never get a response *sigh*.
Thanks all.
Word to the wise- don't waste time complaining about your instructor. Many people here are self taught, without the help of instructors, schools, classmates, or even these forums.
But I think you're making it more complicated than it should be. What classes are you planning on writing? What does each class do? How do they fit together?
Don't worry, I'm really not interested in complaining about my instructor, I only put that in to avoid any possible "ask your teacher what she wants" responses. Are you saying that it's just more or less a UML diagram?
If my professor asked for a 1-page design, I'd probably explain in text what I was trying to do, with small pictures here and there to demonstrate what I meant. Maybe you could ask some of your fellow students what they're doing for it?Quote:
Originally Posted by Herah
Ask yourself a few questions first:
1) What classes/objects do you plan to create for this program's structure? What will be each object's uses?
2) Will there be inheritance involved? If so, you can draw up an inheritance tree with object details to show as a polymorphic structure.
3) What relates to what? Related objects should be kept in individual packages to maintain organization and avoid naming issues. This also allows for tight object to object communication, which is all a true object-oriented program is: objects talking to each other.
Thanks guys, I went with the UML diagram I had already made for the project and added a gui class to it. Should be good enough for now :)
Sounds great there. normally a design is just like a blueprint of your entire project. #Classes, #Members, #methods and relationships between classes. Of course there are classes that have nothing to do with each other but as they said, it depends on what you want to achieve. Hope you made it.