Activity 1.2.0 — The Circuit Design Process

0 of 0

Circuit design is not about guessing or wiring components at random. It follows the Engineering Design Process — a structured eight-step method to solve electrical problems efficiently, safely, and repeatably.

Before touching any components or breadboards on the bench, engineers start by defining requirements and simulating their ideas virtually. Below, explore the full design flow and complete your laboratory safety pre-check.

What is the first step in the circuit design process?

Define the Problem or Need. Every project must begin with a clear explanation of what is being built, the constraints (e.g. dimensions, power limits), and the target inputs and outputs.

Electronic systems are classified into two broad design architectures: Analog and Digital. Understanding their fundamental differences shapes how we process signals.

Analog Design

Deals with continuously varying voltage and current signals.
Signals can take any infinite mathematical value within a physical range.
Highly sensitive to environmental noise, temperature shifts, and component aging.
Typical Examples: Audio amplifiers, radio transmitters, power supplies.

Digital Design

Deals with discrete binary states (HIGH / 1 and LOW / 0).
Inputs are thresholded into clean binary logic boundaries.
Immune to low levels of physical noise; highly predictable and easily stored.
Typical Examples: Microcontrollers, memory chips, processors.

Project Spotlight: The Random Number Generator (RNG)

Throughout this course, you will construct a Random Number Generator (RNG) board that integrates both analog and digital domains:

Analog Subsystem

Generates physical entropy (thermal noise) which is amplified and shaped. Because the signal varies continuously, it requires high gain and noise filtering.

Digital Subsystem

Receives the conditioned analog signal, converts it to logical high/low clock pulses, counts the pulses, and displays the final digits on a 7-segment display.

Design Integration: Modern systems rarely use pure analog or pure digital designs. Almost every complex system involves sensors (analog input) translating physical events to binary values (digital processing) for calculation.

Designers use specialized software to implement the design flow. Multisim handles virtual schematic entry and simulation, while Design Mode Software (DMS) directs physical assembly and testing.

Multisim Workflow (Simulation)

Open software and create a new project canvas.
Place theoretical component symbols from libraries.
Wire pins together to form electrical connection networks (nets).
Place virtual measurement instruments (scopes, DMMs).
Run the simulator engine (SPICE) to test behavior.
Adjust component values to fix output errors.
Export the schematic database.

DMS Workflow (Breadboarding)

Import the verified schematic export from Multisim.
Select your target hardware platform (e.g. myDigital board).
Position physical ICs and components onto coordinates.
Make physical wire connections to matching terminals.
Perform a power check (continuity check) with DMM.
Apply supply voltage and test circuit states.
Sync with physical hardware probes to collect telemetry.

Why Documentation is Crucial

Documentation is not a tedious chore; it is an essential part of engineering. Without logs and annotations, other team members (or you, weeks later) cannot replicate, verify, or debug your circuits.

Reason	Explanation
Communication	Allows teachers, students, and engineers to verify and understand the circuit's purpose.
Replication	Enables others to construct the exact same circuit with matching performance.
Troubleshooting	Saves time during debugging by documenting target voltages at specific test points.
Engineering Record	Serves as a historical log of design iterations, failures, and improvements.

What is the difference between Multisim and DMS?

Multisim is used for drawing schematics and running mathematical simulations in a purely virtual environment. DMS (Design Mode Software) is used to interface with real hardware, guide physical component placement on breadboards, and collect physical telemetry.

Why should you always simulate before building?

Simulation catches design errors (such as incorrect component values or short circuits) early in a risk-free environment. This prevents physical component destruction (e.g. burning out ICs or blowing diodes) and saves hours of manual debugging time.