An EEE methodology chapter that just says “MATLAB Simulink was used to simulate the system” is not a methodology — it is a caption. Examiners in India, the UK, Australia, and the US all ask the same question when they read it: what solver, what step size, what convergence criterion, and how do you know the model is correct? Here is exactly what to write for every major EEE project type.
Fig. 1 — Electrical Engineering Methodology 2026: MATLAB Simulink workflow, ETAP power system analysis, control system development, IoT architecture, validation strategy, and IEEE/IEC-aligned research methodology planning.
An electrical engineering methodology chapter must document five things precisely: the simulation platform and version with solver type and step size, all model parameters with sources, the hardware instrument specifications and calibration status, the testing procedure with operating conditions, and the validation method against analytical results or benchmarks. The most commonly missing elements are the Simulink solver type and step size in simulation projects, and the instrument model with measurement range in hardware projects. Without these, your results cannot be reproduced — and reproducibility is what every examiner, in every country, actually tests for.
- What Makes EEE Methodology Different from Other Branches
- Five EEE Project Types and What Each Methodology Needs
- MATLAB Simulink Methodology — Simulation, Control and Signal Processing
- Power System Methodology — ETAP, PSCAD and Load Flow Studies
- Control System Methodology — PID, Fuzzy Logic and State Space
- Hardware and Circuit Testing Methodology — Lab Rigs and Prototypes
- Renewable Energy and IoT Methodology
- Standards Reference — IEEE and IS Codes for India
- Before and After — Weak vs Strong Paragraphs
- Pre-Submission Checklist
- Frequently Asked Questions
Electrical engineering projects span more software tools than any other branch. A student in Chennai might be simulating a grid-connected solar inverter in MATLAB Simulink while a student in Manchester is modelling fault current in a 33 kV distribution network using ETAP, and a student in Toronto is building a real-time motor speed controller on STM32. All three are final year EEE projects. All three need a methodology chapter. And all three fail in exactly the same way — they describe what the software did, not how it was configured or why the results can be trusted.
The general methodology guide on this site covers the six-section structure that works across all engineering branches. This guide goes deeper — into the specific solver settings, tool versions, parameter sources, standards codes, and hardware specifications that electrical engineering examiners actually check. If your project involves MATLAB, ETAP, PSCAD, Proteus, LTspice, Arduino, or any combination of simulation and hardware, this is where your methodology chapter gets built.
Section 01What Makes EEE Methodology Different from Other Branches
Two things make electrical engineering methodology uniquely challenging. First, EEE projects almost always have both a simulation component and a hardware component — and students routinely document the simulation well but treat the hardware as an afterthought, or vice versa. Both halves need equal rigour. An examiner who sees a well-documented Simulink model paired with “the circuit was built on a breadboard and tested” will reduce your methodology score significantly — regardless of how good your results are.
Second, EEE results are highly sensitive to operating conditions that look minor but are not. A power factor correction circuit tested at 230 V, 50 Hz gives different THD readings than one tested at 220 V. A PID controller tuned at no-load behaves differently under full load. A solar panel characterisation at 800 W/m² irradiance is not the same as one at 1000 W/m² (STC). Every operating condition that could affect your output must appear in the methodology. No exceptions.
The single question your methodology must answer is: could another engineer reproduce your results using only what you have written? For simulation: same software, same solver, same model parameters, same operating point. For hardware: same components with same ratings, same instruments with same ranges, same test conditions. If the answer is no at any point, that section of your methodology is incomplete.
Section 02Five EEE Project Types and What Each Methodology Needs
| Project Type | Examples | Mandatory Elements | Most Often Missing |
|---|---|---|---|
| Simulation Only | Load flow, fault analysis, inverter modelling, motor drive simulation | Software version, solver type and step size, all model parameters with sources, operating point, convergence criterion, validation | Solver type + step size + validation method |
| Hardware Only | Power converter prototype, motor controller, smart meter, filter circuit | Component specs (make, model, rating), instrument model and range, schematic with values, operating conditions (V, Hz, load), calibration, test run count | Instrument model and range + calibration date |
| Simulation + Hardware (Hybrid) | Simulink-designed controller on Arduino/STM32, HIL testing, converter validated by prototype | Both sets above + HIL setup, sampling frequency, ADC/DAC resolution, validation acceptance criterion (%) | ADC resolution and sampling frequency |
| Power System Analysis | Load flow, short circuit, protection coordination, harmonic study, stability | Network data (bus, line parameters, transformer ratings), load model type, base MVA and kV, IEEE/IS standard cited, study cases defined | Base MVA/kV + load model type clearly stated |
| Renewable Energy / IoT | Solar PV design, wind modelling, IoT energy monitor, EV charging analysis | Irradiance/wind data source and year, PV/wind model parameters, communication protocol, MCU specs, sensor accuracy, location and climate zone | Irradiance/wind data source + sensor accuracy |
Section 03MATLAB Simulink Methodology — Simulation, Control and Signal Processing
MATLAB is used in more EEE final year projects globally than any other tool — and it is also the most inconsistently documented. Most students write the software name and nothing else. What examiners actually need is the solver, the step size, the model parameters, and how results were validated. The solver is the most critical item: different solvers produce different results for the same model, especially in power electronics.
| Element | What to Document | Example |
|---|---|---|
| Software version | Full MATLAB version + Simulink + toolboxes | MATLAB R2024a, Simulink, Simscape Electrical (Power Systems), Control System Toolbox |
| Solver type | Continuous or discrete, solver name, step size or sample time | ode23tb (stiff/TR-BDF2), max step size: 1×10⁻∴ s. Chosen due to MOSFET/diode switching discontinuities. |
| Simulation time | Total duration and rationale | 0.5 s (25 cycles at 50 Hz) to capture steady-state and transient following load step at t = 0.2 s |
| Model parameters | All component values with units and sources | Source: 11 kV (L-L), 50 Hz, Zs = 0.1 + j0.5 Ω; transformer: 11/0.415 kV, 500 kVA, Dyn11, X = 4% |
| Operating point | Load condition, power factor, switching frequency | Full load: 400 kW, 0.85 pf lagging; switching frequency: 10 kHz (IGBT model) |
| Validation | How simulation output was verified | Output voltage ripple (2.3%) and efficiency (94.1%) compared against CCM theoretical values (2.1%, 95.2%) — deviation within 3%, accepted threshold 5% |
| Max Step Size | Output Voltage THD (%) | Simulation Time (s) | Change from Previous |
|---|---|---|---|
| 1×10⁻⁴ s | 4.82 | 12.4 | — |
| 1×10⁻⁵ s | 4.31 | 48.7 | 10.6% |
| 1×10⁻⁶ s | 4.28 | 312.1 | 0.7% ✓ Selected |
Section 04Power System Methodology — ETAP, PSCAD and Load Flow Studies
Power system projects have one documentation requirement no other EEE type shares: the network model data table. Every bus, every line, every transformer in your model must be listed with its parameters and data source. Without this, your results are unverifiable.
| Element | What to Document | India-Specific Note |
|---|---|---|
| Software and version | ETAP 20.x / PSCAD v5.x / DIgSILENT PowerFactory 2024 | ETAP most common in Indian power sector; PSCAD for EMT/transient studies |
| System base | Base MVA, base kV at each voltage level | Indian grid: 100 MVA base; voltage levels: 765/400/220/132/66/33/11/0.415 kV |
| Network data source | Bus data, line parameters, transformer ratings — real utility data, IEEE test system, or stated assumptions | IEEE 33-bus test system widely used when real DISCOM data unavailable — cite clearly |
| Load model type | Constant power (PQ), constant current (PI), constant impedance (Z), or ZIP composite | CERC planning studies use constant power model — cite if applicable |
| Study cases | All cases: base, peak, light load, N-1 contingency — defined explicitly | Indian summer peak (May-June) vs winter — seasonal variation significant |
| Convergence criterion | Method (NR/GS), tolerance (pu), max iterations | Standard: Newton-Raphson, tolerance 1×10⁻⁴ pu, max 50 iterations |
| Voltage limits | Per-unit voltage limits and standard cited | CEA Regulations 2010: ±5% of nominal (India) / IEEE Std 1250 (global) |
For Indian power system projects, the two most important regulatory references are CEA Technical Standards for grid connection and CERC Grid Code 2023 for generation interconnection. For distribution-level (33 kV and below), cite the relevant State Electricity Regulatory Commission (SERC) standards. Globally, cite IEEE Std 399 (Brown Book) or IEEE Std 3002 series for load flow and short circuit studies.
Section 05Control System Methodology — PID, Fuzzy Logic and State Space
Control system projects have a specific documentation challenge: the controller design process itself must be documented, not just the final controller parameters. Seeing “Kp = 2.5, Ki = 0.8, Kd = 0.05 were used” immediately makes an examiner ask: how were these values determined? The tuning method is part of the methodology.
| Controller Type | Mandatory Documentation | Validation Method |
|---|---|---|
| PID Controller | Plant transfer function, tuning method (Ziegler-Nichols / MATLAB PID Tuner / Cohen-Coon / manual), final Kp, Ki, Kd with units, anti-windup strategy | Step response: rise time, settling time, overshoot, steady-state error vs design spec |
| Fuzzy Logic Controller | Input/output variables, membership function type and ranges, rule base (number of rules), defuzzification method (centroid/bisector) | FLC vs PID step response comparison; ITAE or ISE performance index for both |
| State Space / LQR | System matrices A, B, C, D with derivation reference, desired pole locations and rationale, Q and R weighting matrices with selection basis | Eigenvalue analysis for closed-loop stability; step response vs open-loop |
| MPC | Prediction horizon N, control horizon M, cost function weights, input/state constraints, solver used (quadprog, OSQP) | Constraint satisfaction verified; comparison against PID baseline |
| Neural Network / AI | Architecture (layers, neurons, activation functions), training algorithm, dataset split (train/val/test), epochs, loss function | RMSE and MAE on test set; comparison against conventional controller |
Section 06Hardware and Circuit Testing Methodology — Lab Rigs and Prototypes
Hardware EEE projects need the most detailed equipment documentation of any EEE project type. Every instrument introduces measurement uncertainty. Your methodology must show you chose instruments appropriate for the quantities measured, that they were calibrated, and that you recorded enough readings to establish repeatability.
| Instrument | Make / Model | Range Used | Accuracy | Calibration |
|---|---|---|---|---|
| Digital Multimeter | Fluke 87V / Mastech MS8268 | 0–750 V AC, 0–10 A | ±0.5% + 1 digit | Factory calibrated; annual recalibration |
| Oscilloscope | Rigol DS1054Z (100 MHz) | 20 V/div, 1 ms/div | Vertical ±3%; time base ±100 ppm | Self-calibration at startup; probe compensation verified |
| Power Analyser | Yokogawa WT310E / Hioki PW3335 | 0–300 V, 0–5 A | ±0.1% of reading | NABL-accredited (India) / NIST-traceable (global) |
| Function Generator | Rigol DG1022Z | 0–25 MHz, 0–10 Vpp | Frequency ±20 ppm; amplitude ±2% | Factory calibrated |
| Current Probe / CT | Fluke i200s / LEM HAL 50-S | 0–200 A AC | ±1% of reading, 1 Hz–50 kHz | Factory calibrated; zero-offset verified before each test |
In Indian university labs, instruments calibrated by NABL (National Accreditation Board for Testing and Calibration Laboratories) accredited facilities carry the highest credibility in project reports. If your lab instruments have NABL calibration certificates, cite them — “calibrated by NABL-accredited facility, certificate no. XX, valid until MM/YYYY.” Globally, the equivalents are NIST-traceable (USA), UKAS (UK), or DAkkS (Germany).
Section 07Renewable Energy and IoT Methodology
Solar PV, wind energy, EV charging, IoT monitoring — these projects combine simulation tools with real-world data sources and physical sensor hardware. Each combination has specific documentation requirements that most students miss.
| Project Type | Data Source to Document | Key Parameters | Standard to Cite |
|---|---|---|---|
| Solar PV System | NASA POWER, NREL NSRDB, MNRE data (India), IMD solar radiation data | Peak irradiance (W/m²), tilt angle (°), ambient temperature (°C), module efficiency (%), system losses (%) | IEC 61853 (module performance); IS 16169 (India PV installation) |
| Wind Energy | NIWE (India), NREL Wind Toolkit (global), ERA5 reanalysis | Hub height (m), wind speed (m/s), cut-in/rated/cut-out speed, turbine power curve source | IEC 61400-1; IS 16169 for grid connection |
| EV Charging / Battery | Battery datasheet (cell chemistry, capacity Ah, C-rate) | SoC range (%), C-rate, temperature range, cycle count for degradation study | IEC 62196 (EV connector); IEEE 2030.1.1 (DC fast charging) |
| IoT Energy Monitoring | MCU and sensor datasheets, communication protocol specification | MCU: ESP32 (12-bit ADC, 240 MHz); sensor: ACS712 (sensitivity mV/A); protocol: MQTT (QoS level) | IEEE 2413 (IoT architecture); IS 16103 (energy meters, India) |
| Smart Grid / Demand Response | DISCOM hourly load data / POSOCO NLDC / OpenEI load profiles | Peak demand (MW), load factor, DR event definition, price signal type (RTP/TOU) | IEEE 2030 (smart grid); CEA Smart Metering Regulations 2022 (India) |
Section 08Standards Reference — IEEE and IS Codes for India
Citing the right standard transforms a number into an engineering conclusion. A THD result of 8% means nothing without knowing which standard defines the limit. IEEE 519-2022 sets 5% THD at the point of common coupling for systems below 1 kV. IS 13234 is the Indian equivalent. Those two citations in one sentence make your result meaningful.
| Application | Indian Standard | Global Equivalent | Key Limit / Use |
|---|---|---|---|
| Power quality — harmonics | IS 13234:1992 | IEEE 519-2022 | THD limit at PCC: 5% (below 1 kV) |
| Power quality — voltage | CEA Regulations 2010 | IEEE Std 1250-2018 | Voltage tolerance: ±5% of nominal |
| Motor testing (efficiency) | IS 12615:2011 | IEEE 112-2017 (Method B) | IE3/IE4 efficiency levels; input-output method |
| Transformer testing | IS 2026:2011 | IEC 60076-1:2011 | No-load loss, load loss, impedance voltage |
| Protection relay | IS 3231:1965 | IEEE C37.112-2018 | IDMT curve constants (SI, VI, EI) |
| Solar PV system | IS 16169:2014 | IEC 61853 / IEC 61727 | Grid connection requirements; module performance |
| Battery / energy storage | IS 16270:2014 | IEC 62619:2022 | Safety requirements for Li-ion cells |
| Smart metering | CEA Smart Metering Regs 2022 | IEEE 2413-2019 (IoT) | Communication protocols, energy meter accuracy class |
| EV charging | BIS IS 17017:2018 | IEC 62196 / IEEE 2030.1.1 | Connector types, charging modes, DC fast charging |
| EMC / Emissions | IS CISPR 11 | IEC CISPR 11:2015 | Conducted and radiated emission limits |
Section 09Before and After — Weak vs Strong Paragraphs
Example 1 — MATLAB Simulink (Power Electronics)
❌ Weak — What Most Students Write
MATLAB Simulink software was used to simulate the boost converter. The circuit parameters were entered and the simulation was run. The output voltage and efficiency were recorded.
✔ Strong — What Examiners Expect
A DC-DC boost converter was modelled and simulated in MATLAB R2024a Simulink with the Simscape Electrical toolbox. The continuous-time solver ode23tb (stiff/TR-BDF2) was selected due to the switching discontinuities introduced by the MOSFET and diode models; the maximum step size was set to 1×10⁻⁶ s based on a step-size sensitivity study (Table 3). Circuit parameters: input voltage Vᵢₙ = 24 V DC, duty cycle D = 0.6 (designed for Vᴾᵤᵗ = 60 V), switching frequency 20 kHz, L = 470 μH (ESR = 0.2 Ω), C = 470 μF (ESR = 0.05 Ω), Rₗ = 72 Ω. Component values were derived analytically using CCM design equations and verified against manufacturer datasheets (Vishay IRLB3034 MOSFET; Vishay VS-30CPQ150 Schottky diode). Simulation duration: 50 ms (1,000 switching cycles) for full steady-state convergence. Output voltage ripple and efficiency were compared against theoretical CCM calculations — deviations of 1.8% and 2.3% were within the accepted ±5% threshold.
Example 2 — Power System (Load Flow in ETAP)
❌ Weak
Load flow analysis was performed using ETAP software. The bus data and line parameters were entered. Newton-Raphson method was used to solve the load flow.
✔ Strong
Load flow analysis of the 33 kV radial distribution network was performed in ETAP 20.6 using the Newton-Raphson method, convergence tolerance 1×10⁻⁴ pu, maximum 100 iterations. The network was modelled using the IEEE 33-bus test system (Baran and Wu, 1989) adapted for Indian 33/11 kV voltage levels. System base: 100 MVA, 33 kV. Line parameters and transformer ratings (33/11 kV, Dyn11) were sourced from the IEEE 33-bus dataset. Loads were modelled as constant power (PQ) consistent with CERC planning study guidelines. Three study cases were defined: base case (peak load 3.72 MW, 2.30 MVAR), 30% load reduction (off-peak), and N-1 contingency (loss of Line 2-3). Voltage limits of 0.95–1.05 pu were applied per CEA Regulations 2010 (India) and IEEE Std 1250-2018 (global).
Example 3 — IoT Hardware (Energy Monitoring System)
❌ Weak
An IoT-based energy monitoring system was developed using Arduino. Current and voltage sensors were used to measure power. Data was sent to a cloud server and displayed on a dashboard.
✔ Strong
A single-phase IoT energy monitoring system was developed using an ESP32 microcontroller (Xtensa LX6 dual-core 240 MHz, 12-bit ADC, 520 KB SRAM). Voltage was measured using a ZMPT101B AC voltage sensor (0–250 V AC, sensitivity 1000 mV/V, linearity ±0.2%); current using an ACS712-30A Hall-effect sensor (range ±30 A, sensitivity 66 mV/A). Both sampled at 1 kHz — 20 samples per 50 Hz cycle, resolving up to the 10th harmonic. Real and reactive power were computed using the instantaneous power method over a 10-cycle averaging window. Data was transmitted via Wi-Fi using MQTT (broker: HiveMQ, QoS level 1). System accuracy was validated against a calibrated Hioki PW3335 power analyser at load levels of 100 W, 500 W, and 1000 W; MAPE of 1.8% for real power and 2.4% for reactive power was recorded.
Section 10Pre-Submission Checklist
| # | Check | Simulation | Hardware | Power System | IoT/RE |
|---|---|---|---|---|---|
| 1 | Software name, version, toolboxes documented | ✓ | — | ✓ | ✓ |
| 2 | Solver type and step size stated | ✓ | — | ✓ | ✓ |
| 3 | Step size sensitivity / convergence study included | ✓ | — | ✓ | — |
| 4 | All model parameters with values, units, and sources | ✓ | ✓ | ✓ | ✓ |
| 5 | Operating conditions fully stated (V, Hz, load, pf) | ✓ | ✓ | ✓ | ✓ |
| 6 | Instrument make, model, range, calibration documented | — | ✓ | — | ✓ |
| 7 | IEEE / IS standard cited for all performance limits | ✓ | ✓ | ✓ | ✓ |
| 8 | Controller tuning method documented (Kp, Ki, Kd source) | ✓ | ✓ | — | — |
| 9 | Validation method stated with % deviation acceptance | ✓ | ✓ | ✓ | ✓ |
| 10 | Data source cited for irradiance / wind / load profiles | — | — | — | ✓ |
| 11 | Number of test runs per condition stated (min. 3) | — | ✓ | — | ✓ |
| 12 | Base MVA and kV clearly stated (power system) | — | — | ✓ | — |
| 13 | Entire chapter in past tense and passive voice | ✓ | ✓ | ✓ | ✓ |
Section 11Frequently Asked Questions
For BE/BTech: 1,200–1,800 words. For MTech/MSc with simulation and hardware validation: 2,500–3,500 words including convergence analysis, controller tuning, and uncertainty quantification. Under 900 words almost always means the simulation setup or hardware specifications are underdocumented.
Use ode23tb or ode15s for circuits with switching components such as inverters, converters, and choppers — not ode45. ode45 is designed for smooth systems and handles switching discontinuities poorly. State your solver choice and justify it with one sentence in your methodology.
For power quality: IEEE 519-2022 (IS 13234 in India). For voltage limits: IEEE 1250 (CEA Regulations 2010 in India). For motor efficiency: IEEE 112. For smart grid and IoT: IEEE 2030 series. For EV charging: IEC 62196 and IEEE 2030.1.1. See Table 8 for the complete reference list.
Yes — simulation-only EEE projects are fully valid. The methodology must then be especially rigorous on solver settings, model parameter sources, convergence verification, and validation against analytical calculations or published IEEE test system benchmarks.
In MATLAB Simulink: not documenting solver type and step size — results cannot be reproduced without this. In hardware projects: not stating the instrument model and measurement range. Both take five minutes to add and are the first things experienced EEE examiners check.
We publish in-depth engineering and research articles for students and professionals across global engineering programmes — from undergraduate to doctoral level.
- Methodology Chapter for Engineering Projects — Complete Guide for All Branches (2026)
- Mechanical Engineering Methodology Chapter 2026 — FEA, Material Testing, Thermal Studies
- Electrical Engineering Final Year Project Ideas 2026 — 50+ Topics
- 50 Most Common Engineering Project Viva Questions with Model Answers
- How to Write Results and Discussion for Engineering Projects 2026
- How to Write a Literature Review for Engineering Projects — All Branches
- The Complete Guide to Engineering Project Viva 2026