2012 17th International Conference on Computer Games (CGAMES) 2012
DOI: 10.1109/cgames.2012.6314556
|View full text |Cite
|
Sign up to set email alerts
|

Proposal of Game Design Document from software engineering requirements perspective

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
7
0
3

Year Published

2014
2014
2022
2022

Publication Types

Select...
3
2
1

Relationship

0
6

Authors

Journals

citations
Cited by 20 publications
(10 citation statements)
references
References 3 publications
0
7
0
3
Order By: Relevance
“…In industry, content and extent of a GDD depend on the project stage and intended audience (e.g. developers, investors), but usually contain a concise description of all objects present in the game (mechanics), the interactions with and between the objects (dynamics), how the game shall look and feel (aesthetics) as well as the experiences intended for the player, an overview of the story of the game, and a technical overview (assumptions and constraints) [12]. In the software lab, a GDD structure is provided as guideline to the students.…”
Section: The Requirements Gamementioning
confidence: 99%
“…In industry, content and extent of a GDD depend on the project stage and intended audience (e.g. developers, investors), but usually contain a concise description of all objects present in the game (mechanics), the interactions with and between the objects (dynamics), how the game shall look and feel (aesthetics) as well as the experiences intended for the player, an overview of the story of the game, and a technical overview (assumptions and constraints) [12]. In the software lab, a GDD structure is provided as guideline to the students.…”
Section: The Requirements Gamementioning
confidence: 99%
“…There are similar elements amongst the Ped-GDD and the current GDDs with differences in the wording with the meaning remained the same. For example, Goals in this Ped-GDD was referred to as objectives by [7], as a milestone by [9], challenge by [10], as illustrated in Table 1. Another example of Social engagement in Ped-GDD is referred to as enemies by [7,8], team size by [9], as illustrated in Table 1.…”
Section: Game Design Document (Gdd)mentioning
confidence: 99%
“…For example, Goals in this Ped-GDD was referred to as objectives by [7], as a milestone by [9], challenge by [10], as illustrated in Table 1. Another example of Social engagement in Ped-GDD is referred to as enemies by [7,8], team size by [9], as illustrated in Table 1.…”
Section: Game Design Document (Gdd)mentioning
confidence: 99%
“…A requirement approach [28], a design technique called a 'game jam' [29] and a deployment strategy are described [30]. A company transitioned from a "Laissezfaire" waterfall team to a simple and well-tuned Lean/Agile team by introducing agile and Kanban in [18].…”
Section: Rq2: What Spi Initiatives Are Used In Game Development? To Wmentioning
confidence: 99%
“…Some examples are described in this section. A Taxonomy and Visual Notation for Modeling Globally Distributed Requirements Engineering Projects helped the process [39] as there was a need for this in requirements engineering, whereas designing a video game with a proposed Game Design Document (GDD) [28] required experience and training. The lack of version control on this GDD was a deterrent to adopting this process improvement.…”
Section: Hybrid Adoption Factors Reuse Processes Such As the Use Of mentioning
confidence: 99%