Design for Results: Considerations for experimental prototyping and play testing using iterative game design<br />Mirjam P...
Overview<br />Motivation<br />Prototypes<br />Play-tests<br />Obtaining Data<br />Discussion<br />
Motivation<br />Toolbox<br /> Discussion<br /> Scope<br />‘if game studies is limited to analysing existing games and desi...
Prototypes<br />a prototype is anything that can be interacted with and  demonstrate how a system works. Also, the prototy...
Paper or physical prototypes
Computationally aided physical prototypes (please suggest a better term! )
Software Prototypes</li></li></ul><li>Play-tests<br />
Obtaining Data<br />
Example of a Production Cycle(for a digital prototype)<br />	consideration of type of prototypes needed depending on resea...
POINT<br />
Feedback/ Discussion<br />Group xp of:<br />Prototypes<br />Play-tests<br />Obtaining Data<br />What did we miss?<br />Opi...
Upcoming SlideShare
Loading in …5
×

Design for Results - Considerations for experimental prototyping and play testing using iterative game design

1,594 views

Published on

Design for Results: Considerations for experimental prototyping and play testing using iterative game design.

Talk given at Game

Published in: Technology, Design
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,594
On SlideShare
0
From Embeds
0
Number of Embeds
21
Actions
Shares
0
Downloads
14
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide
  • This paper is concerned with development of experimental research prototypes, sometimes also called demonstrators. A commonly used development method is iterative design which, as described by Salen and Zimmerman shortcite{Salen2001}, is a play-based design process. A prototype is extit{``played, evaluated, adjusted and played again, allowing the designer or design team to base decisions on the successive extit{iterations} or versions of the game. Iterative design is a cyclic process that alternates between prototyping, play-testing, evaluation, and refinement.&apos;&apos;}
  • it must be stressed that the iterations can and should happen even inside the early prototype development, and in some cases, between the test sessionsfootnote{For instance, test the prototype with the first participant, fix existing problems and develop further promising new ideas, and test the evolved version of the same prototype with participant two, and so on.}: The traditional waterfall model cite{waterfallmodel} proposes a process where the design, implementation, and evaluation follows each other in a linear manner. The iterative design process for games see, e.g. cite{fullerton04,Salen2001}, emphasizes on iterations where the game is designed, tested, and evaluated continuously during the process and developed further. There has been some criticism that even this kind of process would not be iterative enough cite{Fallman} and that design, implementation, and evaluation should be done tightly together.
  • Participant role: informant/co-designer   &lt;--- Jorgensen, “co-researcher”
  • OUR VIEW; IF U CANT DO IDEAL TEST EARLY, U SHOULD STILL DO QUICK AND DIRTY TESTING AND DO IT A LOT. BUT DO NOT EXPECT IT TO PROVIDE PERFECT DATA
  • Filled in by research question.easy to fall into a frame of mind where one aims to produce a good game, loosing focus of obtaining research material.The very reason for the development of research prototypes is to find methods, features or approaches that can be used in other games, games which are specifically made to be fun, challenging and perhaps carry a message. The researcher needs to approach the design of the prototype both as a researcher and as a game designer.Practicality. Resources, time etc – and ideology regarding validation. Own and projected.
  • Jorgensen also talked about video commentaries. So maybe another arrow still under: “feedback” -&gt; after the game. “”video commentary model, Jorgensen”.
  • Design for Results - Considerations for experimental prototyping and play testing using iterative game design

    1. 1. Design for Results: Considerations for experimental prototyping and play testing using iterative game design<br />Mirjam P Eladhari<br /> Elina M.I. Ollila<br />
    2. 2. Overview<br />Motivation<br />Prototypes<br />Play-tests<br />Obtaining Data<br />Discussion<br />
    3. 3. Motivation<br />Toolbox<br /> Discussion<br /> Scope<br />‘if game studies is limited to analysing existing games and design spaces, it can be problematic to imagine or theorise about potential game features outside of these design spaces. Models about the nature of games and their features run the risk of being incomplete or wrong, simply because certain design spaces have not yet been explored”<br />navigational aid in the wicked problem-space of game design<br />
    4. 4.
    5. 5. Prototypes<br />a prototype is anything that can be interacted with and demonstrate how a system works. Also, the prototypes are usually disposable<br /><ul><li>Prototyping by acting and showing
    6. 6. Paper or physical prototypes
    7. 7. Computationally aided physical prototypes (please suggest a better term! )
    8. 8. Software Prototypes</li></li></ul><li>Play-tests<br />
    9. 9. Obtaining Data<br />
    10. 10. Example of a Production Cycle(for a digital prototype)<br /> consideration of type of prototypes needed depending on research question;<br /> early design (design process continuing throughout iteration cycles) -- body storming, video scenarios; <br /> collect feedback, redesign;<br /> physical/mixed prototyping and scenario design;<br /> play test;<br /> data analysis;<br /> interpretation and potential dissemination;<br /> reiteration of design for software prototype;<br /> implementation of software prototype;<br /> quality assurance of prototype;<br /> design of test scenarios;<br /> play test;<br /> data analysis;<br /> interpretation and potential dissemination.<br />
    11. 11.
    12. 12.
    13. 13.
    14. 14. POINT<br />
    15. 15. Feedback/ Discussion<br />Group xp of:<br />Prototypes<br />Play-tests<br />Obtaining Data<br />What did we miss?<br />Opinions? Ideas?<br />
    16. 16.
    17. 17. END<br />
    18. 18. Obtaining Data<br />

    ×