1. CS 152 & CS 154 Bill Crum, Lecturer Bill White, Instructional Coordinator Earth Chandrraungphen, Lab TA

2. Rule #1 Forget what you have heard about this course in the past. Previously this course was taught in FORTRAN 77, this semester we will use FORTRAN 90.

3. Grades 90 A 80 B 70 C 60 D CS 154 40% Projects 40% Exams 20% Labs CS 152 50% Projects 50% Exams Expect no curve It is possible for everyone to earn an A

4. Factors that WILL NOT influence your grade. Your GPA Your major (or change of major) Your probation status Your candidate status Your financial aid status Your proximity to the cut-off The number of times you have already taken this course Grades are earned and not given!

5. What a 3 credit grade means Assume you need 124 credits for your degree. If you currently have 121 credits and a 3.5 GPA then if you earn in CS 154: “A” your GPA is now 3.51 “B” your GPA is now 3.49 “C” your GPA is now 3.46

6. Important Dates First Exam - February 5 th (in class) Second Exam – March 11 th Third Exam – April 8 th Fourth Exam - Finals Week (Assume Saturday) Project 1 – February 13 th, 11:00pm Project 2 – March 5 th, 11:00pm Project 3 – April 2 nd, 11:00pm Project 4 – April 30 th, 11:00pm Last Day to Drop – March 22 nd

7. Academic Integrity All CS 152/154 course work MUST be done individually. Penalties for cheating are severe and WILL result in a failing grade for the course, for all involved. In some circumstances, cheating results in suspension from the university.

8. Academic Integrity We check all assignments against each other using the MOSS service from the University of California MOSS compares algorithms and your best effort to disguise your submission from detection will fail. There are an infinite number of ways to solve the problems of this course and I expect your solution to be unique.

9. Examples of violations Submitting a solution that is not your own. Collaborating on a solution with another student. All work is to be done individually. Sharing your work with another student. Accepting work from another student. Leaving your work unprotected.

10. Peer Pressure There is extensive pressure on this campus to help a friend in need. Students in this course are not to be the source of help. The consequences of violating course policy are too step to risk. Tell your “friend” in times of need that they must look elsewhere for the assistance they are requesting.

11. Key to Avoiding Suspicion Protect your work. Share it with no one. Protect your ITaP account, share it with no one. (This is an ITaP policy!) It is okay to discuss problems and solutions in this course, but if you find yourself in front of code that is not your own, you should begin to wonder if you are crossing the line in this course. Do your own work!

12. Consequences We consider ALL involved with a policy violation to be equally guilty.  All will receive a failing grade for the course. Do not ask for a consequence other than a failing grade. We will not consider such a request. Why would we just give you a zero?

13. Lecture Policies Be on time. Pay attention.  Do not sleep, eat, or chat. Do not leave early.

14. Lab Policies Be on time. Students that arrive late will be asked to leave and their submission refused. You must submit your work from your assigned lab. You are not to access email or messengers during lab time. If you miss more than 2 lab assignments, you will fail the course.

15. Exam Policies Be on time. Late students are refused entry to the exam. Bring your student ID. No talking for ANY reason. Protect your work. A violation of any of the above may result in a failing grade for the course and/or exam.

16. Late Work Students who have a serious documented hardship may appeal for the opportunity to make up missed work.  The key word here is documented. If you know you will miss class ahead of time you must contact the appropriate staff member in advance. Failure to deal with requests for make up work in a timely manner may result in a denial of the opportunity to make up work. If you miss a deadline, there is NO GUARANTEE that you will be able to make it up.

17. Checking your Grades You will be able to check your grades on- line. You must make an appeal for a re-grade in a timely manner. We will not consider an appeal if too much time has elapsed since the assignment was due. You are responsible for verifying the grades we have recorded are correct.

18. Submission of Work We cannot assist you if…  You fail to submit the correct file for grading.  You forget to submit your work.  You attempt to submit your work after the turnin command has been shut off. You may submit your files as often as you like, the most recent submission will be graded. Please attempt to submit work early and notify a staff member if you experience difficulties.

19. How to succeed in CS I recognize that many of you have never done programming before. I do expect that you place considerable effort in practice and study to compensate for your lack of experience. Get the text and read it regularly! Find good web resources for programming. Find a few extra texts that might help as well!  Math library has programming texts. (3 rd floor)  FORTRAN books are cheap! Check half.com

20. Where to go for help? Start with your TA during lab. Visit Bill White or I during office hours. Don’t call or email for help. Bill White and I also instruct a C programming course with over 1,000 students. You will find the TA to be very friendly, helpful, and capable! EMAIL

21. Final Advice Your success in this course depends on your motivation. This course may seem light the first few weeks, but the course will then begin to move VERY quickly. Don’t get left behind. Practice writing code. Read as much as you can!

22. First Assignment All students need to set up their UNIX accounts for this course.

23. Lastly… Do not ask about any section changes until week #2. Do not ask about being signed in to the course until week #2. Labs DO NOT meet this week, but they will meet next week (CS 154).