for small games, game design isn''t probably even necessary. you can just think of how to do it, and then do it

with game designs though, one important thing is that you can''t reach your goal before you know what it is.. what i''m saying is that the more clear picture you have about what you''re trying to accomplish, more likely you''re going to get there. but if you''re goal is a little bit fuzzy and you''re not absolutely sure of what direction you should be heading to, then it''s likely that you get lost on the way..

it''s not important to do the design exactly by the book. u know, your goal is not even to make a perfect design. your main goal is to get the game finished and working, and when you''re doing the program design your goal is to get the program working.. so think about things that you need to describe in order to make that happen.

I'm doing a Bsc In S/W Engineering and I've used a number of development methodoligies. Now I'm not saying use SSADM, as that wount help much with game development, but I have found some stuff like flow charts useful. Also make sure your data structures are solid. Also if you are using OO well designed classes will prcactically write the program itself (not litrally, I'm affraid I've yet to find the OO gnomes who appear in the middle of the night and write the code for me ). Also I know that you said that you didn't want to use any high level documentation as you projects are too small but it's a whole lot easier to learn how to use tools like flowcharts and stuff properly on smaller programms than with huge programms also it gets you into the habbit of doing it, and gives you chance to create your own 'flavor' of the methodology.

Sorry if that was a little to long winded.

Edited by - Mr_Black on 1/28/00 5:58:14 AM