Presentation is loading. Please wait.

Presentation is loading. Please wait.

Repetition Control Structures School of Business Eastern Illinois University © Abdou Illia, Spring 2003 (Week 9, Friday 3/07/2003)

Similar presentations


Presentation on theme: "Repetition Control Structures School of Business Eastern Illinois University © Abdou Illia, Spring 2003 (Week 9, Friday 3/07/2003)"— Presentation transcript:

1 Repetition Control Structures School of Business Eastern Illinois University © Abdou Illia, Spring 2003 (Week 9, Friday 3/07/2003)

2 2 Learning Objectives n Understand using Trailer record to control Repetitive structures n Understand using End-Of-File (EOF) condition to control Repetitive structures n Design programs using Trailer record logic and EOF condition.

3 3 Recall (Algorithm vocabulary) START STOP SYMBOLS NAME Terminal interrupt symbols USE Terminal point (start, stop, or break) Input/Output symbol Reading data from an input medium or writing data to an output medium Process symbol Processing input data

4 4 Recall (Algorithm vocabulary) SYMBOLS NAME Flowline symbol USE Sequence of operations and direction of data flow Decision symbol Decision-making operations Predefined-process symbol Operations specified elsewhere (not in the current algorithm)

5 5 Recall (Algorithm vocabulary) SYMBOLS NAME Connector symbol USE Exit to, or entry from, another part of the Flowchart Preparation symbolControl operations: Set limit on loop-control variables, Initialize accumulators, etc. Annotation symbol Addition explanation; comments.....

6 6 Problem: Defective parts A manufacturing company produces a large number of automotive parts each year in its two plants. Some of these plants are returned to the main sale Office because of defects in manufacture. An input record is prepared for each defective part, containing a code, part number, type of part, and date returned. The code is either 1 or 2, indicating whether plant 1 or plant 2 made the defective part. Example of file containing input records A trailer record containing a plant code of 9 to signal the end of the input file

7 7 Problem: Defective parts The company needs a read-and-print program to process the records and produce a listing of their contents. In addition the number of defective parts manufactured by each plant is to be totaled for future reference. The output of the program is to consist of a printed listing of the contents of the input records, followed by the total computed for each plant.

8 8 Solution: Using Trailer record (Program Flowchart) READ CODE, PART, TYPE, DATE WRITE CODE, PART, TYPE, DATE CODE ≠ 9 ? COUNT1 = COUNT1 + 1 START NO YES WRITE COUNT1, COUNT2 STOP COUNT1 = 0 COUNT2 = 0 CODE = 1 ? YES COUNT2 = COUNT2 + 1 READ CODE, PART, TYPE, DATE NO Loop controlled by a Trailer record Priming Read: - Placed before the loop - Gets the computer ready (primes the computer) to make the loop test Loop Read: -Within the loop -Causes next record to be read.

9 9 Solution: Using Trailer record (Pseudocode) Start COUNT1 = 0 COUNT2 = 0 Read CODE, PART, TYPE, DATE DOWHILE CODE ≠ 9 IF CODE = 1 THEN COUNT1 = COUNT1 + 1 ELSE COUNT2 = COUNT2 + 1 ENDIF Write CODE, PART, TYPE, DATE Read CODE, PART, TYPE, DATE ENNDO Write COUNT1, COUNT 2 Stop

10 10 Questions n What if the Priming Read is omitted ? n What if the Loop Read is omitted ? n What if the DOWHILE statement (in the previous slide) is replaced by an IF statement ?

11 11 Solution: Using Trailer record (Program Flowchart) Adds Heading line(s) to the output Additional test for invalid code

12 12 Solution: Using Trailer record (Pseudocode) Start Write heading(s) COUNT1 = 0 COUNT2 = 0 Read CODE, PART, TYPE, DATE DOWHILE CODE ≠ 9 IF CODE = 1 THEN COUNT1 = COUNT1 + 1 ELSE IF CODE = 2 THEN COUNT2 = COUNT2 + 1 ELSE Write ‘Bad Input’ ENDIF Write CODE, PART, TYPE, DATE Read CODE, PART, TYPE, DATE ENDDO Write COUNT1, COUNT2 Stop

13 13 Solution: Using Trailer record & Modules Task 1: Write the headings n Note: Many ways for identifying mains tasks Task 2: Initialize counters Task 4: Write totals for each plant. n Identify main tasks performed by the program Task 3:Write detail records

