The past week has been full of documentation and this week we’re going to do even more. During class we reviewed documentation of our peers and gave each other feedback, I was able to give feedback for Paul and Victor’s feature and technical specification documents and was able to receive feedback for my own feature and technical specification documents. This was done by sharing the document and commenting on parts of the document that we liked or thought needed some more work done. This helped me collect some very valuable and iterable feedback from other people and helped me improve my documents.
Specifically, after reading Victor’s technical design document, I realised that my own technical design document needed work. Victor had laid out each object with three distinct sections: requirements, details and scripts, this allowed me to clearly identify the each section of information that was being communicated by the document. I decided to apply this format and idea to my own technical design document which previously had headings for each object but just information in no particular order splurged through the sections.
In addition to this we explored creating an art bible using some example games such as Limbo, Badland and Hearthstone. Art bible are important because it allows you to set artistic rules for your game and therefore will bring some visual consistency to your game. They also explain why your game looks the way it does and helps third parties in understanding and creating assets for your game.
Leave a comment