1 Brainstorming and Storyboarding Sriram Mohan. 2 Outline  Background Barriers to Elicitation  Techniques Brainstorming Storyboarding.

Slides:



Advertisements
Similar presentations
The Writing Process Communication Arts.
Advertisements

Rapid Prototyping Dimensions and terminology Non-computer methods
DiscoverDefineDesignDevelopDeliver PROCESS TM. Intelligaia Technology confidential & proprietary Discover Overview: Gather information, brainstorm, competitive.
Web E’s goal is for you to understand how to create an initial interaction design and how to evaluate that design by studying a sample. Web F’s goal is.
The Writing Process.
ACTIVELY ENGAGING THE STAKEHOLDER IN DEFINING REQUIREMENTS FOR THE BUSINESS, THE STAKEHOLDER, SOLUTION OR TRANSITION Requirements Elicitation.
1 Brainstorming and Storyboarding Sriram Mohan/Steve Chenoweth RHIT Chapters 12 & 13, Requirements Text.
1 Brainstorming CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 16, 2004.
Storyboards CSSE 371, Software Requirements and Specification Steve Chenoweth, Rose-Hulman Institute September 14, 2004 In the book – This is Ch 13 The.
1 Team Skill 2 - Understanding User and Stakeholder Needs (Chapters 8-13 of the requirements text) CSSE 371, Software Requirements and Specification Don.
Functional Requirements – Use Cases Sriram Mohan/Steve Chenoweth (Chapters 14, 21 – Requirements Text) 1.
1 Team Skill 1 - Analyzing the Problem Sriram Mohan/ Steve Chenoweth 371 Ch 5 in Requirements Text.
Fundamentals of Information Systems, Second Edition
Brainstorming and Idea Reduction
From Scenarios to Paper Prototypes Chapter 6 of About Face Defining requirements Defining the interaction framework.
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 1. Interviews 2. Workshops 3. Brainstorming.
Storyboarding Chimacum Middle School Website Storyboarding Secrets from Hollywood Basics of Web Design A sample Restaurant Sample.
Team Skill 2 Understanding Stakeholders Needs
Brainstorming Steve Chenoweth & Chandan Rupakheti RHIT Chapters 12 & 13, Requirements Text, Brainstorming Techniques document Brainstorming involves generating.
Jennifer O’Donnell EDUC 681 Survey of Instructional Technology Applications Adobe Captivate.
The Flipped Classroom. What does it mean to “Flip?” What is typically presented in class (i.e. lectures, content, background knowledge, or real life experiences)
Pod Casting as an Assessment Tool Presented By Anne Baker Science Teacher Edgemont Campus.
The Writing Process My Favorite Things.
Teaching Your Students to Design High Quality Videos Why should students make videos? How to teach students to make high quality videos for projects in.
Instructional Design Brian Newberry. Instructional Design Instructional Design is a systematic process for the creation of educational resources.
Perimeter and Area Let the fun begin! Summer 2003Betsy Bellinger and Stacey Spillman2 Why do I need to know this???  To find out the size of your foot.
Brainstorming 1. “The hardest single part of building a software system is deciding precisely what to build. No other part of the conceptual work is as.
Advanced Topics in Requirement Engineering. Requirements Elicitation Elicit means to gather, acquire, extract, and obtain, etc. Requirements elicitation.
Introduction to PowerPoint 2010
IS 466 ADVANCED TOPICS IN INFORMATION SYSTEMS LECTURER : NOUF ALMUJALLY 22 – 10 – 2011 College Of Computer Science and Information, Information Systems.
Storyboarding 1. Purpose of Storyboarding  To gain an early reaction from users on the concepts proposed for the application.  They are an effective.
What about Chapter 7?. What is the usability process? Tyldesley’s 22 possible Measurement Criteria Let’s focus on usability–A usability initiative needs.
Requirements Engineering Requirements Elicitation Process Lecture-9.
Class Usability Experience User slides are in BLUE.
Richwoods High School Group 4 Project Richwoods High School.
Prof. James A. Landay University of Washington Autumn 2008 Video Prototyping October 14, 2008.
Chapter 9 Prototyping. Objectives  Describe the basic terminology of prototyping  Describe the role and techniques of prototyping  Enable you to produce.
Functional Requirements – Use Cases (Chapters 14, 21) Sriram Mohan 1.
Team Skill 2 Understanding User and Stakeholder Needs The Challenge of Requirements Elicitation (8)
Melissa Nelson EDU 521 Fall First Grade Standards Whole Class KWLLearning Centers Small Groups Math : Determine and compare sets of pennies.
Inspiration Software, Inc. By Suzanne Sherman. Visual Learning Inspiration Software is based on the premise that visual learning helps students to improve.
ICS 463, Intro to Human Computer Interaction Design: 5. Design Processes Dan Suthers.
Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.
1 Team Skill 1 - Analyzing the Problem Continued and Product Features and Challenges Sriram Mohan.
Storyboarding Steve Chenoweth & Chandan Rupakheti RHIT Chapters 13, Requirements Text and storyboarding web article.
Blackboard Collaborate Webinar Software Bryony Bramer - Virtual Learning Environment Manager Chris Rowell - Technology Enhanced Learning Advisor Learning.
Techniques for presenting content
Introduction to Evaluation without Users. Where are you at with readings? Should have read –TCUID, Chapter 4 For Next Week –Two Papers on Heuristics from.
1 Team Skill 2 - Understanding User and Stakeholder Needs (Chapters 8-13 of the requirements text) Sriram Mohan.
Software Requirements and Design Class 4 Khalid Ishaq.
Overview Prototyping Construction Conceptual design Physical design Generating prototypes Tool support.
Team Skill 2 Understanding User and Stakeholder Needs Storyboarding (13)
Trends & Concepts in the Software Industry II Synthesis.
Team Skill 3 - Defining the System (Chapters of the requirements text ) Sriram Mohan 1.
INFO 638Lecture #91 Software Project Management Conclude Adaptive Project Framework INFO 638 Glenn Booker.
SWE 214 (071) Chapter 12: Brainstorming and Idea Reduction Slide 1 Chapter 12: Brainstorming and Idea Reduction.
Prof. James A. Landay University of Washington Winter 2007 Video Prototyping January 22, 2007.
Q&A Platform for Live Events Make it super easy for anyone in your audience to ask their questions and vote up the ones they like.
Chapter 5 Trawling For Requirements. Determining What the Product Should Be without understanding the work that it is to become a part of Many projects.
Advanced Higher Computing Science
Team Skill 1 - Analyzing the Problem
HOW TO PREPARE A GOOD STORYBOARD
Recall The Team Skills Analyzing the Problem (with 5 steps)
CMGT 445 Competitive Success/snaptutorial.com
CMGT 445 Education for Service/snaptutorial.com
Structured Note-Taking For All Warren Mott Students
Applying Use Cases (Chapters 25,26)
Applying Use Cases (Chapters 25,26)
Interviewing Sriram Mohan.
User Stories Agile Methodology HEE Learning Hub
Presentation transcript:

