DC Electronic Circuits — Design & Development Study Notes

From design brief to circuit specification

Design and development in DC electronic circuits starts long before you draw a schematic. The core skill is turning an idea (often vague) into a clear, testable specification that a circuit can be designed against. If you skip this step, you usually end up “tuning by guesswork”—changing parts until it sort of works—rather than engineering a predictable outcome.

A design brief is the high-level statement of what you’re trying to achieve (for example: “Make a battery-powered night-light that turns on when it’s dark.”). A design specification translates that brief into measurable requirements and constraints. Good specifications are written so that you can later prove whether the design succeeded.

What a good specification looks like

A strong specification includes:

• Function: what the circuit must do (e.g., “LED turns on when ambient light is below threshold”).
• Performance targets: numerical values and tolerances where possible (e.g., “LED current $I_{LED} = 10\,mA \pm 2\,mA$”).
• Power constraints: supply type and acceptable current draw (e.g., “Powered by $9\,V$ battery, quiescent current under $200\,\mu A$”).
• Environment: temperature range, humidity, handling, vibration.
• Safety and reliability: protection against reverse polarity, short circuits, overheating.
• Cost and availability: maximum bill of materials (BOM) cost, preferred common components.
• Build constraints: breadboard/stripboard/PCB, maximum size, connector types.

A common misconception is that specifications only matter in big projects. In reality, even small DC circuits become dramatically easier when you decide (early) things like supply voltage, maximum current, and what counts as “good enough”.

Turning a brief into engineering numbers

Often you must convert human requirements into electrical parameters:

• “Bright enough” becomes LED current and luminous intensity (from the LED datasheet).
• “Runs for a week” becomes average supply current, then battery capacity.
• “Detects a button press reliably” becomes logic thresholds, debounce strategy, and pull-up/pull-down values.

Worked example: runtime requirement to current budget

A device must run for $20\,hours$ from a battery rated at $500\,mAh$. What average current is allowed?

Use the capacity relationship (conceptually: current (\times) time):

$I_{avg} = \frac{Q}{t}$

Where $Q$ is capacity in $mAh$ and $t$ in $h$.

$I_{avg} = \frac{500\,mAh}{20\,h} = 25\,mA$

So your whole circuit—LED, control, losses—should average about $25\,mA$ or less (and realistically lower, because battery ratings depend on discharge rate and cutoff voltage).

Exam Focus

• Typical question patterns:
  • Convert a written brief into a list of measurable electrical requirements (voltage, current, power).
  • Identify constraints (battery type, max current, cost) and explain how they affect design choices.
  • Given a target runtime or brightness, calculate an allowable current or resistor value.
• Common mistakes:
  • Writing vague requirements (“low power”) instead of measurable ones (e.g., “$I_q < 200\,\mu A$”).
  • Forgetting that requirements interact (higher LED current improves brightness but reduces runtime).
  • Ignoring worst-case conditions (battery voltage sag, component tolerances).

Schematics, circuit conventions, and communicating a design

Design work must be communicable—to teachers/examiners, teammates, and your future self. That’s why schematics and conventions matter: they’re the language of electronics.

A schematic is an abstract drawing that shows electrical connections and component functions, not physical placement. In design-and-development tasks, schematics are typically assessed for clarity, correctness, and use of standard symbols.

Key schematic conventions

A clear schematic reduces mistakes during building and troubleshooting:

• Use reference designators: $R1, R2$ (resistors), $C1$ (capacitors), $D1$ (diode/LED), $Q1$ (transistor), $U1$ (IC).
• Label net names for important nodes: $VCC$, $GND$, $V_{OUT}$.
• Keep signal flow readable: inputs on the left/top, outputs on the right.
• Use ground symbols consistently. Many circuit errors are simply “not actually sharing ground.”
• Avoid ambiguous crossings. Use junction dots for connections.

Symbols vs real components

A common beginner error is to think the schematic symbol “is” the component. In reality, a symbol represents the component’s electrical behavior, while the real part has:

