CIS 203 – Systems Analysis and Design – Fall
2008
Syllabus
Instructor
Information:
|
Name: Shawn Lupoli Adjunct Professor of CIS |
Office: n/a |
|
|
E-mail: slupoli@frederick.edu NOTE: Students
must use Blackboard to send e-mails and follow the e-mail rules provided
below. All student e-mail accounts
must originate from the MyFCC.frederick.edu system to avoid deletion by the
SPAM filters or firewalls. |
Phone
Number: 410/455-6965 301/846-2505
(dept) |
|
|
Office Hours: n/a |
Campus Mail Box Number:
TBA |
|
Course
Information:
|
Credits: 3 |
Last Day to Drop: Monday, November 3, 2008 |
|
Prerequisites:CIS106 |
Co-requisites: None |
|
Meeting Day(s): Wednesday (NOTE: Major Team Project Groups will meet outside of
class as scheduled by the group’s membership.) |
Meeting Time(s): 5:00 p.m. to 6:15 p.m. |
Course
Description:
|
Presents concepts of structured systems analysis and
design techniques such as problem definition, cost analysis, charting and
scheduling, implementation planning and documentation. Emphasizes project management,
communications and analytical skills. |
Core
Learning Outcomes: By the completion of the course
students will be able to:
|
1. demonstrate
the role of a systems analyst |
|
2. analyze
systems feasibility and requirements |
|
3. develop systems proposals, prototypes, data
flow diagrams, procedures and objects. |
|
4. describe
systems specifications |
|
5. design effective input, output, user
interfacing, file/database management. |
|
Class discussion, Lecture, Small Group Interaction,
Laboratory Work, Interactive Web Site. |
|
Systems
Analysis and Design in a Changing World, 5th ed.,
Satzinger, Jackson and Burd, Course Technology, 2009 {Required} |
|
NOTE: Additional Software Usage may be required. Additional Handouts will be provided |
Tests
/ Papers / Projects
|
Point
Value
(Percentage)
|
Final
Grade Scale |
Projects
(5 @ 50 points each)
|
25% |
90-100% = A |
On-Line
quizzes (10 @ 10 points each)
|
10% |
80-89% = B |
Major
Team Project (200 points)
|
20% |
70-79% = C |
Exams
(Midterm & Final – 200 points each)
|
40% |
60-69% = D |
Participation
& In-Class Labs (50 points)
|
5% |
Less
than 60% = F |
|
Assignments: All projects must be prepared on computer and be neatly
organized. To receive credit for a
project, the project must: A. make use of good structure and
appropriate design technique B. use appropriate indentation for all
pseudocode or coding C. adhere to project specifications
(these may be given during lecture) D.
be well organized and neatly prepared E.
include all appropriate documentation
and graphical presentations A project that only solves the
problem in a minimal manner will receive a “C” grade. Higher grades are reserved for exceptional
effort. If an assignment is late, ten percent
(10%) may be deducted for each day it is late; and it will be accepted at the
discretion of the instructor and ONLY if the assignments have NOT been
returned to the class. Assignments
will NOT be accepted after the last class. If you miss a day when an in-class
project is scheduled, you will not be allowed to make up the project unless
you notify the instructor of your absence prior to that class. Team Projects Late Team Projects will not be
accepted. Each team will have a leader
appointed by the instructor. The
instructor will determine the Major Team Project Score, but a survey of the
individuals in a team may be used in determining each student's major project
grade. Typically a majority vote of
the students should govern what the team does, but individual team members
may appeal to the instructor for intervention. The instructor may pass guidance to the
team through the leader. Make Up Exams and Quizzes: If it is necessary to miss an exam or quiz, you will be
allowed to take a MAKE-UP ONLY if you have a valid excuse and have notified
your instructor beforehand. If you
want to make up an exam, it is your responsibility to schedule a time for the
make-up exam before the next scheduled class. Failure to follow this procedure may
result in NO MAKE-UP EXAM!!! The type
of make-up exam is left to the instructor's discretion and may include essay
exams. |
||
|
1.
You must use your FCC provided MyFCC e-mail address for
your correspondence in this class. 2.
If your are not sending an e-mail from Blackboard, your
subject line must end with CIS_203_HYB1 3.
Each e-mail message must pertain to only one topic and
the subject line should contain the name of the assignment, followed by your
class number. E-mail should pertain
to only topic
e.g., Clarify the use of Polymorphism in the UML
Diagram for Assignment 4 and you should include your full name in the message
body. 4.
Examples of proper subject lines: a.
Question about grade on Assignment 4: CIS_203_HYB1 b.
Missed class on Tuesday: CIS_203_HYB1 5.
The student should expect to receive a reply to
electronic communications within 48 hours, not including weekends. 6.
Assignment instructions will be given by the instructor
and are typically not to be e-mailed. |
|
You will receive a progress report in Blackboard’s Grade
Book by the end of the sixth week of classes.
However, feel free to discuss any problems or conflicts concerning
this course with me at any time. |
|
Class and on-line sessions attendance is required. Absence from class or a session does not
excuse a student from completing assignments, quizzes, examinations or other
requirements of the course on time.
For each unexcused absence exceeding one, 2 percentage points will be
deducted from your final course grade. Excused absences include emergencies,
religious holidays, and official college functions or closing. Notify me beforehand if it is necessary for
you to miss class. |
|
Software that is copyrighted is
intended for use in its original form.
Duplicate copies can be produced only if written the manufacturer
grants permission. The |
|
Each student is expected to perform his/her own academic
work. Plagiarism and other forms of
academic dishonesty are considered an extremely serious offense. The student
is personally responsible for understanding the various forms of academic
dishonesty as they are explained in the "Student Code of Conduct"
in the Student Handbook. Ignorance of
any requirement for academic honesty will not constitute an excuse from
disciplinary proceedings. Any form of cheating will be considered grounds for
failure of the course. |
|
The instructor reserves the right to adjust the
assignments or schedule. This may also
change the date(s) of one or more of the exams. Any affected assignment due dates may also
be adjusted. In the event the schedule
is adjusted, the student will remain responsible for all work listed in this
syllabus. |
|
Class |
Date |
Subject |
Content |
Assignments |
|
1 |
27-Aug |
Introductions |
§ Introductions and course
overview. § Student Interviews |
|
|
On-Line |
|
Chapter 1 |
The
World of the Information Systems Analyst § Analyst as a Business
Problem Solver § Systems that Solve
Business Problems § Skills of a Systems
Analyst § Environment surrounding
the analyst § Analyst’s role in
strategic planning § Rocky Mountain
Outfitters and its strategic information systems plan § Analyst as a system
developer (the heart of the course) |
|
|
2 |
3-Sep |
|
Review of
Chapter 1 In-Class
Laboratory – Problem Solving |
Project 1 |
|
On-Line |
|
Chapter 2 & On-Line Appendix A |
Approaches
to Systems Development § Systems Development Life
Cycle (SDLC) § Methodologies, Models,
Tools & Techniques § Traditional & Object Oriented
Approach § SDLC Variations § Current Trends in
Development § Tools to Support System
Development Principles
of Project Management |
Quiz 1 |
|
3 |
10-Sep |
|
Review of
Chapter 2 In-Class
Laboratory – Tools Investigation |
|
|
On-Line |
|
Chapter 3 & On-Line Appendix B & Guide to MS
Project |
The
Analyst as a Project Manager § Project Management § Project Initiation &
Planning § Project Definition § Schedule Production § Confirming Feasibility,
Staffing & Launching PERT/CPM Charts On-Line Guide to MS Project |
Quiz 2 |
|
4 |
17-Sep |
|
Review of
Chapter 3 & Appendix A In-Class
Laboratory - Microsoft Project |
Project 1 Due Project 2 |
|
On-Line |
|
Chapter 4 |
Investigating
Systems Requirements § The Analysis Phase in
More Detail § Functional and Technical
Requirements § Stakeholders—the Source
of System Requirements § Techniques for
Information Gathering § Business Process
Reengineering § Validating the
Requirements |