CSCI 1301 – Introduction to Computing and Programming

Summer 2007

Syllabus

Instructor: Brian A. Smith
Email: bsmith@cs.uga.edu
Office: 183 Boyd GSRC
Office hours: Tuesday & Thursday 1:30-3:30 & by appointment

 

We will primarily be using Crimson Editor in class. We will discuss how to compile and execute programs from the command line in class and/or lab. You may use any Java development environment you like to do the programming assignments. For those interested in using an Integrated Development Environment (IDE), I highly recommend Eclipse, an open-source platform available for free at http://www.eclipse.org. I am happy to provide guidance on the use of an IDE outside of class.

We will be introducing some fundamental ideas in Computer Science and programming, focusing on the Java programming language. This will include the fundamentals of the object-oriented paradigm (classes, objects, encapsulation, inheritance and polymorphism), basic data structures such as arrays and lists, and basic algorithm design.

 

The grading scale is as follows:

 

o        90-100 guarantees an A

o        88-89 guarantees an A-

o        86-87 guarantees a B+ 

o        80-85 guarantees a B

o        78-79 guarantees a B-

o        76-77 guarantees a C+

o        70-75 guarantees a C

o        68-69 guarantees a C-

o        65-67 guarantees a D

o        Below 65 is an F

 

I reserve the right to further curve the course grades. Any such curve will not reduce any student’s grade.

 

Lab assignments are to be completed at the assigned lab. When necessary, files should be mailed to cs1301a@cs.uga.edu. This will make it much easier for your lab instructors to grade your work and provide prompt feedback. If you are unable to complete the assignment in the allotted time, inform your lab instructor and submit the work before the next lab. Your lab instructors, like yourselves, have other responsibilities this summer. Submitting your work on schedule will help them manage their time, so please be courteous and try your best to do so.

The four course projects will be assigned on a biweekly basis. They will be due on Fridays before midnight. Late projects will be subject to a 20% penalty. In the event of a family emergency, serious illness/injury, or other significant event, please let the instructor know as soon as is reasonably possible.

Participation in classroom discussion is a valuable part of the class. It is not necessary to raise your hand before making a comment. Simply be courteous and respectful to everyone in the class. If you have a question during lecture or if a point is not explained to your satisfaction, don’t wait until the lecture is over to get clarification. There’s a good chance that someone else is wondering the same thing.

Please turn your cell phones off or to silent during class and lab times.

 

Cheating is a clear mark of disrespect for the University, your instructors, and your fellow students and I take it very seriously. If I suspect cheating on a lab assignment, exam, or course project, I will/must report it to the Office of the Vice President for Instruction. If academic dishonesty is established, I will seek a minimum penalty of an F for the course and an academic dishonesty notation on the offending student’s transcript. I may also seek a one semester suspension. Subsequent violations are subject to mandatory expulsion under Section 11 of the Academic Honesty Policy.

 

Cheating is not only unethical; it is also far more costly than a bad grade. At worst, a poor grade on a project or exam will lower your overall course grade by a few percent. Cheating can damage or end your academic career while destroying your academic and personal reputation. The effects of cheating can follow you beyond the University, as dishonesty reports will be read by future employers that require transcripts.

 

Students may discuss lab assignments and course projects with one another. You may use whiteboards or chalkboards to explain coding techniques, provided code is not copied from the board and used in an assignment. You are encouraged to talk to one another, learn from one another, and help one another.

 

Students may not work on lab assignments and course projects with one another. You may not show your code to another student until after the deadline for submission has passed. You may not help another student debug his/her code. You may not email or otherwise transmit solutions or partial solutions to any course assignment to one another until after the deadline for submission has passed.

 

Students may not copy code or portions of code from any source, including the internet, unless the project description explicitly allows for such use. Even then, all borrowed code must be cited within comments, even if modified. To do otherwise is to commit plagiarism. (For example, this syllabus was written by modifying previous, publicly-available syllabi from Dr. Robert W. Robinson and Tarsem Purewal. A notation appears in the comments of the webpage.)

If you are uncertain whether a particular activity constitutes academic dishonesty, do not take action until you have clarified the situation with the instructor. I will be more than happy to provide such clarification. Students are encouraged to consult with the instructor whenever help is needed. In addition to the instructor's scheduled office hours, students can make appointments for other times, or visit Boyd 183 whenever the instructor is present.


Computer Science
Departmental Policy Statement
Academic Honesty

The Computer Science Department recognizes honesty and integrity as necessary to the academic function of the University. Therefore all students are reminded that the CS faculty requires compliance with the conduct regulations found in the University of Georgia Student Handbook. Academic honesty means that any work you submit is your own work.

Common forms of academic dishonesty which students should guard against are:

1.    copying from another student's test paper or laboratory report, or allowing another student to copy from you;

2.    fabricating data (computer, statistical) for an assignment;

3.    helping another student to write a laboratory report or computer software code that the student will present as his own work, or accepting such help and presenting the work as your own;

4.    turning in material from a public source such as a book or the Internet as your own work.


Three steps to help prevent academic dishonesty are:

5.    Familiarize yourself with the regulations.

6.    If you have any doubt about what constitutes academic dishonesty, ask your instructor or a staff member at the Office of Judicial Programs.

7.    Refuse to assist students who want to cheat.


All faculty, staff and students are encouraged to report all suspected cases of academic dishonesty. All cases of suspected academic dishonesty (cheating) will be referred to the Office of Judicial Programs. Penalties imposed by the Office of Judicial Programs may include a failing grade in the course and a notation on the student's transcript. Repeated violations are punishable by expulsion from the University. For further information please refer to the UGA Code of Conduct, available at the URL below.

http://www.uga.edu/judicialprograms/2006-07%20Code%20of%20Conduct.pdf


Revised 8/2006


syllabus | lab assignments | projects | slides | resources | course home| instructor home