- Lab/Lecture Notes
- Message Boards
CS 2110 - Course Syllabus
2010 Spring Session
LectureMondays, Wednesdays, and Fridays, 12:00 - 12:50 pm
LabsMonday, 5:00 - 6:45 pm
Monday, 7:00 - 8:45 pm
Tuesday, 9:00 - 10:45 am
Instructor: Prof. Mark Sherriff
Office: Olsson 228A
Office Hours: TTh, 10:00 am - 11:30 am
Lab 1 - Mon@5:00 - Rachel Kralles and John Will
Lab 2 - Mon@6:00 - Jordan Fix and Brandon Marc-Aurele
Lab 3 - Tue@9:00 - Briana Whelan and Andrew Wilkes
Office Hours and Lab Schedule: Google Calendar
Email the Staff: UVa CS 2110 Staff Account - firstname.lastname@example.org
Email the staff account for direct HW questions.
Modern Software Development Using Java. 2nd edition.
Paul Tymann and Michael Schneider
Thomson / ISBN 987-14239-0123-5
Students may wish to own (or have good access to) a good Java reference book.
A few other readings may be assigned, either through handouts, on the web, or PDFs on-line.
Upon successful completion of this course, students will:
- Comprehend more advanced principles of object-oriented programming and how a programming language supports these, and apply these by developing larger and more complex programs than in their first programming course. (Topics include polymorphism, inheritance, collection classes, generics, etc.)
- Comprehend and apply principles of design at the class and object level. These principles include abstraction, encapsulation, and information hiding. This also includes the ability to define and evaluate class interfaces to solve specified design problems, as well as the ability to understand, apply, and evaluate the use of reusable components to solve such problems.
- Comprehend and analyze problems and programming issues such as dynamic memory management, indirect object references, and recursion. Also, be able to apply this knowledge by implementing software that includes these features.
- Apply knowledge of software development practice to effectively use strategies, tools and environments such as interactive development environments, debuggers, testing frameworks, etc.
- Comprehend important basic concepts of software engineering and the development of large software systems, including the software lifecycle, requirements, design, and software quality. In their development activities, students will be able to apply basic unit testing and carry out a software inspection.
- Comprehend the basic principles of the architecture of larger software systems, in particular object- oriented frameworks. Students will be able to apply this knowledge by developing a GUI using a framework.
You should meet the following requirements to take this class:
- Have taken CS 101 (CS 1110) (or placed out of CS 101 (CS 1110)) with a C- or better;
- NOTE: Passing CS 150 (CS 1120) DOES NOT give you prerequisite credit for this course!;
- Can attend class and lab regularly.
Your final course average will be calculated using the following method:
Lab - 10% - Attendance and participation in lab is required.
Homework Assignments / In-Class Quizzes - 25% - Each assignment/quiz has a set number points assigned to it, the sum of which equals at least 100.
Development Project - 15% - In a team of 4, you will develop a "larger" software project, following a specified process.
Test 1 - 15% - Covering the first third of the course.
Test 2 - 15% - Covering the second third of the course.
Final Exam - 20% - Covering mainly the remainder of the course, with some stuff from the first two-thirds.
Participation/Professionalism Penalty - up to 5% penalty - Excessive missed classes, rude behavior toward instructor or classmates, etc can be held against a student when final grades are calculated.
Your final letter grade will be determined by the following scale:
Rounding - Grade averages not falling as integers will be rounded up or down with consideration to class attendance and participation.
Pass/Fail - A course average of 60 or higher is required for a pass.
- Please feel free to stop by my office any time. I'm usually there 9:00-5:00 every day. However, it's always a good idea to email me before you come, just to make sure I'm there, and to make sure I don't leave early.
- Also, feel free to call my office (982-2688) if you can't stop by.
- I can't stress enough that email is the best way to get in touch with me. I check it literally every 5 minutes or so.
- Please don't hesitate to contact me if you have any problems, concerns, questions, or issues regarding the course, material, or anything else in the class.
- Attendance in lecture is vital to learning the material and making a good grade in this class.
- Attendance will not specifically be taken every lecture, but I will use the information from in-class exercises to get an idea as to who comes to class and who doesn't.
- Further, some graded quiz exercises may take place during lecture.
- Attendance in lab, however, is required. If you are late, you may only earn a portion of the participation grade depending on the severity of your lateness.
- Homework assignments will not be handed out in class. Everything will be available online.
- There will be a (minimum of) five homework assignments during the course of the semester. The assignments will include questions regarding and taken from the chapters assigned for each lecture. Specific grading criteria will be provided with each assignment.
- In this course, for each lab and homework assignment, you will each be assigned a partner from the same lab.
- You will have the ability to declare a certain number of other students (three or so) that you refuse to work with at the outset. After that, your partner will be psudo-randomly assigned before each homework assignment goes out.
- Partners may not collaborate with any other set of partners.
- During the course of the semester, you will be expected to complete a project of larger scale than the homework assignments. The project will follow a specified development process and you will work in teams of four. Lab time will be given over specifically for project work.
- There will be a total of three tests/exams during the course of the semester, counting the final exam.
- Any test that is missed due to any absence that is not a University Excused Absence will result in a zero (0) for that grade.
- Any test that is missed due to a University Excused Absence or due to circumstances that are approved by me beforehand must be made up within a week of the missed test.
- All grading appeals must be made in writing and submitted with the original assignment (if it is electronic, this is not necessary) either to the instructor (for tests and the project) or to the Head TA (for all other HW assignments).
- All regrade requests must be made within one week of the assignment being returned to the student. After that point, regrades may be done at my discretion.
- Bottom line: the sooner you bring something to my attention, the sooner we can correct it. Do not expect me to be exceedingly generous if you bring HW1 and HW2 to me on the last day of class.
- This syllabus is to be considered a reference document that can and will be adjusted through the course of the semester to address changing needs. This syllabus can be changed at any time without notification. It is up to the student to monitor this page for any changes. Final authority on any decision in this course rests with the professor, not with this document.
- In this course, there will be a focus on working well together and learning about the development process. A large portion of that process involves interpersonal skills and conflict management. Students and staff are all expected to treat each other with respect.
- This includes, but certainly is not limited to:
- Excessive web browsing during class
- Disrespectful language
- Promptness for all deadlines and class meetings
- Quality work
- Students can and will be penalized for unprofessional behavior.
The School of Engineering and Applied Science relies upon and cherishes its community of trust. We firmly endorse, uphold, and embrace the University's Honor principle that students will not lie, cheat, or steal, nor shall they tolerate those who do. We recognize that even one honor infraction can destroy an exemplary reputation that has taken years to build. Acting in a manner consistent with the principles of honor will benefit every member of the community both while enrolled in the Engineering School and in the future.
Students are expected to be familiar with the university honor code, including the section on academic fraud (http://www.student.virginia.edu/~honor/proc/fraud.html). Each assignment will describe allowed collaborations, and deviations from these will be considered Honor violations. If you have questions on what is allowable, ask! Unless otherwise noted, exams and individual assignments will be considered pledged that you have neither given nor received help. (Among other things, this means that you are not allowed to describe problems on an exam to a student who has not taken it yet. You are not allowed to show exam papers to another student or view another student's exam papers while working on an exam.) Send, receiving or otherwise copying electronic files that are part of course assignments are not allowed collaborations (except for those explicitly allowed in assignment instructions).
Assignments or exams where honor infractions or prohibited collaborations occur will receive a zero grade for that entire assignment or exam. Such infractions will also be submitted to the Honor Committee if that is appropriate. Students who have had prohibited collaborations may not be allowed to work with partners on remaining homeworks.
LNEC and Other Special Circumstances
If you have been identified as an LNEC student, please let the Center know you are taking this class. If you suspect you should be an LNEC student, please schedule an appointment with them for an evaluation. I happily and discretely provide the recommended accommodations for those students identified by the LNEC. Please contact me one week before an exam so we can make accommodations. Website: http://www.virginia.edu/studenthealth/lnec.html
If you have other special circumstances (athletics, other university-related activities, etc.) please contact your instructor and/or Head TA as soon as you know these may affect you in class.