CSCE 155
Introduction to Computer Science I
Class Syllabus
Fall 2004
Lectures & Labs
Regular
Lecture Section Honors
Lecture Section
Time: 8:30 – 9:20 AM MWF Time: 2:30 – 3:20 PM MWF
Room 106, Avery Hall Room 111, Avery Hall
Regular Labs Sections Honors
Lab Section
Section 152 12:30 – 2:20 PM M Section 151 3:30 – 5:20 PM M
Section 153 11:30 – 1:20 PM T
Section 154 1:30 –
3:20 PM W
Catalog Listing
Introduction to
problem-solving with computers including problem analysis and specification,
algorithm development, program design, and implementation in a high-level
programming language. Laboratory
assignments develop mastery of a high-level programming language and
practices. (Honors course covering same
topics as CSCE155, but in greater depth.)
Class Objectives
The objective of this class is to familiarize students
with problem solving approaches using computer programming. We study how to specify a problem, how to
come up with a solution, how to convert the solution into a program, and how to
solve the problem correctly using the program. The conversion of a solution to
a program comes in many ways. In this
class, we focus on Object-Oriented Programming (OOP) where we build “software
objects” that are distinct and standalone that programs can use to carry out
more complex tasks.
Prerequisites
CSCE105; MATH103 or equivalent or appropriate scores on the Math Placement Exam
Text Book
Wu, C. Thomas. (2004). An Introduction to Object-Oriented
Programming with Java, New York, NY: McGraw-Hill, 3rd Edition (Required)
Assignments
There will be six (6) programming assignments to help you understand some of
the basic concepts. Java programming language must be used for all the
assignments. The assignments are due at the class time on the indicated dates. We will use a
flexible slip date system for the assignments. Each student is given an
automatic extension of six (6) calendar days. You can use these on any
assignment(s) during the course. However, the total number of “late” days
cannot exceed six. After you have used your “late” days, if you submit homework
late, you will not get any credit for
it. Then, it is better to submit a partially completed homework than a
late one. If you have a special reason for being late, get permission
from the instructor or the TA well ahead of the due date.
You will also be required to hand in an on-line copy. In addition, you
are required to hand in a hardcopy of your code at class time on the due date.
You are expected to write well-documented, modular code. Programs which do not compile or which do
not run will not receive any credit. Programs
that compile and run will be graded as follows: 45% Program Correctness,
15% Software Design, 10% Programming Style, 15% Testing,
and 15% Documentation.
Examinations
We will have two mid-term (in-class) exams and a final exam. The dates for the
tests are listed in the lecture schedule. There will be no makeup
tests.
Laboratories
You must register for a lab section as a part of this course. The laboratories are designed to supplement the lectures and provide hands-on experiences on topics that need additional attention. It is a significant part of the course and you are strongly encouraged to fully take advantage of this opportunity. You are required to read the lab handouts and the reading assignments before coming to the lab. You are also required to take the on-line pretest prior to coming to each lab. There are 15 laboratories altogether.
Final Grade
You will receive a numeric score for each programming assignment and the test. Each mid-term exam contributes 75 points; the final exam is worth 150 points. Each of the six assignments contributes 100 points, totaling 600 points altogether. Each laboratory carries 40 points, totaling 600 points altogether. As matter of policy, no I (incomplete) grades will be given. Your final grade will be based on the following table.
|
Tests |
0-149 |
150-164 |
165-179 |
180-194 |
195-209 |
210-224 |
225-239 |
240-254 |
255-269 |
270-284 |
285-300 |
|
1140-1200 |
F |
C |
C+ |
B- |
B |
B+ |
A- |
A |
A |
A |
A |
|
1080-1139 |
F |
C- |
C |
C+ |
B- |
B |
B+ |
A- |
A |
A |
A |
|
1020-1079 |
F |
D+ |
C- |
C |
C+ |
B- |
B |
B+ |
A- |
A |
A |
|
960-1019 |
F |
D+ |
C- |
C |
C+ |
B- |
B |
B+ |
B+ |
A- |
A |
|
900-959 |
F |
D |
D+ |
C- |
C |
C+ |
B- |
B |
B+ |
A- |
A- |
|
840-899 |
F |
D- |
D |
D+ |
C- |
C |
C+ |
B- |
B |
B+ |
B+ |
|
780-839 |
F |
D- |
D |
D |
D+ |
C- |
C |
C+ |
B- |
B |
B |
|
720-779 |
F |
F |
D- |
D |
D+ |
D+ |
C- |
C |
C+ |
C+ |
B- |
|
660-719 |
F |
F |
F |
D- |
D- |
D |
D+ |
C- |
C |
C |
C+ |
|
600-659 |
F |
F |
F |
F |
F |
D- |
D |
D+ |
C- |
C- |
C |
|
000-599 |
F |
F |
F |
F |
F |
F |
F |
F |
F |
F |
F |
Academic Misconduct
Violations of academic integrity will result in automatic failure of the class and referral to the proper university officials. The work a student submits in a class is expected to be the student’s own work and must be work completed for that particular class and assignment. Students wishing to build on an old project or work on a similar topic in two classes must discuss this with both professors. Academic dishonesty includes: handling in another’s work or part of another’s work as your own, turning in one of your old papers for a current class, or turning in the same or similar paper for two different classes. Using notes or other study aids or otherwise obtaining another’s answers for an examination also represents a breach of academic integrity. Sanctions are applied whether the violation was intentional or not.
To help avoid these problems, please start assignments early and seek help when you need it.