• a package and pinout that can be wired incorrectly,
• tolerances (e.g., $\pm 5\%$ resistors),
• limits (max current, max power dissipation).

Notation you’ll see in DC circuit design

Worked example: labeling to prevent wiring mistakes

Suppose you design a transistor LED driver. If you label the transistor pins clearly (collector, base, emitter for BJT; drain, gate, source for MOSFET) and label the node at the LED as $V_{LED}$, you make it much easier to:

• verify expected voltages during testing,
• explain operation in written answers,
• spot a swapped pin during assembly.

Exam Focus

• Typical question patterns:
  • Interpret a schematic and explain what each block does.
  • Redraw a circuit using correct symbols and labels.
  • Identify missing labels/grounds or ambiguous connections.
• Common mistakes:
  • Confusing “voltage at a node” with “voltage across a component.”
  • Omitting a shared reference ground between subcircuits.
  • Mislabeling transistor terminals and then reasoning from the wrong model.

Using datasheets and selecting components (design choices with consequences)

Design-and-development is largely the skill of choosing components that meet requirements with margin. A datasheet is the manufacturer’s contract: it tells you how the part behaves and what it can safely tolerate.

Why datasheets matter in DC circuits

DC circuits often look simple, but many failures come from ignoring practical limits:

• A resistor overheats because its power rating is too low.
• An LED burns out because current isn’t limited.
• A transistor doesn’t switch fully because base/gate drive is insufficient.
• A regulator overheats because of excessive power dissipation.

Resistors: not just “a value”

A resistor is defined by more than $R$:

• Resistance $R$ in $\Omega$
• Tolerance (e.g., $\pm 1\%$, $\pm 5\%$)
• Power rating (e.g., $0.25\,W$)

Power in a resistor:

$P_R = V_R \times I_R$

Also commonly:

$P_R = I_R^2 \times R$

$P_R = \frac{V_R^2}{R}$

Where $V_R$ is voltage across the resistor and $I_R$ is current through it.

Worked example: check resistor power rating

A resistor $R = 330\,\Omega$ limits LED current from a $5\,V$ supply. If LED forward voltage is about $2\,V$, the resistor sees:

$V_R = 5\,V - 2\,V = 3\,V$

Current:

$I = \frac{3\,V}{330\,\Omega} \approx 9.09\,mA$

Resistor power:

$P_R = V_R \times I = 3\,V \times 9.09\,mA \approx 27.3\,mW$

A $0.25\,W$ resistor is comfortably safe.

Capacitors in DC circuits

Even in “DC” systems, voltages change during switching, startup, and noise events. Capacitors are used for:

• Decoupling/bypass near IC power pins (stabilizes supply during fast current changes)
• Smoothing after rectifiers or in supply rails
• Timing (RC delays)

Key datasheet ideas:

• Capacitance $C$
• Voltage rating (must exceed worst-case voltage)
• For electrolytics: polarity matters; reverse voltage can damage them.

Diodes and LEDs

A diode is directional: it conducts strongly in forward bias and blocks (approximately) in reverse bias until breakdown.

For LEDs, two datasheet values are central:

• Forward voltage $V_F$ (depends on color and current)
• Forward current $I_F$ (recommended operating current)

A very common mistake is treating $V_F$ as fixed. In reality, it varies with current and temperature—so you design the resistor/current limit to control $I_F$.

Transistors (BJT and MOSFET) as design elements

Transistors are often used as switches in DC projects (driving motors, relays, high-power LEDs).

• A BJT is current-controlled (base current controls collector current).
• A MOSFET is voltage-controlled (gate voltage controls conduction; gate draws negligible DC current but needs correct voltage).

Key selection criteria:

• Maximum voltage (e.g., $V_{CE}$ for BJT, $V_{DS}$ for MOSFET)
• Maximum current
• Power dissipation and thermal limits
• For MOSFETs: whether it fully turns on at your available gate voltage (often called “logic-level” behavior)

