Published June 27, 2008 | Version 9892

A Classification Scheme for Game Input and Output

Authors/Creators

Description

Computer game industry has experienced exponential growth in recent years. A game is a recreational activity involving one or more players. Game input is information such as data, commands, etc., which is passed to the game system at run time from an external source. Conversely, game outputs are information which are generated by the game system and passed to an external target, but which is not used internally by the game. This paper identifies a new classification scheme for game input and output, which is based on player-s input and output. Using this, relationship table for game input classifier and output classifier is developed.

Files

9892.pdf

Files (221.6 kB)

Name Size
md5:0c49515112def5a7698afe16d4d7e599
221.6 kB Preview Download

Additional details

References

  • K. Claypool, M. Claypool, "Teaching Software Engineering Through Game Design", Proceedings of the 10th annual SIGCSE conference on innovation and technology in computer science education, 2005, Vol.37(3), pp. 123-127.
  • http://en.wikipedia.org/wiki/Portal:Sports_and_games
  • C. Crawford, The Art of Computer Game Design, Columbus: McGraw- Hill, 1984.
  • D. Johnson, and J. Wiles, "Computer Games with Intelligence", The 10th IEEE International Conference on Fuzzy Systems, 2001, Volume 3, pp. 1355-1358.
  • http://en.wikipedia.org/wiki/Game
  • M. Shaw, "An Input-Output Model for Interactive Systems", Proceedings of the SIGCHI conference on Human factors in computing systems, (CHI -86), ACM Press, New York, 1986, pp. 261-273.
  • P. Dickinson, Instant Replay: Building a Game Engine with Reproducible Behavior. http://www.gamasutra.com/features/20010713/dickinson_01.htm
  • H. Jiang, G. Drew Kessler, J. Nonnemaker, "DEMIS: A Dynamic Event Model for Interactive Systems", VRST-02, ACM, 2002.
  • A. M. Memon, "GUI Testing: Pitfalls and Process", Computer, 2002, Volume 35, Issue 8, pp. 87-88. [10] Lakos, J., Large-Scale C++ Software Design, Addison-Wesley, 1996. [11] S. Jungmayr, "Identifying Test-Critical Dependencies", In Proceedings of the International Conference on Software Maintenance, IEEE Computer Society, October 2002, pp- 404-413.