Now, I'm not saying that it's bad to make a plan, or anything, but the whole software engineeering mentality just pushes things WAY too far. Following some premade design methodology when it doesn't fit the project is really stupid. Fine, so choose one of the other premade methodologies then. But wait, what if… BUM BUM BUM! …they're all wrong for your needs? Do it your own way? Hell no! That wouldn't be acceptable. That wouldn't be "software engineering."
ps: I just got home from a midterm in my software engineering class, so you can see how I might be extra hatey at the moment. The midterm was stupidly easy. I don't regret sitting in the back with my laptop all the time, not paying attention.
You will find as you develop larger projects that the various Software Engineering methods are very useful. You will also find that its pretty much impossible to NOT use one.
Just make the program and tell them you used the prototyping method.Back on topic here, I know what you mean. When classes ask you to design your tiny ltttle programs fifrst, before you code them…Argh…
My highschool programming class was mostly just pseudo code, but that was still incredibly annoying. XDJust plan your stuff out and go, thats what I do.