Voltage regulators

Regulators provide stable voltage from a varying source (battery, adapter). A major practical issue is heat: linear regulators dissipate:

$P_{reg} = (V_{IN} - V_{OUT}) \times I_{OUT}$

If this is large, the regulator may overheat without a heatsink or airflow.

Worked example: regulator dissipation

You regulate $12\,V$ down to $5\,V$ at $200\,mA$ using a linear regulator.

$P_{reg} = (12\,V - 5\,V) \times 200\,mA = 7\,V \times 0.2\,A = 1.4\,W$

That is significant heat for a small package.

Exam Focus

• Typical question patterns:
  • Choose an appropriate resistor/capacitor/transistor for a stated requirement and justify with ratings.
  • Use datasheet-style values (max current, voltage rating) to check safety margins.
  • Calculate resistor power or regulator dissipation.
• Common mistakes:
  • Ignoring power ratings and thermal limits.
  • Treating LED forward voltage as a fixed “supply” and omitting current limiting.
  • Choosing a MOSFET that needs a higher gate voltage than the control circuit can provide.

Core DC design calculations: Ohm’s law, dividers, and bias networks

Most DC design calculations are built from a small set of ideas applied carefully. The difficulty is usually not the math—it’s picking the right model and knowing which approximations are valid.

Ohm’s law (and what it really means)

Ohm’s law relates voltage, current, and resistance for an ohmic component (like an ideal resistor):

$V = I \times R$

Where:

• $V$ is voltage across the resistor in $V$
• $I$ is current through it in $A$
• $R$ is resistance in $\Omega$

It matters because most design tasks involve setting currents (LEDs, transistor bases, pull-ups) using resistors.

A common misconception is applying Ohm’s law to non-ohmic devices (diodes, LEDs) as if they had a fixed resistance. For those, you usually approximate with a forward voltage and then use Ohm’s law for the resistor that sets current.

Voltage dividers (setting a node voltage)

A voltage divider uses two resistors in series to create a fraction of the input voltage at their junction.

If $R_1$ is the top resistor (from $V_{IN}$ to the node) and $R_2$ is the bottom resistor (from node to ground), then:

$V_{OUT} = V_{IN} \times \frac{R_2}{R_1 + R_2}$

This works well only if the divider is not heavily loaded. When you connect a load, it effectively changes $R_2$ (because the load is in parallel), shifting the output voltage.

Worked example: divider design

You need $V_{OUT} = 2\,V$ from $V_{IN} = 10\,V$ using $R_1$ and $R_2$.

You want:

$\frac{R_2}{R_1 + R_2} = \frac{2}{10} = 0.2$

So:

$R_2 = 0.2\,(R_1 + R_2)$

$0.8\,R_2 = 0.2\,R_1$

$R_1 = 4\,R_2$

Pick convenient values, e.g. $R_2 = 10\,k\Omega$ and $R_1 = 40\,k\Omega$.

Now check current wasted by divider:

$I_{div} = \frac{V_{IN}}{R_1 + R_2} = \frac{10\,V}{50\,k\Omega} = 0.2\,mA$

Whether $0.2\,mA$ is acceptable depends on your power budget.

Pull-up and pull-down resistors (making inputs behave)

A floating input can pick up noise and randomly read high or low. A pull-up resistor connects an input node to $VCC$ so it defaults high; a pull-down resistor connects to ground so it defaults low.

Design tradeoff:

• Smaller resistance gives stronger default but wastes more current when the switch closes.
• Larger resistance saves power but may be more noise-sensitive.

If a switch pulls an input to ground and you have a pull-up $R_P$ to $VCC$, then when pressed the current is:

$I = \frac{VCC}{R_P}$

Worked example: choose a pull-up for power

If $VCC = 5\,V$ and you choose $R_P = 10\,k\Omega$:

$I = \frac{5\,V}{10\,k\Omega} = 0.5\,mA$

