Computer Science Department
CS314
|
Objectives | General Information | Course Materials | Quizzes |
Assignments | Projects | Exams | Grading |
Prerequisite: CS253 and all the prerequisites for CS253 including CS166 (Discrete Structures) and CS200 (Data Structures).
This course will expose students to techniques used to develop large software systems. Major topics include system and requirements engineering, object-oriented design, and systematic code testing techniques. Students will use CASE tools for many of the topics mentioned below.
The following topics will be covered in the course (not necessarily in the given order):
Late work will not be accepted without prior permission. Extensions may be granted when permission is sought in advance for reasons that are unexpected and beyond your control.
Homework assignments are to be done individually. Projects are to be done in groups. You are responsible for any announcements made in class and on WebCT.
All written work must be typed on 8.5 by 11 paper, have at least 1 inch margins and be printed in 10, 11 or 12 point type. Work should be single-spaced. Diagrams have to be drawn with the help of Rational Rose. All work must be neat and legible.
Read the departmental policy on cheating, incompletes and class attendance.
About 10 short quizzes will be given in class throughout the semester. All quizzes will be discussed in class. The goal is to motivate class discussion on the topics to be discussed later. Some quizzes will test your knowledge of material covered earlier. Quizzes are worth 5% of the final grade.
There will be about 4 homework assignments spread out during the semester. Assignments will be made available through WebCT. Each assignment needs to be done individually. Most assignments will involve writing programs and testing. Some will involve using CASE tools. Assignments are worth 25% of the final grade.
Assignment | Assigned | Due | Topic |
1 | September 5 | September 19 | Implementation of a GUI-based application using Swing classes |
2 | September 19 | September 26 | Metrics analyzer and RCS |
3 | October 1 | October 15 | JUnit |
4 | October 15 | October 29 | xSuds |
You are expected to work in a group of four to develop a software application. You will write a requirements document, a design document and code for the project. The project is worth 20% of the final grade. Project descriptions will be made available through WebCT sometime in October and will be divided into parts that follow the lecture material. You may turn in a draft of each document before the actual due date. This is for your benefit. It gives me a chance to review the document and give you comments for improvement. You will not be awarded points for the drafts. The final project demo will be held in the last week of the semester (before finals week). For every phase of the project, each teammember will do a peer evaluation.
Teams formed | October 1 |
Project assigned | October 17 |
Requirements document due | November 11 |
Design document due | December 2 |
Project code due | December 11 |
There are two exams: one midterm exam in class (20%) and one final exam (30%) during the final's week.
Exam | Date |
Midterm exam: | October 17, in class |
Final exam: | TBD |
Homework: | 25% |
Quizzes: | 5% |
Project: | 20% |
Midterm exam: | 20% |
Final exam: | 30% |
Final letter grades will be based on the relative distribution of total scores and not on any preset numerical grade. Click here to see your grades.
Last modified: October 30, 2002.