LU#03 – Defining Requirements and Design Rationales

03-01 (box.fu, github) | 03-02 (box.fu, gitlab) | 03-03 (box.fu, gitlab) | 03-4 (box.fu, gitlab)

Videos

03-01 | Elicitating Requirements

  • Types of Requirements
  • Challenges after data collection
  • Initial Processing of the Data
  • Simple Quantitative Analysis
  • Simple Qualitative Analysis
    • Affinity Diagramming
    • Thematic Analysis

03-02 | Conceptual Models: User Focus

  • User Groups
  • Personas

03-03 | Conceptual Models: Context Focus

  • Use Cases
  • Scenario

03-04 | Conceptual Models: Task Focus

  • Task Analysis
  • Hierarchical Task Analysis
  • Contextual Design
    • Physical model
    • Artifact model
    • Sequence model
  • Task Flow

Additional Material

? John M Carrol. 1999. Five reasons for scenario-based design. In Proceedings of the 32nd annual hawaii international conference on systems sciences. 1999. HICSS-32. Abstracts and CD-ROM of full papers, 11-pp. PDF

? Jeff Johnson and Austin Henderson. 2002. Conceptual models: begin by designing what to design. interactions 9, 1 (January 2002), 25–32. DOI:https://doi.org/10.1145/503355.503366

? Alan Cooper, Robert Reimann, and Dave Cronin. „About Face 3. The Essentials of Interaction Design„. Wiley Publishing, 2007. Chap. 5 „Modeling Users: Personas and Goals“

Also interesting are Chapter 10.5 (Data Analysis, Interpretation, and Presentation), Chapter 10.6 (Task Description), Chapter 10.7 (Task Analysis) in:
Jenny Preece, Yvonne Rogers, and Helen Sharp. 2015. Interaction design: beyond human-computer interaction (Fourth edition ed.). Wiley, Chichester.