As a part of my Software Engineering class, I will be maintaining a blog to discuss my discoveries and progress in this journey. Now as the rest of my website suggests, I have no long term intentions of being a software engineer for my career. However that doesn't mean there isn't tons to learn and improve on my way to becoming a Video Game Designer. This week we discussed the meaning of "requirements" in Software Engineering and how you can utilized the Agile method in order to figure out what your client needs, and what must be done to give them what they need. This week brought up quite a few parallels between Game Design and Software Engineering that I hadn't seen before and brought to light a few issues of my own that will improve my design abilities down the road.
I never knew how much design actually goes into Software Engineering. So much of the work goes on paper and schematics much the same way that in Game Design you don't just jump into building the game, you have to figure out all of the main concepts for the game, the story and everything else your game is going to require, assuming that it is your game. If you have a publisher and are making their game for them, then Software Engineering and Game Design become even more similar where you have to talk with your publisher to figure out what their requirements are. By far my biggest issue when it comes to the design process is diving too deep before scoping out the full breadth of what must be done. It is hard to resist digging into what software you'll use, exactly how each design piece will fit, etc. before you are grounded in the full extent of the project. This is something I really hope to practice this semester and hope it helps me be successful in my career.
0 Comments
|