If power is critical, $100\,k\Omega$ reduces that to $0.05\,mA$, but you must ensure the input is still stable.

Simple transistor bias (enough drive to switch)

When using a BJT as a switch, you want it saturated (fully on) so it drops little voltage and wastes little power. In many introductory designs, you estimate a base resistor so there is sufficient base current.

Conceptually:

• You choose a collector current $I_C$ (load current).
• You provide base current $I_B$ large enough that the transistor saturates.

Because transistor gain varies, a conservative approach is to overdrive the base relative to the minimum needed in active mode.

Exam Focus

• Typical question patterns:
  • Calculate resistor values for LED current limiting, pull-ups, or dividers.
  • Predict the effect of adding a load to a divider (loaded divider reasoning).
  • Explain why a pull-up is needed and estimate switch current.
• Common mistakes:
  • Forgetting that divider output changes under load.
  • Using Ohm’s law directly on a diode/LED without a current-limiting resistor.
  • Choosing pull-ups so low that they waste battery life unnecessarily.

Power supply and protection design in DC systems

Power design is where real-world constraints show up: internal resistance of batteries, startup surges, wiring errors, and noise from motors. A “working” circuit on a bench supply can fail in a portable device if you don’t design the power path properly.

Sources: batteries and adapters

A battery is not an ideal voltage source. Under load, its voltage can sag due to internal resistance and chemistry. This matters because:

• LED brightness may change with battery level.
• Microcontrollers (if present) may reset if voltage dips.
• Motors draw high startup current.

Decoupling and bulk capacitance

Two capacitor roles are commonly distinguished:

• Decoupling capacitor (often small, e.g., ceramic) placed close to IC power pins to handle fast current spikes.
• Bulk capacitor (often larger) stabilizes the supply rail against slower changes (e.g., motor switching).

The design idea is not “add any capacitor,” but “place appropriate capacitance where current pulses occur.” Placement matters because wiring has resistance and inductance.

Protection: reverse polarity and overcurrent

Practical DC designs often include protection against predictable mistakes:

• Reverse polarity: if the battery is inserted backwards, sensitive parts can be destroyed. A common remedy is a diode or a MOSFET-based protection circuit.
• Overcurrent/short circuit: include fuses, resettable fuses, or current limiting depending on scale.

Even if protection circuits aren’t complex in your course, you should be able to explain why they’re used and what failure they prevent.

Grounding as a design decision

“Ground” is the reference node, but in real builds the ground path has resistance. High currents (motors, LEDs) flowing through shared ground wiring can create voltage drops that upset sensitive parts.

A design practice is to separate high-current return paths from sensitive signal returns (often called “star grounding” conceptually), especially on stripboard or PCB.

Worked example: estimating supply drop in wiring

If a motor draws $1\,A$ and the ground return wire has resistance $0.2\,\Omega$, the ground lift is:

$V = I \times R = 1\,A \times 0.2\,\Omega = 0.2\,V$

That $0.2\,V$ error can be enough to shift thresholds in low-voltage logic or sensor circuits.

Exam Focus

• Typical question patterns:
  • Explain roles of decoupling vs bulk capacitors in a DC design.
  • Calculate heat in a linear regulator or voltage drop in wiring.
  • Propose simple protection for reverse polarity and justify it.
• Common mistakes:
  • Placing decoupling capacitors far from the IC/load.
  • Ignoring that motors and relays create supply dips and electrical noise.
  • Assuming “ground is ground” with no voltage differences along return wiring.

Designing common DC subcircuits (building blocks)

Complex systems become manageable when you recognize them as combinations of smaller blocks. Design-and-development questions often assess whether you can select and connect these blocks correctly, and predict how each block behaves.

Current limiting for LEDs

An LED needs controlled current. The most common approach is a series resistor.

If you have supply $V_S$, LED forward voltage $V_F$ at the desired current, and desired current $I$, then:

$R = \frac{V_S - V_F}{I}$

Worked example: LED resistor

