SWE 619 Course Syllabus
Schedule Updates Home page
   OO Software Specification and Construction
   Fall 2009

Professor:  Paul Ammann 
Office:  ENGR 4428, 993-1660 
Email:  pammann@gmu.edu
URL:  http://cs.gmu.edu/~pammann/619.html
Class Hours:  Wednesday 4:30 to 7:10, Innovation Hall, 208
Prerequisite:  SWE Foundation Courses or equivalent 
Office Hours:  anytime electronically; Wednesday 7:15-8:15 (directly after class); by appointment

Course Description

To give the students a solid understanding of modern software construction. To prepare students to construct sequential and concurrent programs. To encourage the construction of software systems of high quality. In-depth study of software construction in a modern language including control structuring and packaging. Concepts such as information hiding, data abstraction, and object-based and object-oriented software construction are discussed and illustrated. This course is part of the core of the SWE program. This section of 619 uses Java.

Course Materials

Assignments

Submit assignments that are Java programs electronically via Blackboard.

Note: Homework is due exactly at the start of class on the due date. Paper and pencil homework can be brought directly to class. Or, you can submit an electronic version via Blackboard.

Note: Blackboard is a pretty horrible system, but it should work ok as a drop box for your assignments, as well as a way for you to check your grades.

The GTA for this course is Dawei Du, who can be reached by email at ddu@gmu.edu.
Update 9/9/09: GTA Office hours are Wednesday and Thursday 1PM to 3PM in ENGR 4456.

Important: For programs, please submit a paper copy as well as the electronic version.   This is because of the way that the University runs it printing services. Thank you for your support.

Details about specific requirements for each assignment are given with each assignment. I typically post a top student solution as the sample solution. Occasionally, I post my own solution or present it in class.

Early homework assignments focus on theortical aspects from Liskov. Later homework assignments reinforce specific programming techniques, as well as the design points made in Bloch. Each homework assignment is designed to be fairly short, and homework is due on a weekly basis.

Quizzes

Each class, except for the first class, begins with a short quiz. Each quiz covers material from the previous session(s).

The goal of the quizzes is to keep students abreast of the material covered in class. Because of the quizzes, there is no midterm exam.

Missed Homework and Quizzes

In recognition of the fact that many students have occasional but unavoidable commitments that preclude attendance at every class, I drop each student's three lowest scores prior to final grade computations. I select the combination of homework and quiz scores most advantageous to the student. For example, I may drop drop 2 quiz scores and 1 homework, or 3 homeworks, or any other combination totaling 3.

In view of this policy, late homework is not accepted and there are no make-up quizzes. In fairness to other students, please do not ask for an exception.

Final Exam

A final exam is held during the University-scheduled exam period.

Honor System:

Students are reminded that the honor system governs all work turned in for credit. Each assignment must be worked on individually. A submission carries with it an implicit statement that the submission is your own work. You may discuss the requirements and syntactical issues, but not solutions or designs. Collaboration is not allowed on the quizzes or on the final. I will refer violators to the GMU Honor Committee according to the procedures given in the GMU Course Catalog. Further details available at the CS Department's Honor Code page.

Grading

Grades are computed as: Assignments (33%), Quizzes (33%), Final (34%).

Other Resources

Of course, java.sun.com is a good place to go for Java help.

Updates

As the semester progresses, I post notices about changes to the course updates page.