Transitioning from requirements to envisioning and describing the activity we would like to support.
Assignment 2: Requirements Analysis for Collaborative Calendar: due 2/2
Rosson & Carroll Ch. 3.
Problem Scenarios are converted to Activity Scenarios: stories that illustrate the activity we'd like to see without implementation details.
Constantine & Lockwood Ch. 5. See also Constantine & Lockwood (2000): Structure and Style in Use Cases for User Interface Design (all of C&L's online articles are strongly recommended!)
Essential use cases are more abstract than the conventional use cases of software engineering. Be sure to understand why.
Since we did not get beyond problem scenarios last week, we'll try a hierarchical task analysis on Monday. Then on Wednesday we will try essential use cases.
We'll also discuss an article on "Email as Habitat"
Assignment 3, Activity Design for Calendars, due 2/9