Flowchart Blocks Overview for APSC 141 F23

Flowchart Blocks for APSC 141 F23

Overview

  • In APSC 141 for Fall 2023, flowchart blocks are essential in structuring programs based on the C programming language.

  • The guidelines provided aim to ensure clarity in flowchart creation which is crucial for the understanding and execution of programming tasks.

Flowchart Components

Start/End Blocks

  • Purpose: Every program requires a clear starting and ending point.

  • In Code: This corresponds to the beginning of the main function and the return statement at the end.

  • In Flowchart: Utilize Start and End blocks to visually represent these points.

Input and Output Blocks

  • Definition: Programs must interact with users or other programs, which involves accepting inputs and providing outputs.

  • **Methods of Input/Output:

    • Examples include:

    • Reading from memory (behind the scenes)

    • Utilizing input devices like keyboards & mice

    • Displaying output on screens in real time

  • Typical Usage in Course: Most course assignments will involve basic textual input and output but creativity is encouraged.

  • In Flowchart: Replace the generic terms "Input" and "Output" with more descriptive actions detailing what data is being processed.

Process Blocks

  • Definition: A process in a flowchart represents any computational activity performed by the code.

  • Characteristics: This could involve:

    • Mathematical operations (e.g., addition, subtraction)

    • Logical operations (e.g., comparisons)

    • Assignment of values to variables

  • In Flowchart: Label processes with specific descriptions instead of simply using "Process".

Conditional Blocks

  • Definition: Conditionals are decision points in the code where a choice or division in flow need to be made.

  • Requirements: Each conditional must have at least two conditions but can accommodate multiple conditions.

  • Characteristics: They create branching paths in a program which rejoin at different points or can lead to a termination of the program in cases of a fatal error.

  • In Flowchart: Use descriptive terms instead of labeling them as "Conditional" and detail the conditions involved in the decision-making.

Loop Blocks

  • Definition: Loops are constructs that allow for repeated execution of code with variations in conditions on each iteration.

  • Utility: Particularly useful for analyzing a single problem from multiple perspectives or instances.

  • Exit Condition: All loops must include a clear exit condition; failure to do so could lead to infinite loops.

  • In Flowchart: Label loop blocks descriptively instead of using the generic term "Loop" to clarify the purpose and behavior of the repeating action.