SCHEDULE OVERVIEW
Below you'll find a TENTATIVE schedule for the semester. Please note that all topics/dates/etc. are subject to change at any time. I fully expect to make adjustments multiple times over the course of the semester.
DETAILED SCHEDULE
| August | |||
| 22 | Class 1 | Introduction; Assign Case Study 1 Leaders • Check Sakai access • Review course syllabus, requirements, and policies | New:Case Study Preferences and Leadership |
| 24 | Class 2 | Information Systems, Information Systems Analysis -- what are they? • 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. | Due: Case Study 1 discussion leader comments |
| 29 | Class 3 | The Systems Development Life Cycle; Case Study 1 • Beyer & Holtzblatt, Ch. 1, Introduction • Batra, D., Xia, W., VanderMeer, D. & Dutta, K. (2010). Balancing Agile and structured development approaches to successfullly 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. • 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. | |
| 31 | Class 4 | Models • 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 ring. News & Observer, June 5, 2012. | Due: Case Study 2-4 Preferences |
| September | |||
| 5 | Class 5 | Problem Definition; Feasibility Study • 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. • 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. | New: Problem Definition |
| 7 | Class 6 | Contextual Inquiry; Information Gathering • 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. • Beyer & Holtzblatt, Ch. 2, Gathering Customer Data & Ch. 3, Principles of contextual inquiry. | |
| 12 | Class 7 | Contextual Inquiry and Information Gathering, Continued • Beyer & Holtzblatt, Ch. 4, Contextual inquiry in practice. • 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. | |
| 14 | Class 8 | Project Management • Armour, P. (2002). Ten unmyths of project estimation. Communications of the ACM, 45(11), 15-18. • Project Management Institute Browse the website, especially "About Us" and "Certification" pages. | |
| 19 | Class 9 | Scenarios; Personas • Beyer & Holtzblatt, Ch. 5, A language of work. • Carrol, 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. | Due: Problem Definition Due: Problem preferences due Wednesday 20th @ 11am |
| 21 | Class 10 | Use Cases • Pilone & Pitman, Ch. 7, Use case diagrams. • 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. • Gottesdiener, E. (2002). Top ten ways project teams misuse use cases -- and how to correct them: Part II: Eliciting and modeling use cases The Rational Edge, July 2002. • Miles & Hamilton, Ch. 2, Modeling requirements: Use cases [optional] | |
| 26 | Class 11 | Project/Team Organization • Burdman, J. (1999). Communication issues. In Collaborative Web Development: Strategies and Best Practices for Web Teams. Reading, MA: Addison-Wesley, 75-87. • Mark, G. (1998). Building virtual teams: Perspectives on communication, flexibility and trust. ACM SIGGROUP Bulletin, 19(3), 38-41. | This is the day we'll form teams! New: Information Gathering Plan New: Draft Models 1 & 2 New: Sign up for private meetings New: Final Project Deliverables |
| 28 | Class 12 | Artifact Models; Flow Charts • Beyer & Holtzblatt, Ch. 6, Work models: The artifact model, pp. 102-107. | |
| October | |||
| 3 | Class 13 | Class is cancelled. This class period should be used for team project meetings. | |
| 5 | Class 14 | Activity Models • Miles & Hamilton, Ch. 3, Modeling System Workflows: Activity Diagrams. • Pilone & Pitman, Ch. 9, Activity diagrams. • Bell, D. (2003). UML Basics Part II: The activity diagram. The Rational Edge, September 2003. [optional] | New: Work Models |
| 10 | Class 15 | Sequence and Decision Models • Beyer & Holtzblatt, Ch. 6, Work models: The sequence model, pp. 96-101. | Due: Information Gathering Plans |
| 12 | University Day | No classes until 12:30pm | |
| 17 | Class 16 | Flow Models • Beyer & Holtzblatt, Ch. 6, Work models: The flow model, pp. 89-96 | Due: Case Study 2 discussion leader comments |
| 19 | Fall Break | No classes | |
| 24 | Class 17 | Interpretation; Case Study 2 • Beyer & Holtzblatt, Ch. 7, The interpretation session. • 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: Work Models |
| 26 | Class 18 | Physical and Cultural Models • Beyer & Holtzblatt, Ch. 6, Work models: The physical model, pp. 115-123. • Beyer & Holtzblatt, Ch. 6, Work models: The cultural model, pp. 107-115. • Monk, A. & Howard, S. (1998).The rich picture: a tool for reasoning about work context. interactions, 5(2), 21-30. | Due: Project Draft Models 1 |
| Private team meetings with Prof. Gotz will be held October 26 - October 30. Sign your team up for a time slot via Sakai. | |||
| 31 | Class 19 | Entity-Relationship (ER) Models • 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) | |
| November | |||
| 2 | Class 20 | ER Models, Continued; Schedule Final Presentations | New: ER ModelDue: Case Study 3 discussion leader comments |
| 7 | Class 21 | Class is cancelled. This class period should be used for team project meetings. | |
| 9 | Class 22 | Data Dictionary and CRUD; Case Study 3 | |
| 14 | Class 23 | Card Sorting, Web Models, and Consolidation • Rosenfeld, L. & Morville, P. (2006). Information Architecture for the World Wide Web. O'Reilly. Ch. 10.7.2, Card sorting and Ch. 12.1 - 12.4, Design and Documentation • Beyer & Holtzblatt, Ch. 9, Creating one view of the customer. Read pp. 151-163. • Beyer & Holtzblatt, Ch. 11, Work redesign. "Directed skimming": please read all figures, captions, and hints. | Due: ER Model |
| 16 | Class 24 | User Environment Model; UI Prototyping; Accessibility (introduction) • Beyer & Holtzblatt, Ch. 15, The User Environment Design. Loiacono, E. (2004). Cyberaccess: Web accessibility and corporate America. Communications of the ACM, 47(12), 82-87. • Loiacono, E., Romano, N. & McCoy, S. (2009) The state of corporate website accessibility. Communications of the ACM, 52(9), 128-132. • Read about the Federal Government's Section 508 • Look at W3C's Web Accessibility Initiative, including the Web Content Accessibility Guidelines Overview | Due: Project Draft Models 2 |
| 21 | Class 25 | Accessibility (continued); Risk and Change; Design Ethics (introduction) • Lorenzi, N,. & Riley, R. (2000). Managing Change: An Overview. Journal of the American Medical Informatics Association, 7, 116-124. • Sicotte, C. et al. (2006). A risk assessment of two interorganizational clinical information systems. Journal of the American Medical Informatics Association, 13, 557-566. | Due: Case Study 4 discussion leader comments |
| 23 | Thanksgiving | No classes | |
| 28 | Class 26 | Design Ethics (continued); Case Study 4 • Friedman, B. (1996). Value-sensitive design. interactions 3(6), 17-23. • Shilton, K. (2010). Technology development with an agenda: Interventions to emphasize values in design. Proceedings of the ASIS&T 2010 Annual Meeting. • 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. | |
| 30 | Class 27 | Project Presentations | Due: Project Presentations |
| December | |||
| 5 | Class 28 | Project Presentations | Due: Project Presentations |
| 12 | Final Exam | Final deliverables due at 8:00 AM. | Due: Final specifications and presentation materials Due: Team evaluations |