Introduction: Ice Breaker 1. What is your job title and organization? 2. What are you really good at? 3. What is your biggest personal accomplishment thus.

Slides:



Advertisements
Similar presentations
Design, prototyping and construction
Advertisements

Steps of a Design Brief V Design Brief  Problem, identification, and definition Establish a clear idea of what is to be accomplished. Identify.
Math CAMPPP 2011 Plenary 1 What’s the Focus? An Introduction to Algebraic Reasoning Ruth Beatty and Cathy Bruce 1.
S.T.A.I.R.. General problem solving strategy that can be applied to a range problems.
LECTURE 1 CMSC 201. Overview Goal: Problem solving and algorithm development. Learn to program in Python. Algorithm - a set of unambiguous and ordered.
Cognitive Walkthrough More evaluation without users.
Human Computer Interaction
DESIGN, PROTOTYPING and CONSTRUCTION
What is Design? Professor: Tapan Parikh TA: Eun Kyoung Choe
ICS 463: Intro to Human Computer Interaction Design 2. User-Centered Design Dan Suthers.
Information & Interaction Design Fall 2005 Bill Hart-Davidson Session 6: analyzing work practices – rationale and challenges; the 5 Contextual Design work.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #10 BOO! BOO!
Course Wrap-Up IS 485, Professor Matt Thatcher. 2 C.J. Minard ( )
Introduction to HCI Marti Hearst (UCB SIMS) SIMS 213, UI Design & Development January 21, 1999.
Creating Effective Facilitation Plans for Capacity Building CHA/CHIP Support Laurie Call 1.
1 User Interface Design CIS 375 Bruce R. Maxim UM-Dearborn.
Talent Management Training Methods.
Web Design Process CMPT 281. Outline How do we know good sites from bad sites? Web design process Class design exercise.
Principles of Programming Chapter 1: Introduction  In this chapter you will learn about:  Overview of Computer Component  Overview of Programming 
Abstraction IS 101Y/CMSC 101 Computational Thinking and Design Tuesday, September 17, 2013 Carolyn Seaman University of Maryland, Baltimore County.
1 REQUIREMENT ENGINEERING Chapter 7. 2 REQUIREMENT ENGINEERING Definition Establishing what the customer requires from a software system. OR It helps.
Business Analysis and Essential Competencies
Computer –the machine the program runs on –often split between clients & servers Human-Computer Interaction (HCI) Human –the end-user of a program –the.
Overview Prototyping and construction Conceptual design
Design, prototyping and construction CSSE371 Steve Chenoweth and Chandan Rupakheti (Chapter 11- Interaction Design Text)
S556 SYSTEMS ANALYSIS & DESIGN Week 11. Creating a Vision (Solution) SLIS S556 2  Visioning:  Encourages you to think more systemically about your redesign.
Process Analysis Agenda  Multiple methods & perspectives There are lots of ways to map processes  Useful in many situations not just HRIS design  Preparation.
22C:082:001 Human-Computer Interaction. Fall Copyright © 2013 Juan Pablo Hourcade. 1 Group Project Phase 1.
HCI – Prototyping. Why Prototype?  Prototyping is a well understood and used technique in design engineering where products are tested via a model prototype.
Organizing Your Information
Requirements Engineering Requirements Elicitation Process Lecture-9.
Assignment Paired Prototyping Some content based on GDC 2006, Gingold and Hecker Brent M. Dingle 2014 Game Design and Development Program Mathematics,
1 ISE 412 Usability Testing Purpose of usability testing:  evaluate users’ experience with the interface  identify specific problems in the interface.
Prototyping. What is a prototype? In other design fields a prototype is a small- scale model: a miniature car a miniature building or town.
Wizard of Oz Prototyping + Making Video Scenarios HCC 729 4/17/14.
Reflection helps you articulate and think about your processes for communication. Reflection gives you an opportunity to consider your use of rhetorical.
A Use Case Primer 1. The Benefits of Use Cases  Compared to traditional methods, use cases are easy to write and to read.  Use cases force the developers.
Chapter 9 Prototyping. Objectives  Describe the basic terminology of prototyping  Describe the role and techniques of prototyping  Enable you to produce.
1 Human Computer Interaction Week 7 Prototyping. 2 Introduction Prototyping is a design technique where users can be involved in testing design ideas.
Software Engineering Project.  Why User involvement?  Requirements Gathering statistics.  Ways of Gathering user requirements.  One-on-One Interviews.
Z556 Systems Analysis & Design Session 10 ILS Z556 1.
The Design Process.
Interacting with consumer Software Engineering. So far… What is Software Engineering? Different software process models waterfall, incremental, spiral.
1 The Requirements Problem Chapter 1. 2 Standish Group Research Research paper at:  php (1994)
Overview Prototyping Construction Conceptual design Physical design Generating prototypes Tool support.
YEAR 11 - IPT Term 2 - Tools for Information Processing hardware and Personal information system.
Design, prototyping and construction(Chapter 11).
Beginning Social Communication High School: Lesson Five.
CIT 341: IT Project Management. Objectives Understand the main concepts of project management Understand how Projects are Delivered within Budget Learn.
PSY 360 ASSIST Learning for leading/psy360assistdotcom.
Finding the Main Idea Try looking in the first sentence or the last sentence of a paragraph. If the main idea is not specifically stated, ask yourself,
Unit 6 Application Design.
Lecture 2 Supplement - Prototyping
Chapter 6 Understanding the Technical Writing Process
Introduction: Ice Breaker
Software Requirements analysis & specifications
Design, prototyping and construction
Informatics 121 Software Design I
Chapter 11 Design, prototyping and construction 1.
Agenda for L :15-11 Warm-up Learning diaries
Language Basics.
G&W Chapter 19: Ambiguity Metrics Software Specification Lecture 26
Usability Techniques Lecture 13.
Title Slide for Data Driven Decision Making Precision Problem solving
Title Slide for Data Driven Decision Making Precision Problem solving
DESIGN, PROTOTYPING and CONSTRUCTION
Creative Design Solutions: Design Thinking
Informatics 121 Software Design I
1.02 Creative Design Solutions: Design Thinking
Design, prototyping and construction
Presentation transcript:

