What methodogies should i consider for making a game?

Question

Im at the begining of making a game. I was wondering what design methodoligies i should use for constructing the game. The game will be in the form of a classic arcade stlye shoot-em up.

Answer 1

In my workplace, we have identified five general methodologies; the waterfall, the v-shaped, the prototyping, the incremental and the spiral development patterns.
For you, I would suggest doing the incremental (iterative) or the spiral pattern. What they have in common is that you start with a very basic, very rudimentary working system and add increasingly sophisticated functionality.
Incremental (iterative) makes you add components. For example, a graphics framework, then sound code, then the ability to save games and so on. Presumably other components include support for joysticks and gamepads.
Spiral on the other hand has you make a complete, rudimentary package from the start and you consider the risks involved in adding the next layer of sophistication. "Is it worth swapping out my sprite based 2D graphics system for a 3D model-based system?"
But keep in mind that "design methodologies" are really nothing more than a way for you to organize your work such that you can offer a reasonable accurate schedule and a cost for implementing the project. For example, you could say it would take you about X number of days to switch from 2D to 3D and you can then determine if your game is going to be that much better for the work you put in.
However, I suspect you're really done this for the fun of it, you just want to dabble in Java and have a bit of fun with it. In which case, I would not bother with a design method any more elaborate than a program logic flowchart and a crude schedule of what to code first.
Hint: threads containing rudimentary controls and a basic 2D graphics framework that can move an image around the screen are probably the first thing you should code.