COURSE SYLLABUS

Information Systems Analysis: Concepts and Practice, IST 654

Prerequisite/Corequisite: None

Audience: The course is intended primarily for students in the Master of Science in
Information Management program, though it can be of interest and value to students in other
programs.

Description:
Concepts and methods of systems analysis through decomposition and modeling. Extensive
practice with structured methodologies. Systems analysis and project management techniques.
Introduction to automated tools and technologies. Group project to apply skills.

Additional Course Description:

IST 654 is an introductory course covering the concepts and techniques of information systems
analysis and design (SA&D), including analysis skills as well as managerial issues. The course
covers techniques used by modern systems analysts and gives extensive practice with
structured methodologies and object-oriented techniques.

Modern organizations large and small need computerized information systems to function and
to maintain their competitive edge. Information systems should relieve organizations of the
burden of slow and cumbersome manual paper-based processes and enable them to conduct
business more efficiently and effectively. Information systems analysis is an important step
before implementing any computerized information system. Mistakes during the analysis stage
will significantly affect the later stages of system development and cost time and money to
correct.

Competence in information systems analysis is crucial to every modern information technology

professional, including those professionals highly demanded by the market such as systems
analysts, business analysts, web developers, information architects, database administrators,
network administrators or software engineers. This centrality is why courses in information
systems analysis are the core of IT programs worldwide.

Credits: 3 credits

Learning Objectives:
After taking this course, the students will be able to:
1. Define various systems analysis and design concepts and terminologies
2. Describe the stages of the system development life cycle model
3. Describe different methodologies and state-of-the-art developments in SA&D techniques and
methods
4. Compare, use, and synthesize different conceptual modelling techniques for systems
analysis (including ERDs, DFDs, and UML)
5. Apply logic modelling techniques (decision tree/table, structured English)
6. Address the managerial issues involved in SA&D
7. Model the importance of collaboration and communication during SA&D
 COURSE SYLLABUS Information Systems Analysis: Concepts and Practice, IST 654 2

Bibliography/Texts/SuppliesRequired:
Dennis, A., Wixom, B. H., & Roth, R. M. (2015). Systems analysis and design (6 ed., Syracuse
University Custom Edition). Hoboken, NJ: Wiley. ISBN: 9781119377184. Available from
https://www.redshelf.com/book/545384/systems-analysis-and-design-545384-9781119377184-
alan-dennis

Bibliography/Texts/SuppliesAdditional:
Visible Analyst Student Edition or QSee SuperLite. Visible Analyst Student Edition is available
for $49 direct from Visual http://www.visible.com/Products/Analyst/vastandard.htm. Instructions
for accessing QSee will be given in class.

Requirements:
This course provides knowledge and hands-on experience in systems analysis. To gain practice
and technical skills, class members will engage in discussions, collaborative and individual
assignments, and a group project. Discussions will assist in the ability to reflect on practical
issues and discuss these with colleagues. Individual problem sets will provide an opportunity to
demonstrate personal mastery of the topic. Collaborative assignments will compliment individual
ones as critical-skill-building exercises. A group project will be the culmination for the course
material and provide students opportunities to integrate their knowledge and to learn from each
other.

Note that many of the skills taught in this course will be reinforced through several alternative
presentations: an initial demo, an in-class pair-and-share exercise, an individual problem set,
and a team project assignment. The goal of these repetitions is to provide several repetitions for
you to master particularly important skills.

Problem sets. Three problem sets will be assigned during the semester: one each on use
cases, entity-relationship diagrams and data flow diagrams. These problem sets provide an
opportunity to practice the particular skill. Problem sets must be completed individually and
without reference to web resources other than the course text.

Project. The term project provides an opportunity for in-depth investigation of a specific systems
analysis case as well as a vehicle for you to exercise and receive feedback on your
communication and investigative skills. The goals are to become familiar with the techniques of
systems analysis and design and to expand your written communication skills. Each team will
work collaboratively on the systems analysis of a new system based on user requirements.

