|
prince george’s community college fall 2003
|
System analysis
CIS 284
course syllabus
Instructor: Sonia Washington
Office Location: M2013 inside M2011
Office Phone: (301) 322-0098
Email: washinsx@pgcc.edu
Office Hours:
Course Reference No: 6790
Class Days/Room: Mon. & Wed. Lanham 122
8:15am – 10:45am Lecture/LAB
SYSTEM ANALYSIS CIS 284
prince george’s community college’s motivated, committed, and intelligent students are ready to pursue a challenge!
System Analysis and Design Methods, 5th Edition, By: Jeffrey L. Whitten, Lonnie D. Bentley, Kevin C. Dittman
This course is built around a major team project, which will require all of your lab hours as well as additional outside research. The team project will account for half of your grade. The entire team will receive the same grade as 50% of the overall project grade. The other 50% of the project grade will be an evaluation of your own performance on the project. Other team members will evaluate you as to your specific contributions to the project, willingness to participate in team functions, meeting deadlines, accuracy of your work, etc. In addition to the team project, you will be graded on a research paper, oral presentations and written tests.
Proposal teams will be assigned early in the semester (no later than the third week). Each team will then work toward the presentation and delivery of the completed project during the last weeks of the semester.
Class discussions will center on the Systems Development Life Cycle. It is this highly structured process and the documentation that accompanies it that is the basis for effective systems analysis and design. Since the success of the course depends on group participation, regular, punctual attendance is required. It is a good idea to inform your team leader or myself of any planned unavoidable absences in order to be sure you do not miss the material presented.

