SWE 619 Course Syllabus

Syllabus

Software Construction
SWE 619 Course Syllabus
Fall 1997

Professor:	Jeff Offutt
Office:	S&T II 355, 993-1654
Email:	offutt(at)ise.gmu.edu
URL:	http://www.ise.gmu.edu/~offutt
Class Hours:	Tue 4:30 -- 7:10, Robinson B228
Office Hours:	Anytime electronically or M 2:00 -- 4:30, or by appointment
Prerequisites:	SWE Foundation Material (informally: solid programming skills, data structures, and elementary discrete math.)

TEXT:

Bo Sanden, Software Systems Construction.
Suggested: Smith, Object-oriented Programming in Ada 95.

OBJECTIVES:

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. This course is part of the core of the SWE program.

CONTENT:

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. The course is heavily based on Ada.

PREREQS:

Data structures, knowledge of structured programming in a high-level language, and concepts of machine organization. You should understand the concepts of common data structures such as linked lists, queues, stacks, and trees, and know how to program them in some programming language.

READING:

We will cover most of the first 6 chapters of Sanden. I expect you to read the assigned material before lecture. Be warned that if you do not read the material before class, you may find the lecture confusing.

EXAMS:

There will be a midterm and a final. Both will be in class.

PROGRAMS:

Programs must be turned in to the TA or to me and are due before class on the day of their due dates. They may not be turned in electronically. Unless otherwise specified, you should turn in 1) a listing of the source code along with something that shows that it compiles cleanly, 2) a listing of the program's output, and when necessary 3) a listing of the program's input. Programs will graded on style and formatting as well as correctness. Programs will be graded on a scale of 100 and unexcused late programs will lose 10 points per class period.

HONESTY:

Each program and homework 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. Violations will result in failure of the course.

MAKEUPS:

Unless arrangements are worked out in advance, missed quizzes and tests cannot be made up. I understand that your job may occasionally take you out of town; so does mine. If you are going to be forced to miss class on the day something is due, let me know ahead of time, in writing, preferably by email (this is for your protection, as I am somewhat forgetful).

GRADING:

Grades will be (approximately) 5% quizzes and homeworks, 40% five programs, 25% the midterm, and 30% the final.

Syllabus

Schedule

Readings

Handouts

My home page

Jeff Offutt
Sat August 23 1997