The schedule provides instructions for what and how to prepare for class as well as assignment due dates. This is a tentative schedule: topics, readings and assignments may be revised at the discretion of the instructor.

In case of adverse weather conditions, the course may be held online (via video or online discussion) or cancelled as appropriate. Official communications will be sent via e-mail.

Monday, January 11: Intro, Information Systems and Analysis

Prep:

Beyer, H. & Holtzblatt, K. (1998). Contextual Design: Defining Customer-Centered Systems. San Francisco: Morgan Kauffman. Chapter 1

If you are unable to read this for the first day of class, please read for January 18.

In class: Sign up for Case Study leaders

After class: Verify access to Sakai. Review course syllabus.

Begin exploring graphics tool(s) to use to make final versions of models. Microsoft Visio is available on computers in the SILS lab, SILS DreamSpark and the ITS Virtual Lab. There are many other tools that you might consider using for this class.

Monday, January 18: No class, University Holiday

Due: Wednesday, January 20 at noon: Discussion points for first Case Study discussion leaders

Monday, January 25: World as Information System; Systems Development Life Cycle

Prep:

Bennett P. (2005). Design is in the details. TEDGlobal 2005 (TED talk, 14:10)

Sellen, A. & Harper, R. (2002). The future of paper. In Sellen & Harper, The Myth of the Paperless Office, Cambridge, MA: The MIT Press. Ch. 7, pp. 185-212.

Batra, D., Xia, W., VanderMeer, D. & Dutta, K. (2010). Balancing Agile and structured development approaches to successfully manage large distributed software projects: A case study from the cruise line industry. Communications of the Association for Information Systems, 27, Article 21, 379-394. (Sakai)

Case Study 1: Jaferian, P., Botta, D., Hawkey, K., & Beznosov, B. (2009). A case study of enterprise identity management system adoption in an insurance organization. Proceedings of the Symposium on Computer Human Interaction for the Management of Information Technology (CHIMIT), 46-55.

In class: Case Study #1 discussion (moved to 2/1 due to weather)

Monday, February 1: Problem Definition; Information Gathering

Prep:

Beyer, H. & Holtzblatt, K. (1998). Contextual Design: Defining Customer-Centered Systems. San Francisco: Morgan Kauffman. Chapter 2

Davis, W. (1999). The problem statement. In W. Davis & D. Yen, The Information System Consultant's Handbook: Systems Analysis and Design. Boca Raton: CRC Press. Chapter 12, 87-90. online Reserves

Davis, W. (1999). The feasibility study. In W. Davis & D. Yen, The Information System Consultant's Handbook: Systems Analysis and Design. Boca Raton: CRC Press. Chapter 13, 91-96. in online Reserves: online Reserves

Alter, S. (2014). Theory of Workarounds. Communications of the Association for Information Systems, 34, Article 55. Sections I & II. Sakai Resources

Swan, L., Taylor, A., & Harper, R. (2008). Making place for clutter and other ideas of home. ACM Transactions on Computer-Human Interaction, 15(2), Article 9.

Dolan, P.L. (2013). EHR design flaws causing doctors to revert to paper. American Medical News. posted 4/8/13.

Review: Case Study 1

Jaferian, P., Botta, D., Hawkey, K., & Beznosov, B. (2009). A case study of enterprise identity management system adoption in an insurance organization. Proceedings of the Symposium on Computer Human Interaction for the Management of Information Technology (CHIMIT), 46-55.

In class: Case Study #1 discussion (originally 1/25)

In class: Problem Definition individual assignment distributed (due February 11 at noon [was 2/15]).

Monday, February 8: Contextual Inquiry; Overview of Models

Prep:

Beyer, H. & Holtzblatt, K. (1998). Contextual Design: Defining Customer-Centered Systems. San Francisco: Morgan Kauffman. Chapters 3 and 4.

Gellatly, A., Hansen, C., Highstrom, M & Weiss, J. (2010). Journey: General Motors' move to incorporate contextual design into its next generation of automotive HMI designs. Proceedings of the Second International Conference on Automotive User Interfaces and Interactive Vehicular Applications, 156-161.

Contextual Inquiry: Workforce Mobility (NozPortfolio, 2010) (YouTube video, 4:05)

Watch this after you have read Gellatly et al.

Hendry, D. (2004). Communication functions and the adaptation of design representations in interdisciplinary teams. Proceedings of the 2004 Conference on Designing Interactive Systems, 123-132.

Siceloff, B. (2012). Bell Tower roundabout will be scaled back to a single lane. News & Observer, June 5, 2012.

Monday, February 15: CLASS CANCELLED, inclement weather

Project team formation will take place 2/22. Project management will be covered on 3/7 when our guest speaker can attend class.

Prep:

Armour, P. (2002). Ten unmyths of project estimation. Communications of the ACM, 45(11), 15-18.

Browse website of Project Management Institute. Get a sense for what certification entails and why one might choose to become certified. Be prepared to discuss.

