INLS 582_002, Systems Analysis

Schedule

1	January 9, 2014	Introductions / What is systems analysis?
Prep:	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. Prep slides, Information systems Information systems followup questions Project specifications
In class:	Part 1: Introductions Review syllabus Select discussion leaders for case study 1 Part 2: Course project discussion Sellen and Harper reading discussion
Assignment:	Post at least one message to Sakai discussion boards before class on Thursday, January 16. Discussion leaders for Case Study 1 send me discussion cues via e-mail by Monday, January 13. Everyone else: submit preferences for leading Case Studies 2-4, via e-mail, by Thursday, January 16. Complete Assignment Zero by Thursday, January 23.

2	January 16, 2014	Case Study 1 / Systems Development Life Cycle / Models
Due:	Monday, 1/13/2014: Case Study 1 Discussion leader discussion cues. Thursday, 1/16/204: Case studies 2-4 preferences.
Prep:	Part 1: Prep slides: Systems Development Life Cycle Beyer & Holtzblatt, Chapter 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. Part 2: Prep slides, 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 lane. (Raleigh) News & Observer, June 5, 2012.
In class:	Part 1: Case Study 1, leaders TBD Systems Development Life Cycle (SDLC) Part 2: Models Discuss problem definition assignment
Assignment:	Reminder: Complete Assignment Zero by Thursday, January 23.

3	January 23, 2014	Problem Statements / Info Gathering / Contextual Inquiry
Due:	Thursday, 1/23/2014: Assignment Zero
Prep:	Part 1: Prep slides: Problem statements 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. Part 2: Prep slides: Contextual Inquiry Beyer & Holtzblatt: Chapter 2: Gathering Customer Data, and Chapter 3: Principles of contextual inquiry 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.
In class:	Part 1: Discussion: Admissions Disasters Part 2: Discussion: Clutter
Assignment:	Problem definitions due Thursday, February 6.

4	January 30, 2014	Contextual Inquiry, cont'd / Project Management
Prep:	Part 1: Prep slides: Contextual Inquiry, cont'd Beyer and Holtzblatt, chapter 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. Part 2: Prep slides: Project Management Browse the Project Management Institute's website, especially the "About Us" and "Certification" pages Armour, P. (2002). Ten unmyths of project estimation. Communications of the ACM, 45(11), 15-18.
In class:	Part 1: Course business/questions Contextual interviews Group discussion of readings Part 2: Project management: good, bad, ugly Group exercise: physics lab re-redux
Assignment:	Reminder: Problem definitions due Thursday, February 6.

5	February 6, 2014	Scenarios, Personas, Use Cases
Due:	Thursday, 2/6/14: Problem definitions
Prep:	Part 1: Prep slides: Scenarios and Personas Beyer and Holtzblatt, Ch. 5 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. Part 2: Prep slides: Use Cases Miles & Hamilton, Ch. 2, Modeling requirements: Use cases (optional) 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, June 2002.
In class:	Part 1: Scenarios and Personas Group discussion of Help Desk exercise Part 2: Use Cases Group discussion of Storm Tracker exercise
Assignment:	Timeline for project selection activities: I will post all problem definitions to course website by Monday, February 10. Please e-mail me THREE TO FOUR projects that you'd want to work on by Tuesday, February 11, at 11:59pm. Try to consider: Your interests: does it sound like a project you'd enjoy? Your skills: what can you contribute to this project? Your aspirations: does the project provide opportunities to learn a valuable technique? The problem: is the project feasible? Will the client be accessible? I will limit the problem definition list to candidate problems by noon, Thursday, February 13. Review the candidate problems before class on Thursday, February 13. In part 1 of our 2/13 class we will select problems and determine project groups.

7	February 20, 2014	Project speed dating! / Artifact models
Due:	Thursday, 2/20/14: Make sure you've read candidate definitions before class!
Prep:	Part 1: Review candidate problem definitions. Part 2: Prep slides: Artifact Models Beyer and Holtzblatt chapter 6: Work Models: the artifact model, pp 102-107 Artifact model example
In class:	Part 1: Project speed dating! Candidate problem definitions Part 2: Artifact models Carnegie artifact model exercise Sample solution to Carnegie artifact model exercise
Assignment:	Teams convene (in person or virtually) at least once before next class. Teams submit information gathering plans by Thursday, February 27. Work model exercise due Thursday, March 20.

8	February 27, 2014	Activity models / Decision models / Sequence models
Due:	Thursday, 2/27/14: Information Gathering Plans (one per team).
Prep:	Part 1: Prep slides: Flowcharts and 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] Activity model example and exercise Part 2: Prep slides: Decision models Prep slides: Sequence models Beyer & Holtzblatt, Ch. 6, Work models: The sequence model, pp. 96-101
In class:	Part 1: Activity diagrams Sample Carnegie activity model Part 2: Decision models, Sequence models Sample Carnegie decision models
Assignment:	Case study 2 discussion leaders (Caroline, Toby, Jon, Linda) submit draft discussion points to me via e-mail by Monday, March 3. Project Draft Models round 1 and progress reports to group workspaces by Thursday, March 27. Please complete the Mid-semester feedback questionnaire at your earliest convenience.

