Topics and due dates have been changed because we missed class on Tuesday, 1/27/04.

BASIC CONCEPTS IN SYSTEMS ANALYSIS

• Saddler, H. (2001). Design: understanding design representations. interactions, 8(4), 17-24. [e-journal, ACM Digital Library]

• The project

Tuesday, 1/13/04: User-centered analysis and design, the systems development life cycle

• Beyer & Holtzblatt, Ch. 1, Introduction. [textbook]
• Booch, G., Rumbaugh, J. & Jacobson, I. (1999). The Unified Modeling Language User Guide. Reading, MA: Addison Wesley. Ch. 1, Why we model. [e-reserve]
• Alter, S. (2001) Which life cycle --- work system, information system, or software? Communications of the Association for Information Systems, 7, Article 17. [e-journal]

Thursday, 1/15/04: SDLC, cont.

DEFINING THE PROBLEM AND GATHERING INFORMATION

• Davis, W. (1994). Business Systems Analysis and Design. Belmont, CA: Wadsworth Publishing Co. Ch. 2, Recognizing and defining the problem. [e-reserves]
• Barreau, D. K. (2001)."Making do": Adapting transaction systems to organizational needs. Library and Information Science Research, 23(1), 27-43. [e-journal]

• Assign problem definition. Due Thursday, 1/29/04.

Thursday, 1/22/04: Contextual inquiry; gathering information

• Beyer & Holtzblatt, Ch. 3, Principles of contextual inquiry. [textbook]
• Beyer & Holtzblatt, Ch. 4, Contextual inquiry in practice. [textbook]

Tuesday, 1/27/04: Class cancelled

Thursday, 1/29/04:Gathering information, cont.

• Wood, L. (1997). Semi-structured interviewing for user-centered design. interactions, 4(2), 48-61. [e-journal, ACM Digital Library]
• Simonsen, J. & Kensing, F. (1997). Using ethnography in contextual design. Communications of the ACM, 40(7), 82-88. [e-journal, ACM Digital Library]

• Problem definitions due

  PROBLEM DEFINITIONS

  PROJECT CHOICES

Tuesday, 2/3/04: Organizing for team projects

• Burdman, J. (1999). Communication issues. In Collaborative Web Development: Strategies and Best Practices for Web Teams. Reading, MA: Addison-Wesley, 75-92. [e-reserve]
• Mark, G. (1998). Building virtual teams: Perspectives on communication, flexibility and trust. ACM SIGGROUP Bulletin, 19(3), 38-41. [e-journal, ACM Digital Library]

• Form project teams.
• Assign information gathering plans. Due Tuesday, 2/10/04.

MODELING WORK

• Beyer & Holtzblatt, Ch. 5, A language of work. [textbook]
• Beyer & Holtzblatt, Ch. 6, Work models: The flow model, pp. 89-96. [textbook]
• Carrol, J. (2000). Five reasons for scenario-based design. Interacting with Computers, 13(1), 43-60. [e-journal]
• Alhir, S. (1998). UML in a Nutshell. O'Reilly. [e-reserves]
  • Ch. 4, A Unified Modeling Language tutorial: Use case diagrams, pp. 71-75.
  • Ch. 8, Use case diagrams.

• Example work models
• Assign flow/sequence models. Due Tuesday, 2/17/04.

Tuesday, 2/10/04: Modeling events and tasks, cont.

• Beyer & Holtzblatt, Ch. 6, Work models: The sequence model, pp. 96-101. [textbook]
• Lejk, M. & Leeks, D. (1998). An Introduction to Systems Analysis Techniques. London: Prentice Hall. Ch. 5, Specifying processes. [e-reserves]

• Information gathering plans due.
• Decision table and tree example

Thursday, 2/12/04: Modeling artifacts; modeling the organization culture; modeling the physical context

