SPRING 2020
COSC 236.001: Introduction to
Computer Science I
Instructor: |
Iliana Zimand |
Course Description: This course provides an introduction to computer science through problem solving, algorithm development, and computer programming. Selected topics in computer science are introduced through programming projects using the Java programming language. It is assumed that all students have taken COSC 175 (or equivalent).
Course Objectives: The objectives of this course are
1. Develop problem-solving skills, as related to computers and
computer programming.
2. Understand fundamental programming concepts and develop
basic programming skills
3. Apply structured-programming techniques to problem solving
and program organization.
4. Develop proficiency in the fundamentals of the Java
programming language
5. Learn how to use the DrJava environment to create, execute
and test Java programs.
6. Prepare for further study in Computer Science/Information
Science.
Prerequisite: (TU catalog) COSC 175 (with a grade of C or
higher) and MATH 119 or equivalent (MATH 231 for IT students).
Class Organization: The course is an introduction to programming via the Java programming language and it is crucial for almost any other computer class so it is important that you do well. Therefore, plan to work 6-8 additional hours per week in the open labs (or at home if you have a computer and the software). It is important that you attend all class meetings in a week (see attendance policies for core courses) and it is the student’s responsibility to make up for missed work.
The software development environment for the course will be DrJava and it is available in our labs. As these are open labs and you are using public machines, you will want to make arrangements for saving your work (e-mail, Tiger File space, USB memory sticks, etc.)
In this class you will have 3 tests (two semester tests, and a cumulative final exam), some unannounced quizzes, 4 programming assignments, and 14 - 15 lab assignments. Students will not be permitted to retain (or copy) exams. Any student wishing to review the exam in greater detail should make an office appointment and I'll be happy to go over it with you in person. Lab assignments will be given each week during lab period; they are due at the start of the next lab. In most cases you will be able to finish the lab assignments during the two-hour lab session. If not, in order to finish the programming assignments you can use the open labs or your own computer. It is very important that you complete all labs and programming assignments: most students will find it extremely difficult to do well on the tests if they do not do the labs and the homework.
Note: Students who don't
already have a TU e-mail account should acquire one. This is the only
account you should use to communicate with me and the TA.
Topics to be covered:
Note: More time with the last 2
topics in COSC 237.
Books and References:
Main
Text: Building
Java Programs: A Back to Basics Approach, by Stuart Reges
and Marty Stepp, Addison-Wesley.
The info for the 4-th edition (2016) is:
ISBN-13: 9780134322766
Class
website:
http://orion.towson.edu/~izimand
Lecture notes, assignments, labs, tutorials, announcements, and other materials
will be posted here. Note: if you try to access the website while on campus, make
sure that you are connected to tu-secure.
Software Downloads:
The program development environment used will be DrJava, a Java programming environment developed specially for students. It is available for free download at http://www.drjava.org. In addition, the Java Development Kit (JDK) must be downloaded here
Grading Policy:
|
Towson
University uses the +/- grading system. The percentage intervals are as given
in the table below:
--- |
A: 93% - 100% |
A-: 90% - 92.9% |
B+: 87% - 89.9% |
B: 83% - 86.9% |
B-: 80% - 82.9% |
C+: 75% - 79.9% |
C: 70% - 74.9% |
--- |
D+: 67% - 69.9% |
D: 60% - 66.9% |
--- |
--- |
F: 0% - 59.9% |
--- |
Course Policies / Guidelines:
All course policies are fundamentally intended to sustain an atmosphere that is non-disruptive and conductive to learning.
2.
Attendance:
Class
attendance is essential to doing well in the course, and coming to class shows your commitment to doing the work and
understanding and learning the material. Students are expected to attend
each class meeting and attendance is mandatory. This
class is not just a lecture and the lecture notes posted online are not a
replacement for class attendance. During the class session, I may use
exercises, questions, and other approaches that may challenge students to solve
problems – student involvement in these discussions is important and this
course will weight attendance and class participation as a small part of the
final grade. Students who miss class meetings or show a pattern of
lateness without permission of the instructor will be penalized with a
reduction in grade.
The
following Attendance Policy was developed by the Computer and Information
Sciences Department for COSC 175, COSC 236 and COSC 237 courses in an effort to
be consistent and to inform students of the attendance expectation in these
courses.
1.
Students are expected to come to
class on time and prepared.
2.
Attendance will be recorded at every
class session lecture and lab
3.
Your 3rd and each subsequent
unexcused absence will lower your grade by 5%.
4.
The equivalent of 2 weeks’ worth of
unexcused absences will result in an automatic F. No exceptions.
In
accordance with University policy, student absences will be excused under the
following circumstances:
1. Cases of illness or
injury that prevent attendance in class (written documentation required)
2.
Religious observance that prevents attendance
in class (two weeks advanced written notice required)
3.
Participation in authorized university
activities during class time (two weeks written notice from authorized
university personnel)
4.
Compelling verifiable circumstances beyond the
control of the student.
Also, all students are
expected to be on-time for (and remain for the duration of) all class sessions
and make every attempt to avoid disrupting the class. Students are required to
notify the instructor via e-mail if they are unable to attend a class meeting.
Written documentation of the reason for the absence will be requested by the
instructor and must be submitted for the absence to be excused. If a student is
absent from an exam during the scheduled time for that exam, the student will
automatically receive a grade of 0 for the exam unless: (a) the student
notifies the instructor of the absence at least 24 hours BEFORE the exam
and supplies a written doctor's excuse explaining the absence or (b) there is
an extraordinary situation which the instructor allows as an acceptable excuse.
If (a) or (b) applies, arrangements for a make-up exam will be made.
Several unannounced
quizzes will be administered during the semester. Quizzes cannot be made-up
under any circumstances.
3.
Assignments: All assignments (along with other course materials) will be
posted on the class website, so you should check it out before emailing the
instructor with any questions pertaining to assignments or daily topics. Keep
in mind that the website is not a replacement for class attendance and not
every instruction given in class will necessarily be repeated online; again,
you should make every effort to attend class on a regular basis (see attendance
policy). Assignments are due at the beginning of class on the due date.
Assignments are expected to be submitted on time regardless of your attendance
on a particular day. Late programming assignments will not be accepted. All assignments should be typed and
appropriately documented. You will not be graded for any loose sheets turned
in. So make sure to staple all the sheets you turn in or to bring them in a
folder. Note that any deadlines indicate the amount of time and effort
required both toward the completion of the assignment and its documentation. Do
not anticipate completing your assignments 1-2 days prior to the final
deadlines.
Department Notes:
1. Third
Attempts in this Course
Only under exceptional circumstances will the department
accept a third attempt of this course. It is the policy of the Department of
Computer and Information Sciences to
deny any third attempt that is not in the best interest of the student.
If this is your third attempt of this course, you must fill out a Third Attempt
Petition and have it approved before continuing in this course. Third Attempt
Petitions are available online at the following link or can be picked up in the
CIS department front office: http://www.towson.edu/registrar/forms.html.
2.
Food and drinks are prohibited from classrooms and
labs. Please use the atrium area for breaks.