Skip to main navigation Skip to search Skip to main content

Formative assessment of programming language learning based on peer code review: Implementation and experience report

  • Beihang University

Research output: Contribution to journalArticlepeer-review

Abstract

In programming courses, the traditional assessment approach tends to evaluate student performance by scoring one or more project-level summative assignments. This approach no longer meets the requirements of a quality programming language education. Based on an upgraded peer code review model, we propose a formative assessment approach to assess the learning of computer programming languages, and develop an online assessment system (OOCourse) to implement this approach. Peer code review and inspection is an effective way to ensure the high quality of a program by systematically checking the source code. Though it is commonly applied in industrial and open-source software development, it is rarely taught and practiced in undergraduate-level programming courses. We conduct a case study using the formative assessment method in a sophomore level Object-Oriented Design and Construction course with more than 240 students. We use Moodle (an online learning system) and some relevant plugins to conduct peer code review. We also conduct data mining on the running data from the peer assessment activities. The case study shows that formative assessment based on peer code review gradually improved the programming ability of students in the undergraduate class.

Original languageEnglish
Article number8660528
Pages (from-to)423-434
Number of pages12
JournalTsinghua Science and Technology
Volume24
Issue number4
DOIs
StatePublished - Aug 2019

Keywords

  • dynamic designation
  • formative assessment
  • peer code review
  • programming language learning

Fingerprint

Dive into the research topics of 'Formative assessment of programming language learning based on peer code review: Implementation and experience report'. Together they form a unique fingerprint.

Cite this