| Computer Science 1 | ||||||
| Top | Lectures | Assignments | Noticeboard | |||
|
Syllabus |
|||||||||||
It is the responsibility of all students enrolled in this course to be familiar with the contents of this document.
| Instructor: | Dr. Timothy A. Davis |
| Office: | 441 Edwards Hall |
| Phone: | 656-0309 |
| Email: | tadavis@cs.clemson.edu |
| Office Hours: | Tuesday 3:30-5:00pm, Wednesday 3:00-4:00pm (or by appointment) |
| TA Office Hours: | See http://www.cs.clemson.edu/~lab101 |
| Lectures: | Tuesday/Thursday 2:00-3:15, Jordan G33 |
| Lab WWW: | http://www.cs.clemson.edu/~lab101 |
| Class WWW: | http://www.cs.clemson.edu/~tadavis/cs101 |
| Credits: | 4 (3,2) |
| Prerequisites: | MTHSC 105 or satisfactory score (520) on the
Mathematics Test, Level II (standard) or consent of instructor |
Introduction to modern problem solving and programming methods. Special emphasis is placed on algorithm development and software life cycle concepts. Course includes use of appropriate tools and discusses ethical issues arising from the impact of computing upon society. Intended for students concentrating in computer science or related fields.
(Note - students wishing only to satisfy the General Education computer skills requirement might consider another course, e.g. CPSC 120.)
This course aims to provide students with an introductory understanding of modern programming techniques, skills and issues. The course uses the Java programming language to achieve this aim. More specifically, the objectives of this course are:
After this course, students should be able to:
Class meetings will mostly be lectures; however, students are encouraged to ask any pertinent questions and participate actively in discussions. A weekly laboratory is also associated with this class. The laboratory sessions will re-enforce lecture material. More information can be found at http://www.cs.clemson.edu/~lab101.
In addition to the lectures and laboratory work, there will be homework assignments, two midterm exams, and a final exam.
This is an intensive but rewarding course - you work hard, but learn a lot and gain considerable experience.
Required reading material for this class:
Some readings may be assigned from books and papers on reserve in the library and from available resources on the WWW.
Five or six programming assignments will be given in addition to lab exercises. All work should be completed independently unless explicitly stated otherwise in the assignment.
Unless otherwise stated, assignments are due at the beginning of class on the specified due date. No credit will be given for assignments submitted late, since solutions may be handed out or discussed in class. All written work must be typed.
The objective of the laboratories is to give students supervised, hands-on experience with the various concepts, tools and techniques covered in lectures. Laboratory attendance is mandatory. Students must attend each laboratory session in order to gain the credit associated with that laboratory. Students may not leave a laboratory session early (unless the work associated with that lab is completed).
Short (generally five-minute) quizzes will be given periodically. Missed quizzes cannot be taken at a later time.
I will attempt to return grades as quickly as possible after they have been submitted. You are responsible for monitoring your own progress - concerns about a grade for an assessed piece of work should be addressed within one week of receiving the grade for that piece of work. Do not wait until the final weeks or after the final exam.
I am willing to discuss specific concerns about grades. I am unwilling to discuss questions or comments along the lines of ``I think I deserve a better grade'' or ``I need an A in this class.''
Plagiarism occurs whenever you explicitly or implicitly assert that someone else's work is your own. Such actions are clearly unacceptable in the context of a degree in which you are receiving certification from the University that you have reached a certain level of achievement in various areas of the field concerned (Computer Science, in this case). Other forms of academic dishonesty include showing your work to another student in a context in which it is reasonable to believe that they may submit it as their own. In summary, the University rules on academic dishonesty apply.
Of course, I encourage students to assist one another in learning and overcoming difficulties with the material, but discussing or sharing answers to specific homework questions or programming assignments, except in cases of explicit group assignments or projects, is considered dishonest. With the widespread use and accessibility of the WWW, re-use of some software (e.g., a commonly used data structure) is permitted as long as you cite the source. You should also indicate how you tested the software.
If you have questions as to what I consider honest, please ask!
Clemson University Official Statement on Academic Integrity
As members of the Clemson University community, we have inherited Thomas Green Clemson's vision of this institution as a high seminary of learning. Fundamental to this vision is a mutual commitment to truthfulness, honor, and responsibility, without which we cannot earn the trust and respect of others. Furthermore, we recognize that academic dishonesty detracts from the value of a Clemson degree. Therefore, we shall not tolerate lying, cheating, or stealing in any form.
Clemson Computer Science Department Academic Honesty Policy
http://www.cs.clemson.edu/html/academics/honest_policy.shtml