9	March 6, 2014	Flow Models / Case Study 2 / Interpretation
Due:	Monday, 3/3: Case study leader 2 discussion points, via e-mail. (Caroline, Toby, Jon, Linda)
Prep:	Part 1: Prep slides: Flow Models Beyer & Holtzblatt, Ch. 6, Work models: The flow model, pp. 89-96 Flow Model example Part 2: Prep slides: the Interpretation Session Beyer & Holtzblatt, Ch. 7, The interpretation session Case study 2: Swarm et al. (2013). A case study for combining technologies for the delivery of information literacy and community to students at remote locations using live synchronous video-conferencing. Journal of Web Librarianship 7, 215-230.
In class:	Part 1: Mid-semester debrief Project question/answer Flow Models Part 2: Case Study 2 Leaders for Case Study 2: Caroline, Toby, Jon, Linda The Interpretation Session
Assignment:	Reminder: Work model exercise due Thursday, March 20.

--	March 13, 2014	Spring Break
In class:	Spring break this week. No class!

10	March 20, 2014	Physical, Cultural, E-R, Semantic Models (oh my)
Due:	Thursday, 3/20/14: Individual Work Model assignments due.
Prep:	Part 1: Prep slides: Physical models Prep slides: Cultural models Beyer & Holtzblatt, Ch. 6, Work Models: The cultural model and The physical model, pp. 107-123. Monk, A. & Howard, S. (1998).The rich picture: a tool for reasoning about work context. interactions, 5(2), 21-30. Part 2: Prep slides: Content models Prep slides: Entity-relationship models Elmasri, R. & Navathe, S. (2007). Ch. 3, Data modeling using the entity-relationship ER) model, sections 3.1-3.4. In Fundamentals of Database Systems, 5th edition. Addison Wesley. (Note: Ch. 7.1-7.4 in later editions)
In class:	Part 1: Physical and Cultural Models Cultural model exercise Part 2: ER Models, part 1
Assignment:	Case study 3 discussion leaders (Mary Pat, Sam, Cameron, Laura P.) submit draft discussion cues to me via e-mail by Monday, March 24. Reminder: Project Draft Models round 1 and progress reports to group workspaces by Thursday, March 27.

11	March 27, 2014	ER Models, Continued / Data Dictionaries, CRUD / Case Study 3
Due:	Monday, 3/24/14: Case study 3 leader discussion prompts, via e-mail. (Mary Pat, Sam, Cameron, Laura P.) Thursday, 3/27/14: Project Draft Models Round 1 (in project dropboxes).
Prep:	Part 1: ER Practice Exercises Part 2: Prep slides: Data Dictionaries and CRUD Case Study 3: Laster et al. (2011). Transitioning from Marketing-oriented design to user-oriented design; a case study. Journal of Web Librarianship 5, 299-321.
In class:	Part 1: Schedule project presentations ER Models, continued Carnegie ER model exercise Carnegie ER model sample solution Part 2: Case Study 3 Leaders for Case Study 3: Mary Pat, Sam, Cameron, Laura P. Data Dictionaries, CRUD Carnegie CRUD
Assignment:	ER Model assignment, due Thursday, April 10.

12	April 3, 2014	ER Modeling Practice / Card Sorting / Web Models / Consolidation
Prep:	Part 1: ER modeling exercises (to come) Part 2: Prep slides: Web Models Prep slides: 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. Do a "directed skim" of this chapter: skim the text, read and understand all diagrams, captions, and sidebars.
In class:	Part 1: ER Model practice / open session Part 2: Web models, etc Card sort exercise
Assignment:	Project draft models 2 and progress report to group workspaces by Thursday, April 10. Reminder: Individual ER Model assignment due Thursday, April 10.

13	April 10, 2014	User Environment Design / Accessibility / Risk and Change
Due:	Thursday, 4/10: Project draft models 2 and progress reports. Thursday, 4/10: Individual ER Models.
Prep:	Part 1: Prep slides: User environment design Prep slides: Accessibility 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. In particular, check out: 508 Law Summary of 508 Standards Tools and Resources, particularly the Technology Tools subsection You don't have to read each item in detail; but get a sense of the breadth of accessibility concerns that Section 508 is meant to address. Explore the W3C's Web Accessibility Initiative, including the Web Content Accessibility Guidelines Overview Part 2: Prep slides: 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.
In class:	Part 1: User Environment Design UED example: MS Office products (as whim dictates) Accessibility Part 2: Risk and Change
Assignment:	Case study 4 leaders (Sarah, Lori, Gretchen) send draft discussion cues due via e-mail by Monday, April 14.

14	April 17, 2014	Design Ethics / Case Study 4
Due:	Monday, 4/14: Case study leader 4 discussion points, via e-mail. (Sarah, Lori, Gretchen)
Prep:	Part 1: Prep slides: 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. Kapor, M. (2006). Architecture is politics (and politics is architecture). Blog post on Mitch Kapor's Blog, 23 April 2006. Lockton, D. (2010). Design with Intent toolkit. Read the intro and browse through the card pack. Part 2: 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:	Part 1: Ethics Part 2: Case Study 4 discussion. Leaders for Case Study 4: Sarah, Lori, Gretchen
Assignment:	Groups prepare for presentations and submit presentation slideshows to group dropboxes by April 24.

15	April 24, 2014	Presentations / Wrap up
Due:	Thursday, 4/24: Group presentations to group dropboxes.
Prep:	Come to class with any final questions or remarks you have about the course.
In class:	Part 1: Final Presentations, order TBD. Part 2: Final notes and thoughts
Assignment:	Final project reports submitted to group dropboxes no later than Friday, May 2, 7:00pm. Plans for presenting final report to client in place or underway by Friday, May 2, 7:00pm. (Note that you are required to describe your client presentation plan in your final specifications) Evaluation of team members submitted to Sakai no later than Friday, May 2, 7:00pm.