Scribd Logo
Upload

Welcome to Scribd!

  • 46 views

    Pseudocode: An Introduction

    Uploaded by

    thetys20
    Pseudocode is a design tool that reflects structured programming concepts better than flowcharts. It follows specific rules: each statement is on its own line, keywords are capitalized, indentation shows hierarchy, and multiline structures are properly ended. Pseudocode uses specific keywords like WHILE and ENDWHILE for looping instead of flowchart symbols. It is easier to modify than flowcharts but lacks visual representation and standardization between companies. Memory locations are represented by descriptive variable names instead of addresses.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Pseudocode: An Introduction

    Uploaded by

    thetys20
    46 views16 pages
    Pseudocode is a design tool that reflects structured programming concepts better than flowcharts. It follows specific rules: each statement is on its own line, keywords are capitalized, indentation shows hierarchy, and multiline structures are properly ended. Pseudocode uses specific keywords like WHILE and ENDWHILE for looping instead of flowchart symbols. It is easier to modify than flowcharts but lacks visual representation and standardization between companies. Memory locations are represented by descriptive variable names instead of addresses.

    Original Title

    Pseudocode Basics

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Pseudocode is a design tool that reflects structured programming concepts better than flowcharts. It follows specific rules: each statement is on its own line, keywords are capitalized, indentation shows hierarchy, and multiline structures are properly ended. Pseudocode uses specific keywords like WHILE and ENDWHILE for looping instead of flowchart symbols. It is easier to modify than flowcharts but lacks visual representation and standardization between companies. Memory locations are represented by descriptive variable names instead of addresses.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    46 views16 pages

    Pseudocode: An Introduction

    Uploaded by

    thetys20
    Pseudocode is a design tool that reflects structured programming concepts better than flowcharts. It follows specific rules: each statement is on its own line, keywords are capitalized, indentation shows hierarchy, and multiline structures are properly ended. Pseudocode uses specific keywords like WHILE and ENDWHILE for looping instead of flowchart symbols. It is easier to modify than flowcharts but lacks visual representation and standardization between companies. Memory locations are represented by descriptive variable names instead of addresses.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 16

    Pseudocode

    An Introduction
    Flowcharts were the first design tool to be
    widely used, but unfortunately they do not
    reflect some of the concepts of structured
    programming very well. Pseudocode, on the
    other hand, is a newer tool and has features
    that make it more reflective of the structured
    concepts. The drawback is that the narrative
    presentation is not as easy to understand
    and/or follow.
    Rules for Pseudocode

    • Write only one statement per line


    • Capitalize initial keyword
    • Indent to show hierarchy
    • End multiline structures
    • Keep statements language independent
    One Statement Per Line
    Each statement in pseudocode should
    express just one action for the computer. If
    the task list is properly drawn, then in most
    cases each task will correspond to one line of
    pseudocode.

    Task List
    Read name, hours worked, rate of pay Pseudocode
    Perform calculations READ name, hoursWorked, payRate

    gross = hours worked * rate of pay gross = hoursWorked * payRate

    Write name, hours worked, gross WRITE name, hoursWorked, gross


    Capitalize Initial Keyword
    In the example below note the words: READ and
    WRITE. These are just a few of the keywords to use,
    others include:

    READ, WRITE, IF, ELSE, ENDIF, WHILE, ENDWHILE

    Pseudocode
    READ name, hoursWorked, payRate
    gross = hoursWorked * payRate
    WRITE name, hoursWorked, gross
    Indent to Show Hierarchy
    Each design structure uses a particular indentation
    pattern
    • Sequence:
    Keep statements in sequence all starting in the same column

    • Selection:
    Indent statements that fall inside selection structure, but not the keywords that form the
    selection

    • Loop:
    Indent statements that fall inside the loop but not keywords that form the loop

    READ name, grossPay, taxes


    IF taxes > 0
    net = grossPay – taxes
    ELSE
    net = grossPay
    ENDIF
    WRITE name, net
    End Multiline Structures
    READ name, grossPay, taxes
    IF taxes > 0
    net = grossPay – taxes
    ELSE
    net = grossPay
    ENDIF
    WRITE name, net

    See the IF/ELSE/ENDIF as constructed above,


    the ENDIF is in line with the IF.

    The same applies for WHILE/ENDWHILE etc…


    Language Independence
    Resist the urge to write in whatever language you are
    most comfortable with, in the long run you will save
    time. Remember you are describing a logic plan to
    develop a program, you are not programming!
    The Selection Structure

    yes no
    amount < 100

    interestRate = .06 interestRate = .10

    IF amount < 100


    interestRate = .06
    Pseudocode  ELSE
    Interest Rate = .10
    ENDIF
    The Looping Structure
    In flowcharting one of the more confusing
    things is to separate selection from looping.
    This is because each structure use the
    diamond as their control symbol. In
    pseudocode we avoid this by using specific
    keywords to designate looping

    WHILE/ENDWHILE
    REPEAT/UNTIL
    WHILE / ENDWHILE
    Start count = 0
    WHILE count < 10
    ADD 1 to count
    count = 0
    WRITE count
    ENDWHILE
    WRITE “The End”
    no
    count
    Mainline
    <10
     Modular
    yes count = 0
    Write
    “The End”
    WHILE count < 10
    add 1 to
    count DO Process
    ENDWHILE
    Stop
    write count WRITE “The End”

    Process
    ADD 1 to count
    WRITE count
    REPEAT / UNTIL
    Start count = 0
    REPEAT
    count = 0
    ADD 1 to count
    WRITE count
    UNTIL count >= 10
    add 1 to WRITE “The End”
    count

    Mainline
     Modular
    write count count = 0
    REPEAT
    yes DO Process
    count
    <10 UNTIL count >= 10
    no WRITE “The End”

    Write Process
    “The End”
    ADD 1 to count
    Stop WRITE count
    Advantages & Disadvantages
    Flowchart Advantages: Pseudocode Advantages
     Standardized  Easily modified
     Visual  Implements structured concepts
     Done easily on Word Processor

    Flowchart Disadvantages: Pseudocode Disadvantages:


     Hard to modify  Not visual
     Structured design elements not  No accepted standard, varies from
    implemented company to company
     Special software required
    Access of Data
    The READ statement tells the computer to get a value from an
    input device and store it in a memory location.

    How to deal with memory locations?

    Memory locations are identified by their addresses, we give


    them names (field names / variable names) using words
    descriptive to us such as ctr as opposed to a location addresses
    such as 19087.
    Rules for Variable Names

    • Begin with lowercase letter


    • Contain no spaces
    • Additional words begin with capital
    • Unique names within code
    • Consistent use of names
    Working with Fields
    Calculations Selection
    + add > greater than
    - subtract < less than
    * multiply = equal to
    / divide >= greater than or equal to
    ** or ^ exponentiation <= less than or equal to
    () grouping <> not equal to

    You might also like