Instructor
Dr. Jeffrey Paone
Office: 280C Brown Hall
Phone: x2587
Email: jpaone {at} mines [dot] edu
Office Hours: T 1:30-3:30, R 10-12, or by appointment
Dr. Jeffrey Paone
Office: 280C Brown Hall
Phone: x2587
Email: jpaone {at} mines [dot] edu
Office Hours: T 1:30-3:30, R 10-12, or by appointment
Lodewijk Brand
Email: lbrand {at} mymail [dot] mines [dot] edu
By the end of the semester, students will be able to:
There will be nine individual programming assignments throughout the semester. Due dates will be specified and are firm. Individual programming assignments must represent individual student work.
All programs (homework assignments, programs, projects, labs) must be submitted in electronic form through Canvas.
Your goal should be to make it easy for us to see how great you did. If we make a couple of good faith attempts but fail to get your program running, we will try once to contact you to help us. If we still cannot get your work to compile, it will receive a zero grade.
There will be two course projects, to be completed in teams of three. The first will be a midterm project due shortly before Fall Break. The second will be a final project due during the last week of class.
All code and files required for the projects must be submitted to Canvas.
There will be two take home exams during the semester.
Make-up exams will be allowed only in accordance with University policy. Make-up exams due to legitimate travel require advance notice and instructor’s approval.
All assignments, projects, quizzes, and exams are due at the date and time specified on the item handout.
Items received less than 24 hours past the due date will receive a 50% grade reduction.
Items not turned in or received more than 24 hours past the due date will receive a grade of zero.
The final course grade will be computed from the following course percentage breakdown:
Final grades will be determined using a straight scale. The straight scale assigns letter grades as follows:
If you have any questions regarding how any assignment, project, or exam is graded and you think you deserve more points than you received, you must see the grader within one week of the day the item was returned to you. No claims, justifiable or not, will be considered after this deadline. If you and the grader cannot reach a consensus, then contact the instructor.
Any assignment returned to the instructor is subject to total re-grading which may result in a grader higher or lower than your original grade.
A portion of the student’s grade will be comprised of online participation.
Students are expected to participate by making regular forum posts, either asking a question or responding to an existing topic. From time to time, there may be specific discussion topics.
Be polite. This also applies to assignment clarifications (e.g. writing “This requirement makes no sense” may not be the best phrasing. Try something like: “I’m not clear what requirement X means. Should I do [x] or [y]?”)
A Piazza post is not a text message; use complete sentences and correct spelling, punctuation, and grammar.
When asking a question, do not post large blocks of code. A single line of code, to clarify your question, may be appropriate. Before posting, ask yourself: would this be giving most of the answer to another student? Thinking about how to phrase the question may help you solve the problem.
When answering a question, do not post the exact code from your homework solution. Possible exception would be something that takes one line and is primarily a syntax question. E.g., to a question like “How do I set the color of my rectangle” you might answer with something like “You need to set the color before drawing. If g is a Graphics object, you can do g.setColor(Color.CYAN);”.
Using pseudocode is an excellent way to answer questions.
The following policy exists for all CS courses in the EECS department. This policy is a minimum standard; your instructor may decide to augment this policy.
If the project is an individual effort project, you are not allowed to give code you have developed to another student or use code provided by another student. If the project is a group project, you are only allowed to share code with your group members.
You are encouraged to discuss programming projects with other students in the class, as long as the following rules are followed:
Any material from any outside source such as books, projects, and in particular, from the Web, should be properly referenced and should only be used if specifically allowed for the assignment.
To prevent unintended sharing, any code stored in a hosted repository (e.g. on github) must be private. For group projects, your team members may, of course, be collaborators.
If you are aware of students violating this policy, you are encouraged to inform the professor of the course. Violating this policy will be treated as an academic misconduct for all students involved. See the Student Handbook for details on academic dishonesty.
All students are expected to follow the University’s Academic Code of Honor.
A student or assigned team working on a program may discuss high-level ideas with other students or teams. However, at time of submission all work submitted must be his/her/their own work.
Use of the Internet as a reference is allowed but directly copying code or other information is cheating. It is cheating to copy, allow another person to copy, all or part of an exam or a project, or to fake program output. It is also a violation of the Code of Honor to observe and then fail to report academic dishonesty. You are responsible for the security of your own work.
We will provide, as part of the course, functional code examples for most of the topics covered. While you are encouraged to examine these examples, your submissions must represent a good-faith effort to complete the assignment. Merely copying and pasting code from the examples will result in a failing grade. Furthermore, relying too heavily on the given examples will fail to prepare you for the much more open-ended midterm and final projects.
The following website http://disabilities.mines.edu outlines Mines's disability services. Any student requiring accommodations contact the instructor via email or schedule an individual meeting within the first two weeks of class to coordinate accommodations.
This course and all learning opportunities at Mines require a safe environment for everyone to be productive, develop professional practices, and to be able to share and learn without fear of discrimination or harassment. Discrimination or harassment of any type will not be tolerated. Sometimes harassment is unintentional, but regardless of intent the instructor will address any language or behaviors that might discriminate, stereotype, or promote harassment. If you witness discrimination or harassment of others, please bring it to the attention of Mines faculty so it can be addressed immediately.