CS 141
Introduction to Computer Science I
 
 
Grading
 
Tentative grade breakdown:
Exams
 
You are responsible for all material in the lecture and lab. I lecture about what I think is important and I test on what I think is important so coming to class is the best way to do well on the exams :-)
Labs
 
The computer laboratory periods are scheduled every Tuesday, in the Internet Teaching Lab in room SC 334 on the third floor of the Science Center. These labs are an essential part of the course. It is important to come prepared for each lab, having looked through the assignment and remembering to bring all necessary materials. Some of the labs are too long to get done during the lab period. Therefore, lab assignments do not need to be turned in until the beginning of the lab of the following week. In addition to the scheduled labs, the TA will have office hours, where he or she will help you complete your lab assignments, answer questions about the course, help with homework, and so on. You may come in anytime during the office hours, at your convenience. This gives you the opportunity to finish your lab work under the supervision of the TA.
Programs
 
In addition to the labs, there will also be additional programs assigned in class. These programs will require more thinking than the labs. Programs will be assigned in class and due two weeks later.
Late Policy
 
With computers, everything that can go wrong will go wrong at the last minute. Therefore, it is absolutely necessary that you begin your assignments early. My suggestions are as follows: Start the assignement as soon as possible, so you will immediately realize if there is something you don't know. If you start it the night before, chances are that you will have some problem that you won't be able to solve that night. Please follow my suggestions. If you don't, I can guarantee trouble. If you fall behind, it will be difficult to dig yourself out.
Academic Integrity
 
Labs and programs for this class must be done individually. Feel free to discuss the assignments and strategies for solving them, but write them up yourselves. Some well-meaning students, in the process of "helping" a friend, wind up essentially doing the assignment for the friend. Not only is this not allowed, but you are really doing your friend a disservice. Programming is learned by doing it yourself. You are encouraged to learn from each other and help each other understand Computer Science. Teach each other and exchange ideas, but be ethical -- don't copy or modify a program which isn't yours (or allow another student to write or debug your programs for you). So, if you are having trouble writing a function, don't copy the function from your friend. If you do, that will be considered cheating. In addition, you will not learn it, and will do badly on the tests. Instead, ask your friend (or somebody else) to explain to you what you need to know to write the function. Then write it yourself. It is considered cheating to look at somebody else's program, or to show your program to somebody else. I take cheating seriously. Furthermore, if you discuss your program with somebody else, that should be acknowledged in your program.

If you find yourself getting behind, please see the course instructor. We can work together to get you back on schedule. Resist the temptation to copy another's work. The penalty for the first offense will be a 0 for the assignment. A second offense will result in an F for the course. Repeated or flagrant cheating, including any cheating on tests, will result in an immediate notification to the academic integrity board.

It is also an academic integrity violation for you to give your work to others. This includes sharing materials privately as well as making assignments available in Github or other public repositories.

Additional information about rights, obligations and procedures related to academic integrity can be found in Section IV of Clarkson's official regulations.

 
 
Questions? Contact Jeanna Matthews