Choose at least 2 of the following books to skim. Read/skim at least 4 sections/chapters. Be prepared to discuss in class.

In class: Guest speaker: Brian Moynihan, MSIS, PMP, Director of Health Informatics at the UNC Health Sciences Library
Form Project teams and discuss project in detail.
Information Gathering Plan project deliverable distributed (due Monday, February 29)

Due: Problem Definition individual assignment was due 2/11 at 12pm.

Monday, February 22: Finish Contextual Interviews; Form Teams; Scenarios; Personas

Prep:

Carroll, J. (2000). Five reasons for scenario-based design. Interacting with Computers, 13(1), 43-60.

Holtzblatt , K., Wendell, J. & Wood, S. (2005). Rapid Contextual Design. San Francisco: Morgan Kaufmann. Ch. 9, Using Contextual Data to Write Personas, 181-191.

Usability.gov: Methods: Scenarios, Personas

More about Contextual Interviews (optional, but skimming or reading recommended)

Holtzblatt , K., Wendell, J. & Wood, S. (2005). Rapid Contextual Design. San Francisco: Morgan Kaufmann. Ch. 3, Planning your contextual interview, p.63-78. Ch. 4, The Contextual Inquiry Interview, p. 79-100

In class: Form Project teams and discuss project in detail.
Information Gathering Plan project deliverable disseminated, see project requirements doc in Sakai (due Monday, February 29)

Monday, February 29: Scenarios and Personas; Work Modeling: overview, Artifact Model, Cultural model

There are a lot of readings for this class session, but most are very short.

Prep for work modeling (overview, artifact, cultural):

Beyer, H. & Holtzblatt, K. (1998). Contextual Design: Defining Customer-Centered Systems. San Francisco: Morgan Kauffman.

Holtzblatt , K., Wendell, J. & Wood, S. (2005). Rapid Contextual Design. San Francisco: Morgan Kaufmann. Ch. 6, Work Modeling, 123-136.

Monk, A. & Howard, S. (1998). The rich picture: a tool for reasoning about work context. interactions, 5(2), 21-30.

Prep for scenarios and personas (if you have not already read these):

Carroll, J. (2000). Five reasons for scenario-based design. Interacting with Computers, 13(1), 43-60.

Holtzblatt , K., Wendell, J. & Wood, S. (2005). Rapid Contextual Design. San Francisco: Morgan Kaufmann. Ch. 9, Using Contextual Data to Write Personas, 181-191.

Usability.gov: Methods: Scenarios, Personas

In class: Artifact Model individual assignment distributed (due Thursday March 17 at 5pm [WAS March 7]).
Draft Models project deliverable distributed (due Monday, March 28).

Monday, March 7: Models: Physical, Flow (communication); Models: Activity, Sequence and Flow Chart

Prep for models (physical, flow)

Holtzblatt , K., Wendell, J. & Wood, S. (2005). Rapid Contextual Design. San Francisco: Morgan Kaufmann.

Prep for models (activity, sequence, flowchart):

Beyer, H. & Holtzblatt, K. (1998). Contextual Design: Defining Customer-Centered Systems. San Francisco: Morgan Kauffman. Ch. 6 p. 96-101

Holtzblatt , K., Wendell, J. & Wood, S. (2005). Rapid Contextual Design. San Francisco: Morgan Kaufmann.

Miles & Hamilton (2006). Learning UML 2.0 Ch. 3. p. 43-62. Modeling System Workflows: Activity Diagrams (starting at p. 41 in e-book).

Pilone & Pitman (2005). UML 2.0 in a Nutshell. Ch 9: Activity Diagrams (starting at p. 144 in e-book)

Optional:

Bell, D. (2003). UML Basics Part II: The activity diagram. The Rational Edge, September 2003.

In class: We will have a hands-on orientation to creating models using Powerpoint and Visio during class in room 117. Meet in our regular classroom (304) and we will walk to 117 together.

Due: Information Gathering Plan project deliverable.

Due 3/17 at 5pm: Artifact Model individual assignment.

Monday, March 14: No Class. Spring Break. ACM CHIIR conference.

Due 3/17 at 5pm: Artifact Model individual assignment.

Monday, March 21: Project Management; Decision Models; Use Cases

Review/revisit project management readings:

Armour, P. (2002). Ten unmyths of project estimation. Communications of the ACM, 45(11), 15-18.

Browse website of Project Management Institute. Get a sense for what certification entails and why one might choose to become certified. Be prepared to discuss.

Choose at least 2 of the following books to skim. Read/skim at least 4 sections/chapters. Be prepared to discuss in class.

Prep for use cases:

Usability.gov: Methods: Use Cases

Pilone & Pitman (2005). UML 2.0 in a Nutshell. Ch 7. Use Case Diagrams. (p. 103-116 in EBL online view)

Gottesdiener, E. (2002). Top ten ways project teams misuse use cases -- and how to correct them: Part I: Content and style issues. The Rational Edge, June 2002. [Explorer may work better than Firefox] Part II: Eliciting and modeling use cases

