Introduction to Electrical Engineering and Computer Science I¶

Course Overview¶

• Institution: MIT
• Course code: 6.01SC
• Track: Introduction to Electrical Engineering
• Tier: S
• Role: Mainline
• Level: Not standardized by provider (use prerequisites)
• Last reviewed: 2026-07-28

MIT's Introduction to Electrical Engineering and Computer Science I provides a cross-layer EE introduction through videos, notes, practice, labs, exams, and code, although its robot platform is dated.

Why choose this course

Mainline course. A particularly complete and well-structured option for this track. Review note: S content / A reproducibility

Before you start

• Recommended foundation: Engineering Mathematics
• Recommended foundation: Programming and Engineering Computing

Verifiable learning outcomes

• Explain the core models in Introduction to Electrical Engineering, including their assumptions and limits
• Solve representative derivations and problems, checking units, limiting cases, or numerical results
• Complete a reproducible experiment or implementation with raw data, parameters, versions, and verification

Workload and pacing

13 weeks at 11 hours/week. This maintainer planning estimate is derived from course role and the density of public practice and labs; it is not a provider workload promise. Pilot two weeks while logging instruction, practice, lab, and review time, then adjust the remaining plan when actual effort differs by more than 25%.

Safety level

Low energy. Keep work isolated, current-limited, and low energy; verify ratings, grounding, short-circuit risk, and emergency shutdown before power-up.

Course Resources¶

Software, hardware, and cost

Software

• Maintainer-suggested open-source/free verification path: Qucs-S, ngspice, KiCad, Python 3, and Jupyter
• The resource inventory lists public code coverage; pin interpreter, dependencies, toolchain, datasets, and PDK versions where applicable

Hardware

• The resource inventory lists lab coverage; prefer borrowing or sharing the following equipment: a current-limited low-voltage supply, breadboard, digital multimeter, and any introductory board or components explicitly specified by the course. Verify ratings, authorization, and safety conditions only after the provider lab manual explicitly calls for them

Cost note

The suggested software stack is available open source or free; this is not a provider requirement or bill of materials. The actual boards, components, fabrication, and instruments—and their costs—depend on the provider lab manual, region, and local availability; prefer simulation, borrowing, or sharing before purchase.

Public resource coverage

Resources and access

“Listed by official page” means the link was discovered on a successfully fetched official source on the verification date; it does not guarantee that every region or account can open the target directly. Access does not grant redistribution rights. Re-check the provider page, target link, and third-party notices before downloading, adapting, or publishing material.

Practice and Verification¶

Practice loop

Introduction to Electrical Engineering and Computer Science I · MIT 6.01SC: Cross-Domain Sensing-Chain Digital Prototype

This is a maintainer-suggested self-study project for Introduction to Electrical Engineering and Computer Science I · MIT 6.01SC, not an official course assignment. Design a complete low-energy chain for Introduction to Electrical Engineering, from physical quantity and sensor through circuitry and sampling to software display, validating interface budgets in simulation with optional current-limited hardware.

Origin: Maintainer-suggested project

Deliverables

• Requirements, block diagram, interface voltage, bandwidth and sample-rate budgets, and a risk register
• An executable end-to-end simulation and optional current-limited prototype below 5 V with source files
• Raw input-to-output data, timestamps, and error records for at least 30 cases
• A design report and two-minute demonstration explaining cross-domain tradeoffs and one corrected failure

Verification

• Keep end-to-end full-scale error below 5% in the nominal range or predeclare a stricter course-aligned threshold
• Produce distinguishable behavior for zero, full-scale, out-of-range, and disconnected inputs
• Cross-check gain, bandwidth, quantization step, and sampling margin independently
• Inject one interface mismatch or saturation fault and show that diagnostics isolate the responsible module

Reproducibility

• Commit requirements, diagrams, simulation, firmware and display sources, a BOM, and a README
• Pin tool versions, dependencies, parameters, and the optional firmware build environment
• Preserve raw measurement or simulation data, calibration files, and report-generation records

Safety boundary: Low energy — Limit any physical work to isolated, current-limited circuits below 5 V; verify ratings and wire only with power removed. No mains, human connection, or moving actuators.

Risks, gaps, and boundaries

Designed for independent study, but the mobile-robot hardware and software stack are dated.

Completion evidence

• Weekly learning log with time, questions, corrected errors, decisions, next steps, and links to that week's reproducible artifacts
• Design-review package with requirements and constraints, trade-offs, editable sources, applicable ERC/DRC/timing/stability checks, exports, and a reproduction test
• Simulation package with model or netlist, inputs, solver and version, parameter-sweep script, benchmark comparison, expected results, and one rerun command
• Code repository with pinned dependencies and toolchain, a minimal run command, tests or waveform/benchmark checks, expected output, and license notes
• Experiment package with schematic/setup, calibration record, raw data, uncertainty, safety checks, failed runs, and steps to rebuild plots from raw data