Definition of a Flowchart
A flowchart is a visual representation of a process or algorithm. It uses standardized symbols and shapes
to illustrate the steps involved in a process, the sequence of actions, and the decision points. Flowcharts
are widely used in various fields, including software development, project management, and business
process modeling, to help visualize complex processes and improve understanding.
Common Flowchart Symbols
1. Oval (Terminator): Represents the start and end points of a flowchart.
2. Rectangle (Process): Indicates a process step or action.
3. Diamond (Decision): Represents a decision point that can lead to different paths based on a
yes/no question or condition.
4. Parallelogram (Input/Output): Used for input and output operations, such as reading data or
displaying results.
5. Arrow (Flow Line): Shows the direction of the flow of the process.
Steps to Develop a Flowchart
1. Identify the Process: Determine the process or algorithm you want to represent.
2. Define the Start and End Points: Clearly identify where the process begins and ends.
3. List the Steps: Break down the process into individual steps or actions.
4. Identify Decision Points: Determine where decisions need to be made and what the possible
outcomes are.
5. Choose Symbols: Use the appropriate flowchart symbols to represent each step and decision.
6. Connect the Symbols: Use arrows to connect the symbols in the order that the steps occur.
7. Review and Refine: Check the flowchart for clarity and completeness, making adjustments as
necessary.
Explanation of the Flowchart:
This is a Problem-Solving Flowchart that provides a step-by-step approach to troubleshooting an issue.
Here’s an explanation of how it works:
1. Start – The process begins.
2. Check for a relevant button or menu item – The user is asked whether they can see a button or
menu item related to what they want to do.
a. If yes, they should click it.
b. If no, the process moves to the next step.
3. Try a random option – If no relevant button or menu item is visible, the user is asked whether they
tried one randomly.
a. If no, they are encouraged to do so.
b. If yes, they proceed to the next step.
4. Search for a solution online – If random attempts didn’t work, the user is advised to search for
the name of the program along with relevant keywords.
5. Check if the action worked – After clicking a button or following the online solution, the user
checks if the problem is solved.
a. If yes, they are done.
b. If no, they proceed to the next step.
6. Check time spent – If the issue is still unresolved, the user checks whether they have been trying
for more than half an hour.
a. If no, they should continue trying.
b. If yes, they are advised to ask for help or give up.
Key Takeaways:
• The flowchart follows a logical troubleshooting approach.
• It encourages self-help by guiding the user through different steps before seeking assistance.
• It incorporates problem-solving strategies such as trial-and-error and online search.
