2.8 Methods to Design a Solution

This topic explains the methods used to design a solution after a problem has been completely understood, including flowcharts and concept maps.

Definition

• Flowcharts
• Concept Maps

Core Concept

Designing a solution is like drawing a blueprint before building a house. You wouldn't start construction without a plan—you'd first sketch the layout, decide where rooms go, and plan the wiring. Similarly, before writing code, you design a solution using flowcharts (which show the step-by-step sequence of operations) or concept maps (which show relationships between ideas). These tools help you visualize the solution, spot errors early, and communicate your plan to others.

Detailed Explanation

Why Design a Solution?

After understanding the problem, the next stage is to design a solution. In solution design, you define how software will meet the requirements and objectives of a problem.

• Design comes after understanding the problem.
• Defines how software will meet requirements.
• Helps in planning before coding.
• Makes implementation smoother.

Method 1: Flowcharts

2.8.1 Flowcharts

A flowchart is a diagrammatic representation of an algorithm. It describes what operations are required to solve a given problem.

• Flowchart illustrates the sequence of operations to be performed to solve a problem in the form of a diagram.
• Computer programmers draw flowcharts before writing computer programs.
• It provides an easy way to analyze and find solutions to problems.
• Once the flowchart is drawn, it becomes very easy to write the program in any computer language.
• It is very helpful in communicating the problem-solving method to other people.
• It also helps in finding and removing logical errors.

Steps for Drawing a Flowchart:

• Start of the flowchart
• Input to the flowchart
• Type of processing required
• Decision to be taken
• Output of the operation
• End of the flowchart

1. Start of the Flowchart: Every flowchart should start with a trigger. The graphical representation of start of flowchart is oval shape.

2. Input to the Flowchart: The flowchart designer must know what exactly the input to the flowchart is. The input is determined from the problem statement. For example, the given problem is to convert temperature from Fahrenheit to Celsius. Here, the input will be the temperature in Fahrenheit. The graphical representation of input is parallelogram.

3. Processing in the Flowchart: The flowchart designer must decide what type of calculation is to be performed or what formula is applied to obtain the required result. For example, to find the area of a triangle: Area = Base × Height2 The graphical representation of processing symbol is rectangle.

4. Decision Making in Flowchart: The flowchart designer must decide which control structure (sequence, repetition, or selection) is to be applied for the solution of the problem. For example, selection structure must be applied to print letter grade of a student based on the marks obtained. The selection structure will check in which range the marks fall and accordingly print the grade. Graphically the decision is represented with a diamond.

5. Output: The flowchart must provide the required output. The output is represented with a parallelogram symbol as well.

6. End of Flowchart: The flowchart should have a defined end, and because of the possibility of multiple decision points, it may have multiple ends. For end of flowchart the oval symbol is used.

Flowchart Symbols Summary:

Example Flowchart: Find Sum, Product, and Average of Five Numbers

From the statement of the flowchart, it is clear that sum, product, and average are to be calculated, and given are five numbers.

• Start
• Input A, B, C, D, E
• SUM = A + B + C + D + E
• PROD = A × B × C × D × E
• AVG = SUM / 5
• Output SUM, PROD, AVG
• End

How to Create a Flowchart in Microsoft Visio:

a) Start Microsoft Visio. b) Click on the category of Flowchart. c) Double-click the Basic Flowchart. d) For each step you wish to design in the process, drag a relevant flowchart symbol and place it onto your drawing. e) Connect the flowchart shapes by holding the mouse pointer over the first symbol, and then releasing it on the other symbol you wish to connect to. f) To place text into a shape, select it, and then type.

LARP (Logics of Algorithms and Resolution of Problems): LARP is a programming language for rapid development of prototypes. However, unlike C++, Java, and other programming languages, LARP uses semi-natural syntax. Therefore, it is very easy for non-programmers to understand. LARP also allows algorithms to be expressed as flowcharts.

Method 2: Concept Maps

2.8.2 Concept Maps

Concept map, like a flowchart, is another way of representing knowledge. A concept map is a graphical tool that represents concepts and relationships between them. This diagram is a popular way to capture understanding of a topic, therefore, it can help with everything from brainstorming to decision-making.