• Beyer & Holtzblatt, Ch. 6, Work models: The artifact model, pp. 102-107. [textbook]
• Beyer & Holtzblatt, Ch. 6, Work models: The physical model, pp. 115-123. [textbook]
• Beyer & Holtzblatt, Ch. 6, Work models: The cultural model, pp. 107-115. [textbook]
• Monk, A. & Howard, S. (1998).The rich picture: a tool for reasoning about work context. interactions, 5(2), 21-30. [e-journal, ACM Digital Library]

• Assign artifact/cultural models. Due Tuesday, 2/24/04.
• Assign draft integrated work models. Due Tuesday, 3/2/04.

Tuesday, 2/17/04: Interpreting and integrating data from multiple perspectives. Dr. Barbara Wildemuth, guest teacher

• Beyer & Holtzblatt, Ch. 7, The interpretation session. [textbook]

• Flow/sequence models due.

MODELING DATA

• Harrington, J. (2002). Relational Database Design Clearly Explained. San Diego: AP Professional. Ch. 2, Entities and data relationships. [e-reserves]
• Elmasri & Navathe. (2000). Fundamentals of Database Systems. Reading, MA: Addison Wesley. Ch. 3, Data modeling using the entity-relationship model. [e-reserves]

Tuesday, 2/24/04: Generalization and specialization, CRUD

• Elmasri & Navathe. (2000). Fundamentals of Database Systems, Reading, MA: Addison Wesley. [e-reserves]
  • Ch. 4.1, Subclasses, superclasses, and inheritance, pp. 73-75.
  • Ch. 4.2, Specialization and generalization, pp. 76-79.
  • Ch. 4.3, Constraints and characteristics of specialization and generalization, pp. 80-86.

• Artifact/cultural models due.

Thursday, 2/26/04: Data dictionaries

• Davis, W. (1994). Business Systems Analysis and Design. Belmont, CA: Wadsworth Publishing Co. Ch. 4, Information gathering: The data dictionary, pp. 81-90. [e-reserves]

• Assign optional artifact makeup model. Due no later than Thursday, 3/18/04.
• Assign entity-relationship model and data dictionary. Due Tuesday, 3/16/04.
• Assign project entity-relationship model and data dictionary draft. Due Tuesday, 3/23/04.

Tuesday, 3/2/04:ER/DD exercise

• Draft integrated work models due.

Thursday, 3/4/04: Object-oriented analysis

• Watson, H.J., Wixom, B.H., Buonamici, J. D. & Revak, J. R. (2001). Sherwin-Williams' data mart strategy: Creating intelligence across the supply chain. Communications of the Association for Information Systems, 5, Article 9. [e-journal]
• Montlick, T. (1995-1999). What is object-oriented software? Software Design Consultants, LLC. [web]
• Satzinger, J. & Orvik, T. (1996). The Object-Oriented Approach: Concepts, Modeling, and Systems Development Danvers: Boyd & Fraser. Ch. 4, Basic object-oriented concepts. [e-reserves]

Tuesday, 3/9/04 & Thursday 3/11/04: Spring Break, no class

FROM ANALYSIS TO DESIGN

• Beyer & Holtzblatt, Ch. 8, Consolidation. [textbook]
• Beyer & Holtzblatt, Ch. 9, Creating one view of the customer. [textbook]
• Beyer & Holtzblatt, Ch. 11, Work redesign. [textbook]
• Beyer & Holtzblatt, Ch. 12, Using data to drive design. [textbook]
• Beyer & Holtzblatt, Ch. 13, Design from data. [textbook]

• Entity-relationship diagram and data dictionary due.

Thursday, 3/18/04: Risk.

• Keil, M., Cule, P., Lyytinen, K. & Schmidt, R. (1998). A framework for identifying software project risks. Communications of the ACM, 41(11), 76-83. [e-journal]
• Cule, P., Schmidt, R. Lyytinen, K. & Keil, M. (2000). Strategies for heading off IS project failure. Information Systems Management, 17(2), 65-73. [ejournal, use pdf version]
• Yen, D. & Davis, W. (1999). Risk payoff analysis. In Davis, W. & Yen, D., The Information System Consultant's Handbook: Systems Analysis and Design. Boca Raton: CRC Press, 301-305. [e-reserves]

