Rules and Symbols

Comprehension strategies

Primary definition

What is a flowchart?

A flowchart is a visual representation of an algorithm using standard geometric shapes connected by directional arrows.

Each shape has a specific purpose. Looking at a diagram lets our brains follow the entire solution smoothly and naturally.

Visual

Understood at a glance

Sequential

Follows one clear path

Universal

Shared by programmers everywhere

Flowchart fundamentals

Symbol 1 of 5

Terminal

The oval of start and end

Marks the exact boundary where an algorithm begins and where it finishes.

Key guidelines:

• Every flowchart starts with a clearly marked beginning.

• Always contains clear words like Start or End.

Start End

Standard symbols

Practical application

The oval in everyday routines

Starting moment

Waking up in the morning represents the start oval for your school day routine.

Ending moment

Going to sleep at night represents the end oval that finishes the day’s activities.

Without a clear start, we cannot know when to begin our steps.

Everyday connections

Symbol 2 of 5

Process

The action rectangle

Represents a concrete action, a single instruction, or a calculation.

Key guidelines:

• Begin with an active, specific action verb.

• Keep one distinct task inside each box.

Pack notebook Tie shoes

Standard symbols

Precise actions

Clear steps with action verbs

Each rectangle must clearly state what action needs to be completed.

Wash

Wash hands with soap and water.

Place

Place book inside school bag.

Add

Add two numbers together.

A well-written step leaves no room for confusion.

Process structuring

Symbol 3 of 5

Flow lines

Directional arrows

Show the sequence and determine the exact order of steps between shapes.

Key guidelines:

• Always feature an arrowhead at the destination end.

• Most commonly flow downwards from top to bottom.

Connected flow

Standard symbols

Orientation rule

How to direct the flow

From top to bottom

The most natural and widely used arrangement for organizing steps on a page.

From left to right

Helpful when laying out wide processes across horizontal display layouts.

Caution: Arrows should never cross over each other carelessly or leave loose ends.

Construction rules

Symbol 4 of 5

Input / Output

The data parallelogram

Represents taking in information from outside or sending answers back out.

Key guidelines:

• Input: receive values from a user or sensor.

• Output: display a message or final calculated result.

Input name Display greeting

Standard symbols

Real-world exchange

Input and output in action

Input (Requesting data)

Prompt: “How many pencils do you need for class?”

Output (Sharing a response)

Screen message: “Your backpack is packed and ready!”

Programs constantly communicate back and forth with the user.

Data communication

Symbol 5 of 5

Decision

The decision diamond

Presents a question that leads to two different branch paths: Yes or No.

Key guidelines:

• Contains a direct question with a question mark.

• Always branches into two labeled paths (Yes / No).

Is it raining?

Standard symbols

Decision making

Two clearly defined branches

Question: Is it raining outside?

Yes branch

Grab an umbrella before leaving.

No branch

Head outside comfortably without an umbrella.

The diamond enables algorithms to adapt intelligently to different real situations.

Conditional logic

Quick reference guide

The five essential symbols

Oval

Start / End

Rectangle

Process / Action

Diamond

Yes / No branch

Parallelogram

Input / Output

↓

Arrow

Flow line

Remembering these five shapes unlocks key problem-solving skills.

Visual synthesis

Written planning tool

What is pseudocode?

Pseudocode is a simple, structured way to write down the steps of an algorithm using plain everyday language before writing code.

It does not belong to a specific language like Python or JavaScript. Anyone can read it and understand it without memorizing complex technical syntax.

Writing pseudocode lets us concentrate on problem-solving without worrying about punctuation rules.

Pseudocode fundamentals

Fundamental rule 1

One idea per line

Messy line (crowded)

Put on socks then find shoes and tie them quickly

Cramming multiple actions into one sentence creates confusion.

Clean lines (separated)

1. Put on socks

2. Put on shoes

3. Tie shoelaces

Each line focuses on one distinct action.

Keeping one action per line helps you read and follow directions easily.

Writing rules

Fundamental rule 2

Clear everyday language

Use everyday words that any classmate can easily understand right away.

Write / Print

To display messages on screen.

Read / Input

To get responses from the user.

Calculate

To perform additions or math steps.

You do not need complicated technical vocabulary to write solid pseudocode.

Writing rules

Fundamental rule 3

Start and end markers

Every block of pseudocode must state explicitly where the steps begin and where they conclude.

Essential keywords:

• First line: Start

• Final line: End

Start

Step 1: Take notebook

Step 2: Write name

End

This keeps directions clear and clearly bounded from start to finish.

Writing rules

Two sides of the same coin

Direct connection between formats

Flowchart

Visual and spatial format.

Ideal for tracing branches and seeing the big picture at a glance.

Pseudocode

Written and sequential format.

Ideal for drafting instructions line by line before typing code.

Both formats express the exact same algorithm using different modes.

Conceptual integration

Guided demonstration • Step 1

Everyday routine

Getting ready to leave home

First step: we place the start oval to establish the beginning.

Line 1: Start

Start

The arrow points directly to our first action

Teacher modeling

Guided demonstration • Step 2

Sequential actions

Adding process rectangles

We add two clear action steps connected by downward flow arrows.

Line 2: Pack snack

Line 3: Put on shoes

Pack snack Put on shoes

Teacher modeling

Guided demonstration • Step 3

Formal closure

Completing with the end oval

We draw a final arrow leading into the end oval to close the plan.

Line 4: End

End

Algorithm complete and validated!

Teacher modeling

Side-by-side comparison

Same algorithm in both styles

Flowchart

Start

↓

Pack snack

↓

