C Sc 335 Syllabus:Object-Oriented Programming and Design
University of Arizona,Fall2013
Catalog DescriptionC Sc 335 -- Object-Oriented Programming and Design (4 units) Fundamentals of object-oriented software development. Includes design principles, inheritance, polymorphism, Unified Modeling Language (UML), event-driven programming with graphical user interfaces, applications of design patterns, and use of existing frameworks.Weeklylab.Prerequisite: C Sc 127B or C Sc 227
When/Where Common lectures on Tuesday and Thursday 3:30-4:45 in Education 211. You also have a recitation section with 22-28 studentson Wednesdays or Thursdays.
Section
/Time
/Location
/Section Leader
/001B / 4:00 - 4:50 Wednesdays / 301 Modern Languages / Eric Cascketta / uofkuv
001D / 12:00 - 12:50 Thursdays / 502 Education / Gabe Kishi / gtkishi
001E / 1:00 - 1:50 Thursdays / 942 Gould Simpson / Zach Montoya / zacharymontoya
Rick's Office Hours 727 Gould Simpson:See byappointment:
Course WebSite (or Google mercer cs, or check our D2L page to also find this link)
Required Textbooks: There is no required text. Online readings will be assigned.
GradingYour letter grade will be determined based on the following weighted average and cutoffs.
18% Test 118% Test 2
9% Lecture and Section Participation
33% Programming Projects
22% Final Team Project / A >= 90%
B80.0 to 89.9
C70.0 to 79.9
D60.0 to 70.9
E60.0
Programming ProjectsYou will be completing allprogramming projectscollaboratively in a team of two in a pair-programming mode.Software development in teams provides valuable experience with social, process, and technical issues. Working with teams may end up being the most important skill you will develop this semester.
Final Team Project The final project will be completed in a teamoffour. Itwill be relatively complex with many new types (classes) that you design. This final team projecthistorically requires about 40 to 60 hours of your time during the final five weeks of class.Because you will be completing a final project instead of a final exam during finals week, the university requires that you must complete a report on your final project. A template will be provided at the end of the semester to guide you in writing it. You must turn it in during the final exam period for project demos to get credit for this.
Late PoliciesWhen other 335 students were surveyed with the question "What advice would you give to future 335 students to be successful in 335?".The most common two responses have always been "Attend class" and "Start your projects on time". All projects should be turned in by the due date and time. Anyassignment project turned in past the deadline and within 24 hours is considered to be one day late. Each late day results in a 10% reduction of the maximum number of points for that project. Projectsnot turned in within 3 days after the deadline will not be accepted with aresulting score will be 0 for all team members. This late policy does not apply to the final team project that will have a separate late policy.
Lecture and Section ParticipationCollaborative active learning participationduring lecturewill be graded as a team like this:
0: Did not show up
1: The team made a half-hearted attempt to complete
2: Answers complete, but need not be correct, while respecting your teammates.
Section participation is graded similarly, but individually:
0: Did not show up
1: You arrive late or leave early according to you section leader's individual preference
2: Paid attention while respecting your classmates
No Participation grade can be made up unless you have a valid reason, listed officially as
- All holidays or special events observed by organized religions will be honored for those students who show affiliation with that particular religion,
- Absences pre-approved by the UA Dean of Students (or Dean’s designee) will be honored
Absence PolicyAttend all lectures and recitation sections. Section and LectureParticipation is worth 9% of your grade. Most lectures will have an active learning activity. During the final project, teams will meet at the end of lecture and count as part of your final project grade. You do not want to be known as the team member who doesn't show up and who doesn't stay connected because your team members will have the ability to vote your final project grade (worth 22% of your grade) to almost 0.
In short, plan on attending all lectures and recitation sections.
Accessibility and Accommodations It is the University’s goal that learning experiences be as accessible as possible.If you anticipate or experience physical or academic barriers based on disability, please let me know immediately so that we can discuss options.You are also welcome to contact Disability Resources (520-621-3268)to establish reasonable accommodations.
Please be aware that the accessible table and chairs in this room should remain available forstudents who find that standard classroom seating is not usable.
Classroom BehaviorThings considered disruptive include talking with others during lectures, cell phone use, game device use, laptop use for anything not course related (playing games, email, etc), sleeping, eating, arriving late or departing early (without prior notification), and newspaper reading. Such activities distract others and interfere with instructional activities. Again, students should use class time to further their learning, through active engagement with the material.
The University of Arizona has an explicit policy on disruptive behavior that includes the instructor's right to kick you out:
For example, if you keep talking as I am glaring at you, I may ask you to leave the class. However, as a colleague (Dr. McCann) writes: 'I know sometimes you can't resist making a comment to your friend. I don't want you to injure yourself by trying to hold it in. Go ahead and whisper that comment. Just don't let it grow into a conversation. If what you have to say is that irresistibly juicy, write a note or hold the thought until after class. I'm confident that the passage of time will not diminish its wit and hilarity. The point, of course, is to avoid distracting other students."
You are also expected to treat others with respect. Disruptive behavior in my CSc 335 course also includes:
- Dissing other students for not knowing what you know, intentionally or not
- Bragging about what a great programmer you are, intentionally or not
- Bragging about how quickly you finished a programming assignment or how easy it was
- Correcting others in a condescending manner
Academic Integrity and Penalties (a.k.a. Cheating) This course requires individual attention and effort. Unless otherwise specified, all work is expected to be that of each team alone. Students are responsible for understanding and complying with the University's Code of Academic Integrity. The Code has the full text. Among other provisions, the Code demands that the work you submit is your own, and that graded programs and exams will not subsequently be tampered with. The Code demands that you do not turn in copied code as if it were your own work. It is immaterial whether the copying is done electronically, by retyping, or using solutions from the Internet, or any other means you may think of.
If your code matches another team's code or from the Internet, or if you indiviually copy during a test, a report will be filed to the Dean of Students with these possible sanctions:
A faculty member may impose any one or a combination of the following sanctions: a written warning, loss of credit for the work involved, reduction in grade, notation of the violation(s) on the student’s transcript, a failing grade in the course, or revocation of a student’s degree. The faculty member may also impose a sanction of suspension or expulsion from the program, department, college, or University.
These sanctions also occur if you help another person or team cheat. Do not give your code to anyone! Do not post your code to the Internet. Don't give code to anyone, especially your friends. Do not help any person cheat in any way even when they promise you they will not use your code.
You may reuse any code from our required textbook, lecture code demos, PowerPoint slides associated with this course, and code written or presented in section. Additionally, you may use code snippets found on the Internet as long as you credit those small pieces of code with the authors's names, even if you modify it. An example: You copy code that allows a JTable to be sorted by column and adjust it to match your particular model. There are several hard to find tricks to this otherwise.
How to Avoid Such Serious Sanctions Begin your projects as soon as possible. Do not wait until the due date! This is when desperation sinks in and you are tempted to take a chance. You are better off getting a 0 than getting caught cheating. The work you turn in must be your own, not another's. Do not copy other projects. Do not give your code to anyone even if the other person or team promises not to turn it in as their own, in which case you who did all the work may suffer the same sanctions. And of course, do not look at another person's test while the test is in progress or try to alter your exam after it's graded. In short, the work you turn in must be your own work, not someone else's.
Required Software We will be usingJava 7 (a high-level computer programming language) and Eclipse Kepler 4.3 (an Integrated Development Environment (IDE)). Both are available in 228 Gould Simpson (and possibly other computer labs). If you have your own computer, you can add the required software for free even though it cost $100's of millions to others. Both are available for Windows, Linux, and Mac OS environments. See our website link for these two required tools:
Q&A with Piazza This semester we will be using Piazza for class discussion. The system is highly catered to getting you help fast and efficiently from classmates and section leaders and Rick. Rather than emailing questions to the teaching staff, we encourage you to post your questions on Piazza.
Subject to ChangeInformation contained in this course syllabus other than the grading and absence policy is subject to change with reasonable notice.