8/13/2019 Envision_MDes
1/11
Interactivity 1
EnvisioningRequirements
FlowchartingScenarios
Wireframing
Context-Scenario Map
8/13/2019 Envision_MDes
2/11
8/13/2019 Envision_MDes
3/11
Requirements
something the design must do or a quality theproduct must have(1)
after collecting and analyzing the user data, designers need to
turn this into requirements - a creative leap
1. Robertson and Robertson, Mastering the Requirement Process (1999)
requirements to be prioritized using MoSCoW Rules
Must have - fundamental
Should have - essential given timeCould have - lesser importance
Want to have - can be left out for the next round
8/13/2019 Envision_MDes
4/11
Requirements
8/13/2019 Envision_MDes
5/11
Flowcharting
Visualizing the interaction process
Analyzing and and describing the interaction process
Sequencing of steps in a process (temporal)
Plan routes and pathways of user experience
8/13/2019 Envision_MDes
6/11
FlowchartingSymbolic Representations
http://www.jjg.net/ia/visvocab/
http://www.jjg.net/ia/visvocab/8/13/2019 Envision_MDes
7/11
8/13/2019 Envision_MDes
8/11
8/13/2019 Envision_MDes
9/11
Wireframes
Planning the layout of interface elements
Documenting screens at various states
No visual/type treatment, just the basics
Propose the needed interactions
8/13/2019 Envision_MDes
10/11
Wireframe + Scenario = Context Scenario Map
http://digital-locker.design.yorku.ca/3005Mw12/Team5/pdfs/phase1.pdf8/13/2019 Envision_MDes
11/11
*flowchart added as additional
information layer
Wireframe + Scenario = Context Scenario Map*
Recommended