Put on shoes

↓

End

Equivalent pseudocode

Start

Pack snack

Put on shoes

End

Notice how each line matches one specific shape.

Algorithmic equivalence

Whole-class guided check

Routine example: Preparing a snack

Let us answer aloud together before sketching on paper:

Which shape comes first?

The oval with the word Start.

Which shape spreads butter?

The action rectangle.

How do we connect steps?

With downward flow arrows.

Great job! Now we will put this into hands-on practice.

Comprehension check

Hands-on partner and solo activity

Working with pencil and paper

Activity prompt:

Grab your paper and pencil. Create a short flowchart and matching pseudocode for a routine you know well.

Choice A

Packing a backpack for school.

Choice B

Making a simple snack at home.

Feel free to share thoughts quietly with your neighbor to talk through steps.

Practical application

Drawing instructions

Steps to build your flowchart

1

Draw an oval at the top containing the word Start.

2

Draw a downward arrow leading into a rectangle with your first action.

3

Add one or two more actions inside separate rectangles connected with arrows.

4

Draw a final arrow pointing to an oval with the word End.

Step-by-step guidance

Writing instructions

Steps to draft your pseudocode

1

Write the word Start on the very first line.

2

Write each action on its own line with a small indentation from the margin.

3

Use direct action verbs like Pack, Put, Zip, or Spread.

4

Finish your list on the final line with the word End.

Step-by-step guidance

Reflection time

Sharing our findings

Let us consider together:

• What happened when you split each action into its own separate shape?

• Could your partner follow your routine without needing any spoken explanation?

When an algorithm is well organized, it explains itself clearly.

Dialogic reflection

Homework assignment • Part 1

Analytical and reflective questions

Each student will answer the following three questions in writing (or by voice recording):

1. Which flowchart symbol felt easiest to remember today, and why?

2. How does seeing a problem as a sequence of clear symbols or short lines help you understand it better?

3. In what everyday situation could you use a simple flowchart or pseudocode to organize your steps?

Homework notes

Homework assignment • Part 2

Brief metacognitive evaluation

Reflect on your own learning journey:

• Which part of today’s class felt clearest?

• Which part felt a bit harder?

• What strategy helped you understand the symbols better?

Reminder: The next session will practice creating simple flowcharts and short pseudocode.

Metacognition

Saint Augustine Preparatory School

Thinking clearly before programming

Symbols and pseudocode are our core tools to turn ideas into structured, logical solutions.

Teacher: Mr. Norman Trujillo (“Norman Trujillo”)

ntrujillo@csa.edu.ni

Computer Science • Grade 6 Thank you for your active participation!

Diapositivas 19 a 23 • Las tres reglas del pseudocódigo

Explicación oral directa: “El pseudocódigo traduce ese diagrama a oraciones escritas. Aplicamos tres reglas de oro: primera, una idea por línea; segunda, palabras sencillas y cotidianas; tercera, escribir siempre Inicio arriba y Fin abajo.”

Diapositivas 24 a 28 • Modelado guiado y preparación de merienda

Explicación oral directa: “Miren cómo construyo en la pizarra la rutina de salir de casa. Inicio, guardo merienda, me pongo zapatos y llego al fin. Noten cómo cada línea escrita coincide con su figura gemela en el diagrama.”

Diapositivas 29 a 35 • Práctica con lápiz y papel, reflexión y tarea

Explicación oral directa: “Ahora tomen su lápiz y su papel. Diseñen un diagrama de cuatro figuras para empacar la mochila o hacer una merienda, y escriban sus cuatro renglones equivalentes. Circulen y revisen con su compañero de mesa.”

Instrucción para la tarea y Google Classroom:

Indique a los estudiantes que deben fotografiar o escanear su trabajo en papel y cargarlo en la tarea asignada en Google Classroom, junto con las respuestas a las tres preguntas analíticas y la autoevaluación metacognitiva.

Guion estructurado para la sesión 1 Página 2 de 2

Slides 24 to 28 • Guided Modeling and Snack Routine

Direct Teacher Script: “Watch as I sketch leaving home on the board. Start, pack snack, put on shoes, and End. Notice how each written line matches its partner shape in the flowchart.”

Slides 29 to 35 • Paper & Pencil Practice and Reflection

Direct Teacher Script: “Now take your paper and pencil. Draw a four-shape flowchart for packing your backpack or making a snack, and write the matching four lines of pseudocode underneath. Share with your partner to test readability.”

Homework and Google Classroom Reminder:

Remind students to photograph or scan their handwritten work and upload it to the assignment in Google Classroom, along with the three analytical questions and their metacognitive self-evaluation.

Structured script for session 1 Page 2 of 2

Instrucción para envío en Google Classroom:

Una vez completada esta hoja de trabajo con lápiz y papel, tómale una foto clara y súbela en Google Classroom dentro de la tarea “Sesión 1: Reglas y símbolos”.

Hoja de trabajo de clase • Página 2 de 2 Colegio Preparatorio San Agustín

Class worksheet • Page 2 of 2 Saint Augustine Preparatory School

• Cierre formal: Fin.

Quiz de autoevaluación diaria:

• Pregunta 1: B (El óvalo).

• Pregunta 2: C (Representar una acción o cálculo).

• Pregunta 3: B (Redactar una sola idea por cada renglón).

Código maestro y solucionario • Página 2 de 2 Colegio Preparatorio San Agustín

• Question 1: B (The oval).

• Question 2: C (Representing an action or calculation).

• Question 3: B (Writing only one clear idea per line).

Master code and answer keys • Page 2 of 2 Saint Augustine Preparatory School