• Concepts are represented as boxes or circles.
• Relationships are shown with lines or arrows.
• Lines are labeled with linking words and phrases to represent connections between concepts.
• Different software tools for concept mapping: CmapTools, Mind Manager.

Example 1: Concept Map of Water Cycle

• Evaporation: Water turns into vapor from oceans, lakes, and rivers.
• Condensation: Water vapor cools down to form clouds.
• Precipitation: Rain, snow, sleet, or hail fall from clouds.
• Collection: Water gathers in bodies like rivers, lakes, and oceans.

Example 2: Concept Map of Video Game Development

Main Concept: Video Game Development

• Game Design:
• Gameplay Mechanics (how players interact with the game)
• Level Design (creating game environments and challenges)
• Storyline (plot and characters)
• Programming:
• Coding (writing the game's code)
• Game Engines (tools like Unity, Unreal Engine)
• Scripting (e.g., how events in the game happen)
• Graphics:
• 2D Art (sprites, backgrounds)
• 3D Models (characters, environments)
• Animation (movement and transitions)
• Sound Design:
• Sound Effects (e.g., jumping, background noise)
• Music (background soundtrack)
• Voice Acting (characters' voices)
• Testing:
• Bug Fixing (finding and solving issues)
• Playtesting (ensuring the game works properly and is fun)
• Quality Assurance (testing for quality and performance)

• Helps capture understanding of a topic.
• Aids in brainstorming and decision-making.
• Shows relationships between concepts.
• Useful for planning and organizing ideas.

Intermediate Level

Designing a solution is a critical step after understanding a problem. Flowcharts are diagrammatic representations of algorithms, showing the sequence of operations using standard symbols: oval (start/end), parallelogram (input/output), rectangle (process), and diamond (decision). They help in analyzing problems, communicating solutions, and finding logical errors before coding. Concept maps are graphical tools that represent concepts and their relationships, using boxes/circles for concepts and labeled arrows for connections. They are useful for brainstorming, planning, and organizing complex ideas. Both methods help in creating a clear plan before implementation.

Important Points

• - Design a solution after understanding the problem.
• - Two methods: Flowcharts and Concept Maps.
• - Flowchart: diagrammatic representation of an algorithm.
• - Flowchart symbols: oval (start/end), parallelogram (IO), rectangle (process), diamond (decision).
• - Flowcharts help in analysis, communication, and error detection.
• - Concept map: graphical tool showing concepts and relationships.
• - Concept maps use boxes/circles and labeled arrows.
• - Tools: Microsoft Visio (flowcharts), CmapTools, Mind Manager (concept maps).

Remember

• - Flowchart: Diagram of steps.
• - Symbols: Oval (Start/End), Parallelogram (IO), Rectangle (Process), Diamond (Decision).
• - Concept Map: Web of concepts and relationships.
• - Flowchart = Sequence; Concept Map = Relationships.
• - Tools: Visio (flowchart), CmapTools (concept map).
• - Design before coding.

Common Mistakes

• - Confusing flowcharts and concept maps: Flowcharts show steps; concept maps show relationships.
• - Using wrong symbols in flowcharts: Oval for start/end, parallelogram for IO, rectangle for process, diamond for decision.
• - Skipping solution design: Jumping to coding without a plan leads to errors.
• - Forgetting to label concept map arrows: Labels explain the relationship between concepts.
• - Assuming flowcharts are only for programming: They are used in many fields for process design.

Quick Revision

After understanding a problem, the next step is to design a solution. Flowcharts are diagrammatic representations of algorithms, using symbols like oval (start/end), parallelogram (input/output), rectangle (process), and diamond (decision). They help in analysis, communication, and error detection. Concept maps are graphical tools that show concepts and their relationships using boxes/circles and labeled arrows. They help in brainstorming, planning, and organizing ideas. Both methods are essential for effective problem-solving and software design.

60-Second Revision

• Flowcharts: Diagram of steps (algorithm). Symbols: Oval (Start/End), Parallelogram (IO), Rectangle (Process), Diamond (Decision).
• Concept Maps: Web of concepts and relationships. Boxes/circles + labeled arrows.