SYLLABUS HANDOUT
for
CPT 125 9A
C++ PROGRAMMING II
Alan R. Reinarz
2001-2002/Spring
Sa 8:00a–11:35a • SOC 145
METHODS OF CONTACTING INSTRUCTOR:
HOME PHONE NUMBER: 556-3071
METRO OFFICE
HOURS
LOCATION
PHONE
FAX
M/W/Sa:
1:00p-2:00p
SOC 300
738-4089
738-4553
T/Th: 4:00p-5:00p
SOC 300
738-4089
738-4553
M: 4:00pB5:00p
EVC 156
289-1364
289-1405
IMPORTANT DATES:
Date class begins: 3/2/02 • Date class ends: 5/18/02 • Last date to drop class: 4/26/02
WELCOME TO METROPOLITAN COMMUNITY COLLEGE!
Ver. 3/8/2002
Metropolitan Community College
Page 2
IMPORTANT DATES: Date class begins:
Last date to drop class:
3/2/2002
4/26/2002
Date class ends:
Class will not meet:
5/18/2002
3/30/2002
SECTION I: THE CLASS AND THE INSTRUCTOR
COURSE SECTION AND TITLE:
CPT 125 9A—C++ Programming II
INSTRUCTOR=S NAME:
Alan R. Reinarz
LOCATION OF CLASS:
SOC 145
LOCATION OF LABS:
SOC 1271
METHODS OF CONTACTING INSTRUCTOR:
e-mail: areinarz@metropo.mccneb.edu
web site (under construction): http://cot.mccneb.edu/areinarz
(home phone): (402) 556-3071
METRO OFFICES
HOURS*
LOCATION
PHONE
FAX
M/W/Sa: 1:00p-2:00p
SOC 300
738-4089
738-4553
T/Th: 4:00p-5:00p
SOC 300
738-4089
738-4553
M: 4:00p-5:00p
EVC 156
289-1364
289-1405
*Stated office hours may need to be changed due to special circumstances or events. If the student wishes to meet with the instructor at a time other
than scheduled office hours, the student should make an appointment with the instructor.
SECTION II: THE COURSE
COURSE DESCRIPTION:
This course is a continuation of the CPT 123 (C++ Programming I) course. Topics covered include abstract data types
(ADTs), structures, classes, input/output, strings, pointers, dynamic data, and object-oriented software development.
COURSE PREREQUISITES:
CPT 123 – C ++ Programming I
COURSE OBJECTIVES: Upon completion of this course, the student will be able to do the following:
1. Understand and utilize abstract data types (ADTs).
2. Understand the differences and similarities of structures and classes.
3. Appreciate the importance of data hiding.
4. Learn the technical details of developing robust classes.
5. Understand and utilize pointers, dynamic data, and reference types in a C++ program.
6. Understand the complexities of operator overloading, a key mechanism in the design of classes.
7. Understand the principles of software engineering with inheritance.
8. Understand and utilize virtual functions and polymorphism.
9. Understand file processing and string stream input/output.
10. Be able to format output data.
11. Understand stream manipulators and stream states.
12. Be familiar with the concept of strings (character arrays).
13. Understand string and character processing functions.
REQUIRED/SUPPLEMENTAL MATERIALS:
1.
Textbook:
Object Oriented Programming Using C++, 2nd ed., Joyce Farrell (2001: Course Technology)
ISBN: 0-619-03361-4
2.
Minimum two (2) 32" High-Density floppy diskettes
SECTION III, PART A: INSTRUCTOR RESPONSIBILITIES
METHODS OF INSTRUCTION:
1Students
will find computer resources for this class at Computer and Office Technology (COT) Computer Labs on all cam-
puses.
Ver. 3/8/2002
Metropolitan Community College
Page 3
In each lecture during this course, the instructor will cover material the student needs to learn and accomplish. In addition,
written handouts will be provided from time to time. These will be used to supplement the text material and expand the
course.
Instruction will consist mainly of lecture material presented by the instructor. In some classes, group discussion and
demonstration will be utilized. In all meetings, discussion opportunities will be provided and the student is encouraged to
ask questions and clarify information as the instructor is lecturing and/or presenting material.
This course requires students to work an average of 1.5 hours per week in hands-on, lab activity. Students are responsible
for completing all lab work outside of the classroom. While you may choose to do this lab work someplace other than the
College, Metro provides computer labs for students who do not have the required resources or facilities available to them.
METHODS OF ASSESSING STUDENT PROGRESS:
Student progress is assessed through the completion of assigned projects and tests. A summary of programming assignments and tests may be found at the end of the syllabus under the heading PROJECTED SCHEDULE OF
ASSIGNMENTS. Attendance and class participation may also be taken into consideration.
SELECTED TESTING/ASSESSMENT METHODS:
The majority of programming assignments require the student to take a basic set of program requirements and, based on
knowledge gained from reading and class, develop a program using the typical program development process. Work will
be evaluated on the adequacy of program planning; correctness of coding generated; usage of comments to describe and
clarify program logic, data element usage, and input/output requirements; adequacy of program testing procedures; and
adequacy of program documentation. Of course, the program should also run correctly.
Typical point assignments for these various aspects of programming for a 25 point program is as follows:
1 input layout(s)
1 program logic (for each function/module)
1 printer/output layout(s)
1 hierarchy diagram
2 standard coding style & related issues
2 flowchart or pseudocode
2 correct procedural logic/method
2 correct compile
Usage of comments in program:
10 correct run
1 general description of the program
--------1 misc. input/output requirements
25 total
1 purpose & use of each variable (variable table)
Full points are awarded for the inclusion of the specified item(s), with points being deducted for notable problems.
Exams may include multiple choice, true/false, and fill-in-the-blank questions, and short programming segments.
MAKE-UP TEST PROCEDURES:
Students MUST be present on the day of an announced test. If the instructor is informed BEFORE THE TEST concerning
a valid absence, other arrangements MAY be made. There will be no retakes of tests. Test dates are not firm and are
therefore subject to change.
LATE ASSIGNMENTS:
Assignments turned in late may lose 10% per class day for up to a week and may then receive a grade of 0. Assignments
may not be accepted after the test has been given. Also, see “Attendance” below.
FINAL COURSE GRADE:
A percentage grade will be obtained by dividing the total points a student earns by the total possible points for the course.
The points for each assignment and test may be found in the PROJECTED SCHEDULE OF ASSIGNMENTS found at the
end of the syllabus. The percentage grade will then determine the letter grade for the course, according to the following
table:
Letter Grade
Ver. 3/8/2002
Percentage Range
Metropolitan Community College
Point Range
Page 4
Letter Grade
A
Percentage Range
90%
100%
Point Range
540
600
B
80%
89.9%
480
539
C
70%
79.9%
420
479
D
60%
69.9%
360
419
F
0%
59.9%
0
359
MAINTENANCE OF STUDENT RECORDS:
All work is graded and returned as soon as possible, almost always by the following class. All grades are kept by the instructor in a grade book and on computer, which students may see at any time by asking the instructor.
SECTION III, PART B: STUDENT RESPONSIBILITIES
METHODS OF LEARNING:
The student will have specific assignments to read and master. These assignments are indicated in the course schedule
and/or outlined by the instructor. The student should have read the material prior to class meeting date.
ATTENDANCE STATEMENT:
The course will be covered partially by assigned portions of the text and may be presented in a sequence different from the
text. Material will also be covered that is not in the text. Attendance is necessary to understand the course material. Each
student is expected to recognize the importance of class attendance and promptness. CHRONIC TARDINESS AND
ABSENCES MAY RESULT IN A REDUCTION IN THE FINAL GRADE BY 10%.
Excessive absences or unsatisfactory progress will subject the student to administrative withdrawal from the course. If a
student should miss a class for any reason, he/she is expected to cover the material he/she missed on his/her own. All
work must be made up to the satisfaction of the instructor.
RETAINING COPIES OF SUBMITTED WORK:
On very rare occasion, the instructor has been unable to find any record of work which a student claims to have submitted.
This may have occurred for any of a number of possible reasons, including loss or theft of the work before it gets to the
instructor, or oversight on the part of the student or instructor. The student should understand that grades are based upon
documented achievement of learning objectives and successful completion of assignments. If work is missing, for whatever reason, it become impossible for the instructor to evaluate it and assign a grade. It is highly recommended that students
keep backup copies of all work submitted toward the unlikely event that it might need to be resubmitted.
STUDENT WITHDRAWAL:
If you cannot attend and complete this course, you should officially withdraw by calling Central Registration, 457-5231.
Failure to officially withdraw will result in either an instructor withdrawal (IW) or failing (F) grade. The last date to withdraw
is 2/2/2001.
TECHNOLOGY RESOURCES:
As you pursue your educational objectives, you may be required to use computer information technology resources at Metropolitan Community College. Use of these resources is a privilege and carries with it a responsibility to respect the rights
and privacy of others, the integrity of facilities, and to follow Student Conduct Guidelines and College Policies.
Ver. 3/8/2002
Metropolitan Community College
Page 5
COLLEGE POLICIES:
All students are expected to abide by College policies. These policies exist so that all students may pursue their
educational goals in a fair and non-threatening environment. Academic and non-academic standards exist for all
students. Academic standards involve acts of cheating or plagiarizing. Non-academic standards include, but are
not limited to, any acts of harassment, disruption of College functions, possession, use or sale of controlled substances or firearms, and inappropriate use of College equipment or property. The College imposes specific disciplinary actions in response to incidents of both academic and non-academic misconduct. These actions may
include: admonition, failing grade, failure of course, disciplinary probation, suspension or dismissal. (A copy of the
current disciplinary procedure is available in each campus Student Services center and from your Program contact
(see below).)
Please note: ANY sharing or transfer of assigned work or test contents or answers between a student and
any other person or party; in part or in whole; whether by disk exchange, E-mail, manual transcription, codevelopment of an assignment, or any other means; unless authorized by the instructor in advance in accordance with the guidelines in the following paragraph; will be considered academic misconduct and be
sanctioned with disciplinary action in accordance with the above paragraph. Both originating and receiving parties will be liable to such sanction.
Sharing of class notes and handouts is authorized. Obtaining assistance from others (including tutors or lab techs)
for specific programming issues or debugging is authorized. However, no further collaboration is authorized for
any standard assignment. Students wishing to collaborate further must contact the instructor for special assignments. Such special assignments must clearly identify in advance which portions are the responsibility of each individual student wishing to collaborate. The learning objectives, level of difficulty, and typical work involved for
each portion must be comparable to that for a single student working alone on the corresponding standard assignment. Each portion will be graded individually. Each portion must clearly represent the competency of the individual responsible for it, and only that individual. The instructor reserves the right to refuse any request for special
assignments.
Indications of unauthorized collaboration and/or intent to defraud include, but are not restricted to, assignments,
submitted by students (not necessarily from the same section) individually under each of their respective names;
but which are essentially identical; are essentially identical except for mechanical changes such as differing variable or module names; are essentially identical except for differing comments; or exhibit essentially identical idiosyncratic features such as errors in syntax, style, logic, output formatting, or spelling. The same criteria apply to
submissions, by one or more students, where those submissions bear indications of copying from any other unauthorized source. Authorized sources are the student textbook for the class, lecture notes, class handouts, and
compiler/interpreter documentation and help materials.
In summary, if you want a grade attached to your name and only your name (the only way I know MCC records
grades), the work you submit must be your work and only your work.
INFORMATION SOURCES:
Refer to both the College catalog and student handbook as sources of general College information such as parking, children on campus, identification cards, etc.
PROGRAM IDENTIFICATION:
Associate Dean of Curriculum Delivery: Tom Pensabene
Location: FOC 8 207
Phone: 457-2502 (Candi Otterpohl)
Email: tpensabene@metropo.mccneb.edu
The Associate Dean of Curriculum Delivery is the person you should contact if you have any questions or problems concerning the instructor or class that cannot be resolved by the instructor to the student's satisfaction.
Ver. 3/8/2002
Metropolitan Community College
Page 6
SECTION IV: PROJECTED SCHEDULE OF ASSIGNMENTS:
Wk
1
Date
3/2/02
2
3/9
Topics
Reading
Assignments
Points
OOPS
3
3/16
 Introduction, Syllabus overview
 C++1 Review - Compiler Hands-on
 Functions Review

 Input / Output
 Classes
4
3/23
 Class Design
Ch 6
5
4/6
 Friends
Ch 7
6
7
4/13
4/20
Review
Exam #1
 Overloading
Ch 8
8
4/27
 Inheritance and Virtual Classes
Ch 9
9
5/4
 Templates
Ch 11
10
5/11
 Exception Handling
Ch 12
11
5/18
Review
Exam #2
 Housekeeping, Miscellaneous
Ch. 1-3
Ch. 4, Ch 13
Ch 10
Ch 5
#1 (due Wk 3)
C4X19 (155)*
50
#2 (due Wk 4)
P1:C5X1(191)
P2:C5X6(193)
#3 (due Wk 6)
P3:C6X9(231)
P4:C7X7(266)
50
#4 (due Wk 8)
P5:C8X1(307)
P6:C8X7(308)
#5 (due Wk 9)
P7:C9X6(358)
P8:C10X7(402)
#6 (due Wk 11)
P9: handout**
P10:C12X5(485)
50
150
50
50
50
150
600
*C4X19(155): Chapter 4, Exercise 19 (page 155)
**Handout based on Deitel exercise 12.3 (page 664)
Ver. 3/8/2002
Metropolitan Community College
Page 7