aceModerate evidence
Published recordEducationGood Space
More
Analysing the Impact of Artificial Intelligence and Computational Sciences on Student Performance: Systematic Review and Meta-analysis
- Truvace record
- TRV-2026-2857raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Systematic review or meta-analysis
- Sources
- 1 sourcePeer-reviewed
- sha256
- 6ee33a6d4d40…check it
Abstract Artificial intelligence (AI) and computational sciences have aroused a growing interest in education. Despite its relatively recent history, AI is increasingly being introduced into the classroom through different modalities, with the aim of improving student achievement. Thus, the purpose of the research is to analyse, quantitatively and qualitatively, the impact of AI components and computational sciences on student performance. For this purpose, a systematic review and meta-analysis have been carried…
The gain
A systematic review and meta-analysis of 25 articles found that AI and computational sciences had a positive impact on student performance, with higher attitude towards learning and motivation, especially in STEM subjects.
What this doesn’t fix
The authors say that implementing these technologies in instruction poses a great educational and ethical challenge for teachers regarding design and implementation, which requires further analysis.
Sources
1 on file- Journal of New Approaches in Educational Researchdoi:10.7821/naer.2023.1.1240
Cite this record
v1Truvace Impact Record TRV-2026-2857, v1: “Analysing the Impact of Artificial Intelligence and Computational Sciences on Student Performance: Systematic Review and Meta-analysis.” Truvace, 2026-11-12. /record/TRV-2026-2857 (accessed on the day you copy it). sha256 6ee33a6d4d4037cd…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2857 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.