This course comes before either specialisation. After it the material divides into a machine-learning path (Machine Learning, Artificial Intelligence, Neural Networks and Deep Learning and Natural Language Processing) and a data-platform path (Big Data Technologies, Cloud Computing for Data Science, Time Series Analysis and Forecasting and Data Engineering and MLOps); this one belongs to neither.
BI is not analytics with nicer charts. It is a different job.
Python for Data Analysis and Visualization taught you to answer a question nobody had asked before. BI is about answering the same question every Monday morning, for someone who will not write code, fast enough that they act on it in the meeting.
That constraint drives every design decision in this course — why the data is modelled as a star, why measures are pre-aggregated, why a dashboard shows six numbers and not sixty.
| Data science (Python for Data Analysis and Visualization) | Business intelligence (here) | |
|---|---|---|
| Question | New each time, often exploratory | Known in advance, asked repeatedly |
| Audience | You, and other analysts | A manager who will not write code |
| Output | A notebook, a model, a finding | A dashboard someone opens unprompted |
| Time frame | Mostly the past and a prediction | Mostly what happened, and how it is trending |
| Success | The finding is correct and new | A decision changed |
| Data shape | Whatever you were given | A deliberately modelled star schema |
The exam's favourite question is the first row of that table. "Differentiate BI, Data Analytics and Data Science" is Outcome 1, Activity 1, and a near certainty on the paper. §1.2 answers it properly.
You have met more of this course than you think.
| From | You have | Used here |
|---|---|---|
| Computer Fundamentals and Office Automation | Excel, pivot tables, slicers, dashboards, VLOOKUP | Power BI is those ideas at scale. A pivot table is a $group; a slicer is a slicer |
| Data Mining, Unit 1 | Star and snowflake schemas, fact and dimension tables, OLAP cubes | Unit 4 here is that unit again. See §4.1 — do not study it twice |
| Database Management Systems | SQL joins, cardinality, keys | Tableau's joins are SQL joins; Power BI relationships are joins declared once instead of written each time |
| Python for Data Analysis and Visualization | pandas, matplotlib, Seaborn, Plotly | Power Query is pandas with a mouse. Every transformation here has a one-line pandas equivalent, and the labs give it |
| Statistical Foundations for Data Science | Aggregation, distributions, correlation | What the measures actually mean, and why an average of averages is wrong |
If you did Computer Fundamentals and Office Automation Unit 5 properly, you already know what a dashboard is for. The new material is the modelling in Unit 4 and the tooling in Units 2–3.
Introduce foundational concepts of Business Intelligence (BI) and Decision Support Systems (DSS), including their scope, evolution, and organizational relevance.
Familiarize students with leading BI tools such as Power BI and Tableau, highlighting their ecosystems, interfaces, and comparative strengths.
Develop skills in data preparation and transformation, using Power Query and
Enable effective data visualization and storytelling, leveraging charts, dashboards, and advanced features to communicate insights.
Equip learners with data modeling techniques, including dimensional modeling, relationships, joins, and governance principles for robust BI solutions.
NOTE
Objective 3 is printed exactly as shown. It stops at "using Power Query and" — the sentence runs straight into objective 4 with its ending missing. From Unit 3 and Outcome 2 it was presumably "…using Power Query and Tableau's data preparation features." Recorded as a finding in SYLLABUS-REVIEW.md.
BI definition, scope and evolution; BI against data analytics and data science; the BI lifecycle and where projects fail; applications across finance, HR, marketing, retail, education and healthcare; maturity models and organizational readiness; DSS concepts, components and architecture; Power BI and Tableau compared.
UNIT 2The Desktop / Service / Mobile ecosystem; connecting to Excel, CSV, SQL Server and Web APIs; Import against DirectQuery; Power Query as a recorded, replayable recipe; calculated columns against measures; SUM, COUNT, AVERAGE, IF and CALCULATE; the average-of-averages trap; sharing through the Service.
UNIT 3VizQL and the Tableau products; live against extract; shelves, the marks card and views; blue against green; data preparation and the filter order of operations; calculated fields; LOD expressions — FIXED, INCLUDE and EXCLUDE; joins against blending and the fan trap; building a story.
UNIT 4Fact and dimension tables; the grain, and additive, semi-additive and non-additive measures; star against snowflake, and why never one flat table; relationships, cardinality and cross-filter direction; data governance — metadata, hierarchies and the six dimensions of quality; model design best practices.
UNIT 5When a dashboard is and is not the right answer; dashboard components; the principles of effective visualization and accessibility; filters, slicers, parameters and drilldowns; layout, alignment and the F-pattern; publishing to the Power BI Service and Tableau Public; storytelling and insight communication.
PRACTICEExam-style questions with fully worked solutions.
LABEvery prescribed lab experiment, with code and expected output.