Software Engineering Process Game

From VitalWiki

Jump to: navigation, search

The game's slurl: http://slurl.com/secondlife/OHIO%20Outreach/173/190/34 or http://slurl.com/secondlife/OHIO%20Outreach/180/160/32

A machinema for the game is available at http://www.youtube.com/watch?v=kkkl3LucxTY.

The user guide for how to play the game is available at http://vital.cs.ohiou.edu/index.php/Software_Engineering_Process_Game_User_Guide.

Role-Playing Game for Software Engineers (RPG-SE) is a 3-D Multiplayer Online Software Engineering Process game based on the SimSE game (a 2-D single player game) from UC Irvine (http://www.ics.uci.edu/~emilyo/SimSE/). It aims to teach students the principles of the software engineering process (currently RPG-SE only supports waterfall model) by simulating the development of a moderately sized software project.

The player will serve as a software engineer, and collaborate with other players to develop a software system. In the game, the player manages the role, by giving him or her tasks such as “creating requirement”, “reviewing design”.

The goal of the game is to release the software to the customer as complete as possible and with as few errors as possible. After the release, the game will end by giving a team score between 0 and 100. Initially, the team will be given a fixed time units for the project. The software should be delivered by the schedule time, otherwise the team will lose 20% of their final score as the penalty.

To play the game, the player just needs to touch the icons in the monitor in front of him or her. During the game, every player can adjust his or her current tasks by touching the “artifact” icon and touching the “task” icon under that artifact. The player can also take a break or go back to work by touching the "rest state" icon. The player’s energy is shown in the “energy” pie chart.

The player can monitor the progress of the project by examining "artifact progress" for four artifacts (shown as progress bar), "artifact errors" for four artifacts (shown as four digits) for each artifact, and “integration progress” (shown as progress bar) for the whole project. The player can also know the status of the other players through the status board above the monitor.

To get the good result, the player has to choose the task according to his or her role’s ability and follows the software developing process rules (e.g. design before coding, or always test everything). Therefore the player can learn the principles of software development processes unconsciously through playing the game. Since the game is multi-player online, it also requires the collaboration skills among the team.

If you have any questions about RPG-SE, please IM Yearn Au.

Personal tools