[MSOE Homepage]

Dr. Taylor's MSOE homepage


Unix is a Four
Letter Word

Photo Album

Personal Homepage

Issues related to MSVC++ 5.0

Standard Template Library Info


Quiz 1 -- Course Policies

Lab 1 -- Using Existing Classes

Lab 2 -- Class Implementation

Project 1 -- Individual Design Project

Project 2 -- Group Design Project

CS-183 - Software Design

Spring Quarter 1999

Electrical Engineering and Computer Science Department
Dr. Christopher C. Taylor

S-331, 277-7339
t a y l o r@m s o e.e d u (remove spaces)

This course continues the study of software development using an object-oriented approach and the C++ programming language. Students design, document, and implement software components and incorporate these components into larger software systems. A group project reinforces the application of the software design process in a team context. (prereq: CS-182) (3-3-4)


On successful completion of this course, the student will:
  • Understand the rationale for object-oriented design and programming.
  • Understand data abstraction and abstract data types.
  • Be familiar with UML class notation and use cases.
  • Understand and be able to apply pointers and dynamic objects.
  • Understand and be able to apply STL iterators.
  • Be familiar with composition, inheritance, polymorphism, and C++ templates.
  • Be able to design and implement simple C++ classes and class libraries.
  • Be able to design small software systems using classification and use cases.
  • Be able to document the design and implementation of small software systems.
  • Be able to work in a team to create a small software system.


C++ Program Design, An Introduction to Programming and Object-Oriented Design, 2nd Ed., by James P. Cohoon and Jack W. Davidson, McGraw-Hill, 1999.


A quiz will be given at the beginning of each lab period. The lowest quiz score will be dropped. No make-up quizzes will be given.


Laboratory reports should include software code written as part of the lab project and should conform to the specified documentation standards. There is a 10% per business day late penalty for lab reports submitted after the scheduled due date. No reports will be accepted after 4:30pm, May 14, 1999.


There will be a mid-term exam and a comprehensive final in this course. It is your responsibility to be present for both exams. Please contact me in advance if you have a valid conflict with a scheduled exam.


Quizzes: (Weekly)


Lab projects:


Mid-term exam: (4/9)


Final exam: (8am, 5/11)





Attendance in lab is mandatory. Students who miss lab or leave early will only be eligible for 50% of the possible points for that lab assignment. Attendance in class and lab is expected. If you decide to drop out of the course, it is your responsibility to notify the registrar. I will not drop you for missing class. If you stop coming to class without notifying the registrar that you are dropping the course, it is likely that you will receive an "F" grade.


Students are expected to act in a professional manner in dealing with all matters pertaining to this course. In particular, deceptive practices of any sort are unacceptable (e.g., submitting source code that does not run correctly without clearly identifying the problems with it). Note that copying is not necessarily unprofessional; engineers copy good ideas from many sources all the time (subject to ethical and legal constraints). If you do copy something, you must give explicit credit to the source (e.g., article, book, web URL); also, be sure you understand anything that you copy, as I may choose to quiz you orally over that material.

Individual lab projects are to be your own work. This does not mean that you cannot discuss ideas and approaches with other students or faculty, but the final product must be yours alone. At times it may be difficult to know where to draw the line between beneficial cooperation and parasitic freeloading. For this course, it is not legitimate to collaborate to the extent of sharing source code for all or part of a particular lab project. In particular, you should never be in possession of a copy (in any form) of all or part of another student's source code. If you have any question as to what types of cooperation are acceptable, please talk to me. Obviously, the group project is treated differently.


You are responsible for assignments and announcements made in class or lab. In addition, you should periodically check your email account and the Web pages for this course.

Special Needs

If you have special educational needs, it is your responsibility to meet with me in my office in the first three weeks of the quarter to discuss them.

Feedback Wanted

I am interested in your feedback on how I can improve this course. Please feel free to stop by my office, send me email, or drop an anonymous note in my departmental mailbox with suggestions on how I can make this a better class for you. Don't wait until evaluation time because I won't see those comments until the quarter is over.

Electronic Submission Procedure

All laboratory reports for this course must be submitted electronically. You are responsible for ensuring that each report is emailed to me. In particular, it is your responsibility to make sure you type in the correct email address, etc... If you do not receive a message confirming that I received your submission, you should assume that I didn't receive it.

All reports will be graded and returned to you by email. The graded reports will be in Adobe Acrobat's Portable Document Format (PDF).

My Spring Quarter Schedule

Time Mon Tues Wed Thur Fri
8   CS183
9 CS183 CS183 CS183
10 O.H. O.H. O.H.
11   O.H. XX
12 XX    
1 Dept Mtg      
3   CS280
4 CS280 CS280 CS280
Additional office hours (O.H.) by appointment.

Tentative Schedule