INFO 440 - L05 - October 14, 2004
Notes By: Prins, Egaas

Lab Feedback
    > Very good work overall

DESIGN PROJECTS
Who are Rosson and Carroll?
    > CS
    > HCI
        - Comes out of the Bay Area 1980s culture
        - How do people react with computers
    > Usability Engineering
        - 
    > A case study -- based approach
    > Rosson teaches at Stanford
    > Terry Winograd did the forward
    > Both are Ph. Ds, academics coming from CS
    > Bill Gates Dream: "Computer on every desktop"
        - alternate dreams --
            1.  take over the world
            2.  get a haircut
            3.  build the largest house in the world
            4.  destroy all innovation
            5.  get smaller glasses
            6.  begin new reality series entitled
                    "Pirates of Silicone Valley"
    > From same world as Norman (Neilson's bitch)
        - Computers are something everybody is using them now

What does scenario-based design mean?
    > A story to help the designeer get closer to the problem
    START WITH A STORY
        - About a problem domain
        - For a person (persona)
        - Where the person finds success through the use of a system

What's the point?
    > User centering
    > Just like personas
        - Focus the team
        - Communicate to the outside world
        - Give a basis for dialog, judgment and decision
            * You can argue about the stories

How else could it be?
    WATERFALL MODEL (each item leads to the next)
        - Requirements
        - Design
        - Coding
        - Unit Testing
        - System Test
        - Acceptance
        - Operation
    > Can iterate around Requirements & Design, then continue with coding

What's in scenario-based design?
    > Scenarios describe use in detail, but as a tentative working representation
    > Scenarios focus on the usability consequences of specific design proposals
    > Scenarios describe the problem situation using natural language understood by all stake holders
    > Scenarios offer a vivid description of use that provokes questions and "what if" discussions
    > Scenarios are concrete descriptions but are also very flexible
    
    > Pick LOTR over Star Wars when designing. You want as many details as possible.

What's in a scenario project
    THREE STAGES
        - Analysis
            * Personas / Requirements (Ch 2)
        - Design
            * Info Architecture / Content Modeling
            * Activities (Ch 3) / Interactions (Ch 5)
        - Prototype & Evaluate
            * Prototype (Ch 6)
            * Usability Test (Ch 7)

Design in the bigger picture
    BOIKO'S VERSION OF THE WATERFALL (Trickles down then goes back to the top)
   +--> 1) Asses Readiness / Get a Mandate
   |    2) Gather Requirements / Do Logical Design (DESIGN HAPPENS HERE!)
   |    3) Select Hardware and Software / Plan Implementation
   |    4) Implement System / Process Content
   |    5) Load and Test Content / Deploy and Test System
   +--< 6) Train Staff / Perform Maintenance
    > Loopback is "job security"
    > This is a wicked problems that changes out from under you
# END #