605.404 Object-Oriented Programming with C++

Home Page

605.404.71, Mondays, 7:15 - 10:00, September 7 - December 14, 1998 (Montgomery County Center) Whats New!!!

Instructor: Jim Stafford (jcstaff@apl.jhu.edu)

Course Description

Student Background:

A good understanding of basic data structures (605.202 Data Structures Using C++) is helpful.
A good understanding of programming in C (605.201 Introduction to C++ Programming) is essential.

Course Texts:

"Object Models, Strategies, Patterns, & Applications", by Peter Coad, 1995, Yourden Press.
"C++ Primer", Third Edition, by Stanley Lippman and Josee Lajoie, 1998, Addison-Wesley..

Required Software:

A C++ compiler. This course addresses a compiler-neutral view of OOP/C++. Most current versions of commercial C++ compilers will be sufficient to complete all class assignments. The labs are equipped with several unix and PC based compilers.

References:

Handouts - class lectures will be made available from this web site.
"Object-Oriented Software Engineering", by Ivar Jacobson, 1992, ACM.
"Object Oriented Analysis and Design with Applications", Second Edition, by Grady Booch, 1994, Benjamin/Cummings.
"UML Distilled", Martin Fowler, 1997, Addison-Wesley.
"Effective C++", Scott Meyers, 1992, Addison-Wesley.
"More Effective C++", Scott Meyers, 1996, Addison-Wesley.
"Design Patterns", by Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides, 1995, Addison Wesley.

Grading: 100 >= A >= 90 > B >= 80 > C >= 70 > F

Homework: no grade
Semester Project:

Mid-Term Exam: 20%
Final Exam: 30%

Homework will be assigned for most classes. They are due the following week and will be covered at the beginning of the next class period. Selected home works will be collected for review by the instructor, but no grade will be assigned. Use homework as a chance to gain hands-on trial and error experience with the topics addressed in class. Sample programs and other code used for these assignments will be made available off this web page. You may down load them using the lab or through the dial-in modems.

One design project will be assigned, covering the entire semester. It will consist of individual analysis and implementation deliverables. Good object oriented principles will be used as the basis for grading all lab projects. User interfaces ("glitz") will not be a consideration in project grades. Both phases may be done in groups up to 3 people.

Exams are given in-class (final) and take-home (mid-term) and will consist of short essays, design and coding problems. Detailed C++ syntax will not be a focus of any exam. All exams are open-book/notes.

Grading Policy:

Late projects are deducted 10% per week.
Project documentation must be typed. Figures may be hand drawn. Hand-written text documentation will not be accepted.
Make-up tests will be provided in the event of a scheduling conflict. Please schedule these well in advance so that an alternate test can be developed.
Class attendance is highly recommended but not mandatory. The student is responsible for obtaining any written or oral information covered during an absence.
All work must be completed by the final exam. No incomplete grades will be assigned except in severe emergencies.

Instructor Availability:

Academic Integrity:

Homework may be shared freely among the students.
Projects are to be the individual work of the student or groups. Problem areas of the projects can be, and are encouraged to be, discussed with other students/groups as well as the instructor. But, at no time, may complete designs or code segments be copied in their entirety.

Related Links

School Links