School of Information and Library Science

University of North Carolina at Chapel Hill

Zari Kamarei

INLS 162-02, SYSTEMS ANALYSIS
FALL 2001
Monday, Wednesday 12:30-1:45
CLASS SCHEDULE


 
 
 

TEXTBOOK

Beyer, H., & Holtzblatt, K. (1998). Contextual Design: Defining Custom-Centered Systems. San Francisco: Morgan Kaufmann. [QA76.9 .S88 B493 1998]
 
 
BASIC CONCEPTS IN SYSTEMS ANALYSIS

Session 1, August 22
Introduction to course; What are information systems?



Session 2, August 27:
Analysis, design and modeling
  • Avison, D & Fitzgerald, G. (1999). Information Systems Development.  In Currie, W. & Galliers, B. Rethinking Management Information Systems.  Oxford:  Oxford University Press. 250-278. [HD 30.213 .R47 1999]
  • Beyer & Holtzblatt, Chapter 1, Introduction, p1-26
  • Booch, G., Rumbaugh, J, & Jacobson, I (1999). Ch.1, Why We Model
  • Gladwell, M. (1999). Clicks and mortar. New Yorker, 12/6/99, 106-115.



Session 3, August 29: (slides
The systems development life cycle
  • Davis, W. S. (1994). Business Systems Analysis and Design. Belmont, CA: Wadsworth. [T58.6 .D39 1994]
    • Chapter 1, Information systems analysis, p3-23

 
DEFINING THE PROBLEM

Session 4, September 5
Problem definition

  • Davis, W. S. (1994). Business Systems Analysis and Design. Belmont, CA: Wadsworth. [T58.6 .D39 1994]
    • Chapter 2, Recognizing and defining the problem, p25-57
  • Assign Problem Definition(Individual) 
Contextual inquiry as systems analysis
  • Beyer & Holtzblatt text, Chapter 3, Principles of contextual inquiry, p41-66

Session 5, September 10:
Interviews for collecting data

Session 6, September 17
Guest Speaker
  • Individual assignment due: Problem definition

  • Session 7, September 19
    Organizing for team projects
  •  Mark, G. (1998). Building virtual teams: perspectives on communication, flexibility and trust. ACM SIGGROUP Bulletin, 19(3), 38-41.
  • Brooks, F. (1995). The Mythical Man-Month. Reading, MA: Addison Wesley [QA 76.758 .B75 1995]
  • West, J. (1998). Building a high-performance project team. In. Cleland, D. (ed). Field Guide to Project Management. New York: John Wiley & Sons, Inc. 239-254.
  • Interview questions
  • Team ideas

  •  
    MODELS OF WORK IN ORGANIZATIONS

    Session 8, September 24:
    Modeling communication flows 


    Session 9, September 26
    Modeling sequences of events
    Detailed task modeling 
    • Beyer & Holtzblatt text, Chapter 6, Work models - The sequence model, p96-101
    • Lejk, M., & Leeks, D. (1998). An Introduction to Systems Analysis Techniques. London: Prentice Hall. [QA402 .L45 1998]
      • Chapter 5, Specifying processes, p58-73
    • Alhir, S. (1998). UML in a Nutshell, O'Reilly. Ch. 4, 71-75; Ch. 8.
    • Assign communication/sequence models (individual)

    Session 10, September 26:
    Modeling the artifacts used
    • Beyer & Holtzblatt text, Chapter 6, Work models - The artifact model, p102-107

    Session 11, October 1:
    Modeling the organizational culture;

    Session 12, October 3
    Modeling the physical context of the work 

    Session 13, October 8:
    Interpreting and integrating data from multiple perspectives
    • Beyer & Holtzblatt text, Chapter 7, The interpretation session, p125-136

     
     
    DATA MODELING

    Session 14, October 10: (slides)
    Semantic modeling; Entity-relationship diagrams 

    • Harrington, J. L. (1998). Relational Database Design Clearly Explained. San Diego: AP Professional. [QA76.9 .D26 H38 1998]
      • Chapter 2, Entities and data relationships, p11-42

    Session 15, October 15:
    Data dictionaries (slides)
    • Davis, W. S. (1994). Business Systems Analysis and Design. Belmont, CA: Wadsworth. [T58.6 .D39 1994]
      • Chapter 4, Information gathering (The data dictionary), p81-90

    Session 16, October 15:
    Example of multi-level sequence model
    Generalization/specialization structures (slides)
    • Elmasri, R., & Navathe, S. B. (2000). Fundamentals of Database Systems. 2nd ed. Redwood City, CA: Benjamin/Cummings. (QA76.9 .D3 E57 2000)
      • Enhanced-ER (EER) model concepts, Chapter 4.1-4.3 only

    Session 17, October 17
    Review of data modeling; Object-oriented analysis (slides)

     
    FROM ANALYSIS TO DESIGN

    Session 18, October 22:
    Consolidating the models

    • Beyer & Holtzblatt text, Chapter 8, Consolidation, p137-149
    • Beyer & Holtzblatt text, Chapter 9, Creating one view of the customer, p151-198

    Session 19, October 24
    A consolidated view of the data 
    • Beyer & Holtzblatt text, Chapter 11, Work redesign, p215-227
    • Beyer & Holtzblatt text, Chapter 12, Using data to drive design, p229-271

    Session 20, October 29:
    Data-driven design (slides)
    • Beyer & Holtzblatt text, Chapter 13, Design from data, p273-291

    Session 21, October 31:
    Evaluating design alternatives - costs, benefits, and risks(slides)
    • Shtub, A., Bard, J. F., & Globerson, S. (1994). Project Management: Engineering, Technology, and Implementation. Englewood Cliffs, NJ: Prentice Hall. [TA190 .S58 1994]
      • Section 3.4, Benefit-cost analysis, p117-126
      • Section 3.5, Cost-effectiveness analysis, p126-130
      • Section 3.6, Issues related to risk, p130-136
    • Yen, D. C., & Davis, W. S. (1999). Risk-payoff analysis. In Davis, W. C., & Yen, D. C., The Information System Consultant's Handbook: Systems Analysis and Design. Boca Raton: CRC Press, 301-305. [T57.6 .D378 1999]
    • Individual assignment due: Entity-relationship diagram and data dictionary

    Session 22, November 5:
    Evaluating design alternatives - implications for workers(slides
    • Beyer & Holtzblatt text, Chapter 14, System design, p295-315
    • Huff, C. (1996). Unintentional power in the development of computer systems. Computers & Society, 26(4), 6-9.
    • Friedman, B. (1996). Value-sensitive design. interactions, 3(6), 17-23.
    • Cule, P., Schmidt, R., Lyytinen, K. & Keil, M. (2000). Strategies for heading off IS project failure.  Information Systems Management, 17, 2, 65-73.
    • Meet with project groups

     
    IMPLEMENTATION ISSUES

    Session 23, November 7
    Scheduling the implementation project (slides

    • Lientz, B. P., & Rea, K. P. (1995). Project Management for the 21st Century. San Diego: Academic Press. [HD69 .P75 L54 1995]
      • Chapter 5, Setting up the project plan, p67-84 only
    • Shtub, A., Bard, J. F., & Globerson, S. (1994). Project Management: Engineering, Technology, and Implementation. Englewood Cliffs, NJ: Prentice Hall. [TA190 .S58 1994]
      • Section 7.5, Gantt chart, p322-325
      • Section 7.6, Activity-on-arrow network approach for CPM analysis, p326-338
    • Team project draft due: Entity-relationship diagram and data dictionary
    • Assign Budgeting and scheduling (Individual)

    Session 24, November 12:

    Discussion of teams' ideas for system design


    Session 25, November 14:
    Fitting the design to the work environment (slide)
    User interface design; Prototyping 
    • Beyer & Holtzblatt text, Chapter 15, The user environment design. p317-334
    • 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. [QA76.76 .D47 B745 1996]
    • Beyer & Holtzblatt text, Chapter 17, Prototyping as a design tool, p367-377
    • Beyer & Holtzblatt text, Chapter 18, From structure to user interface, p379-391
    • Friedman, B. (1996). Value-sensitive design. Interactions, 3, 6, 17-23

    Session 26, November 19
    Communicating the design and project plans (slides)

    • Beyer & Holtzblatt text, Chapter 10, Communicating to the organization, p199-212
    • Individual assignment due: Budgeting and scheduling



    November 21
    Thanks Giving Recess

    Session 27, November 26
    Managing the change process ; Course evaluation (slides)
    • Regan, E. A., & O'Connor, B. N. (1994). End-User Information Systems: Perspectives for Managers and Information Systems Professionals. New York: Macmillan. [HD30.213 .R44 1994]
      • Chapter 10, Organizational change, 390-411.
    • Markus, M. L., & Benjamin, R. I. (1996). Change agentry--the next IS frontier. MIS Quarterly, 20(4), 385-407.
    • Informal discussion of presentations


    Session 28, November 28:
    Team Presentations
    12:30-12:50  Phoenix 
    12:55-1:15 OTD..........
    1:20-1:40 FRIAD......

    Session28, December 3
    Team Presentations
    12:30-12:50 Library Instruction-
    12:55-1:15 Robertson Scholars
    1:20-1:40 TTA..........................

    Session 29, December 5
    Team presentations
    12:30-12:50 Techno Teachers
    12:55-1:15 KEL Library............
    1:20-140 Library Home Page

    Session 30, December 17  3:00 p.m.:
    Team project due: Final project documentation