Rapid Prototyping for Discovery-Based Learning. Presented 03/03/10 at the Society for Applied Learning Technologies conference by Lisa Meece and Jennifer Bertram.
12. “Prototyping is about people. Users are not often able to articulate what they want …and they cannot visualize it from written specifications.” -Kenneth Lantz
13. Components of a Prototype Learner instructions as they’ll appear in the final version Screen represents real-life situations Simplified graphics, very different than what will be in the finished version Functionality as it will work in the finished version
Prototyping is about people. Users are not often able to articulatewhat they want an information system to do, and they cannot visualizeit from written specifications. Prototyping enables them to seea system, "play" with it and modify it before it isimplemented.http://www.manageknowledge.com/prototyp.html
References and Further Reading
From Idea to PrototypePrototypes should:Be created quickly.Support the brainstorming process with the client. Allow ideas to change and flex - the first idea isn’t going to be the best idea. Keep you from getting too invested in the first idea, so you can realize the best idea when it emerges.Show how the interaction works, not what content is on the screen.Not include final graphics.Not necessarily be the software that the course is created in; speed is more important than reusability.Questions to ask the SME:Who is the audience?Who do you work with?What problem are we solving?What do they need to do to solve the problem? What to they need to know to solve the problem? How does this task/challenge/problem unfold in real-life?What are the consequences - positive or negative?Brainstorming Questions:What goes wrong?What are the consequences when that happens?How can it be prevented? (knowledge, people, processes)