Syllabus
Systems Analysis
INLS 162-001, Spring 2004
| Instructor: Stephanie W. Haas |
Email:
stephani@ils.unc.edu |
| Office: 305 Manning Hall |
Phone: 919-962-8360 |
| Office Hours: Tuesday & Thursday, 2:00-3:00,
by appointment, and drop in. |
| Class Meetings: Tuesday & Thursday,
3:30-4:45, 307 Manning Hall. |
Course Description
This course will introduce the basic concepts underlying systems
analysis,
focusing on contextual inquiry/design and data modeling, and the
application of those analysis techniques in the analysis and design of
organizational information systems.
Course Objectives
- Develop an understanding of the role of
information systems in modern
organizations.
- Become familiar with a variety of information systems
analysis and problem-solving tools and approaches.
- Gain practical experience with information systems analysis
and design, working as part of a project team.
Textbook and Readings
Beyer, H. & Holtzblatt, K. (1998). Contextual Design:
Defining Customer-Centered Systems. San Francisco: Morgan
Kaufmann.
Additional readings are on
e-reserve ("[e-reserve]") or
available
via the Web ("[e-journal]" or "[web]").
Class Policies
- I will always be prepared for class, and
will start class on time.
If unforeseeable circumstances prevent this for
any reason,
I will try to notify you
beforehand if at all possible. I expect the
same of my students:
be prepared for class, be ready
to start class on time, and try to let me know
if you can't be there.
- You are encouraged and expected to participate in discussions.
- Reading assignments should be done before
the class for which
they are assigned
so you can ask questions and participate in
discussions.
- Assignments must be passed in at the beginning
of the class in
which they are due. The assignment description will
specify whether the assignment should be emailed to me
or handed in on paper.
- If there is something you don't understand,
ask a question!
If you don't want to ask
during class, please come see me at some other time.
-
If your team is having difficulty with some aspect of your project, please
come to see me. One of the educational outcomes of this class
should be an increase in your effectiveness in getting advice from
more experienced colleagues.
- The Honor Code, which prohibits giving or receiving unauthorized aid
in the completion of assignments, is in effect in this class. The
Instrument of Student Judicial Governance gives examples of actions that
constitute
academic dishonesty.
There are some specific guidelines for this class.
- You may give and receive assistance regarding the use of hardware and
software.
- I encourage you to discuss issues raised in class or by the readings
with
each other. You may also ask your classmates for clarification of class
notes.
- Individual home work assignments are to be done individually. You may
consult the course readings, your notes, and even other print or web
sources. (Keep in mind, however, that what you find in other sources may
not be consistent with what I want you to do.) You may not consult your
classmates or other people; all questions should be addressed to me.
- Team assignments are to be done as a team, with the team taking
responsibility for all products. Work on the project should be
distributed equitably among team members. I expect team members to
discuss, consult, and even debate with each other about the project
throughout the term.
Class List
Please subscribe to the class list. Go to the
mailing lists home page. The
list name is inls162_001. I will send
out a test message or two the first week of class. I will use
the list to send out announcements. You can use the list to
ask questions of the class in general, to share helpful hints
about software, etc. To post to the list, you can send email
to inls162_001@listerv.unc.edu, or go to the list's web page.
Assignments and Grading
Your grade will be based on individual assignments (45%),
a team project (45%), and class and team participation (10%).
Individual work
Problem definition: 9%
Flow/sequence models: 9%
Artifact/cultural models: 9%
Entity-relation diagram and data dictionary: 9%
Budgeting and scheduling: 9%
Team project work
Information gathering plan: 10%
Final specifications, including presentation to class/client: 35%
Participation (class and team): 10%
All assignments will be graded on the following scale
(graduate/undergraduate):
- 95 - 100% H / A
- 90 - 94% P+ / A-
- 85 - 89% P / B+, B, B-
- 80 - 84% P- / C+, C
- 70 - 79% L / C-, D
- 69% and below F
This page was last modified on December 22, 2003, by Stephanie W. Haas.
Address questions and comments about this
page to Stephanie W. Haas at
stephani@ils.unc.edu
© 2002, 2003 Stephanie W. Haas All rights reserved.