In class:
Guest: Brian Moynihan, MSIS, PMP, Director of Health Informatics at the UNC Health Sciences Library
Case Study #2 discussion.
Process and Decision Models individual assignment distributed (due Monday, April 4).

Due: Second Case Study discussion leaders: discussion points due on Wednesday, March 23 at noon.

Monday, March 28: Affinity Diagrams; Card Sorts; Web Models; catch-up

Prep for affinity diagrams:

Holtzblatt , K., Wendell, J. & Wood, S. (2005). Rapid Contextual Design. San Francisco: Morgan Kaufmann. Ch. 8, Affinity Diagram

Prep for card sorting:

Rosenfeld, L. & Morville, P. (2006). Information Architecture for the World Wide Web. O'Reilly. Ch. 10.7, focus on Card Sorting section

Usability.gov: Methods: Card Sorting

Prep for web:

Rosenfeld, L. & Morville, P. (2006). Information Architecture for the World Wide Web. O'Reilly. Ch. 12.1-12.4, Design and Documentation

Case Study #2:

Laster, S., Stitz, T. & Bove, F. (2011). Transitioning from marketing-oriented design to user-oriented design: A case study. Journal of Web Librarianship, 5, 299-321.

Due: Project Status Update and Draft Models project preliminary deliverable

Due: Discussion points for second Case Study discussion leaders (Wednesday, March 23 at noon) and third Case Study discussion leaders (Wednesday, March 30 at noon).

Monday, April 4: Models: ER, CRUD; Data Dictionary; Use Cases

Prep:

Haas, S.W. (2013). Entity-Relationship Models, Part 1: Entities and Attributes (slides, in Sakai)

Haas, S.W. (2013) Entity-Relationship Models, Part 2: Relationships (slides, in Sakai)

Case Study #3:

Sutcliffe, A., de Bruijn, O., Thew, S. Buchan, I, Jarvis, P. McNaught, J., Procter, R. (2014). Developing visualization-based decision support tools for epidemiology. Information Visualization 13:3(1), 3-17.

ADVISES paper prototype (video, 3:16) The video illustrates the paper prototyping of the preliminary design referred to in the article.

Optional:

Elmasri, R. & Navathe, S. (2007). Ch. 7, Data modeling using the entity-relationship (ER) model, sections 7.1-7.4. In Fundamentals of Database, 6th edition. Addison Wesley. (Note: Ch. 3.1-3.4 in earlier editions)

In class: Case Study #3 discussion;
ER Model individual assignment distributed (due Monday, April 11).

Due: Process and Decision Models individual assignment.

Due: Discussion points for third Case Study discussion leaders (Wednesday, March 30 at noon).

Monday, April 11: Affinity Diagrams; User Environment Model; Consolidation; Risk and Change

Prep:

Beyer, H. & Holtzblatt, K. (1998). Contextual Design: Defining Customer-Centered Systems. San Francisco: Morgan Kauffman.

Sicotte, C. et al. (2006). A risk assessment of two interorganizational clinical information systems. Journal of the American Medical Informatics Association, 13, 557-566.

Optional:

Holtzblatt , K., Wendell, J. & Wood, S. (2005). Rapid Contextual Design. San Francisco: Morgan Kaufmann. Ch. 7 Consolidated Sequence Models

Lorenzi, N,. & Riley, R. (2000). Managing Change: An Overview. Journal of the American Medical Informatics Association, 7, 116-124. (Sakai)

Optional: submit Draft Models team preliminary deliverable for a second round of feedback.

Due: ER Model individual assignment.

Due: Fourth Case Study discussion leaders: discussion points due on Wednesday, April 13 at noon.

Monday, April 18: Accessibility; Ethics

Prep:

Review accessibility statements and services available:

Usability.gov. Accessibility Basics

Shilton, K. (2010). Technology development with an agenda: Interventions to emphasize values in design. Proceedings of the American Society of Information Science & Technology 2010 Annual Meeting.

Goldstein, J. To Increase Productivity, UPS Monitors Drivers' Every Move. NPR, Broadcast 4/17/14.

Case Study #4: Guillemette, M., Fontaine, I., Caron, C. (2009). A hybrid tracking system of human resources: A case study in a Canadian university. Communications of the Association for Information Systems, 24(1), Article 15.

In class: Case Study #4 discussion

Monday, April 25: Project Presentations, Last Day of Class

In class: Project Presentations

Saturday, April 30. Final Exam Period. 12pm.

Due: Final project deliverable must be submitted in Sakai.

Revision history

4/4: finalized April schedule

3/1: removed p. 133-136 from Holtzblatt, Wendell & Wood (2005) reading list. Changed Case Study #2 to 3/28 from 3/21.

2/26: major rework of 2/29-3/28 due to snow day on 2/15

2/1: changed Problem Description deliverable due date to 2/11 at 12pm.

1/26: moved discussion for Case Study #1 to 2/1 due to inclement weather on 1/25

1/14: added links to articles available in the online Reserves