Different components of the project will be due on a regular schedule throughout the semester.
The intent of the frequent submissions is to keep your project team on schedule, to provide an
opportunity to practice the skills being discussed in class and to provide an opportunity for
frequent feedback. To achieve these goals, deadlines for the components will be strictly
enforcedlate components will not be accepted. Note that these components will be graded,
but the grade will be strictly for your feedback about that section so that you can revise it as
needed for the final submission. I do not expect that the initial submission will be at the required
final level but that it will improve to the required level with feedback and additional work.

Reports. Four short reports are required at different points in the course.

Two individual reports on your team process are required. At midsemester, you should
individually submit a one-page report describing the dynamics within your team (the team
dynamics report). This report is intended to help me identify individuals and teams that are
 COURSE SYLLABUS Information Systems Analysis: Concepts and Practice, IST 654 3

having trouble working together before it is too late to intervene. The points for the report are
given for submission.

At the end of the semester, you will submit an evaluation of your fellow team members
contributions to your project team (the team report). The assessments of your fellow team
members will be taken into account in determining your project grade. An individual who in the
opinion of the majority of other team members contributes less to the project will receive less
credit for the project (including the possibility of no credit in the case of no contribution). The
points for the report are given for submission.

Third, once the final project reports are submitted, you will select another teams project to read
and comment on (the peer project evaluation). The goal is to provide students with an
audience for their reports beyond just the instructor and for me to assess your ability to read,
critically evaluate, and comment on a systems analysis report.

Finally, a portion of learning comes from reflection. For this purpose, at the end of the course
you will submit a one- to two-page essay reflecting on the learning and experiences (the
reflective essay).

Class participation. Participation in general discussion is included in this portion of the grade. It
is important that you make a good-faith effort to contribute to class discussions. This means that
you need at least a substantive contribution to the discussion during every week of the class to
receive full credit for participation. Nonattendance in class for part of the semester will be
reflected in a decrease in this grade (and most likely in other grades as well). Part of the
participation grade will be assigned at midsemester and the remainder for the second part of the
semester.

Discussion. In addition to the general class discussions, there will be one separately graded
discussion during the course: a discussion of systems analyst careers in Week 2.

Grading:
Weighting for course assignments is given in the table below.

Percentage of Total
Format Description
Course Grade
Discussion 1 Systems analyst careers
Report 1 Team dynamics report
Participation 10 Participation for Classes 15
Problem set 10 Problem set on use cases
Problem set 10 Problem set on DFDs
Problem set 10 Problem set on ERDs
Presentation 5 Presentation of final projects
Participation 15 Participation for Classes 611
Project 35 Final group project
Report 1 Team reports
Report 1 Peer evaluation of reports
Report 1 Reflective paper
 COURSE SYLLABUS Information Systems Analysis: Concepts and Practice, IST 654 4

Assignments are due as specified on the learning management system. The penalty for late
assignments is 10% for submission within the first 24 hours (i.e., after the deadline until the
same time the next day), and an additional 25% for each week thereafter (i.e., before the start of
the next class). An exception to this rule is possible in an extreme circumstance in which there
is no reasonable way to anticipate or control the situation. Computers crashing, viruses, lost
files, etc., are specifically not grounds for an extensionat this point in your professional
careers, you should know how to manage your technical infrastructure.

According to the grading policy of the School of Information Studies, a basic grade will be
awarded for student performance that is judged to be satisfactory for the course level
(undergraduate or graduate). All other grades will be determined in comparison with the
standards of the basic grade. For graduate students the basic grade is B. Fulfilling the
requirements for an assignment coupled with the absence of errors (in writing, arithmetic,
formatting) will earn a grade no higher than B+. To earn an A- or A grade, the assignment must
go beyond the minimum expected in terms of quality (e.g., insight, creativity, analysis,
thoroughness, synthesis).

