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. Classroom time will be divided into 2 sections with a 15 min break.
Detailed Schedule
| Date | 6:00PM-7:15PM | 7:30PM-8:45PM | |
|---|---|---|---|
| 01/16/2017 | No Class: MLK Holiday | ||
| 01/23/2017 Class 1 |
Introduction; Assign Case Study 1 Leaders • Check Sakai access • Review course syllabus, requirements, and policies |
Information Systems, Information Systems Analysis -- what are they? |
Due: Case Study 1-4 Preferences |
| 01/30/2017 Class 2 |
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. |
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: Due: Case Study 1 discussion leader comments; 8:00AM* |
| 02/06/2017 Class 3 |
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. |
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. |
New: Problem Definition |
| 02/13/2017 Class 4 |
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. |
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. |
Due: Problem Definition Due: Problem preferences due Wed 02/15/2017 @ 11am. |
| 02/20/2017 Class 5 |
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. |
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 |
| 02/27/2017 Class 6 |
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] |
Artifact Models; Flow Charts |
|
| 03/06/2017 Class 7 |
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] |
Sequence and Decision Models |
Due: Information Gathering Plans New: Work Models |
| 03/13/2017 | No Class: Spring Break | ||
| 03/20/2017 Class 8 |
Flow Models | Interpretation; Case Study 2 |
Due: Case Study 2 discussion leader comments; 8:00AM* Due: Work Models |
| 03/27/2017 Class 9 |
Physical and Cultural Models |
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) |
Due: Project Draft Models 1 |
| 04/03/2017 Class 10 |
ER Models, Continued; Schedule Final Presentations | Data Dictionary and CRUD; Case Study 3 |
New: ER Model Due: Case Study 3 discussion leader comments 8:00AM* |
| 04/10/2017 Class 11 |
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. |
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: ER Model Due: Project Draft Models 2 |
| 04/17/2017 Class 12 |
Accessibility (continued), Risk and Change • 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. |
Design Ethics • 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. |
Due: Case Study 4 discussion leader comments 8:00AM* |
| 04/24/2017 Class 13 |
Case Study 4; Course Wrap-Up • 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. |
Project Presentations | Due: Project Presentations |
| 05/01/2017 |
|||
| 05/08/2017 | Final deliverables due at 8:00 AM. | Due: Final specifications and presentation materials Due: Team evaluations |