SYLLABUS HANDOUT
for
CPT 221 7A
COBOL I
Alan R. Reinarz
2001-2002/Spring
M/W 10:00aB11:40a  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/4/02 Date class ends: 5/15/02 Last date to drop class: 4/26/02
WELCOME TO METROPOLITAN COMMUNITY COLLEGE!
IMPORTANT DATES:
Date class begins:
Date class ends:
Last date to drop class:
3/4/2002
5/15/2002
4/26/2002
SECTION I: THE CLASS AND THE INSTRUCTOR
COURSE SECTION AND TITLE:
CPT 221 7ACCOBOL I
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:
The student gains experience in using programming techniques with the language of COBOL. Students are required to program, debug, and test specified business oriented problems using COBOL.
COURSE PREREQUISITES: CPT 105 (Principles of Data Processing/Logic)
COURSE OBJECTIVES:
Upon completion of this course, the student will be able to:
1. Describe the structure and divisions of a COBOL program.
2. Describe and code the Identification and Environment Divisions.
3. Describe and code the File Section and Working-Storage Section of the Data Division.
4. Code a COBOL program that performs basic I/O operations, arithmetic operations, MOVEs, and PERFORMs.
5. Demonstrate programming techniques used for control break processing.
6. Demonstrate programming techniques used for validating data.
7. Code COBOL programs using one-dimensional tables.
.REQUIRED/SUPPLEMENTAL MATERIALS:
Textbook:
Edition:
Author:
Publisher:
Structured COBOL Programming
Ninth
Stern and Stern
John Wiley and Sons.
1Students will find computer resources for this class at Computer and Office Technology (COT) Computer Labs on
all campuses.
Metropolitan Community College
Page 1
SECTION III, PART A: INSTRUCTOR RESPONSIBILITIES
METHODS OF INSTRUCTION:
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 3 hours per week in hands-on, lab activity. Students are responsible for completing all lab work outside of the classroom. A “personal” version of the software used in this
class is available to the student at additional cost. Metro provides the necessary software in this classroom and in
all “Computer and Office Technology” computer labs
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 60 point
program is as follows:
3
3
2
6
input layout(s)
printer/output layout(s)
hierarchy diagram
flowchart or pseudocode
Usage of comments in program:
2 general description in Identification Division
2 misc. input/output requirements
2 data element usage, especially Working-Storage
5 program logic (Procedure Division)
5 coding style, etc.
5 methodology
10 correct compile
15 correct run
--------60 total
Full points are awarded for the inclusion of the specified item(s), with points being deducted for notable problems.
Exams consist mostly of 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 AAttendance@ below.
Metropolitan Community College
Page 2
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
Percentage Range
Point Range
A
90%
100%
585
650
B
80%
89.9%
520
584
C
70%
79.9%
454
519
D
60%
69.9%
390
453
F
0%
59.9%
0
389
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 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. There may be several reasons this has occurred, 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 achievement of learning objectives and successful completion of assignments. If work is missing, for
whatever reason, it becomes 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 4/26/2002.
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.
Metropolitan Community College
Page 3
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 Assoc. Dean.)
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 Computers & Visual Arts:
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 that cannot be resolved by the instructor to the student's satisfaction.
Prerequisites for CPT 221 that were Covered in CPT 105
Hardware, Software, and Data
Flowcharts and Hierarchy Charts
Record layout/report layout
Variables and constants
Numeric and non-numeric data
Metropolitan Community College
Structures: loops, case, IF-ELSE
Counters and accumulators (including using a line counter)
Arrays: subscripts, direct access, sequential
and binary search
Page 4
Modularized programming (subroutines)
Metropolitan Community College
Control break logic
Page 5
SECTION IV: PROJECTED SCHEDULE OF ASSIGNMENTS:
Wk
Date
1
3/4/02
3/6
2
3/11
3/13
3
3/18
3/20
Topics
Chapters
Points
Chapter 1
Chapter 2
Chapter 3
Handout
Punch and Run
Program
(Assignment #1)
50
DATA DIVISION (WORKING-STORAGE SECTION),
PROCEDURE DIVISION (Basic COBOL statements),
Designing and Debugging Structured Programs
Assignment #1 due
Chapter 3
Chapter 4
Chapter 5
Input/Output program
(Assignment #2A)
60
MOVE Statement, Editing Printed Output.
ACCEPTing the system date,
Arithmetic Statements
Assignment #2A due
Chapter 6
Math Program
(Assignment #2B)
60
Chapter 7
4
3/25
3/27
Review
Exam #1
5
4/1
4/3
IF statement, EVALUATE statement,
Control Break Processing, Line and Page Counters
Assignment #2B due
Chapter 8
Chapter 10
6
4/8
4/10
Conditions names (88 levels),
PERFORM statement, GO TO statement
Chapter 8
Chapter 9
7
4/15
4/17
INSPECT, Data Validation
Redefining numeric data as alphanumeric
Assignment #3 due
Chapter 11
Handout
8
4/22
4/24
Review
Exam #2
9
4/29
5/1
Defining Arrays with the OCCURS clause,
Hard-coded Tables and the Redefines Clause,
Literal and Variable subscripts
Assignment #4 due
Chapter 12
10
5/6
5/8
Load time tables,
PERFORM . . . VARYING ,
Intrinsic Functions, Defining numeric fields as
COMP or COMP-3
Assignment #5 due
Chapter 12
Chapter 9
Chapter 7
Handout
5/13
5/15
Review & Preview of COBOL II
Exam #3
11
Assignments
Introduction to COBOL,
IDENTIFICATION and ENVIRONMENT DIVISIONS,
DATA DIVISION (FILE SECTION),
Using Micro Focus COBOL
90
Control Break
Program
(Assignment #3)
60
Data Validation
Program
(Assignment #4)
60
110
Table Program
(Assignment #5)
60
100
650
Metropolitan Community College
Page 6