Failure to complete any course requirement (e.g., missing a problem set) will result in a course
grade of B or lower, regardless of the grades received on other components.

An incomplete grade, I, can be given only if the circumstances preventing the on-time
completion of all course requirements were clearly unforeseeable and uncontrollable. If an
incomplete is required, a written contract that specifies the missing work, the date by which it
will be completed, and the default grade that will be given if that deadline is missed must be
completed.

If you wish to discuss a grade, submit a written explanation of your argument and arrange for a
private conversation. Except for unusual circumstances, no appeal for an individual assignment
or project will be considered more than two weeks after the graded paper is returned. For final
course grades, no appeal will be considered more than two months after the final day of
classes.

It is unfair to allow some students additional opportunities, such as extra-credit assignments

without allowing the same options to all students. Accordingly, extra-credit assignments are not
possible.

Course-Specific Policies:
Conduct of discussions. It is expected that students will behave professionally both in language
and attitude when commenting or responding to discussions. Public disparagement of your
fellow students in this course is unacceptable and may result in disciplinary action. Additionally,
discussions should model your ability to think critically about course topics and articulate ideas
clearly. Responses should be detailed and explanatory. Simple unconstructive replies such as I
agree (or disagree) with the previous comment will not be considered valid unless elaborated
upon. If you have any concerns regarding the suitability of a comment (yours or anothers),
please contact the instructor.

Guidelines for preparing assignments. Prepare a professional document. Include tables and
graphs that support your content where appropriate.

When you prepare assignments or post on the discussion boards, be sure to provide proper
bibliographical information for any sources referenced, for direct quotations, and for the source
 COURSE SYLLABUS Information Systems Analysis: Concepts and Practice, IST 654 5

of key concepts or ideas. It is critical to include quotation marks and citations when you cut and
paste from any source. Any citation format is acceptable (I personally use APA format), as long
as it provides sufficient information for a reader to find the source (i.e., authors names; title of
article or book; title, volume, and issue of journal (if appropriate); page numbers; publisher; date
of publication). If you cite a web page, be sure to indicate the URL and the date on which you
accessed the page, as pages do change. Failure to cite sources is considered plagiarism and
subject to sanctions ranging from being required to redo the assignment through expulsion (see
above). If you have any questions about what must be cited or how to cite, please feel free to
ask.

In addition to punctuality, grammar, presentation, and ability to follow instructions are very
important, as in the real world. If your work does not meet professional standards, up to 30% of
your score may be deducted. It is essential that you spell check and proofread your documents.

In assignments you may be asked to offer opinions. As with discussions, simply stating your
opinion does not constitute a complete response. You must support any opinion with arguments
and evidence.

Academic Integrity Policy

Syracuse Universitys academic integrity policy reflects the high value that we, as a university
community, place on honesty in academic work. The pilot policy in effect at the School of
Information Studies defines our expectations for academic honesty and holds students
accountable for the integrity of all work they submit. Students should understand that it is their
responsibility to learn about course-specific expectations, as well as about university-wide
academic integrity expectations. The pilot policy governs appropriate citation and use of
sources, the integrity of work submitted in exams and assignments, and the veracity of
signatures on attendance sheets and other verification of participation in class activities. The
pilot policy also prohibits students from submitting the same work in more than one class
without receiving written authorization in advance from both instructors. Under the pilot policy,
students found in violation are subject to grade sanctions determined by the course instructor
and nongrade sanctions determined by the School or College where the course is offered. SU
students are required to read an online summary of the universitys academic integrity
expectations and provide an electronic signature agreeing to abide by them twice a year during
preterm check-in on MySlice. For more information and the pilot policy, see
http://academicintegrity.syr.edu.

For IST 654, you are permitted and encouraged to discuss course material with your
classmates, especially regarding group assignments. However, individual assignments should
not be worked on in a collaborative manner.

