GENERAL INFORMATIONLecture: Lecture will be held Tuesdays and Thursdays, 3:30pm - 4:45pm in Root Hall A017.
Final exam: Tuesday May 9th @ 3:00pm
Instructor: Andy Carrillo (firstname.lastname@example.org)
Office hours:I am available to assist CS260 students in the Unix Lab, room A-017 during my hours listed here.
Prerequisite: C or better in CS 151.
Required text: No physical textbook is required for this class. Links to public domain reading assignments and relevant information will be provided as they are needed.
- The official Processing reference site can be found at: http://processing.org/reference/
- A good Java reference site can be found at: http://tutorialspoint.com/java/
- Processing IDE: http://processing.org/download/?processing
- Java JDK: http://oracle.com/technetwork/java/javase/downloads/index.html
- Eclipse IDE: http://eclipse.org/
- A good Java reference site can be found at: http://tutorialspoing.com/java/
File Transfer Tools:
- Windows, Mac OSX, Linux - FileZilla: http://filezilla-project.org/download.php?type=client
- Windows Users - WinSCP: http://winscp.net/eng/docs/guide_install/
- Mac Users can also use terminal commands like 'sftp' and/or 'scp' to transfer files between their machines and the CS Server
- Terminal Manual Entries: "$ man sftp" and "$ man scp"
- Info: http://security.illinois.edu/content/scp-and-sftp-unix-and-mac-os
- Info: http://itservices.usc.edu/sftp/cline
- Other Alternatives
- Uploading/Downloading with Google Drive, Dropbox, etc.
- Sending Email Attachments to yourself
GA Lab hours: Graduate assistants will be available to help you in the
computer science Unix lab, room A-015 in the basement of Root Hall, for about 40
hours per week. You are encouraged to go to this lab to work on your assignments. The
computers are Linux machines that can be accessed with your cs260xx login credentials.
You can ask the graduate assistants for help with your programs and you can work with
any other CS 260 peers.
Lab Hours are posted here.
Syllabus Changes: Any changes made to the syllabus will be announced in class.
|Week 1-5||Processing - Classes, Constructors, Objects, UML, Inheritance, Data types, basic input and output, statements, operators and expressions, control flow and loops|
|Week 6+||Java - Interfaces, Packages, File input/output, Function Overloading, Lambda Expressions, GUI Programming|
Tuesday May 9th @ 3:00pm
There will likely be one quiz per week (probably Thursdays) and one homework assignment per week due the following week. Assignments will be announced in class and will be posted at cs.indstate.edu/~andyac/cs260/assignments.html
Announcements regarding the course will be made both during class and via email to your @sycamores.indstate.edu email address. You should regularly check this email account or have it forwarded to an account that you check regularly. You can set the account to forward by logging into your indstate.edu email from Internet Explorer (the "light" version of the webmail client that opens up from Firefox or Chrome does not give the option to forward email).
GRADING, ASSIGNMENTS, AND EXPECTATIONS
The students of this course have the following responsibilities: read assigned readings before lecture, attend lecture, complete homework assignments, take exams, and complete a project. The final grade consists of:
Quizzes: 25% total. There should be a quiz approximatly once per week.
Homework: 30% total. There will be a homework assignment most weeks. The total of all homework assignments is worth 30% of the final grade. If you turn in the assignment late, I will grade it at 70%, for an extra day. Homeworks turned in after I've finished grading WILL NOT BE ACCEPTED. NOTE: you may ask me to look over an assignment before it is due and I may help by pointing out mistakes that need correction and provide other feedback.
Exams: 25% total. We will have three exams. Point values for each exam will be determined at a later date.
Class Attendance/Participation: 20% total. Attendance will be taken at the beginning of each class. Half of your attendance/participation score will consist solely of whether you were present when attendance was taken each day - the total number of days present divided by the number of lectures in the semester. The other half of your attendance/participation grade will be assigned at the end of the semester based on how attentive you were in class throughout the semester.
The class attendance grade serves the purpose of giving you credit for coming to class. You benefit from coming to class by seeing me present the new material, getting to ask questions, interacting with your classmates, keeping up on what is going on in the course, etc.
The exams and quizzes serve as benchmarks of your ability to relatively quickly solve problems related to the material. This helps me assign a grade, and also gives you motivation to pay attention and keep up with the assignments.
The weekly homework assignments are designed to solidify your knowledge by having you write programs.
A possible final project will be discussed further after the first few weeks of the semester. Students may choose a larger programming project that will be completed by the end of the semester and presented to the class.
Expectations: An average student should spend 3-6 hours OUTSIDE of class each week (in addition to class time) working PRODUCTIVELY to complete their coursework for this class. Some students may need to spend more time than others. Make sure not to fall behind.
Classroom conduct: You may not use cell phones, iPods/music players, etc. during class. You should be civil and respectful to both the instructor and your classmates, and you should arrive to class a few minutes before the scheduled lecture so you are ready for lecture to begin on time. You may use your computer during class if you are using it to follow along with the examples that are being discussed. You may not check email, facebook, work on other courses, etc. during class.
Important Note: If you wait until the last minute to begin your homework assignments, I will not be available to answer questions if you have problems. Programming assignments are notorious in the sense that oftentimes most of the time completing the assignment occurs after you thought you had the problem solved; this is called debugging, and is typically most of the effort in completing a program. You MUST start your homework early. We suggest attempting the assignment the day it is given, or the day after, so that if you have a problem you can ask early. If you continue to have problems in trying to complete the assignment, you will have time to ask again. Working on programming assignments is much less stressful if you start early!
Please follow these guidelines to avoid problems with academic misconduct in this course:
Homeworks: You may discuss the homework assignments, but should solve them on your own. To make sure you are not violating this, if you discuss with someone, you should DESTROY any collaborative work, go your seprate ways, spend at least an hour doing something completely unrelated to the assignment, and then you should be able to RECREATE the program/solution on your own, then turn that in. If you cannot recreate the solution on your own, then it is not your work, and you should not turn it in.
Note on sources: If you use some other source, the web or whatever, you are required to cite it! Not doing so is plagiarism.
Exams: This should be clear - no cheating during exams. The exams will be closed-book, closed-notes, no computer, and no calculator.
Projects: You should not copy code from the Internet or anywhere else. The project should be your own work. It will be fairly obvious to me if you do copy code from the Internet, and the consequences will be at the least a 0 on the project.
If cheating is observed, you will at the least receive a 0 for the assignment (and may receive an F for the course), and I will file a Notification of Academic Integrity Violation Report with Student Judicial Programs, as required by the university's policy on Academic Integrity. A student who is caught cheating twice (whether in a single course or different courses) is likely to be brought before the All-University Court hearing panel, which can impose sanctions up to and including suspension/expulsion. See the Student Code of Conduct and Academic Integrity Resources for more information.
Please ask the instructor if you have doubts about what is considered cheating in this course.
If you have special needs for the classroom environment, homework, or quizzes, please inform the instructor during the first week of classes. If you have any such needs, you should go to the Student Academic Services Center to coordinate this. See Student Academic Services Center - Disabled Student Services for more information.
DISCLOSURES REGARDING SEXUAL MISCONDUCT
Indiana State University fosters a campus free of sexual misconduct including sexual harassment, sexual violence, intimate partner violence, and stalking and/or any form of sex or gender discrimination. If you disclose a potential violation of the sexual misconduct policy I will need to notify the Title IX Coordinator. Students who have experienced sexual misconduct are encouraged to contact confidential resources listed below. To make a report or the Title IX Coordinator, visit the Equal Opportunity and Title IX website: http://www.indstate.edu/equalopportunitytitleix/titleix.
The ISU Student Counseling Center
HMSU 7 th Floor
The ISU Victim Advocate
Trista Gibbons, email@example.com
HMSU 7 th Floor
Campus Ministries United
For more information on your rights and available resources http://www.indstate.edu/equalopportunitytitleix/titleix