Introduction: Ice Breaker

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.
S.T.A.I.R.. General problem solving strategy that can be applied to a range problems.
Human Computer Interaction
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.
1 User Interface Design CIS 375 Bruce R. Maxim UM-Dearborn.
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.
Web Design Process CMPT 281. Outline How do we know good sites from bad sites? Web design process Class design exercise.
Human Computer Interaction & Usability Prototyping Design & Prototyping HCI Prototyping.
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.
Requirements Engineering Requirements Elicitation Process Lecture-9.
Prototyping. What is a prototype? In other design fields a prototype is a small- scale model: a miniature car a miniature building or town.
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.
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.
Design, prototyping and construction(Chapter 11).
Lecture #1: Introduction to Algorithms and Problem Solving Dr. Hmood Al-Dossari King Saud University Department of Computer Science 6 February 2012.
Contextual Inquiry Preparation for Tuesday, 9/9/14.
Unit 6 Application Design.
EMERGINGDEVELOPINGSECURE Name, describe, follow instructions, recall information, match, sort, label, arrange, use, tell, memorise Apply skills, solve.
Quality Assurance processes
Lecture 2 Supplement - Prototyping
Welcome to M301 P2 Software Systems & their Development
Chapter 6 Understanding the Technical Writing Process
Topic: Introduction to Computing Science and Programming + Algorithm
Articulating Your Practice C3 - Session #3
Chapter 14 Designing Qualitative Research
Making Oral Presentations
Architecture Concept Documents
INTRODUCTION TO MANAGEMENT
Algorithms An algorithm is a sequence of steps written in the form of English phrases that specific the tasks that are performed while solving the problem.It.
Requirements Elicitation – 1
By Dr. Abdulrahman H. Altalhi
Introduction to Computer Programming
Professor Office Hours – Study Groups
Software Requirements analysis & specifications
Informatics 121 Software Design I
Design, prototyping and construction
Chapter 9 Requirements Modeling: Scenario-Based Methods
Informatics 121 Software Design I
Chapter 11 Design, prototyping and construction 1.
Lesson 2 Programming constructs – Algorithms – Scratch – Variables Intro.
G&W Chapter 19: Ambiguity Metrics Software Specification Lecture 26
Usability Techniques Lecture 13.
Reaching Every Student
Title Slide for Data Driven Decision Making Precision Problem solving
Title Slide for Data Driven Decision Making Precision Problem solving
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
DESIGN, PROTOTYPING and CONSTRUCTION
INTRODUCTION To COMPUTER what is information? Information is that which informs. In other words, it is the answer to a question of some kind. It is thus.
Creative Design Solutions: Design Thinking
Evaluation.
Informatics 121 Software Design I
Creative Design Solutions: Design Thinking
1.02 Creative Design Solutions: Design Thinking
Evaluation: Inspections, Analytics & Models
Design, prototyping and construction
COMP444 Human Computer Interaction Prototyping
Evaluation: Inspections, Analytics, and Models
Presentation transcript:

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

Z556 Systems Analysis & Design Session 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 Objective Best Team Minimize core storage C Maximize output readability E Maximize program readability D Minimize statements B, 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 High cost 1000 Low cost 50 Analysis Design Development Implementation

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 work for Google, and you have an idea about a design of a new wearable technology (better than Google Glass), 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

A flow model to map out the coordination, interaction and responsibilities of roommates shopping for a couch.

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

Examples of Ambiguity

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 75 0-2 5-9 10-12 13-16 17-20 21-24 25-27 28-32 Over 32 infinite

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 75 0-2 5-9 10-12 13-16 17-20 21-24 25-27 28-32 Over 32 infinite

Convergent Design (Gause & Weinberg, 1989) The second poll 75 0-2 5-9 10-12 13-16 17-20 21-24 25-27 28-32 Over 32 infinite

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