nd
METRO OFFICES
HOURS* LOCATION PHONE FAX
M/W 1:00p-2:30p
M/W: 4:00p-5:00p
EVC 156
SOC MAH 300
289-1364
738-4089
289-1405
738-4553
T: 4:00p-5:00p FOC 008 203 457-2624 457-2946
*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.
Home phone: (402) 556-3071
DATE CLASS BEGINS:
DATE CLASS ENDS:
LAST DATE TO DROP CLASS:
DATES CLASS DOES NOT MEET:
3/16/2004
5/25/2004
5/10/2004 none
The student gains experience in using programming techniques with the language of COBOL. Students are re-quired to program, debug, and test specified business oriented problems using COBOL.
CPT 105 (Introduction to Computer Programming)
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
Structures: loops, case, IF-ELSE
Counters and accumulators (including using a line counter)
Arrays: subscripts, direct access, sequential and binary search
Modularized programming (subroutines)
Control break logic

Upon successful 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.
Textbook: COBOL for the 21 st Century
Edition: Tenth Edition, Author: Stern, Stern, and Ley, Publisher: John Wiley and Sons.
OR Structured COBOL Programming
Edition: Ninth (or Eighth), Author: Stern and Stern, Publisher: John Wiley and Sons.
Two 3.5 " diskettes.
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.
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. 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.
MCC’s IBM iSeries server may be accessed off-campus via the World-Wide Web and the Internet. Student versions of COBOL are available from Micro Focus and other software vendors for installation on PC’s. Other MCC campuses may have additional COBOL options. These and other options may be discussed with the instructor. However, in many cases, the instructor may not be able to provide support for non-COBOL problems the student may encounter.
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 that 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.
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 withdraw (IW) or failing (F) grade. The last date to withdraw is identified on the first page of this syllabus handout.

Students are reminded that materials you may use as sources for this course may be subject to copyright protection. Additional information about copyright is provided on the library webpage at http://www.mccneb.edu/library , by your instructor, or by the
College's Copyright Officer.
The College imposes specific actions in response to incidents of student dishonesty (cheating, plagiarism, etc.) that may include receiving a failing grade on a test, failure in the course, suspension from the College, or dismissal from the College. The disciplinary procedures are available in the Counseling/Advising Centers.
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.
The ownership of student works submitted in fulfillment of classroom requirements shall remain with the student(s): By enrolling in classes offered by Metropolitan Community College, the student gives the College license to mark on, modify, and retain the work as may be required by the process of instruction, as described in the course syllabus. The institution shall not have the right to use the work in any other manner without the written consent of the student(s).
Please note: Nothing in the preceding paragraph overrides the restrictions on sharing or distribution of solutions to assignments and tests discussed above under the Academic Honesty Statement.
Metropolitan Community College is committed to continuous improvement of teaching and learning. You may be asked to help us to accomplish this objective. For example, you may be asked to respond to surveys or questionnaires. In other cases, tests or assignments you are required to do for this course may be shared with faculty and used for assessment purposes. This will be done in accordance with FERPA guidelines.
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.
By using the information technology systems at MCC (including the computer systems and phones) you acknowledge and consent to the conditions of use as set forth in the Metropolitan Community College Procedures Memorandum on Acceptable Use of Information
Technology and Resources. It is your responsibility as a student to be familiar with these procedures. The full text of the Procedures
Memorandum may be found at the following website: http://www.mccneb.edu/itprocedures.htm

Program Area
Academic Dean
Academic Dean’s office phone
Computer Technology and Visual Arts
Thomas C. Pensabene
457-2660
The Office of the Academic Dean should be contacted with any questions or problems that your instructor is not able to resolve to your satisfaction.
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.
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.
The majority of programming assignments (labs) 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. Full points are awarded for the inclusion of the specified item(s), with points being deducted for notable problems. Typical point assignments for these various aspects of programming, based on a 60 point total, are as follows:
Planning & external documentation: Usage of comments in program: 5 coding style, etc.
3 input layout(s)
3 printer/output layout(s)
2 general description (in Identification Division)
2 misc. input/output requirements
5 methodology
10 correct compile
2 hierarchy diagram
6 flowchart or pseudocode
2 data item usage (esp. in Working-Storage)
5 program logic (in Procedure Division)
15 correct run
---------
60 total
Exams consist mostly of fill-in-the-blank questions and short programming segments.
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
A
B
C
D
F
Percentage Range
90%
80%
70%
60%
0%
100%
89.9%
79.9%
69.9%
59.9%
Point Range
585
520
454
390
0
650
584
519
453
389

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.
Assignments tuned in late may lose 10% per class day for up to a week and may then receive a grade of 0. No assignments will be accepted after the test has been given. Also, see “Attendance” above.
Test will be returned after grading for review in class and then recollected and retained for record keeping purposes. All other work is graded and returned as soon as possible, usually by the following week. 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.
10 th ed. pp. [9 th ed. pp.] (8 th ed. pp.)
Points
50
Wk Date
1
2
3/16/2004
3/23
Topics
Introduction to COBOL,
IDENTIFICATION and ENVIRONMENT DIVISIONS,
DATA DIVISION (FILE SECTION),
Using IBM iSeries and other COBOL systems
DATA DIVISION (WORKING-STORAGE SECTION),
PROCEDURE DIVISION (Basic COBOL statements),
Designing and Debugging Structured Programs
Assignment #1 due
3
4
3/30
4/6
MOVE Statement, Editing Printed Output.
ACCEPTing the system date,
Arithmetic Statements
Assignment #2A due
Review
Exam #1
5 4/13
6
7
8
9
10
11
4/20
4/27
5/4
5/11
5/18
5/25
IF statement, EVALUATE statement,
Control Break Processing, Line and Page Counters
Assignment #2B due
Conditions names (88 levels),
PERFORM statement, GO TO statement
INSPECT, Data Validation
Redefining numeric data as alphanumeric
Assignment #3 due
Review
Exam #2
Defining Arrays with the OCCURS clause,
Hard-coded Tables and the Redefines Clause,
Literal and Variable subscripts
Assignment #4 due
Load time tables,
PERFORM . . . VARYING ,
Intrinsic Functions, Defining numeric fields as
COMP or COMP-3
Assignment #5 due
Review & Preview of COBOL II
Exam #3
Reading
Chapter 1
Chapter 2
Chapter 3
Handout
Chapter 3
Chapter 4
Chapter 5
Chapter 6
Chapter 7
Chapter 8
Chapter 10
Chapter 8
Chapter 9
Chapter 11
Handout
Chapter 12
Chapter 12
Chapter 9
Chapter 7
Handout
Assignments
Punch and Run
Program
(Assignment #1)
Input/Output program
(Assignment #2A)
Math Program
(Assignment #2B)
Control Break
Program
(Assignment #3)
Data Validation
Program
(Assignment #4)
Table Program
(Assignment #5)
60
60
90
60
60
110
60
100
650