Gamified Requirement Elicitation for a Multi-Modal Decision Support System. The Case of SYNCHROMODE
This paper presents a comparative analysis of traditional and gamified requirement elicitation methods used to define the needs of the SYNCHROMODE multimodal decision support system, demonstrating how a serious game engaged diverse stakeholders in a physical workshop to identify and validate core system requirements.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you are trying to build a massive, high-tech "traffic control center" for a city. This isn't just about traffic lights; it's a complex system (called SYNCHROMODE) that needs to coordinate buses, trains, trucks, emergency vehicles, and apps all at once.
Before you can build the software, you need to know exactly what the people who will use it need. This is called Requirement Elicitation. Usually, this is done by sitting in a room with experts and asking, "What do you need?" It's like asking a group of chefs to list ingredients for a soup. It works, but it can be boring, and sometimes people are too shy to speak up or get stuck in their own heads.
The authors of this paper tried a different recipe: Gamification. They turned the "boring meeting" into a serious game.
Here is how they did it, explained simply:
1. The Setup: Two Ways to Cook the Soup
The team looked at three cities (Madrid, Thessaloniki, and South Holland).
- The Traditional Way: In all three cities, they used standard methods (like writing down "user stories" and "use cases") to figure out what the system needs.
- The Gamified Way: In Thessaloniki (Greece), they decided to try something fun. They invited 36 experts (from police, bus companies, tech firms, and universities) to a workshop.
2. The Game: "Traffic Crisis Simulator"
Instead of just asking questions, they split the experts into two teams and gave them a game booklet and a board.
- The Scenario: One team had to solve a traffic accident on the highway during rush hour. The other team had to handle a massive traffic jam at the city entrance in the evening.
- The Rules:
- They had to answer questions about how to fix these problems.
- Points System: If they mentioned a need the team already knew about, they got 1 point. If they discovered a new need nobody had thought of yet, they got 3 points.
- Voting: They voted on the best answers.
- Prizes: The winners got a physical prize.
- The "Game Masters": Two moderators kept the game moving and explained the rules.
Think of this like a board game version of a city planning meeting. Instead of just talking, you are playing a role, racing against a timer, and earning points for being clever.
3. The Results: Did the Game Work?
After the game, the researchers compared the results to the "boring" traditional lists they made earlier.
- Validation: The game confirmed almost everything (22 out of 24) the team already thought was important. This proved their initial ideas were good.
- Discovery: The game also uncovered new requirements that the traditional method missed.
- Agreement: The experts agreed on solutions much faster during the game. The "consensus" (how much everyone agreed) was higher than in a standard meeting.
- Fun Factor: When asked later, 79% of the participants said the game was a better way to figure out what the system needs than the traditional methods. They found it engaging and easier to participate in.
4. The Takeaway
The paper concludes that turning a serious work meeting into a game is like adding a secret ingredient to a recipe. It doesn't change the food (the final software requirements), but it makes the chefs (the experts) more excited, more willing to share their ideas, and more likely to agree on the best solution.
In short:
- Problem: Getting experts to agree on what a complex system needs is hard and often boring.
- Solution: Turn the meeting into a game with points, roles, and scenarios.
- Outcome: People participated more, found new ideas, and agreed faster.
The authors suggest that for big, complicated projects involving many different types of people, gamification is a powerful tool to get the best ideas out of the room.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.