Making a Game of System Design

1
Making a Game of System Design

• By William Swartout and Michael van Lent
• Presented by Patti Kraker

2
Conventional vs. Game

• Conventional Software
• Design driven by specification
• Designed to function in real world
• Game Software
• Users experience is driving force for design
• Operates in artificial game world

3
Question of the Article

• Could same ideas be applied to applications with
  more serious-minded goals?
• Two classes of applications
• Test bed for emerging technologies
• Experience-based systems

4
Test Bed for emerging Technologies

• Allows testing in rich environment
• Environment reveals interdependencies and
  research issues

5
Experience-Based Systems

• Seek to influence users through an experience
• Power of immersion

6
Experienced-Based Education

• Example FSC (Full Spectrum Command)
• Used by U.S. Army
• Teaches decision making, synchronization, and
  leadership
• Sequence of missions each designed to support
  specific training objective

7
Experience-Based Communication

• Influencing users beliefs and attitudes
• Communicates viewpoints from interactive
  perspective
• Example U.S. Military Academys Office of
  Economic and Manpower Analysis
• Seeks to inform players about Armys values and
  recruitment

8
Experience-Based Therapy

• Used for phobias and post traumatic stress
• Must be designed carefully
• Systems could result in unwanted outcomes
• Still topic of research and debate

9
Simulation vs. Games

• Simulation
• Creates virtual duplicate of reality
• Users goals mimic real life goals
• Users act freely
• Games
• Creates compelling experience for player
• Goals selected and designed to increase and
  maintain involvement
• Illusion of freedom

10
Conclusion

• Game design techniques can make experience more
  memorable
• As test bed, allow integration of technologies
  and evaluation of overall experience with partial
  implementation