Course Outcome Writing and CO–PO Mapping Guide for EEE Courses

Course Outcome Writing and CO–PO Mapping Guide for EEE Courses

Course Outcome Writing and CO–PO Mapping Guide for EEE Courses

← Back to Outcome Based Education
Department of Electrical and Electronic Engineering, BUET · OBE Guide

Course Outcome Writing and CO–PO Mapping Guide for EEE Courses

Write measurable Course Outcomes, choose Bloom levels deliberately, and justify CO–PO mappings with evidence that stands up in course files, review meetings, and accreditation discussions.

Faculty members Course coordinators OBE committee members Students

Quick explanation

A good outcome statement is short, specific, observable, and easy to connect to assessment evidence.

Course Outcome

A clear statement of what a student should be able to do by the end of a course or a major learning block.

Program Outcome

A broader graduate attribute the student should achieve by graduation.

Bloom level

The intended cognitive depth of the CO: Remember, Understand, Apply, Analyze, Evaluate, or Create.

Mapping strength

The extent to which a CO contributes to a PO, based on what is actually taught and directly assessed.

Accreditation-sensitive source note. Current BAETE criteria require programs to demonstrate outcome achievement through teaching-learning, assessment, and course-file evidence. The BAETE V2.1 SAR template permits binary or ternary CO–PO correlation reporting. Therefore, the 0–1–2–3 mapping scale used here is presented as a recommended departmental calibration rubric, not as a formal BAETE mandate.
BUET EEE implementation note. This page uses the currently published BUET EEE PO-a to PO-l structure for immediate usability. The data model also contains a future BAETE Manual v3-style PO set so the department can update the guide later without rewriting the whole page.

Writing strong Course Outcomes

A Course Outcome should describe student performance, not teacher coverage or a syllabus topic.

Action verb + knowledge/skill + context/condition + expected standard/performance

Anatomy of a good CO

Use one dominant observable verb. Name the specific EEE task clearly. Add context where it matters. Add a performance expectation or evidence path when the course naturally supports one.

  • What will the learner do?
  • On what EEE knowledge, skill, or artifact?
  • Using what method, tool, or context?
  • How will acceptable performance be recognized?

Common mistakes

  • using vague verbs such as know, understand, learn, or be familiar with
  • writing a syllabus topic instead of a student performance
  • putting too many verbs into one CO
  • mapping a PO because the topic appeared in class rather than because students produced evidence
  • claiming design, investigation, teamwork, ethics, sustainability, or communication without an assessed artifact

Weak versus improved EEE examples

AreaWeak COImproved COLikely Bloom level
CircuitsUnderstand nodal analysis.Calculate node voltages and branch currents in linear DC networks using nodal and mesh methods, and verify power balance in solved circuits.Apply
ElectronicsKnow BJT amplifiers.Analyze bias stability, midband gain, and small-signal behavior of single-stage BJT amplifiers from circuit parameters and measured characteristics.Analyze
Electrical machinesLearn induction motor operation.Predict torque-speed characteristics and efficiency trends of three-phase induction motors from equivalent-circuit parameters and test data.Analyze
Power systemsBe familiar with load flow.Compute bus voltages and line flows in balanced power networks using Newton–Raphson load-flow formulation, and interpret operating-limit violations.Analyze
Communication systemsUnderstand digital modulation.Compare BER–bandwidth tradeoffs of common digital modulation schemes under AWGN conditions using analytical expressions and simulation results.Evaluate
Control systemsKnow root locus.Design a lead or lag compensator using root-locus specifications to satisfy transient-response and steady-state-error requirements.Create
Signal processingLearn the FFT.Implement FFT-based spectral analysis for discrete-time signals and interpret aliasing, leakage, and resolution effects.Apply / Analyze
Embedded systemsUnderstand interrupts.Develop interrupt-driven firmware for sensor-actuator interfacing on a microcontroller and validate timing behavior with defined test cases.Create
Digital systems / FPGAKnow Verilog.Design, simulate, and verify a finite-state machine in Verilog HDL that meets stated functional and timing requirements.Create
Measurement and instrumentationBe familiar with calibration.Calibrate a measurement chain using standard references and quantify sensitivity, repeatability, and uncertainty from recorded data.Analyze
Power electronicsUnderstand converters.Design and evaluate a buck converter to meet ripple and efficiency specifications using simulation and hardware measurements.Create / Evaluate
Laboratory coursesDo op-amp experiments.Measure gain, bandwidth, slew rate, and offset characteristics of op-amp circuits using standard lab instruments, and analyze deviation from theory.Apply / Analyze
Project / thesisLearn research methods.Investigate an EEE problem through literature review, simulation or experiment, data interpretation, and evidence-based conclusions presented in a formal report or defense.Evaluate / Create

Bloom’s taxonomy for EEE courses

Use revised Bloom levels to choose a realistic cognitive target and match assessment methods to intended performance.

Searchable EEE action verb bank

CO–PO mapping logic

Alignment chain

PEO → PO → CO → Teaching-learning activity → Assessment task → Attainment evidence → CQI

A defensible mapping works both forward and backward. A CO should not point to a PO unless the course teaches that capability and assesses it directly enough to leave evidence in the course file.

Use this test before mapping

  1. Does the CO explicitly demand the capability described by the PO?
  2. Do students practice that capability in the course?
  3. Is there direct evidence in an assessment artifact?
  4. Would an external reviewer accept that evidence from the course file?

Current BUET EEE PO guidance

POUsually map when the CO requires...Do not map unless...

Recommended internal mapping-strength rubric

