Spring 2000 CS12 Information Page

Page has been visited this many times since April 30,2000

Instructors:

• Daniel Tabuenca

Office: Bourns B261
Email:

• dtabuenc@cs.ucr.edu

NOTE: No one C++ book has been found to adequately cover all the topics of this class. Thus, you may need to refer to other books for certain topics.

Assignments

• Lab 1 (Week of April 24)
• Lab 2 (Week of May 1)
• Lab 3 (Week of May 8)
• Lab 4 (Week of May 15)
• Lab 5 (Week of May 22)
• Lab 6 (Week of May 29)
• Lab 7 (Week of June 5)

Useful Links

• Course Evalutaions
• Final Review
• Linux Reference
• My sample source code
• Midterm Review (updated 5/09/2000)
• C String Function Manual Pages
• CS12 Mailing List Subscription
• CS 12 Mailing List Archives
• C++ FAQ
• C FAQ
• Style Guidelines for Programming in C/C++
• Example of C++ Style and Commenting
• Debugging Guidelines
• Guidelines for Software Design
• Program Documentation

Grading Method

The approximate percentages are given below:

Labs 15%
Assignments 35%
Midterm s 24%
Final 26%

The class will be graded based on a straight scale (A = 90% and above, B = 80 - 89%, ?)

Midterms

Dates and times for midterms will be anounced during lecture.

Labs

Every week in lab you will be given an assignment. Labs will be checkedoff by the TA during the lab hours, so you must show up. Labs are written such that the average student can finish within the 3 hours. Since you can only receive your points within the lab time, if you find that you are requiring more than the 3 hours to finish your lab, you may want to start the lab program earlier. No late labs will be accepted. You must discuss any lab absences with me prior to the lab.

Programming Assignments

You will have programming assignments throughout the quarter. No late programming assignments will be accepted. Partial credit will be given. Programs that do not compile will be given a zero (even if it is due to a simple mistake, be sure to recheck that it compiles before turning in your assignment). If you have a problem with getting an assignment in on time, you must discuss this with me prior to the due date.

Programs will be graded based on correctness as well as commenting, style, and readability. It is extremely important that you acquire good programming skills in this class since programming is the core of all upper division computer science courses. Thus, start your programs in a timely manner and work on small sections of a program at a time, debugging and testing the program in stages. Do not leave the commenting of your program to the end. These points should be considered the easy points to get on an assignment. It is assumed that you have learned good style and how to comment properly. Please feel free to ask if you have questions.

You need to include a few pieces of information at the beginning of each program. You should include the following: your name, SSN, login, lab section number, and assignment name (lab1, as1, ?). Points will be taken off if you do not include all this information.

Note, some programming assignments and labs may build on previous programming assignments and labs, so be sure to do your best for each program you write.

Getting Help

Most general questions about assignments, labs, and general C++ issues should be sent to the mailing list e-mail: cs12@cs.ucr.edu. Everyone should subscribe to the mailing list by going to http://mail.cs.ucr.edu/mailman/listinfo and selecting the CS12 mailing list. Using the mailing list will help us reduce the number of duplicate questions asked and will get questions answered quicker. If your questions are confidential in nature DO NOT USE THE MAILINGLIST. Address any specific and/or confidential issues by e-mailing either dtabuenc@cs.ucr.edu or eseffel@cs.ucr.edu.

The TAs for this class also have office hours. You can go the office hours of any of the TAs for this class. You are not restricted to the office hours of the TA for your lab.
This will give you many other opportunities to ask questions.

Extra Credit

I do not typically give extra credit. Be sure not to get behind on the assignments and be sure to do each to the best of your ability so that you will not have a reason to desire
extra credit.

Turning In Assignments

You will be turning in your assignments electronically. Please make sure that you understand the instructions when they are gone over in lab. Since this is a computer science class, in order to get points for an assignment you must not only do the assignment, but you must make sure that you turn it into the grader correctly. Even if you do the assignment and then make a mistake turning your assignment in, it will not be graded, you must make sure it gets to the grader. Thus, do not wait until the last minute, that way if you make an honest mistake, you will have time to correct your mistake before the deadline. Some points to pay attention to:

• You may turn in an assignment more than once, but only the last one will be seen and graded.
• Turn in your assignment early. All the computers vary in their clocks slightly. The turn in program will only accept programs up until midnight of the due date based on the clock of the computer in which the turn in program is being run. If your program is not accepted, it is considered late (even if it is not midnight according to the clock on your computer). So do not push the deadline. Also leave time for the computers to be running slow if there are a lot of people trying to turn in programs at the same time.
• Be sure to choose the correct class and assignment.
• Be sure to read the list of files that your computer shows was turned in to make sure that it lists the .cpp or .cc file for your program.
• Do not turn in more than one version of a particular .cpp or .cc file at a time. The grader is not responsible for figuring out which one you really wanted to be graded.
• Be careful if you are working from home. You can only turn in files that are located in your CS account, so be sure you know how to transfer from your home computer to your account. Once in your account, you can proceed with the turn-in from any location.

Grading

If you have a problem with the grading of an assignment, you need to bring your assignment to me promptly. Your grades will be periodically emailed to you. Be sure to check that the grade you see on your returned paper is what I have recorded, also check your lab scores. I will not discuss any regrading if it is over a week since it has been returned to you. Graded assignments will be returned to you in lab, be sure all the required information is listed at the top of your assignment so that it will be able to be returned to you. Please take responsibility for your grade so there will not be any problems.

Cheating Policy

Unfortunately I have found that cheating occurs far too often and have learned that it is something that I must address up front. An anonymous page on the web has been set up by the Department to report cheating incidents for the instructor to look into. You may report incidents of cheating that you witness to the following web page:

https://www.cs.ucr.edu/cheating

You will be given a handout about cheating in lab. You are required to read the handout, sign it, and return it to the TA. You will not have any grades of assignments or labs recorded until the signed handout is received. Cheating is taken very seriously and will result in an 'F' for the quarter.

Topics

It is assumed that you know the following topics in C++: variables, selection structures, loops, functions, arrays, formatting output, file processing.

The following is a list of topics that you should know by the end of this class (Not necessarily in the order we will cover them).

• Recursion Chapter 3
• Strings Chapter 9
• Pointers Chapter 9
• Classes Chapters 6 & 7
• Friends Chapter 7
• Operator Overloading Chapter 8
• Inheritance Chapter 9
• Virtual Functions Chapter 10
• Templates Chapter 12
• Linked Lists Chapter 15