14 14 Solution: Using Trailer record & Modules n Structure Chart (or Hierarchy Chart) – Shows relationships of all modules within a program Higher level: Represents the Control Module (or Driver Module) Lower level: 1)Represents Modules that may be given control during program execution 2)Each module performs one or a small number of tasks.

15 15 Solution: Using Trailer record & Modules n Overall Control program Flowchart & Pseudocode A000 Start Process headings (B000) Process initialization (B010) Read CODE, PART, TYPE, DATE IF CODE = 9 THEN Write ‘No data’ ELSE DOWHILE CODE ≠ 9 Process a detail record (B020) Read CODE, PART, TYPE, DATE ENDDO Process totals (B030) ENDIF Stop

16 16 Solution: Using Trailer record & Modules n Modules’ Flowcharts & Pseudocodes B000 Enter Write headings Return WRITE HEADING(S) RETURN B000 B010 Enter COUNT1 = 0 COUNT2 = 0 Return RETURN B010 COUNT1 = 0 COUNT2 = 0 B030 Enter Write ‘Total defective plant 1 parts:’, COUNT1 Write ‘Total defective plant 2 parts:’, COUNT2 Return WRITE ‘TOTAL EFFECTIVE PLANT 1 PARTS:’, COUNT1 RETURN B030 WRITE ‘TOTAL EFFECTIVE PLANT 2 PARTS:’, COUNT2

17 17 Solution: Using Trailer record & Modules B020 Enter IF CODE = 1 THEN COUNT1 = COUNT1 + 1 ELSE IF CODE = 2 THEN COUNT2 = COUNT2 + 1 ELSE Write ‘Bad Input’ ENDIF Write CODE, PART, TYPE, DATE Return n Modules’ Flowcharts & Pseudocodes

18 18 Solution: Using End-Of-File condition n Not always necessary to physically place a trailer record n Most programming languages support a built-in function for testing the End-of-File A000 Start Process headings (B000) Process initialization (B010) Read a record IF end of file (EOF) THEN Write ‘No data’ ELSE DOWHILE not end of file (not EOF) Process a detail record (B020) Read a record ENDDO Process totals (B030) ENDIF Stop

19 Exercise Redo the Weekly Payroll problem done during Week 2 (see next 3 slides): 1) Using a Trailer record (NUM = 999) 2) Using an End-Of-File condition

20 20 Exercise : Weekly Payroll problem Construct a program flowchart and corresponding pseudocode to solve the following problem: ABC company needs a weekly payroll report for its salespeople. Input to the program is a salesperson’s name, number, and weekly sales. Output is the salesperson’s name, number, and pay. Each salesperson receives a base pay of $300 as well as a 10% commission on his or her total sales up to and including $500. Any sales over $500 merit a 15% commission for the employee. (For example, if sales = $600, then pay = $300 + $50 [or.10 * 500] + $15 [.15 * 100] = $350). Use a DOWHILE loop and a counter to compute the weekly payroll for exactly 20 employees. Exercise 19 (Chapter 4)

21 21 Initial Solution: ( Program Flowchart ) READ NAME, NUM, SALES WRITE NAME, NUM, PAY COUNT < 20 ? PAY = 300 * (SALES *.10) START STOP NOYES COUNT = 0 SALES > 500 ? PAY = (500 *.10) + ((SALES – 500) *.15) COUNT = COUNT + 1 NO YES

22 22 Initial Solution: ( Pseudocode ) Start COUNT = 0 DOWHILE COUNT < 20 Read NAME, NUM, SALES IF SALES > 500 THEN PAY = (500 *.10) + ((SALES – 500) *.15) ELSE PAY = (SALES *.10) ENDIF Write NAME, NUM, PAY COUNT = COUNT + 1 ENDDO Stop

23 23 Solution: Using Trailer record ( Program Flowchart ) (To be done in class)

24 24 Solution: Using Trailer record ( Pseudocode ) (To be done in class)

25 25 Solution: Using EOF ( Program Flowchart ) (To be done in class)

26 26 Solution: Using Trailer record ( Pseudocode ) (To be done in class)


Download ppt "Repetition Control Structures School of Business Eastern Illinois University © Abdou Illia, Spring 2003 (Week 9, Friday 3/07/2003)"

Similar presentations


Ads by Google