Difference between revisions of "Game Design Document"
From Design Computation
Abel Maciel (talk | contribs) (Created page with "{{Video game industry}} A '''game design document''' (often abbreviated '''GDD''') is a highly descriptive living software design document of the vid...") |
Abel Maciel (talk | contribs) |
||
Line 1: | Line 1: | ||
+ | [[Category:Game Design]] | ||
+ | [[Category:Video Games]] | ||
+ | [[Category:Project Management]] | ||
+ | |||
{{Video game industry}} | {{Video game industry}} | ||
A '''game design document''' (often abbreviated '''GDD''') is a highly descriptive [[living document|living]] [[software design document]] of the [[video game design|design]] for a [[video game]].<ref name="ox240">[[#Oxland|Oxland 2004]], p. 240</ref><ref name="bs14">[[#BrSch|Brathwaite, Schreiber 2009]], p. 14</ref><ref>[[#Bates|Bates 2004]], p. 276.</ref><ref>[[#Bethke|Bethke 2003]], pp. 101–102</ref> A GDD is created and edited by the development team and it is primarily used in the [[video game industry]] to organize efforts within a development team. The document is created by the development team as result of collaboration between their [[Game designer|designers]], [[Game artist|artists]] and [[Game programmer|programmers]] as a guiding vision which is used throughout the [[video game development|game development]] process. When a game is commissioned by a game publisher to the development team, the document must be created by the development team and it is often attached to the agreement between publisher and developer; the developer has to adhere to the GDD during game development process. | A '''game design document''' (often abbreviated '''GDD''') is a highly descriptive [[living document|living]] [[software design document]] of the [[video game design|design]] for a [[video game]].<ref name="ox240">[[#Oxland|Oxland 2004]], p. 240</ref><ref name="bs14">[[#BrSch|Brathwaite, Schreiber 2009]], p. 14</ref><ref>[[#Bates|Bates 2004]], p. 276.</ref><ref>[[#Bethke|Bethke 2003]], pp. 101–102</ref> A GDD is created and edited by the development team and it is primarily used in the [[video game industry]] to organize efforts within a development team. The document is created by the development team as result of collaboration between their [[Game designer|designers]], [[Game artist|artists]] and [[Game programmer|programmers]] as a guiding vision which is used throughout the [[video game development|game development]] process. When a game is commissioned by a game publisher to the development team, the document must be created by the development team and it is often attached to the agreement between publisher and developer; the developer has to adhere to the GDD during game development process. |
Revision as of 20:12, 13 April 2020
A game design document (often abbreviated GDD) is a highly descriptive living software design document of the design for a video game.[1][2][3][4] A GDD is created and edited by the development team and it is primarily used in the video game industry to organize efforts within a development team. The document is created by the development team as result of collaboration between their designers, artists and programmers as a guiding vision which is used throughout the game development process. When a game is commissioned by a game publisher to the development team, the document must be created by the development team and it is often attached to the agreement between publisher and developer; the developer has to adhere to the GDD during game development process.- ↑ Oxland 2004, p. 240
- ↑ Brathwaite, Schreiber 2009, p. 14
- ↑ Bates 2004, p. 276.
- ↑ Bethke 2003, pp. 101–102