Disability-Related Accommodations
Syracuse University values diversity and inclusion; we are committed to a climate of mutual
respect and full participation. If you believe that you need accommodations for a disability,
please contact the Office of Disability Services (ODS), disabilityservices.syr.edu, located at 804
University Avenue, room 309, or call 315.443.4498 for an appointment to discuss your needs
and the process for requesting accommodations. ODS is responsible for coordinating disability-
related accommodations and will issue Accommodation Authorization Letters to students as
appropriate. Since accommodations may require early planning and generally are not provided
retroactively, please contact ODS as soon as possible. Our goal at the iSchool is to create
learning environments that are useable, equitable, inclusive, and welcoming. If there are
aspects of the instruction or design of this course that result in barriers to your inclusion or
 COURSE SYLLABUS Information Systems Analysis: Concepts and Practice, IST 654 6

accurate assessment or achievement, please meet with me to discuss additional strategies

beyond official accommodations that may be helpful to your success.

Religious Observances Notification and Policy

SUs religious observances policy, found at
supolicies.syr.edu/emp_ben/religious_observance.htm, recognizes the diversity of faiths
represented in the campus community and protects the rights of students, faculty, and staff to
observe religious holy days according to their tradition. Under the policy, students should have
an opportunity to make up any examination, study, or work requirements that may be missed
due to a religious observance provided they notify their instructors no later than the end of the
second week of classes through an online notification form in MySlice listed under Student
Services/Enrollment/My Religious Observances/Add a Notification.

Student Academic Work Policy

Student work prepared for University courses in any media may be used for educational
purposes if the course syllabus makes clear that such use may occur. You grant permission to
have your work used in this manner by registering for, and by continuing to be enrolled in,
courses where such use of student work is announced in the course syllabus.

I intend to use academic work that you complete this semester in subsequent semesters for
educational purposes. Before using your work for that purpose, I will either get your written
permission or render the work anonymous by removing all your personal identification.

Course Evaluations
There will be an end-of-course evaluation for you to complete this term, described below. This
evaluation will be conducted online and is entirely anonymous. You will receive a notification
from the Syracuse University Office of Institutional Research & Assessment (OIRA) department
in your e-mail account with the evaluation website link and your passcode.

End-of-semester evaluation will be available for completion in Week 10 prior to your final
exams week. This evaluation is slightly longer and it is used to gauge the instructor
performance and make adjustments to the course to ensure it meets our student needs.

We faculty work hard to do the best possible job when preparing and delivering courses for our
students. Please understand that not only does the school use the course evaluations to make
decisions about the curriculum in order to improve where necessary, but it also uses them to
make decisions about faculty members. Please take the time and fill out this evaluation as your
feedback and support of this assessment effort is very much appreciated.

Week/ Required
Topic Assignment Due
Lecture Reading
The context of systems
1 Ch. 1
analysis
Feasibility analysis and the Discussion of systems analyst careers
2 Ch. 2
system proposal Project proposal
3 Requirements determination Ch. 3 Project initial feasibility
4 Use cases and CASE tools Ch. 4 Project requirements
Project use cases
5 Process modelling Ch. 5
Team dynamics report
 COURSE SYLLABUS Information Systems Analysis: Concepts and Practice, IST 654 7

Week/ Required
Topic Assignment Due
Lecture Reading
Requirements problem set
6 Data modeling Ch. 6
Project DFD
Normalization and object-
7 Ch. 14 Project ERD
oriented analysis
Ch. 7
8 Moving into design DFD problem set
and 8
9 Interface design Ch. 9 ERD problem set
Object-oriented design and
Ch. 12
10 systems construction, Project Interface
and 13
deployment, and operations
11 Project presentations Project presentations
Project final paper
Team reports
Reflective paper
Peer project evaluations

All readings from Dennis, Wixom, & Roth, Systems Analysis and Design. Additional readings
may be provided online.