1 Brainstorming and Storyboarding Sriram Mohan

2 Outline  Background Barriers to Elicitation  Techniques Brainstorming Storyboarding

3 Three Common Barriers  “Yes, But…” Syndrome Develop techniques to get rid of the “But” early.  Undiscovered Ruins Syndrome “the more you find, the more you know” --> find the right balance  User and Developer Syndrome Communication gap between the users.

4 Outline  Background Barriers to Elicitation  Techniques Brainstorming Storyboarding

Phases of Brainstorming  Idea Generation  Idea Reduction 5

6  Encourages participation by all  Allows participants to build on one another's ideas  High bandwidth: many ideas in short period of time  Encourages out-of-the-box thinking Benefits

7 One Brainstorming Method  Write down ideas on post-it notes, put on wall  Read ideas out loud  Capture ideas in person’s own words  Generate as many ideas as possible  No criticizing!  Take turns being the facilitator

8 A Similar Method  Use an easel or whiteboard  Ask for ideas and write them down as they are said aloud  Once again - no criticizing!

9 Idea Reduction  Prune ideas…, After the crazy and wild ones disappear  Give one-line description for each remaining idea  Classify the ideas into groups

Idea Reduction…  But there are situations, where not all ideas can be taken forward, in this case we have to choose the ideas that we take forward. How do we do this? Vote on the ideas (i.e. rank them) Prioritize the ideas 10

Web based brainstorming  Using the internet to facilitate the brainstorming in a collaborative way.  Is this useful? Why?  How do we do it? 11

Practice Brainstorming  Idea Generation(7 minutes) Lets generate ideas for features, requirements, enhancements, user interfaces or anything that you would like to see on our sample project. Please raise your hand and point out your ideas.  Once we are done lets practice Idea Reduction (10 Minutes) Eliminate Invalid Ideas One line description Voting 12

13 Outline  Background Barriers to Elicitation  Techniques Brainstorming Storyboarding

14 Story  Who are the players?  What do they do?  How do they do it?

15 Get the idea from some Storyboard Examples  More movies --This one’s from Blade Runner  In the movie industry, storyboarders don’t think they get enough credit – See omba.htm omba.htm

16 Another Storyboard Example  More movies – Ace Ventura: When Nature Calls Storyboard from Storyboarding 101, by James O. Fraioli. Michael Weise Productions, 2000, ISBN

17 Another Storyboard Example  From software & web development. This one’s “Understanding your automobile,” at a.edu/authoring/studio/guid ebook/storyboard_example. html a.edu/authoring/studio/guid ebook/storyboard_example. html  You can check out their website for more about their methodology and templates…

18 Key Points  Purpose – Elicit “Yes, But” reactions  Storyboards should be sketchy  A place to add innovative content Above, right – “At the forefront of innovative content, interactivity is valuable only if it is user-friendly.” From mediadigest/md0001/04.htmlwww.rthk.org.hk/ mediadigest/md0001/04.html

19 Storyboard Types  Passive Rough Sketches, screen shots  Active Flash movie, linked PowerPoint presentation.  Interactive Realistic, and a live prototype

20 Advantages of Storyboard  Inexpensive  User friendly, informal, interactive  Provides an early review of user interfaces of the system  Easy to create and easy to modify

Scenarios  Scenario is a narrative describing foreseeable interactions of types of users (characters) and the system or between two software component  Used in usability research  Famous example As we may think? - Vannevar Bush 21

Extra Credit  Extra Credit 1: What are the tradeoffs on scenarios when compared to use cases and storyboards? Can we use them in gathering requirements? Turn it in using Angel (Lessons – Weekly Content – Week 02 – Day 02 – Scenario’s Extra Credit)  Team Extra Credit 1: Provide storyboard diagrams for your project as a part of Milestone 2. It will be worth 25 points towards your teams Milestone 2 grade. 22

Special Extra Credit  Write a report on the “As we may think” article. This will be due on Monday the 17 th of September by class time. Please your reports to me. It is worth a lot more than 10 points.  The report should provide Synopsis of the article Your perspective on the article 23