605.404 Object-Oriented Programming with C++

Home Page

605.404.71, Wednesdays, 6:15 - 10:05, June 7 - August 23, 2000 (Montgomery County Center)
Whats New!!!

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

Course Description

Student Background:

A good understanding of basic data structures (605.202 Data Structures) is helpful.
A good understanding of programming in C is essential.

Student Commitment

Students should be prepared to spend between 6-16 hours a week outside of class depending on background and willingness to form development teams.

Course Texts:

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

Required Software:

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. The instructor will be providing solutions using the college's g++ (version 2.8.1) compiler.

References:

Handouts - class lectures will be either reproduced or made available from this web site.
"UML Distilled", Martin Fowler, 1997, Addison-Wesley.
"The Unified Modeling Language User's Guide", by Grady Booch, 1999, Addison-Wesley.
"The Unified Modeling Language Reference Manual", by James Rumbaugh, 1999, Addison-Wesley.
"The Unified Software Development Process", by Ivar Jacaobson, 1999, 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 homework 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 use any instructor provided code as a foundation for follow-on assignments the semester project.

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. Because of the size of the class, group size must be 2 to 3 people.

Exams may be given in-class but are usually take-home. They 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

GNU Toolkit - contains many pre-compiled unix tools for the PC, including g++, make, and gdb.
Programmer's File Editor (Free-ware) - provides a multi-window PC window editing environment.
gvim vi-style editor (Free-ware) - provides a PC version of the vi editor, both terminal and graphical versions
doc++ documentation software (Free-ware) - provides a "javadoc-like" tool for building html-based and printable source code documentation.
Rational Rose Case Tool (student version) - provides a good tool for creating most UML diagrams.
PKZIP (shareware version) - provides file archive and compression capabilities.
WS_FTP (limited edition) - provides graphical FTP interface.
STL Links (Ian Burren WEB Page, Mark Sebern WEB Page)

Information Links

Quick Start for Rational Rose (contributed by John Madden) - Provides a download-to-drawing quick tutorial on getting started with Rational Rose.
Association of C and C++ Users (ACCU) C++ Resource Index - Provides list of lnks to other sites. The list is rather extensive, and a good place to look for answers to questions. The links cover areas such as learning C++, libraries in C++, style guides, standards, and compilers.

C/C++ Users Journal

@ C++ Archive - Good place for a C++ tutorial to brush up on those skills. Contains a good amount for information on uses of C++; games, algorithm implementation, etc. Decent list of other resources as well. Tends to be a lot of advertising, but not so much that it interferes with the intent of the site.

tutorials

Bjaurne Stroustrup's FAQ - not a lot of technical C++ information. There is a good bit of historical information as well as information on why C++ is the way it is.
Rational UML Resources - This is the place to go for a online learning about UML.

School Links