DSDM is falls under the "new" agile development methods.
As well as SCRUM, there's eXtreme Programming and RUP.
Unfortunately, all these design methods assume you're conversing with a customer. You update them on your progress and they play an active part in the project's direction. That really isn't for you.
I believe the idea behind RUP/UP is that you identify modules, design and build them then when you've finished, compare the finished module to the original requirements. It's likely (especially in your situation) that the requirements will have changed by the time you finish developing a module, so you update all your design documents, analyses and then go back into implementation. These are called iterative design methods, for obvious reasons.
Hopefully, the subsequent iterations don't require you to scrap the code. It needs to be modular such that you can then move onto the next chunk without your design choices from other modules having any great effect.
What'll really score you some marks is to mention
MoSCoW timeboxing. You could carry out the iterations 4 or 5 times to get the module perfected. However, you'd have overrun by about 6 months. Set yourself a very strict time period in which to finish the iterative process for a particular module, say 2 weeks. If it isn't finished, roll back to your previous iteration and
move on. The idea being that you have *something*, which may or may not fit the requirements.
The MoSCoW part comes from prioritising the elements of the requirements analysis which are most important, down to "probably not going to make it in". If you finish a module early, then you can perhaps implement the more desirable, but not essential features.
Like you suggested, take applicable parts from all methodologies and use them to your advantage. Wikipedia is surprisingly helpful in describing all the Agile Methods.
[center]
iv tryed everything!!!!!!!!!! could u please just add The gun and shooting Code thats All!!!!!!!!!