CS 212-01 Software Development
|Lectures:||Monday, Wednesday, Friday, 3:30pm – 4:35pm|
|Location:||Lo Schiavo Science Center, Room G12|
This course gives students experience designing, implementing, testing, and debugging large programs. Students will also get advanced Java programming experience; covering topics such as inheritance, multithreading, networking, database programming, and web development.
Please contact the instructor if you have any questions or concerns regarding the course or projects.
|Name:||Professor Sophie Engle|
|Office:||Harney Science Center, Room 532|
|Hours:||Mondays, Wednesdays, 5:00pm – 6:30pm
and by appointment
Please contact the teacher assistant for all homework-related matters.
|Room:||Harney Science Center, Room 530/535|
|Hours:||Tuesdays, 2:30pm – 4:00pm
Thursdays, 10:30am – 12:00pm
You may also visit the CS Tutoring Center for help with this course.
You must have completed CS 112 Introduction to Computer Science II with a grade of C or better.
There are no required books for this class. However, it is recommended that students have a Java reference book. Please see the instructor for recommendations.
Announcements will be posted on the course website in Canvas at:
Canvas has multiple options for automatically notifying you when new announcements are posted. Students are responsible for staying current on all course announcements.
At the end of this course, students should be able to:
- Independently design programs
- Produce professional-quality code
- Implement large programs of greater than 2,000 lines of code
- Design and execute tests to identify software bugs
- Repair software bugs, redesigning and refactoring code when necessary
- Utilize, analyze, and critique code written by others
Assessment of these outcomes will be done by a combination of quizzes, exams, homework, projects, and code review.
The following is an estimated list of topics and weekly schedule. Check the course website for the latest schedule.
|Week 01:||Course Introduction|
|Week 02:||File IO and Exceptions|
|Week 03:||Data Structures|
|Week 04:||Object Oriented Design|
|Week 06:||Basic Multithreading|
|Week 07:||MIDTERM EXAM|
|Week 08:||Advanced Multithreading|
|Week 09:||Advanced Multithreading|
|Week 10:||Regexs and Unit Testing|
|Week 11:||Sockets, HTML, and HTTP|
|Week 12:||Servlets and Sessions|
|Week 13:||Databases and SQL|
|Week 14:||FINAL EXAM|
|Week 15:||Comprehensive Example|
|Week 16:||Special Topics|
|Finals:||Final Project Grading|
Interactive grading for the final project will be held during finals week. Exact dates and times will be posted towards the end of the semester.
This course will be a hybrid flipped classroom, with an emphasis on mastery learning. Class time will consist of a mix of traditional slide-based lectures, interactive code walkthroughs, in-class lab exercises, and in-class quizzes. You are expected to spend between 15 to 20 hours per week minimum outside of class.
Assignments consist of homework exercises and quizzes. You will usually be given class time to work on these assignments, allowing you to get help from the instructor. If you do not finish these assignments in class, you will need to complete them on your own time.
Quizzes will often be given unannounced at the start of class. You will usually have several opportunities to retake the quiz to maximize your score.
There will be two exams: a midterm and final exam. The final exam is not comprehensive, and will be held during the last week of class.
Finals week will be reserved for interactive project grading. A signup sheet will be posted towards the end of the semester. If you have travel plans during finals week, please confirm your travel dates first with the instructor.
Project assignments place an emphasis on code quality—it is not enough to achieve correct results. Each project will undergo a rigorous code review checking for specific criteria, such as proper encapsulation and generalization, efficiency, and maintainability. We use a mastery learning approach with projects: you may not move on to the next project until (a) the project produces correct output, and (b) the project passes the code review process.
As such, the project grade will depend on the number of projects completed by each student. The exact grade for each project depends on the submission process. Each student receives one opportunity per project to fix and resubmit the project. Additional resubmissions may result in a point deduction.
Additional details on each project and the project submission process will be posted on the course website.
The final grade for this course will depend on a mix of assignments (homework and quizzes), exams (midterm and final), and projects. The specific breakdown is as follows:
Please note that this is a tentative breakdown and subject to change.
Letter grades will be assigned according to the following scale:
For example, you will receive a C letter grade if your grade is greater than or equal to 70% and less than 77%. Please note this scale is subject to change. See the Undergraduate Student Regulations for more information about letter grades and how they are translated into GPA.
Students are expected to be on-time to all classes. Attendance is mandatory for all exams, quizzes, labs, and exercises. Exam dates will be posted on the course calendar.
All deadlines and exam dates are firm. No late homework or quizzes will be accepted. All projects, except the final project, may be submitted (or resubmitted) up to the last day of class. The final project will be submitted at interactive grading during finals week.
Exceptions to this policy are made only in the case of verifiable medical or family emergency. Extensions and makeup exams must be arranged PRIOR to the original deadline unless in case of extreme emergency (such as an emergency room visit).
All students are expected to know and adhere to the University of San Francisco's Academic Honor Code. Go to http://www.usfca.edu/catalog/policies/honor for details. The first violation of the Honor Code will result in an automatic 0 on the offending assignment, and repeat violations will result in an automatic F for the course.
Simply put, do not cheat. Cheating includes copying code from the web, copying code from other students, working too closely with other students (all work in this class must be done individually), or having anyone other than yourself write your code.
We will be running MOSS on code to detect cheating in class. This tool determines the similarity of two programs, and as a result also detects shared logic (often the result of working too closely together). See http://theory.stanford.edu/~aiken/moss/ for more information.
Peer Tutoring Services
The CS Tutoring Center provides peer tutoring services and workshops for lower-division computer science courses, including CS 212 Software Development. See http://tutoringcenter.cs.usfca.edu/ for more details.
The Learning and Writing Center (LWC) also provides assistance to students in their academic pursuits. Services are free to students and include individual and group tutoring appointments and consultations to develop specific study strategies and approaches. Please visit http://www.usfca.edu/lwc for more information.
Student Disability Services
If you are a student with a disability or disabling condition, or if you think you may have a disability, please contact Student Disability Services (SDS) within the first week of class to speak with a disability specialist. If you are determined eligible for reasonable accommodations, your disability specialist will send your accommodation letter to the instructor detailing your needs for the course. For more information, please visit http://www.usfca.edu/sds or call (415) 422-2613.
The syllabus page shows a table-oriented view of the course schedule, and the basics of course grading. You can add any other comments, notes, or thoughts you have about the course structure, course policies or anything else.
To add some comments, click the "Edit" link at the top.