Introduction: Ice Breaker 1. What is your job title and organization? 2. What are you really good at? 3. What is your biggest personal accomplishment thus far? 4. What is your primary expectation for this class? 5. What is your guilty pleasure (i.e., something that makes you please although you may feel guilty about it)?

S556 SYSTEMS ANALYSIS & DESIGN Week 1

Exploring Requirements (Gause & Weinberg, 1989)  5 teams were given the same requirement for a computer program except for a single sentence:  Team A: complete the job with the fewest possible hours of programming  Team B: minimize the number of program statements written  Team C: minimize the amount of memory used  Team D: produce the clearest possible program  Team E: to produce the clearest possible output

Exploring Requirements (Gause & Weinberg, 1989) Primary ObjectiveBest Team Minimize core storageC Maximize output readability E Maximize program readability D Minimize statementsB, C Minimize programming hours A

Exploring Requirements (Gause & Weinberg, 1989)  If you tell what you want, you’re quite likely to get it  Simple, but difficult task!

Boehm’s Observations on Project Cost AnalysisDesignDevelopmentImplementation Cost Low cost High cost

Primary Concepts in SA&D  Understand organizational issues  Understand the users  Understand the problems

Understand Organizational Issues  Do not jump into the development stage when asked to build an information system  e.g., Social Networking Site  Analyze organizational issues  e.g., culture, organizational structures

Understand the Users  Contextual design: gathering data, data- driven design, the management team, and organizational context

Understand the Problems  Once an information system would be a solution, analyze what kind of system they would need  Define the problems in organizations (assignment #1)  Avoid ambiguity in stating requirements

Understand Design Representations (Saddler, 2001)  A “design” lives only in our heads and in our representations until it’s became in its final form, such as software, hardware, print, or another medium

Understand Design Representations (Saddler, 2001)  If you have an idea about a design of a next new smartphone, what’s the appropriate form of representation for that idea?

Understand Design Representations (Saddler, 2001)  Representational form:  Conversations  Proposals and plans  Sketches  Symbolic and schematic  Scenarios and storyboards  Prototypes

Understand Design Representations (Saddler, 2001)  Roles that representations play:  Specification  Making ideas and intentions tangible  Making ideas manipulable  Involving multiple ways of thinking—verbal, visual, symbolic, & emotional  Limiting the issues  Summarizing design decisions

Sequence Model

Exercise on Convergent Design

Getting the Ambiguity Out (Gause & Weinberg, 1989)  Convergent design = a design process that consciously and visibly recognizes, defines, and removes ambiguity as effectively as possible

Examples of Ambiguity  Create a means for protecting a small group of human beings from the hostile elements of their environment

Examples of Ambiguity

Convergent Design Exercise (Gause & Weinberg, 1989)  You need to work independently  Privately writing your best estimate so as to make a firm commitment, and capturing your first impressions, so you won’t forget them when you hear other opinions

Convergent Design (Gause & Weinberg, 1989)  Question 1:  How many points were in the star that was used as a focus slide for this presentation?

Convergent Design (Gause & Weinberg, 1989)  The 100 participants provided 18 different answers Over 32 infinite 75

Convergent Design (Gause & Weinberg, 1989)  Question 2:  What factors do you think are responsible for the differences among answers?

Convergent Design (Gause & Weinberg, 1989)  Observational & recall errors  Interpretation errors  Mixtures of sources of error  Effects of human interaction

Convergent Design (Gause & Weinberg, 1989)  The second poll Over 32 infinite 75

Convergent Design (Gause & Weinberg, 1989)  The second poll Over 32 infinite 75

Convergent Design (Gause & Weinberg, 1989)  Question 3:  Write down, verbatim to the best of your recall ability, the question that you think you answered in question 1

Convergent Design (Gause & Weinberg, 1989)  Question 4:  Write down the variants to the question that you think the other classmates wrote when they were asked to recall the question that they thought they were answering

Convergent Design (Gause & Weinberg, 1989)  From this exercise, what did you learn? And how is it relevant to systems analysis & design?

Convergent Design (Gause & Weinberg, 1989)  Each variant statement of this relatively trivial problem does produce a different way of looking at the problem, which in turn produces a different solution.  Our problem statements must be precise