- Shopping Bag ( 0 items )
Ships from: Halethorpe, MD
Usually ships in 1-2 business days
Ships from: Punta Gorda, FL
Usually ships in 1-2 business days
Designed for beginners with no programming or computer experience, this revised textbook teaches structured programming concepts. Although primarily aimed at college students, it may appeal to programmers who maintain existing COBOL programs . It focuses on elements of the COBOL 85 standard. Topics include data validation, sequential file processing and OOP principles.
Other applications process large volumes of input at periodic intervals. Payroll procedures used to update the master collection of payroll information prior to printing pay checks are often performed in batch mode at periodic intervals. We will see that COBOL is ideally suited for both interactive and batch processing applications.
When an applications program is written for a specific user it is called a customized program. COBOL is ideally suited as a language for writing customized applications programs. Although we will focus on COBOL for applications programming in this text, we now provide a brief description of another type of applications software called an applications package.
If the tasks to be performed by a program are relatively standard, such as preparing a budget, an applications package might be purchased as an alternative to writing a customized program in a language such as COBOL. Such packages are sold by software vendors. Typically, documentation is provided by the manufacturer in the form of a user's manual, which explains how to use the package. For example, Lotus for Windows is a widely used package for applications such as budgeting, scheduling, and preparing trial balances.
If a package exists that can be used as is for an application, purchasing it will almost always be cheaper and easier than writing a customized program. But if an application has special requirements, then writing a customized program may be preferable to modifying an existing package.
2. Design the Program Using Program Planning Tools Programmers use design or program planning tools such as flowcharts, pseudocode, and hierarchy charts to help map out the structure and logic of a program before the program is actually coded.
3. Code and Enter the Program The programmer writes and then keys or enters the source program into the computer system using a keyboard.
4. Compile the Program The programmer makes certain that the program has no rule violations.
5. Test the Program The programmer develops sample data and uses the program to operate on it to ensure that processing is correct.
6. Document the Program The programmer writes procedure manuals for users and computer operators so they can run the program on a regularly scheduled basis.
Most novices believe that computer programming begins with coding or writing program instructions and ends with program testing. You will find, however, that programmers who begin with the coding phase often produce poorly designed or inadequate programs. The steps involved in programming should be developmental, where coding is undertaken only after the program requirements have been fully specified and the logic to be used has been carefully planned.
Moreover, there are steps required after a program has been coded and tested. Each program must be documented with a formal set of procedures and instructions that specify how it is to be used. This documentation is meant for (1) those who will be working with the output, (2) computer operators who will run the program on a regularly scheduled basis, and (3) maintenance programmers who may need to make modifications to the program at a later date.
When a systems analyst decides what customized programs are required, he or she prepares program specifications to be given to the programmers or software developers so that they can perform their tasks. Typically, the program specifications consist of:
1. Record layout forms to describe the formats of the input and output data on disk or other storage medium. Figure 1.1 illustrates two examples of record layouts. (We will use version (b) for most of our illustrations.) They indicate:
2. Printer Spacing Charts for printed output. Printed output requires a format not typically needed for other types of output:
|1||An Introduction to Structured Program Design in COBOL||2|
|2||The IDENTIFICATION and ENVIRONMENT DIVISIONs||35|
|3||The DATA DIVISION||58|
|4||Coding Complete COBOL Programs: The PROCEDURE DIVISION||100|
|5||Designing and Debugging Batch and Interactive COBOL Programs||130|
|6||Moving Data, Printing Information, and Displaying Output Interactively||183|
|7||Computing in COBOL: The Arithmetic Verbs and Intrinsic Functions||240|
|8||Decision Making Using the IF and EVALUATE Statements||281|
|9||Iteration: Beyond the Basic PERFORM||322|
|10||Control Break Processing||360|
|12||Array Processing and Table Handling||437|
|13||Sequential File Processing||520|
|14||Sorting and Merging||560|
|15||Indexed and Relative File Processing||597|
|16||Improving Program Performance Using the COPY, CALL, and Other Statements||650|
|17||The Report Writer Module||675|
|18||An Introduction to Object-Oriented Programming||703|
|App. A||COBOL Character Set and Reserved Words||A-2|
|App. B||Data Set for Programming Assignment 2 in Each Chapter||A-7|
|App. C||Differences Among the COBOL Standards||A-9|
|App. D||COBOL for the AS/400||A-13|
|App. E Glossary||A-29|