You want $I = 15\,mA$ from a $9\,V$ battery for a red LED with $V_F \approx 2\,V$.

$R = \frac{9\,V - 2\,V}{15\,mA} = \frac{7\,V}{0.015\,A} \approx 466.7\,\Omega$

Choose a standard value like $470\,\Omega$.

Diode as protection (flyback for inductive loads)

Inductive loads like relays and motors resist changes in current. When switched off, they can generate a high voltage spike that damages transistors.

A flyback diode placed across the coil provides a safe path for the current when switching off, limiting the spike.

The key conceptual point: the diode is normally reverse-biased and does nothing during steady operation. It becomes forward-biased only when the coil voltage reverses during turn-off.

RC timing (delays and smoothing)

An RC network combines resistor and capacitor to create a time-dependent voltage. In design tasks, RC is used for:

• power-on reset delays,
• debounce filtering,
• simple low-pass smoothing.

Rather than memorizing shapes, focus on the qualitative behavior: the capacitor voltage cannot change instantly; the resistor limits how fast it charges/discharges.

Simple voltage reference with a Zener diode (where appropriate)

A Zener diode can maintain an approximately constant voltage in reverse breakdown, often used as a reference or clamp. However, it requires correct bias current via a resistor, and it dissipates power.

A common mistake is drawing a Zener “to get a voltage” without designing the series resistor and checking power.

Exam Focus

• Typical question patterns:
  • Design an LED indicator with correct resistor and power check.
  • Explain why a flyback diode is needed and where it goes.
  • Describe how an RC delay changes a signal and why it helps (debounce/noise filtering).
• Common mistakes:
  • Putting the flyback diode the wrong way around (it must be reverse-biased during normal operation).
  • Forgetting that component ratings (diode current, capacitor voltage) must exceed worst-case conditions.
  • Treating RC timing as “magic” rather than as controlled charge/discharge behavior.

Transistor switching design (making small signals control big loads)

A central design-and-development skill in DC electronics is using a small control signal (sensor, switch, logic output) to control a larger current load (motor, relay, lamp). Transistors provide this interface.

BJT as a low-side switch

A typical configuration is low-side switching:

• Load connects to $V_S$.
• Transistor connects the load to ground when on.

Why it matters: it’s simple and works well for many loads. The design job is ensuring the transistor is fully on and protected.

Key behaviors to understand:

• The base-emitter junction behaves somewhat like a diode. When on, $V_{BE}$ is around $0.7\,V$ for silicon BJTs (approximate, varies with current and temperature).
• The base resistor limits base current.

Worked example: base resistor sizing (conceptual)

A load needs $I_C = 200\,mA$. You drive the base from a $5\,V$ control signal through $R_B$. Assume $V_{BE} \approx 0.7\,V$ and choose a conservative base current $I_B = 10\,mA$.

Then:

$R_B = \frac{V_{IN} - V_{BE}}{I_B} = \frac{5\,V - 0.7\,V}{10\,mA} = \frac{4.3\,V}{0.01\,A} = 430\,\Omega$

Choose a nearby standard value (e.g., $470\,\Omega$) and check that the control source can supply the base current.

The key idea is not the exact number—it’s the reasoning: you must provide adequate base drive while protecting the signal source.

MOSFET as a low-side switch

MOSFETs are often preferred for higher currents because they can have very low on-resistance, reducing voltage drop and heating. The main design risk is gate drive: a MOSFET that isn’t fully enhanced at your gate voltage behaves like a resistor and heats up.

Design considerations:

• Ensure the MOSFET turns on at your gate voltage.
• Add a gate resistor (often small) if needed to reduce ringing.
• Add a gate pull-down so it stays off when the input floats.

Driving relays and motors

Relays and motors are inductive, so you typically include:

• a transistor switch,
• a flyback diode across the coil,
• adequate supply decoupling.

Exam Focus

• Typical question patterns:
  • Explain how a transistor allows a low-power control signal to drive a high-current load.
  • Calculate a base resistor or reason about why a transistor isn’t saturating.
  • Add required protection components (flyback diode, pull-down).
