Circuits and logic in the lab: toward a coherent picture of computation

Elizabeth Patitsas, Kimberly D. Voll, Mark Crowley, Steven A. WolfmanWCCCE 2010 · DOI

TL;DR

This paper details how the University of British Columbia's first-year computer science course, which blends logic, digital circuits, and hardware labs, was significantly revamped to create a more cohesive learning experience. By re-framing the labs around an overarching "story" of computer design and improving logistical and pedagogical aspects, student frustration was reduced, and engagement with the material was substantially enhanced.

What Problem Does This Paper Address?

Many introductory computer science courses struggle to bridge the gap between theoretical concepts taught in lectures and practical, hands-on lab experiences. In the context of a first-year course at UBC covering discrete mathematics, proofs, logic, and digital circuitry, this disconnect was particularly pronounced. Students perceived the hardware labs as disconnected from the rest of the course, leading to frustration and dissatisfaction. The challenge was to create a unified narrative that made the relationship between abstract theory and concrete implementation clear and motivating for students.

Methods

The authors implemented a multi-faceted approach to restructure the course:

  • Overarching Story: The lab curriculum was re-organized around a unifying "story" of computer design, tracing the journey from basic logic gates to a simulated CPU. This narrative was explicitly referenced throughout the term in both lectures and labs to reinforce connections.
  • Lab Content and Pedagogy: Labs were shifted from confirmatory activities (verifying known concepts) to exploratory and experimental ones. This included tasks like identifying "mystery" integrated circuits and debugging circuit simulations, encouraging problem-solving and critical thinking.
  • Logistical Improvements:
    • Equipment: The requirement for students to purchase their own hardware kits was eliminated. Instead, university-owned kits were managed and distributed by teaching assistants (TAs), reducing financial burden and frustration.
  • Workflow: Lab instructions were streamlined, with clear "TODO" markers for pre-lab work and a reduction in extraneous text. This aimed to make labs more manageable within the allotted time.
  • Teaching Assistant (TA) Management:
    • Training: Weekly meetings were introduced for TAs, led by a "Lab Coordinator," to beta-test upcoming labs, receive training, and discuss pedagogical strategies.
  • Collaboration: Labs were reformatted to strongly encourage pair programming, fostering student interaction and reducing reliance on TAs for basic questions.
  • Grading Scheme: The grading scheme was clarified, with labs marked out of ten points and a clear emphasis on analysis of observations rather than just correctness. Dedicated marks for pre-lab exercises were introduced to incentivize preparation.
  • Discussion Periods: Short, open-ended discussion periods were added to the beginning of labs, led by TAs, to explicitly bridge lab activities with lecture material.

Datasets

Not discussed in the paper. The evaluation relies on student survey data and anecdotal feedback from students and TAs.

Key Insights and Ideas

  • The Power of Narrative: Framing the lab experience around a coherent "story" of computer design is crucial for connecting abstract theory to practical implementation. Students are more likely to engage when they see a clear progression and purpose.
  • Exploration Over Confirmation: Shifting lab activities from simply verifying known outcomes to actively exploring, experimenting, and problem-solving significantly boosts student engagement and learning.
  • Reducing Logistical Friction: Eliminating financial burdens (like kit purchases) and streamlining instructions can dramatically improve student perception and reduce frustration, allowing them to focus on learning.
  • TA Empowerment: Investing in structured TA training and fostering a collaborative environment among TAs can lead to better teaching quality and a more positive lab experience for students.
  • Pair Programming Benefits: Encouraging students to work in pairs can improve the quality of their work, foster collaboration, and reduce the demand on TA support.

Key Results

  • Student survey data showed improvements in the perception of labs tying into the rest of the course material. In spring 2008, the mean score was 3.4 (median 3), which rose to 3.5 (median 4) by the halfway point of spring 2009.
  • Student perception of pre-lab work contributing to understanding also improved, from a mean of 2.7 (median 3) in 2008 to 3.3 (median 4) in 2009.
  • Anecdotal evidence from TAs indicated increased satisfaction with the new lab materials and format, and a perception of increased student satisfaction.
  • The elimination of mandatory kit purchases led to significantly fewer complaints, with students viewing the "Magic Box" as fun equipment rather than a financial burden.

Limitations and Future Work

  • Lab #1 Improvement: The authors acknowledge that the first official lab, introducing the unifying CPU simulation, remains unsatisfactory and needs a friendlier format to avoid intimidating students.
  • Bridging Theory and Lab: For units like proof techniques, where a direct hands-on lab component is not obvious, finding suitable lab material to maintain the course's narrative coherence is an ongoing challenge. Developing discussion periods to better tie back to lectures is a current direction.
  • Collaboration Policies: While pair programming was encouraged, the initial policy of requiring students to register with a partner was found problematic and relaxed. Future work may involve more proactive partner assignment.
  • "Lab #0" Update: The initial "Lab #0" (for login and basic setup) is outdated and needs revision to set a more positive and collaborative tone from day one.
  • TA Meeting Attendance: While beneficial, TA meeting attendance has been an issue, partly due to perceived seniority and skepticism from returning TAs. Instructors need to clearly communicate the importance of these meetings.

Summary updated

BibTeX
@inproceedings{patitsas2010circuits,
  author = {Elizabeth Patitsas and Kimberly D. Voll and Mark Crowley and Steven A. Wolfman},
  title = {{Circuits and logic in the lab: toward a coherent picture of computation}},
  booktitle = {WCCCE},
  year = {2010},
  doi = {10.1145/1806512.1806523},
}
Figure