Engr 691-12: Special Topics in Engineering Science
Fall Semester 2000
The fall semester 2000 class meets in 351 Weir Hall
from 4:00 p.m. to 5:15 on Monday
The class is taught by Prof. Conrad Cunningham, whose
office is 312 Weir Hall. Prof. Cunningham's official
office hours for this semester are 1:30
p.m. to 3:30 on Tuesdays and Thursdays 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
and his email address is firstname.lastname@example.org
The WWW home page for this class is
The final examination for this class is scheduled for 8:00 a.m. on
Thursday, 14 December 2000.
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."
The goal of this course is to increase the students' abilities to
understand, use, and construct sophisticated software abstractions.
This special topics course will examine concepts and techniques
for design and code reuse and generic programming in the context of
Java and other object-oriented technologies. The course will focus on
use of design contracts, software design patterns, and application
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. Use of the Java programming language will be
required in programming exercises.
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.
- Required Textbook:
- Mark Grand.
Patterns in Java: Volume 1, Wiley, 1998.
- Suggested Textbook:
- Darren Govoni.
Java Application Frameworks,
Wiley, 1999. ISBN: 0-471-32930-4.
- Several journal and conference articles, research reports, and
other materials as appropriate.
The actual topics and their order will be refined as the semester
- Review of data abstraction
- Review of object orientation
- Design-by-contract techniques
- Unified Modeling Language
- Software design patterns
- Application frameworks
- Component concepts and technologies
- Software product line techniques
As a student in Engr 691, you are expected to conduct yourself in
a professional manner according to the
Honor Code of the School of Engineering, the Information
Appropriate Use Policy, the M Book, and any other
Limited Collaboration Policy. Unless otherwise
indicated, any homework assignment or programming exercise given in
this class will be an individual assignment. The work you submit is
to reflect the knowledge, understanding, and skill that you have
attained as an individual. However, the instructor does want to
encourage the development of a community of scholars who are actively
engaged in discussion of the ideas related to this course. With this
in mind, you are allowed to discuss solutions of the homework and
programming problems with other students if done so according to the
- You may discuss ideas for homework and
programming assignments with your classmates. However, you
cannot collaborate on writing the solution or the
program code. That is, you can talk about the problems and
ideas for solving them, but you cannot write things down with anyone
else. You are, of course, prohibited from copying or seeing another
student's written solution, and you are not allowed to show your work
to anyone else. Similarly, you are not allowed to copy text or
program code from a book or a page on the Web unless explicitly
authorized to do so by the instructor.
- You should accept help with care. If you work
too closely with another student, you might mislead yourself into
believing that you understand the concepts and techniques better than
you actually do. Don't forget that the instructor has office hours
and can probably give you hints or suggestions to get you started.
- You should give help with care. Do not help
anyone too much. When you have solved a problem, it is tempting to
just tell other students how you solved it. Instead, try to allow
them to come to the solution on their own. Maybe give them a hint to
help them get "over a hump." Remember that helping someone too much
will hurt them in the long term if they can't work through problems on
the exams by themselves. So avoid the temptation to do so. If you
can't help other students without giving away the whole solution,
direct them to see the instructor (who may or may not have a way to
"edge" them toward the solution).
- You are not obligated to help anyone. If you
feel uncomfortable helping another student for any reason, please
direct them to see the instructor.
- Except as described above, all work in this class is
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".
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:
| Homeworks/Projects || 40% |
| Exams || 60% |
- All students are expected to study the relevant portions of the
textbooks and handouts in conjunction with our class discussions
(i.e., before coming to class). Explicit reading assignments
will not always be given.
- 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
- 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.
- Several of the homework assignments will be programming
For these exercises, you will need to submit appropriate design
documentation, a listing of your program code, and appropriate printed
output from your program testing. Make sure that you clearly label
the assignment as described above.
- As appropriate, there may be a few in-class assignments or quizzes
that count toward the assignment/project portion of the grade.
- The projects will be carried out in small groups. 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 programming
- 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.
- I plan two examinations, a mid-term and a final. Both exams will
- 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.
[ ENGR 691 Home
[ Cunningham's Home
| Current Courses
[ Department's Home
| Graduate Courses
| Undergraduate Courses
Send any comments or suggestions to Prof. Conrad Cunningham,
Copyright © 2000, H. Conrad Cunningham
Last modified: Thu Feb 1 10:29:20 2001