• Common mistakes:
  • Forgetting that control outputs have a maximum current—oversized base current can overload them.
  • Omitting the flyback diode and then attributing failure to “bad transistor.”
  • Assuming any MOSFET will work at $3.3\,V$ or $5\,V$ gate drive without checking behavior.

Prototyping and construction: breadboard, stripboard, and PCB thinking

Design-and-development is iterative: you build, test, learn, and refine. Construction method affects reliability and how you debug.

Breadboards (fast iteration, higher noise/loose connections)

Breadboards are excellent for rapid prototyping but introduce:

• accidental loose connections,
• higher stray capacitance and inductance,
• confusing power rails (some rails are split).

A frequent build error is assuming the entire power rail is continuous when it’s actually broken in the middle.

Stripboard/veroboard (more robust, needs planning)

Stripboard requires you to plan track cuts and component layout. You must think physically:

• where currents flow,
• where grounds join,
• how to keep noisy parts (motors, relay coils) away from sensitive nodes.

PCB fundamentals (even if you don’t manufacture one)

Even if your course doesn’t require a PCB, “PCB thinking” improves your designs:

• Keep high-current loops short.
• Place decoupling capacitors close to the devices they support.
• Avoid routing sensitive signals next to switching nodes.

Design for test (making debugging possible)

A professional habit is adding test points or at least leaving accessible nodes so you can measure:

• supply voltage at the load,
• output voltage,
• transistor base/gate drive.

If you design a circuit that can’t be measured without disassembling it, you’ve made troubleshooting much harder than it needs to be.

Exam Focus

• Typical question patterns:
  • Compare prototyping methods and justify a choice for a given project.
  • Suggest layout improvements to reduce noise or wiring errors.
  • Identify likely breadboard mistakes from symptoms.
• Common mistakes:
  • Poor grounding and long return paths that create unexpected voltage drops.
  • Placing decoupling incorrectly (or leaving it out) and getting intermittent resets/noise.
  • Treating physical layout as irrelevant to circuit behavior.

Testing, measurement, and validation against the specification

You don’t finish a design when it “turns on.” You finish when it meets the specification reliably and you can prove it.

Measurement tools and what they tell you

A digital multimeter (DMM) is the core tool for DC circuits:

• Voltage measurements show node potentials relative to ground.
• Current measurements require inserting the meter in series (a common source of accidental shorts if done incorrectly).
• Resistance/continuity measurements should be done with power off.

The key skill is choosing where to measure based on what you expect. Testing is guided by a model: “If my transistor is on, I expect low voltage at its collector/drain,” etc.

Building a test plan (validation)

A simple test plan maps each requirement to a test:

• Requirement: $I_{LED} = 10\,mA \pm 2\,mA$
  • Test: measure voltage across resistor and compute current.
• Requirement: reverse polarity protection
  • Test: reverse supply briefly and confirm no damage and correct behavior after.
• Requirement: runtime
  • Test: measure average current and estimate runtime from battery capacity.

Tolerances and worst-case thinking

Real components vary. If you design an LED current of $10\,mA$ using a resistor with $\pm 5\%$ tolerance, the current varies too.

Design-and-development questions often reward you for discussing:

• worst-case current,
• safe operating margins,
• what happens as battery voltage changes.

Worked example: current from measured resistor voltage

You measure $V_R = 2.8\,V$ across a resistor labeled $330\,\Omega$.

$I = \frac{V_R}{R} = \frac{2.8\,V}{330\,\Omega} \approx 8.48\,mA$

This is a common validation method: you infer current from resistor voltage because it’s safer than putting the meter in series everywhere.

Exam Focus

• Typical question patterns:
  • Propose measurements to confirm a circuit meets a performance requirement.
  • Use measured voltages to compute currents and power.
  • Discuss tolerance effects and explain how to design with margin.
