Using game days to teach a multiagent system class

Leen Kiat Soh

Research output: Chapter in Book/Report/Conference proceedingConference contribution

9 Scopus citations

Abstract

Multiagent systems is an attractive problem solving approach that is becoming ever more feasible and popular in today's world. It combines artificial intelligence (AI) and distributed problem solving to allow designers (programmers and engineers alike) to solve problems otherwise deemed awkward in traditional approaches that are less flexible and centralized. In the Fall semester of 2002,1 introduced a new game-based technique to my Multiagent Systems class. The class was aimed for seniors (with special permission) and graduate students in Computer Science, covering some breadth and depth of issues in multiagent systems. One of the requirements was participation in four Game Days. On each Game Day, student teams competed against each other in games related to issues such as auction, task allocation, coalition formation, and negotiation. This article documents my designs of and lessons learned from these Game Days. The Game Days were very successful. Through role-playing, the students were motivated and learned about multiagent systems.

Original languageEnglish (US)
Title of host publicationSIGCSE Bulletin (Association for Computing Machinery, Special Interest Group on Computer Science Education)
Pages219-223
Number of pages5
Volume36
Edition1
DOIs
StatePublished - Mar 2004
Event35th SIGCSE Technical Symposium on Computer Science Education - Norfolk, VA, United States
Duration: Mar 3 2004Mar 7 2004

Other

Other35th SIGCSE Technical Symposium on Computer Science Education
Country/TerritoryUnited States
CityNorfolk, VA
Period3/3/043/7/04

Keywords

  • Active Learning
  • Game Days
  • Game-based Learning
  • Multiagent Systems

ASJC Scopus subject areas

  • Hardware and Architecture
  • Software
  • Food Science

Fingerprint

Dive into the research topics of 'Using game days to teach a multiagent system class'. Together they form a unique fingerprint.

Cite this