UML Diagrams are a lot more important then you would think. Sure you can go out and make the game then reverse engineer them but you will run into problems along the way.

The goal for us when we create UML diagrams is to plan out how the code is going to work and interact so we can find some of the problems before they occur. And hell it only takes a week or two. (maybe shorter if your only making a small game)

At first I despised them, then I used them in a project and they made everything so much easier. If you get used to making them then you will love yourself for it because you will start using them as your suedo code.

Thats cool it really does make since that it would just improve the organization of your code. What program do you use? We are using Visual Paradigm 6, the teacher said that he used to use Rational Rose but that there is a bug in one of the features he likes to use in class.

__________________
Grant Shonkwiler()
"I would love to fix the world if someone would just give me the source code" WebsiteIndustry blogLinkedIn

I do believe that the standard is Microsoft Visio Studio. (sorry if I didn't spell the program correctly) It's whole purpose is to create UML diagrams of al shapes and sizes. It has classes and connectors built in. Though there is a slight difference between what you are taught and what is in the program. Thats the problem with UML diagram Software. The people who write the software are not the ones who created the UML language. Thus there are some minor errors. Mostly like dependencies being solid lines and references being dashed lines with a white arrow. ect All the classes and boxes are correct though.

I do find UML to be extremely useful in planning the design of a system although I rarely use anything more then class diagrams. Since it is universal 'language', any other programmer should be able to look at the diagram and also understand the design.

Personally I find Visio to be too heavy handed and I use UMLet instead which is much quicker to prototype designs.