Engr 660: Software Engineering II
(Software Product Lines)
Fall 2003
Syllabus

Locations

The Fall 2003 class meets in Weir 235 from 11:00 until 12:15 on Tuesday and Thursday.

The class is taught by Prof. Conrad Cunningham, whose office is 203 Weir Hall. Prof. Cunningham's official office hours for this session are 10:00 a.m. to Noon on Wednesday or by appointment at other times.

Prof. Cunningham's voice telephone number is (662) 915-5358 and fax number is (662) 915-5623. His WWW home page is http://www.cs.olemiss.edu/~hcc/ and his email address is cunningham@cs.olemiss.edu (send?).

The WWW home page for this class is http://www.cs.olemiss.edu/~hcc/engr660/ .

The final examination for this class is scheduled for Noon on Thursday, 11 December 2003.

Student Disabilities Services Statement

"It is the responsibility of any student with a disability who requests a reasonable accommodation to contact the Office of Disability Services (915-7128). Contact will then be made by that office through the student to the instructor of this class. The instructor will then be happy to work with the student so that a reasonable accommodation of any disability can be made."

Course Goal

The goal of this course is to increase the students' abilities understand, use, design, and construct general families of software systems.

Course Description

This course will examine concepts and techniques for the design and implementation of software product lines, software frameworks, and other generic programming artifacts.

Prerequisites

This class is intended for students admitted in full standing to the graduate program of the Department of Computer and Information Science. Students are expected to have a background in object-oriented programming, algorithms, data structures, and programming languages similar to the undergraduate courses CSCI 111, 112, 211, 433, and 450. Students are expected to have a mature understanding of data abstraction, inheritance, polymorphism, composition, and other object-oriented concepts.

Graduate students in other fields should not be enrolled in this class without the explicit permission of the instructor and of their department. Any students in this category are expected to provide the instructor with a note from their advisor or department chair indicating such permission.

Source Materials

Readings:

Journal and conference articles, research reports, and other materials as appropriate.

Course Topics

The actual topics and their order will be refined as the semester progresses.

• information hiding and modular design
• program families
• object-oriented frameworks
• design patterns
• commonality/variability analysis
• software product line methods
• process patterns
• design contracts
• etc.

Professional Conduct

As a student in Engr 660, you are expected to conduct yourself in a professional manner according to the Honor Code of the School of Engineering, the Information Technology Appropriate Use Policy, the M Book, and any other relevant policies.

Unless otherwise stated explicitly for an assignment, all assignments and projects in this class are covered by the School of Engineering's Honor Code statement on plagiarism. It is plagiarism "to knowingly deceive, copy, paraphrase, or otherwise misrepresent your work in a manner inconsistent with professional conduct".

Grading

The grading scale is A [90..100], B [80..90), C [70..80), D [60..70), and F [0..60).

Credit toward the semester grade will be allocated to each of the components as follows:

Assignments

• All students are expected to study the relevant portions of the source materials in conjunction with our class discussions (i.e., before coming to class).

• In preparing and submitting homework papers make sure that:
  • your name, the course number or name, the assignment identifier, and individual exercises are clearly marked on the paper. (If it is a group assignment, give the group identifier and the names of all members.)
  • for any handwritten work, you write legibly on only one side of the paper in a black or blue pen or dark pencil. (Do NOT use red or green ink!) Some assignments may require that materials be generated with a word processor and/or other tools.
  • your paper is stapled together in the upper left corner.

• As appropriate, there may be a few in-class assignments or quizes that count toward the assignment/project portion of the grade.

• Some of the projects may be small group projects; others may be individual efforts. One of these might involve presentation of a paper or other material to the class on some aspect of software architecture or related software technology. Another project may involve a significant analysis and design effort.

• All students or groups are expected to complete their assignments by their due dates. If an assignment is submitted late, a penalty of 10 percent of that assignment's grade will be assessed for each day it is late. A homework assignment will not be accepted after graded papers have been returned, after a solution has been distributed, or after the final examination.

Examinations

• I plan two examinations, a mid-term and a final. Both exams will be required. I may decide to replace the final exam by a final project by mid-semester.
• The exams may include both in-class and take-home components.
• Please do not ask to take the final exam at an earlier time than set for the entire class.

Support Acknowledgment

This special offering of ENGR 660 is partially funded by a gifft from Acxiom Corporation.

[ ENGR 660 Home ]
[ Cunningham's Home | Teaching | Current Courses ]
[ Department's Home | Courses | Graduate Courses | Undergraduate Courses ]