COURSE SURVEY TOPICS:
q Describe fundamental information system concepts using a basic computer information systems vocabulary.
q Describe the principal characteristics of businesses as information systems and shared characteristics of systems and subsystems.
q Describe the components of effective communications, interviews, and technical writing used by systems analysts.
q Describe the purpose of the system team and identify the roles and responsibilities of the system team members.
q Describe and construct multilevel data flow diagrams and data dictionaries.
q Describe the phases of the Systems Development Life Cycle (SDLC): Study Phase, Design Phase, Development Phase, and the Operational Phase.
q Describe, develop, and evaluate Candidate Systems using weighted candidate evaluation matrices.
q Describe the identification of system processing, control, and test requirements.
q Describe the process of file normalization and its advantage.
q List the major principles of input and output design.
q List and describe the steps that are used by programmers to develop computer programs and to ensure that the programs function properly.
q Define and distinguish between the four major stages of the operation phase and the difficulties of changeover and the challenges of routine operation.
Group Project Objectives:
q Develop interactive group communications skills.
q Develop the use of concepts of systems analysis learned in the course.
q Develop the use of effective fact-finding skills.
q Develop the use of effective presentation skills.
q Develop an awareness of the benefits and difficulties in using the team concept.
Guidelines for the tests:
1. A student never takes a test late. However, if a foreseeable problem exists, I will try to arrange for you to take a test early.
2. Tests are returned during the class session after the test is taken (or on another date that I announce). Sometimes tests cannot be returned immediately because of time constraints. In these circumstances, they will be returned at the next regular class session.
3. During the class session in which we discuss a test or quiz, you may take any notes.
4. All tests are returned to me and are college property.
5. In general, tests are not cumulative. That is, Test 2 covers material covered after Test 1. The final test covers all chapters and material covered.
6. The Student Review is conduct by the students. Every student is to create a Question and Answer Test. The Question and Answer Test consist of at least 3 questions from each chapter with the CORRECT answer. This Review Sheet must be typed and ready to hand in during the assigned due date. The Instructor will select one or two people to conduct the Student Review Session. The Overall Questions will be typed in Microsoft PowerPoint. The class will be put in groups and compete against each other without using any notes or textbooks. SRQDue = Student Review Questions Due
7. Cheating will not be tolerated. Do not give reason for suspicion.
|
EXAMS AND GRADES |
|
|
Work |
Points |
|
Team Project:: Project Score – 25% |
250 |
|
Team Project:: Member Performance – 25% |
250 |
|
Two Tests – 10% each (100 points each test) |
200 |
|
Final Test – 15% |
150 |
|
Research Paper – 10% |
100 |
|
Oral Presentation – 5% |
50 |
|
Total Points |
1000 |
FINAL GRADES are calculated based on total point accumulation as follows:
900 – 1000 = A 800-899 = B 700 – 799 = C 600 – 699 = D Below 600 = F
|
WEEk |
DATE |
TOPIC
|
READING assignments |
5 mins. Oral Presentation Case # |
|
1 |
08/25/03 08/27/03 |
Syllabus, Paper Selections, Profile,Ch1 Players in the Systems Game and Information System Building Blocks |
Syllabus – CH1 and 2 CH 3 and 4 |
|
|
2 |
09/01/03 09/03/03 |
College Closed – LABOR DAY Information System Development and Project Management |
CH 5 |
1 |
|
3 |
09/08/03 09/10/03 |
Systems Analysis Requirements Discovery and Exercise (Teams Assigned) |
CH 6 SQRDue#1
|
2 3 |
|
4 |
09/15/03
09/17/03 |
Student Review for Test 1 & Read Project TEST 1 (CH 1-6) & Project LAB Begins
|
CH 7 |
4
|
|
5 |
09/22/03 09/24/03 |
Data Modeling and Analysis Process Modeling |
CH 8 CH 9 |
5 6 |
|
6 |
09/29/03 10/01/03 |
Feasibility Analysis/ System Proposal System Design |
CH 10 CH 11 |
7 8 |
|
7 |
10/06/03
10/08/03 |
Application Architecture/Modeling
Database Design & Student Review for Test 2 |
CH 12 & SQRDue#2
R. Paper Due
|
9
10 |
|
8 |
10/13/03 10/15/03 |
TEST 2 (CH 7-12) Output Design & Prototyping |
CH 13 CH 14 |
|
|
9 |
10/20/03 10/22/03 |
Input Design & Prototyping User Interface Design |
CH 15 CH 16 |
|
|
10 |
10/27/03 10/29/03 |
System Construction/Implementation No CLASSES – Professional Day! |
CH 17 & SQRDue#3
|
|
|
11 |
11/03/03
11/05/03 |
System Operations and Support & Student Review for Test 3 Final Test 3 (CH 1-17) |
|
|
|
12 |
11/10/03 11/12/03 |
GROUP PROJECT GROUP PROJECT |
|
|
|
13 |
11/17/03 11/19/03 |
GROUP PROJECT GROUP PROJECT |
|
|
|
14 |
11/24/03 11/26/03 |
GROUP PROJECT GROUP PROJECT |
|
|
|
15 |
12/01/03 12/03/03 |
GROUP PROJECT COMPLETED NOTEBOOKS DUE! |
|
|
|
Final |
12/8 to 12/14 |
Dec 12 TEAM PRESENTATIONS – Turn in DISKS/other Information |
|
|
Attendance:
Research on college success demonstrates that class attendance is a significant factor in student success. Considerable material will be covered during each class session. There will be discussion of assignments, and handouts, will be distributed. If a student must miss class, it is his/her responsibility to get the notes and assignments from a classmate and check with the instructor regarding any handouts, etc., preferably before the next class period. The class begins at 8:15AM.
Remember, 50% of your grade is dependent upon you and your teammate efforts. Whenever you miss a class or are late, you are not only affecting your grade but the grade of your teammates.
WRITTEN WORK:
All written assignments must be typed. Must use a word processor. Must use Microsoft Word 97, 2000 or 2002. Must turn in both a printout and an electronic copy, prepared with Microsoft Word. Include footnotes/endnotes, and follow APA guidelines for citations. Note the rules concerning plagiarism. All assignments are due in the beginning of class. No assignments are except after 15 minutes of class.
PAGES AND CELL PHONES
Pages should be non-audible. Cell phones should be turned off.
TAPE RECORDERS
Tape recorders may only be used with the prior consent of the instructor.
EATING AND DRINKING IN CLASS
Eating in the classroom is forbidden. Drinks will be allowed as long as care is exercised. Eating and drinking are absolutely forbidden in any of the computer labs.
STUDENT HANDBOOK
The Prince George’s Community College Student Handbook contains official policies and procedure regarding student conduct, academic integrity, and related matters. You are responsible for conducting yourself in accordance with those policies. The Student Handbook also contains a wealth of information designed to help students achieve success. Please pick up your free copy from the College Life Office in the Largo Student Center (near the bookstore).
STUDENTS WITH DISABILITIES
Prince George’s Community College is committed to a policy of reasonable accommodation and services to persons with disabilities. In order to receive services, students with disabilities mist register with Disability Support Services. Call between 8:30 am and 4:30 pm, Monday through Friday, 301-322-0838 to schedule an appointment.
CLASSROOM
If you do not understand or having problems with the concepts or flow of the class, please see the instructor in her office. Class time is for lecturing and exercises. We must use our time wisely.
REQUIRED COMPUTER SOFTWARE
All of the computer projects required in this course must be accomplished using Microsoft Office 2002. Any of the software located on the PGCC Lab computers are available for use by the Systems Analysis Class.
FOLDERS/3RING BINDERS/PLASTIC PROTECTIVE SLEEVES
All projects must be submitted in an approved folder (a 9”x11.5” folder with pockets). On the outside of the folder, print your name, the course name, meeting days/times, and the name of your instructor. You need a 3 hole plastic protective sleeve sheets & (qty: 2-3) 3 Ring Hard Binders.
LATENESS POLICY
Any project not turned in when it is due is late, regardless of the reason that it is late will receive a zero. No tears, no excuses, and no exceptions.
CAVEAT CONCERNING CHEATING
No cheating! Any student caught looking at someone else’s assignment or cheating in any way will receive a zero (0) for that assignment.
By the conclusion of the course, students will have demonstrated mastery of the Systems Development Life Cycle by:
1. Successful performance on Exams
2.
The
completion of a marketable systems proposal which includes the feasibility of
the proposed system, the selection of an appropriate candidate, the design,
development and demonstration of the proposed system, giving evidence to the
skills learned in the course.
![]()
![]()
![]()
![]()
IMPORTANT DATES |
|
|
Aug. 25, 2003 |
Classes Begin – Fall 2003 |
|
Aug. 30-Sept 1 |
College Closed – Labor Day |
|
Oct. 3, 2003 |
Last Day to withdraw from 1st half-semester classes |
|
Oct. 13, 2003 |
Last Day to change from “credit” to “audit” or from “audit” to “credit” for 15 week classes |
|
Oct. 15, 2003 |
Midterm/End of 1st half-semester classes |
|
Oct. 16, 2003 |
Beginning of 2nd Half Semester classes |
|
Oct. 29, 2003 |
Professional Development Day – No Classes |
|
Nov. 21, 2003 |
Last day to withdraw from 15-week classes |
|
Nov 27-Nov 30 |
College Closed – Thanksgiving Day |
|
Dec 8-14, 2003 |
Final Examination period/last week of classes |

