1 Brainstorming and Storyboarding Sriram Mohan/Steve Chenoweth RHIT Chapters 12 & 13, Requirements Text.

Slides:



Advertisements
Similar presentations
Easy, like an attachment. But can your doc stand on its own? Yes. Only teachers can upload files to course site. So definitely a push- tool. Maybe.
Advertisements

The Writing Process Communication Arts.
M2 – Explain the tools and techniques used in the creation of an interactive website. By Arturas Vitkovskij.
Rapid Prototyping Dimensions and terminology Non-computer methods
SECOND MIDTERM REVIEW CS 580 Human Computer Interaction.
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.
Chapter 10 Schedule Your Schedule. Copyright 2004 by Pearson Education, Inc. Identifying And Scheduling Tasks The schedule from the Software Development.
Maths Counts Insights into Lesson Study
ACTIVELY ENGAGING THE STAKEHOLDER IN DEFINING REQUIREMENTS FOR THE BUSINESS, THE STAKEHOLDER, SOLUTION OR TRANSITION Requirements Elicitation.
Web services for Improving the development of automatic generalisation solutions Nicolas Regnauld Research & Innovarion Ordnance Survey 07 th March 2006,
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.
Functional Requirements – Use Cases Steve Chenoweth & Chandan Rupakheti (Chapters 14, 21 – Requirements Text)  Quiz question 9 relates to this, when you’ve.
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.
App Project GROUP C: CSAVER CREATED AND PRESENTED BY SHAH, AVRAJ, JOSEPH AND SULAIMON MONEY MANAGEMENT APP TITLE: CLEVER SAVER LECTURER: MARIAN HEPBURN.
Simple brief By: Ayat Farhat
Pod Casting as an Assessment Tool Presented By Anne Baker Science Teacher Edgemont Campus.
The Writing Process My Favorite Things.
Instructional Design Brian Newberry. Instructional Design Instructional Design is a systematic process for the creation of educational resources.
Assignment Task 3: Teacher Resource Living & Learning with Technology EDN
National History Day How to: Creating a Documentary
The Civil War: Quiz Yourself
Advanced Topics in Requirement Engineering. Requirements Elicitation Elicit means to gather, acquire, extract, and obtain, etc. Requirements elicitation.
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.
Brainstorming! Click left mouse button or press space bar to advance presentation. Click right mouse button to go back. Press ‘Esc’ key to exit.
Brainstorming! Click left mouse button or press space bar to advance presentation. Click right mouse button to go back. Press ‘Esc’ key to exit.
Requirements Engineering Requirements Elicitation Process Lecture-9.
How to start Milestone 1 CSSE 371 Project Info There are only 8 easy steps…
Usability testing: A reality check for Plain Talk A brief overview October 7, 2008 Dana Howard Botka Manager, Customer Communications, L&I Plain Talk Coordinator,
44222: Information Systems Development Documenting a Solution Ian Perry Room:C41C Extension:7287
Storyboarding The Why and the How…. A set of drawings that represent screen layout sequences First used by filmmakers to plan the sequences of movie scenes.
Team Skill 3 – Organizing Requirements & Product Management (Chapters of the requirements text ) Sriram Mohan/Steve Chenoweth RHIT 1.
Functional Requirements – Use Cases (Chapters 14, 21) Sriram Mohan 1.
UML Class Diagram Tutorial by Florin Zidaru. Outline 1. UML Class Diagram. What is it? Why do we need it? 2. Tutorial Description and Presentation. 3.
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.
Creating User Interfaces Review midterm. Work on User Observation studies Homework: Spring break! Use opportunity to work on user observation study!
1 Team Skill 1 - Analyzing the Problem Continued and Product Features and Challenges Sriram Mohan.
1 Brainstorming and Storyboarding Sriram Mohan. 2 Outline  Background Barriers to Elicitation  Techniques Brainstorming Storyboarding.
Storyboarding Steve Chenoweth & Chandan Rupakheti RHIT Chapters 13, Requirements Text and storyboarding web article.
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.
Analyzing the Problem Continued and Product Features and Challenges Steve Chenoweth & Chandan Rupakheti RHIT Pages Requirements Text.
Software Requirements and Design Class 4 Khalid Ishaq.
Team Skill 2 Understanding User and Stakeholder Needs Storyboarding (13)
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.
Team Skill 1 - Analyzing the Problem
Interviewing S.Vidya,AP/CSE.
HOW TO PREPARE A GOOD STORYBOARD
Recall The Team Skills Analyzing the Problem (with 5 steps)
Storyboarding.
Interviewing Sriram Mohan.
Presentation transcript:

1 Brainstorming and Storyboarding Sriram Mohan/Steve Chenoweth RHIT Chapters 12 & 13, Requirements Text

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  Describe the problem clearly  Discover = Idea Generation New Ideas Idea Development  Decide = Idea Reduction Eliminating Combining Choosing 5 Describe Discover Decide

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

Describe  Everyone has to agree on the problem to be brainstormed before you start.  It helps if they all have time beforehand to think of ideas on their own.

8 Discover - 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

9 Discover - A Similar Method  Use an easel or whiteboard  Ask for ideas and write them down as they are said aloud  While facilitator writes down the “headline” for each idea, the person giving it can explain just a little more  Try to get more ideas related to ones you are hearing  Once again - no criticizing!

Discover - Idea Development  Find ideas that are “most intriguing” Usually they have some “issues” but also a lot to like  Pick one, and brainstorm ways to “push them toward acceptable”  Then do this to a couple more  Gives “ideas about these ideas” which could make them into winners

11 Decide - Idea Reduction  Prune ideas…, After the crazy and wild ones you couldn’t help disappear  Give one-line description for each remaining idea  Combine ideas  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? See if any more can be combined Vote on the ideas (i.e. rank them) Prioritize the ideas Try to decide based on “acceptable risk” and “desired opportunities” so you don’t end up with just easy ones everyone already knew Try to leave with “as many as you can afford to consider further”  Put all remaining ideas on someone’s action list to develop 12

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

Practice Brainstorming – Do as Teams  Describe - Features, requirements, enhancements, user interfaces or anything that you would like to see on our sample project.  Discover - Idea Generation (14 minutes) Let’s generate ideas for this. (7 minutes) Find ones that are intriguing & find ways to support those (7 minutes)  Decide - Once we are done lets practice Idea Reduction (10 Minutes) Eliminate invalid ideas Group those that should go together One line description Voting & Prioritizing  Leave with action list 14

15 Outline  Background Barriers to Elicitation  Techniques Brainstorming Storyboarding

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

17 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

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

19 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…

Google Chrome  ebooks/chrome/ ebooks/chrome/

21 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

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

23 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 24

Extra Credit  Extra Credit 1: What are the tradeoffs on scenarios when compared to DFD’s and storyboards? Can we use them in gathering requirements? Turn it in using Angel (Lessons – Extra Credit – Week 2 – Scenario’s Extra Credit) Due Friday Class Time  Extra Credit 2: Read the “As we may think” article and write a report on it with special emphasis on the use of scenarios to describe a vision and your perspective on it. (Lessons - Extra Credit - Week 2 - As we may think) Due September 23rd  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. 25