CST 8283 COBOL Programming

Session 1 Course Introduction Program Development Cycle

Session 1 References Course outline COBOL From Micro to Mainframe (R.T Grauer) COBOL Programming Supplementary Notes (optional) Simple Program Design (L. A. Robertson) (optional) Session slides / Reference Manual

Session 1 References (continued)

Instructor Mel Sanschagrin (Capt. COBOL)

Telephone 727-4723 ext 7299

e-mail
Office

SANSCHM@ALGONQUINCOLLEGE.COM
Room T319, Technology Building Woodroffe Avenue Campus

CST 8283 COBOL Programming Course Objectives

Course participants will be able to: 1. develop structured / top down COBOL programs, including

tested, executable and maintainable code;

Internal and external documentation; logical diagrams for process and data structures.
4

CST 8283 COBOL Programming Course Objectives (continued)

Course participants will be able to: 2. Decipher, interpret, and correct COBOL code

3. Modify COBOL code to add or change programs functions

COBOL Programming Administration

Marking and Grading scheme

Mid-term test ---> 35%

Final Exam -----> 40% 3 projects --------> 20% (5%, 5%, 10%) participation -----> 5% (session exercises) ---To pass the course, you must score 50% on combined Mid-term test and Final exam (37.5 points of available 75)
6

NOTE

COBOL Programming Administration (continued)

Projects Project 1A (2%) and 1B (3%) Project 2A (2%) and 2B (3%) Project 3A (10%) Parts A and B to be submitted (and marked) separately.

Project criteria WORD documents (e.g. PROJECT1A.DOC)

7

COBOL Programming Administration (continued)

At end of some sessions, reference to samples or examples for further detail Provide further explanation of session content Assistance in exercise or project work

COBOL Programming Session 1 --- Objectives

Participant will be able to : define the steps of the Program Development Cycle
define

the need and use of logical narratives and diagrams ( Logical Models) the meaning of the different symbols used in Flowcharts and Function charts
9

define

Logical Models

A Logical Model is a description of the logical steps required to

Solve

a problem Handle a business process Provide information from available data

NOTE -- the logical model is independent of the code; it is a model of the logic -- not the code.
10

Logical Models

Logical model
Graphical

or narrative representation of process (actions to be taken), data information

Program

language independent

11

Logical Models

Logical models are used to:

develop solution set test solution set communicate solution set develop related process and data code for the solution set document final solution set for support and maintenance

12

Logical Models basic types

Sequential step diagrams * Sequential step narratives * Decomposition diagrams * Data Definition diagrams or narratives Data flow diagrams Decision tables and trees Input / process / output diagrams *

13

Logical Models Types

Sequential step diagrams and narratives

flowchart

- diagrams the sequence of actions - includes individual actions and decision points - uses a specific set of symbols narrative of action sequence - includes individual actions and decision points - uses a prescribed language set (structured language)
14

pseudocode-

Logical Models general outline -- flowchart

Input (data)

Process

Output (information)

Delineation detection / correction

15

Logical Models Flowcharts

shows the flow / sequence of activities within a solution set diagrams the flow and the control / decision points can be used in a top down approach

(structured flowcharts)

symbols represent the type of activity internal narrative specifies the actual activity ANSI standard

16

Logical Models Flowcharts conventions and symbols

Process (one action or activity)

Pre-defined Process

Decision point Begin or end

Input or Output

17

Logical Models Flowcharts conventions and symbols

Process (one action or activity)
Pre-defined Process

Decision point Begin or end

Input or Output

18

Logical Models Flowcharts conventions and symbols

Process (one action or activity) Pre-defined Process

Decision point Begin or end

Input or Output

19

Logical Models Flowcharts conventions and symbols

Process (one action or activity) Pre-defined Process

Decision point Begin or end

Input or Output

20

Logical Models Flowcharts conventions and symbols

Process (one action or activity) Pre-defined Process

Decision point Begin or end

Input or Output

21

Logical Models Flowcharts -- conventions

top to bottom --- left to right one function / process per page clear narrative in each symbol what is being done (opcode/ action) what is the object of the action (operand/object) arrows show flow of the activities all flow charts must have a beginning and an end

22

Logical Models Flowcharts -- symbols - sample

start

Initiate process End of job

no
yes

Main process

stop
23

Logical Models Flowcharts -- example

start Calculate mark no Process Fail record Mark =>50 yes Process Pass record

end
24

Logical Models Types

Decomposition Diagrams
Function Charts - a diagram of the functional breakdown of processes (AKA - hierarchy charts, structure charts)

- a modular structure of the solution set (from overall function down to specific tasks)
25

Logical Models Function Charts

Functional breakdown or de-composition of a potential solution set for a specific problem overall function processes involved activities within each process -- tasks within activities

note -- there may be common processes,

functions and activities
26

Logical Models Function Charts

definition -- a chart or diagram which describes the functional breakdown or decomposition of a higher level function processes activities tasks

27

Logical Models Function Charts - considerations

As each level is described, it is validated prior to further breakdown The order of execution is determined for each subordinate process or activity Any duplicate processes or activities are noted Any repetitive processes or activities are noted Any one on one breakdowns are eliminated Any modules conditionally executed are noted Data or control elements are noted
28

Logical Models Function Charts - considerations

One on One breakdowns are not permitted An upper level module controls the execution of a subordinate modules Modules either control subordinate modules or do actual work -- not both A numbering scheme is commonly used to help distinguish modules and their hierarchical level Statement in each module should clearly describe the function/process/activity
29

Logical Models Function Charts - example

dive trip
Take dive vacation

Prepare for vacation

Enjoy daily dive and other activities

Return Home

30

Logical Models Function Charts- example

Prepare for vacation

Book trip with agent

Get Passport

Pack scuba gear

31

Logical Models IPO / HIPO charts

IPO charts, HIPO charts, Defining diagrams overall relationships of

Input Process output

general

solution outline (any level) may show sequence of processes may show detail of both input and output

32

IPO / HIPO chart / Defining diagram

Define the general aspects of the problem in terms of the expected input, the overall processing steps and the expected output.

I
Input specifications

P
processing steps and sequence

O
Output description

33

Logical Models Types

Data Flow Diagram

- shows flow of data through processes and the data conversion through each process.
Data store

Data store

Data store
34

Logical Models Types

other tools decision table- shows decisions and related actions

HIPO chart / Defining diagram- shows input, process, output Nassi Schneiderman- shows process breakdown
35

Session 1 exercise 1
Draft a two or three level function chart that shows your activities in getting up in the morning (assuming you do get up in the morning and not in the afternoon) Remember to think in broad general terms at the top of the hierarchy and move to more specifics as you break the function down to processes.

36

Session 1 exercise 2
Draft a flowchart or pseudocode for one of the processes or activities in your function chart. The flowchart should detail the specific actions taken within the process or activity. Remember to think in specific terms and include any decision points that are required.

37

Session Wrap-up
Once you have completed the two exercises, submit them to me, via Mail Box (3rd floor), or by e-mail SANSCHM@ALGONQUINCOLLEGE.COM I will return my solution for each of these to you. Refer to EXAMPLE1 Proceed to Session2

38