Study guide · 4.2
Represent data visually
Visuals turn raw numbers and processes into something people can grasp quickly. The skill is choosing the right format for the data and the message, building it cleanly in productivity software and using flowcharts to make procedures easy to follow.
A study feature written by ExamDragon, not part of the real exam. Each heading is one of Certiport's skills for this objective.
4.2.1Identify the appropriate visual formats to express various data sets
- Line charts show change over time, such as monthly sales across a year.
- Bar or column charts compare amounts across categories, such as sales by region.
- Pie charts show parts of one whole that add up to 100 percent; they work best with few categories.
- Scatter plots show the relationship between two numeric variables; histograms show how values are distributed.
- Tables are best when people need exact values or must look up individual figures.
Example: To show how website visits rose over twelve months a line chart is used, while a bar chart compares visits from five countries.
4.2.2Produce business graphics by using productivity software
- Spreadsheet, word processing and presentation programs can insert charts, diagrams, icons and shapes.
- Use a consistent style, a clear title, readable labels and a limited colour palette.
- Use built-in diagram tools for organisation charts, timelines, cycles and process steps.
- Keep the visual simple: remove decorations such as 3D effects and heavy gridlines that do not add meaning.
- Link a chart to its source data so it updates when the numbers change.
Example: For a quarterly meeting, a manager inserts a timeline diagram of project milestones and a column chart of budget against actual spending into the presentation.
4.2.3Build tables, charts, and visual representations of raw data
- Organise raw data first: one header row, one type of data per column, no blank rows and consistent units.
- Convert a data range into a table to get sorting, filtering and automatic formatting.
- Select the data, insert a chart, then add a title, axis titles, data labels and a legend when needed.
- Start value axes at zero for bar charts so differences are not exaggerated.
- Do not rely on colour alone to tell series apart; use labels or patterns too.
Example: A volunteer types survey answers into a spreadsheet, formats the range as a table, filters out incomplete answers and creates a bar chart of the most popular options.
4.2.4Compose procedural flowcharts and instructions
- A flowchart shows the steps of a process and the decisions within it.
- Common symbols: an oval for start and end, a rectangle for an action, a diamond for a yes or no decision and a parallelogram for input or output.
- Arrows show the direction of flow; every decision has a labelled path for each answer.
- Write each step as a short action starting with a verb, in the order it happens.
- Test the flowchart or written instructions by having someone follow them exactly.
Example: An IT team draws a flowchart for password resets: start, then the decision 'Can the user sign in?'; Yes leads to end, No leads to verify identity, then send reset link, then end.
Key terms
- Line chart
- A chart that connects data points to show change over time.
- Bar chart
- A chart that uses bars of different lengths to compare categories.
- Legend
- The key that explains what each colour or symbol in a chart represents.
- Flowchart
- A diagram of a process using standard symbols connected by arrows.
- Raw data
- Data that has been collected but not yet organised or analysed.
Easy to confuse
- A pie chart cannot show change over time, and it misleads when the parts do not add up to one whole.
- Starting a bar chart's axis above zero makes small differences look large.
- Too many colours, categories or effects make a chart harder to read, not more impressive.
After this guide: You can choose a suitable chart for a data set, build clear tables and charts, and draw a flowchart for a procedure.