How do you prepare for the future?
Start working on the present assignments!
How do you prepare for the future? Start working on the present assignments!
Oral Presentations – (50pts) length 5pts, eye contact 5pts, organized 5pts, professional attire 5pts, content & beyond the instructions 30pts.
Research Paper – (100pts) cover page 5pts, table of contents 10pts, double space pages 10pts, footnote 5pts, 4 bibliography 10pts, Content Information 60pts.
CODE RULES in effect as of September 22, 2003
CODE RED: If a student is late for class, 2 points will be deducted from their grade.
CODE GREEN: If a student leaves the class early during a group meeting before class is over 2 points will be deducted from their grade.
Research Paper Topics
This is to be a paper written like any standard research paper. It will have a cover page, table of contents, contain a minimum of 8 double space typed pages on the chosen subject, be footnoted, and contain a bibliography of at least 4 references. Consult any style manual (Prentice-Hall Handbook for Writers is one) or make an appointment for free help at the college writing center on the third floor of Accokeek Hall for assistance.
This paper will be due on October 8, 2003. NO EXCEPTIONS OR EXTENSIONS.
You must select one item from the following list of topics for your paper. No topic can be selected by more than three students a category.
The copy of your Research Paper that is submitted will not be returned. It is recommended that you make a copy of your report that you retain.
To encourage early submission of your paper:
If turned in before or by 9/17/03, you can earn 10 extra points. If turned in after 9/17, before or by 9/24/03, you can earn 5 extra points.
Research Paper Topics |
|
System Analyst1. Systems Development Life Cycle2. Expert System3. Presentation Date: 9/3/03 |
Computer-Assisted Systems Engineering (CASE)1. Application Development Environment (ADE) 2. Model Driven Development (MDD) 3. Presentation Date: 9/8/03 |
|
Computer Security 1. 2. 3. Presentation Date: 9/10/03 |
1. 2. 3. Presentation Date: 9/15/03 |
|
1. 2. 3. Presentation Date: 9/22/03 |
1. 2. 3. Presentation Date: 9/24/03 |
Databases1. 2. 3. Presentation Date: 9/29/03 |
WEB Pages (Development)1. 2. 3. Presentation Date: 10/1/03 |
Computer Crime1. 2. 3. Presentation Date: 10/6/03 |
Future Directions, Computers/Computing1. 2. 3. Presentation Date: 10/8/03 |
Each person will present Creative & Interesting Presentations for 4-5 minutes. The Paper is due October 8, 2003. If for any reason, class is delayed, please be ready to present the next class along with the scheduled presentations.