An integrated LLM, static analysis, and retrieval pipeline for concept-linked feedback in .NET web programming


Abstract

Programming education continues to struggle with a gap between cohort scale and feedback quality. Manual code review is slow and inconsistent in large classes, while traditional automated tools emphasize compliance and defect detection rather than pedagogy. Recent Artificial Intelligence (AI) systems offer promise, but classroom-ready pipelines with transparent evaluation on accuracy, latency, and cost remain scarce.

We design and evaluate a classroom-oriented feedback pipeline for practical web programming in a .NET environment. The system integrates: (i) a large language model for explanations and improvement strategies, (ii) a static analyzer for precise rule-based findings, and (iii) retrieval-augmented access to curated course materials for grounding. The study uses 200 anonymized C# submissions collected across three consecutive semesters (Fall 2024, Spring 2025, Summer 2025). A fixed prompt template and a rubric aligned with formative assessment guide outputs. We compare the pipeline against conventional tools and instructor workflows, and we run ablations to assess the effect of retrieval and static-analysis signals. Primary endpoints are the technical accuracy of findings, the usefulness and specificity of comments, mean end-to-end latency, and estimated cost per submission.

The integrated pipeline achieved 89.08% technical accuracy on real student submissions, with a mean end-to-end latency of 54.6 seconds and an estimated cost of USD 0.0203 per submission. Retrieval increased concept linkage and assignment awareness relative to a Large Language Model (LLM) baseline, while static-analysis signals reduced unsupported claims and tightened alignment with rubric criteria. Against conventional tools, the pipeline produced more specific, concept-linked guidance rather than checklist-style defect flags, and it met practical turnaround targets suitable for routine classroom use. Coupling a large language model with static analysis and retrieval over course materials delivers timely, specific, and learner-centered feedback at a classroom scale while maintaining low operational cost. The article contributes an end-to-end, reproducible protocol and a documented design for prompts, grounding, and safety rules. Limitations include a single-institution .NET focus and the absence of long-term learning measures. Future work will examine generalization to other languages and course types, governance of the knowledge base, and impacts on equity and durable learning.

Ask to review this manuscript

Notes for potential reviewers

  • Volunteering is not a guarantee that you will be asked to review. There are many reasons: reviewers must be qualified, there should be no conflicts of interest, a minimum of two reviewers have already accepted an invitation, etc.
  • This is NOT OPEN peer review. The review is single-blind, and all recommendations are sent privately to the Academic Editor handling the manuscript. All reviews are published and reviewers can choose to sign their reviews.
  • What happens after volunteering? It may be a few days before you receive an invitation to review with further instructions. You will need to accept the invitation to then become an official referee for the manuscript. If you do not receive an invitation it is for one of many possible reasons as noted above.

  • PeerJ Computer Science does not judge submissions based on subjective measures such as novelty, impact or degree of advance. Effectively, reviewers are asked to comment on whether or not the submission is scientifically and technically sound and therefore deserves to join the scientific literature. Our Peer Review criteria can be found on the "Editorial Criteria" page - reviewers are specifically asked to comment on 3 broad areas: "Basic Reporting", "Experimental Design" and "Validity of the Findings".
  • Reviewers are expected to comment in a timely, professional, and constructive manner.
  • Until the article is published, reviewers must regard all information relating to the submission as strictly confidential.
  • When submitting a review, reviewers are given the option to "sign" their review (i.e. to associate their name with their comments). Otherwise, all review comments remain anonymous.
  • All reviews of published articles are published. This includes manuscript files, peer review comments, author rebuttals and revised materials.
  • Each time a decision is made by the Academic Editor, each reviewer will receive a copy of the Decision Letter (which will include the comments of all reviewers).

If you have any questions about submitting your review, please email us at [email protected].