• Optional artifact makeup model. due.

Tuesday, 3/23/04:Practical Matters #1: Costs, benefits, budgets

• Shtub, A., Bard, J. & Globerson, S. (1994). Project Management: Engineering, Technology, and Implementation. Englewood Cliffs, NJ: Prentice Hall. [e-reserves]
  • 3.4, Benefit-cost analysis, pp. 117-126.
  • 3.5, Cost-effective analysis, pp. 126-130.
  • 3.6, Issues related to risk, pp. 130-136.

• Project entity-relationship diagram and data dictionary due.
• Assign Budgeting and Scheduling. Due Tuesday, 4/6/04.
• Assign ER Makeup Assignment, due no later than Thursday, 4/1/04.

Thursday, 3/25/04: Practical Matters #2: Scheduling and project management

• Lientz, B. & Rea, K. 91995). Project Management for the 21st Century. San Diego: Academic Press. Ch. 5, Setting up the project plan, pp. 67-84. [e-reserves]
• Shtub, A., Bard, J. & Globerson, S. (1994). Project Management: Engineering, Technology, and Implementation. Englewood Cliffs, NJ: Prentice Hall. [e-reserves]
  • 7.5, Gantt chart, pp. 322-325.
  • 7.6, Activity-on-arrow network approach for CPM analysis, pp. 326-338.
• Armour, P. (2002). Ten unmyths of project estimation. Communications of the ACM, 45(11), 15-18. [e-journal, ACM Digital Library]

Tuesday, 3/30/04: Evaluating design alternatives - implications for workers.

• Beyer & Holtzblatt, Ch. 14, System design. [textbook]
• Huff, C. (1996) Unintentional power in the development of computer systems. Computers & Society, 26(4) 6-9. [e-journal, ACM Digital Library]
• Friedman, B. (1996). Value-sensitive design. interactions 3(6), 17-23. [e-journal, ACM Digital Library]

Thursday, 4/1/04: Discussion of teams' ideas for project design

• ER makeup assignment due.

IMPLEMENTATION ISSUES

• Beyer & Holtzblatt, Ch. 15, The user environment design. [textbook]

• Budget and scheduling assignment due.
• State transition diagram examples

Thursday, 4/8/04: User interface design; prototyping; communication

• Brown, J. S. & Duguid, P. (1996). Keeping it simple. In Winograd, T. (ed.). Bringing Design to Software. New York: ACM Press; Reading, MA: Addison-Wesley, 129-145. [e-reserves]
• Beyer & Holtzblatt, Ch. 17, Prototyping as a design tool. [textbook]
• Beyer & Holtzblatt, Ch. 18, From structure to user interface. [textbook]
• Beyer & Holtzblatt, Ch. 10, Communicating to the organization. [textbook]

Tuesday, 4/13/04: Managing the change process

• Regan, E. & O'Connor, B. (1994). End-User Information Systems: Perspectives for Managers and Information Systems Professionals. New York: Macmillan. Ch. 10, Organizational change. [e-reserves]
• Markus, L. & Benjamin, R. (1996). Change agentry -- the next IS frontier. MIS Quarterly, 20(4), 385-407. [e-journal]

Thursday, 4/15/04: Change, cont.; course evaluation

• Hackney, R. & McBride, N. (2002). Non-implementation of an IS strategy within a UK hospital: Observations from a longitudinal case analysis. Communications of the Association for Information Systems, 8, Article 8, 130-140. [e-journal]

Tuesday, 4/20/04: Team presentations

1. Optimizing Project Appraisals for Traffic Counting Services
2. Strong's Coffee
3. Study Abroad/Financial Aid
4. NCSU Conflict of Interest Reporting System

Thursday, 4/22/04: Team presentations

1. Branch's Bookshop Inventory & Maintenance
2. NC Reportable Disease Card
3. Needs Assessment for SOP Management System
4. CPC Form From Hell

Thursday, 4/29/04, 4:00 p.m.: Project specifications and team evaluations due.