StrengthMeaningEvidence usually neededRecommended internal heuristicCommon misuse
0 / blankNo meaningful contributionNo direct evidence path, or only topic mentionLeave blankFilling every cell “just in case.”
1Introductory / low contributionOne limited direct task or light exposureOften about 5–10% of assessmentGiving 1 even when nothing is assessed.
2Moderate / practiced contributionClear direct assessment in one substantial task or several smaller tasksOften about 10–25% of assessmentUsing 2 for a major design, lab, or thesis artifact.
3Strong / major assessed contributionThe CO and a major assessment artifact clearly target the POOften above 25–30% or a major design/lab/project deliverableAssigning 3 without substantial direct evidence.
Important warning. A mapping strength should not be assigned merely because a topic is mentioned in class. It should be supported by teaching-learning activity and direct assessment evidence.

Worked examples by course type

CO: Analyze first-order RL and RC transient responses from governing equations and waveform plots, and predict time constants and steady-state values.

Likely map: PO-a strong; PO-b moderate to strong.

Evidence: worked tutorial set, midterm analytical problem, final exam script.

CO: Measure and analyze the gain, bandwidth, and non-ideal behavior of op-amp circuits using oscilloscope and function generator, and compare measured results with theoretical predictions.

Likely map: PO-d strong; PO-e moderate to strong; PO-j weak to moderate if reports are graded.

Evidence: lab sheet, raw data, lab report rubric, viva records.

CO: Design and evaluate a buck converter to meet ripple and efficiency specifications using simulation and hardware testing.

Likely map: PO-c strong; PO-d moderate; PO-e moderate to strong.

Evidence: design brief, simulation file, hardware validation, report, design review rubric.

CO: Develop, integrate, test, and document a microcontroller-based monitoring or control system that meets stated functional, safety, and performance requirements.

Likely map: PO-c strong; PO-e strong; PO-j moderate; PO-i moderate if team evidence exists; PO-k weak to moderate if planning and budgeting are assessed.

Evidence: proposal, Gantt chart, demo rubric, peer evaluation, technical report, presentation.

CO: Investigate a focused EEE problem through literature review, simulation and/or experiment, data interpretation, and evidence-based conclusions communicated in a thesis and oral defense.

Likely map: PO-b moderate; PO-d strong; PO-j moderate to strong; PO-l moderate to strong.

Evidence: proposal, literature matrix, methodology, data analysis, thesis chapters, defense rubric.

Interactive tools

These tools run fully offline in the browser. They produce first-pass suggestions; final academic judgment remains with the course instructor and OBE committee.

A. CO Builder Tool

B. Bloom Verb Finder

C. CO Quality Checker

D. CO–PO Mapping Assistant

Assessment methods used in this CO
Select POs to evaluate

E. Mapping Matrix Generator

PO columns to include

F. Example Library Filter

G. Checklist Tool

0 of 0 items completed.

Checklist, templates, FAQ, and references

Copyable templates

Frequently asked questions

How many COs should a course have?

The reviewed BAETE materials do not prescribe a fixed number. Recommended practice is to keep the set limited, distinct, and assessable rather than long and repetitive.

Can one CO map to many POs?

Yes, but it should be uncommon. Most COs make a major contribution to only a small number of POs. Too many mappings usually indicate vague CO wording or evidence inflation.

Can a theory course map to design?

Yes, but only if there is a genuine design task with requirements, constraints, trade-offs, or open-ended solution development. Closed-form analytical problems alone are usually not enough for a strong design mapping.

Can a lab course map to communication?

Yes, if reports, oral presentation, posters, or technical documentation are directly assessed. If reporting is ungraded or perfunctory, the mapping should be weak or absent.

Can PO-g or PO-h be mapped because sustainability or ethics was mentioned once?

No. Sustainability and ethics mappings should be supported by explicit teaching-learning activity and assessed evidence such as a design reflection, case analysis, report criterion, or viva question.

Does investigation always require students to design the experiment from scratch?

No. Investigation can be demonstrated through appropriate experimentation, data interpretation, literature-backed inquiry, or realistic evidence synthesis. The key requirement is direct evidence of inquiry and interpretation.

References and source notes

This page separates formal accreditation-sensitive statements from recommended departmental practice. The mapping assistant provides conservative guidance; departments should still apply the officially adopted program template and internal OBE committee decisions.

Disclaimer

Guidance Notice

This page provides general academic guidance on Outcome Based Education (OBE), Course Outcome (CO) formulation, Bloom’s taxonomy application, and CO–PO mapping practices for Electrical and Electronic Engineering courses. It is intended as a support resource for faculty members, students, and accreditation preparation activities.

The content does not constitute an official rule, regulation, accreditation decision, or binding departmental, university, or regulatory policy. It should not be interpreted as a substitute for formally approved BUET curriculum documents, departmental guidelines, course-file templates, or accreditation requirements issued by relevant authorities.

Faculty members are expected to exercise professional academic judgment and refer to authoritative sources—including BUET academic policies, departmental OBE guidelines, BAETE accreditation manuals, Washington Accord graduate attributes, and program-specific criteria—when preparing Course Outcomes, CO–PO mappings, assessment strategies, and attainment reports.

This resource has been prepared using a combination of established academic practices and AI-assisted synthesis of publicly available accreditation and engineering education materials. While reasonable care has been taken to ensure accuracy and relevance, the content may contain simplifications, interpretive differences, or outdated elements.

Users are responsible for independently verifying all information before official or accreditation use. In the event of any inconsistency between this page and official BUET, BAETE, or accreditation documents, the official documents shall prevail. The Department of EEE, BUET reserves the right to revise or update this content without prior notice.

Bloom’s Taxonomy Curriculum

Back to Top