LIS 453: Systems Analysis and
Management
Caroline Haythornthwaite and Bryan Heidorn
Spring 2007, GSLIS, UIUC
GSLIS
Students: Will find course information on Moodle.
http://courses.lis.uiuc.edu/course/view.php?id=36
Systems analysis is
the process of determining requirements for a
system to be implemented by systems designers and programmers. It
requires communication with current users, stakeholders, and innovators
to understand the nature of the tasks, interactions and data associated
with the project. The systems analyst is not a passive recipient of
such information - they use this input along with what they know about
the area, the type of task, other kinds of similar implementations, and
the nature of the use and users of the final system to create a viable
plan for implementation. In coordination with the design team receiving
that plan, the systems analyst works on specifying details from high
level architecture to low level specific details.
Understanding the fundamentals of systems analysis is as important for
those expecting to engage with vendors on buying systems as it is for
those expecting to create systems. In both cases, it is highly
important to understand the way computing systems are created so that
discussions of systems are two-way conversations rather than one-way
sales or promotion.
Basic approach for this course
We
will be learning about the systems analysis process, with concentration
on how to collect information and specify requirements using UML
modeling. The work will
be grounded in a semester long project. The course is
suitable for students with any background. Those with no computing
background are particularly encouraged to join the class.
Text for the course
Systems Analysis and Design with UML
Version 2.0: An Object-Oriented Approach (2005) by Alan Dennis,
Barbara Haley Wixom, David Tegarden.
Generally
one or two chapters from the text will be assigned each week, and other
readings as assigned for class discussion. See below or notes with
individual weeks. NB. Updates will be made on the Moodle pages.
Topics and Readings by Week
Jan. 16 .... Chapter 1. Intro to systems analysis
Jan. 23 .... Chapter 2. Intro to object oriented
systems analysis
What is a digital library? Digital
Library Federation
http://www.diglib.org/
Read the descriptions under the tabs for Collect, Produce, Preserve,
Use, Build
Jan. 30 .... Chapter 3. Project Initiation &
Chapter 4. Project Mgt
Feb. 6 ..... Chapter 5. Requirements Determination
Two
page intro to ACM issue: Holtzblatt, K. & Beyer, H.R.,
Requirements gathering: the human factor. Communications of the ACM, 38(5),
p. 31-32.
Beyer, H. R., & Holtzblatt, K. (1995). Apprenticing with the
customer. Communications of the ACM,
38(5), 45-52.
Star, S. L. & Strauss, A. (1999).
Layers of silence, arenas of voice: The ecology of visible and
invisible work. CSCW, 8
(1-2), 9-30.
Feb. 13 .... Chapter 6. Functional Modeling
Feb. 20 .... Chapter 7. Structural Modeling
Feb. 27 .... [Chapter 8. Behavioral modeling:
optional]
Dynamic
processes
Marty,
P. (2005). Factors influencing the co-evolution of computer-mediated
collaborative practices and systems: A museum case study.
Journal of Computer-Mediated
Communication, 10(4), article 12.
http://jcmc.indiana.edu/vol10/issue4/marty.html
Brown, B.A.T. (2001). Unpacking a
timesheet: formalisation and representation. CSCW, 10(3-4), 293-315.
Weick, K. E., & Roberts, K. (1993).
Collective mind in organizations: Heedful interrelating on flight decks.
Administrative Science Quarterly, 38,
357-381.
Mar. 6 ..... Chapter 9. Design
CSCW
& Distributed work
Mar. 13 .... Chapter 10. Class and Method Design
Mar. 20
... March Break.....
Mar. 27 .... Chapter 11. Data Mgt Layer Design
Apr. 3 ..... Chapter 12. HCI
[Chapter 13. Physical Layer, optional]
Brown. J. S. & Duguid, P. (1994).
Borderline issues: Social and material aspects of design. Human-Computer Interaction, 9, 3-36.
Nielsen: from Usability Engineering,
Chpt 1, Executive summary; Chpt 2, What is usability; Chpt 6, Usability
Testing; Chpt 7, Usability assessment methods beyond testing.
Apr. 10 .... Chapter 14. Construction
Apr. 17 .... Chapter 15. Installation and Operations
Rogers, E. (1995) Elements of diffusion. Chapter 1 In Diffusion of Innovations, 4th edition.
NY: The Free Press. (pp.
1-37).
Apr. 24 .... Extras
[some options, to be finalized]
Gaver, W.W., Dunne, A., Pacenti, Elena
(1999). Design: Cultural probes. Interactions,
6(1), 21-29.
Star, S. L. & Griesemer, J. (1989).
Institution ecology, translations, and coherence: Amateurs and
professionals in Berkeley's museum of vertebrate zoology, 1907-1939. S
ocial Studies of Science, 19,
387-420.
Twidale, M. B., Nichols, D. M. & Paice, C. D. (1997). Browsing is a
collaborative process.
Information
Processing and Management, 33(6), 761-783.
Twidale,
Michael (no date). Over-the-shoulder learning: Supporting brief
informal learning embedded in the work context. Available online at:
http://www.lis.uiuc.edu/~twidale/pubs/otsl1.html
Assignments
Assignments are all related to your project. Before creating the
final report, you and your group hand in early versions of parts of the
final:
Feb. 6: Project Notification/Problem Statement: Week 4 (group) 5%
Feb. 13: User Community Assignment: Week 5 (individual) 5%
Feb. 20: Functional Models: Week 6 (individual) 5%
Feb. 27: Reading Assignment: Week 7 (individual) 5%
Mar. 13: Structural Models: Week 9 (individual) 10%
Apr. 10: Database Assignment: Week 12 (not counting break) (group) 10%
Apr. 24 or May 1: Class Presentation of your Project: Weeks 14-15
(group) 10%
May 1: Complete written version of your case study: Week 15 (group) 40%
FOR MORE DETAILS SEE:
https://netfiles.uiuc.edu/pheidorn/www/LIS4532007/Assignments.html
And for details on the overall project, see:
https://netfiles.uiuc.edu/pheidorn/www/LIS4532007/Project.html