• Common mistakes:
  • Measuring current incorrectly (placing the meter across a supply like a voltmeter, which can short it).
  • Forgetting to power off before resistance/continuity checks.
  • Claiming the design “works” without linking results back to the specification.

Systematic fault-finding and iteration (debugging as a design skill)

Fault-finding is not random part swapping. It’s a structured process: observe symptoms, form hypotheses, test them, and isolate the fault. In many assessed projects, the quality of your debugging method is as important as the final circuit.

A reliable troubleshooting workflow

1. Check the power first: Is the correct voltage present where it should be, under load?
2. Confirm ground continuity: Many “mystery” failures are broken ground connections.
3. Verify component orientation:
   • diode direction,
   • electrolytic capacitor polarity,
   • transistor pinout.
4. Divide and conquer: test subcircuits separately (power, sensor, driver, output).
5. Measure expected node voltages and compare to your predicted values.

This workflow matters because it prevents you from chasing secondary symptoms. For example, if the supply is sagging, many nodes will look “wrong,” but the root cause is the power stage.

Typical failure modes in DC circuit builds

• Open circuit: broken track, loose breadboard connection.
• Short circuit: solder bridge, wrong wiring.
• Wrong value: resistor bands misread, capacitor mis-selected.
• Wrong pinout: transistor pins vary by package; relying on “it looks right” is risky.

A classic misconception is thinking that if a component “reads correct” on a meter, it must be correct in-circuit. Some faults only show under load (e.g., a weak battery that measures $9\,V$ with no load but collapses under current draw).

Iteration: improving the design after testing

Design-and-development expects you to refine:

• If an LED is too dim, you adjust current but re-check resistor power and battery life.
• If a switch chatters, you add debounce (RC or software) but confirm it doesn’t slow response too much.
• If a transistor heats, you reduce dissipation (better MOSFET, lower current, heatsinking, or different topology).

Good iteration is evidence-based: you change one thing, measure again, and record results.

Exam Focus

• Typical question patterns:
  • Given symptoms (e.g., LED never turns on), identify likely faults and propose tests.
  • Interpret measured node voltages to locate a fault.
  • Explain a design modification after testing and justify it.
• Common mistakes:
  • Changing multiple variables at once, making it unclear what fixed the issue.
  • Skipping the power/ground checks and jumping straight to “the sensor must be broken.”
  • Not considering load effects when diagnosing (battery sag, regulator overheating).

Design documentation: presenting and justifying your development process

In assessed design-and-development work, documentation is not decoration—it’s how you demonstrate engineering reasoning. Even a perfect circuit can score poorly if you can’t explain decisions, show evidence of testing, and present a clear final design.

Core documents in a DC circuit design project

• Schematic: final circuit with correct symbols, values, labels.
• BOM (Bill of Materials): component list with values, quantities, ratings, and part identifiers.
• Design justification: brief reasoning for key choices (why that resistor value, why that transistor, why that protection).
• Test results: measurements linked to specification requirements.
• Iteration record: what changed, why, and what improved.

Communicating calculations clearly

When you show calculations, clarity is as important as correctness:

• state the formula,
• define variables,
• substitute values with units,
• give a final value with units.

This prevents “answer-only” work that’s hard to follow and easy to mark down.

Risk and safety considerations

Depending on project context, safety might include:

• avoiding exposed conductors,
• ensuring correct polarity markings,
• limiting current to prevent overheating,
• choosing components with adequate voltage and power ratings.

Even in low-voltage DC projects, short circuits can cause hot wires, burned tracks, or battery overheating.

Exam Focus

• Typical question patterns:
  • Explain and justify component choices using calculations and ratings.
  • Present a final design with schematic + BOM + brief testing evidence.
  • Describe improvements made during development and link to measured outcomes.
• Common mistakes:
  • Listing components without ratings or justification (e.g., “a transistor” instead of specifying why it fits current/voltage needs).
  • Providing calculations with missing units or unexplained steps.
  • Reporting tests without linking them to specific specification requirements.