Andrei Mikriukov
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Research Subjects
Andrei Mikriukov has a total of 25 co-authors. Here are the top co-authors by number of shared publications:
- Giancarlo Succi
Alma Mater Studiorum, University of Bologna, 40126 Bologna, Italy
5 shared publications - Alexander Tormasov
Constructor Knowledge Labs and Constructor University, Bremen, Germany
3 shared publications - Abu Huraira
Constructor Knowledge Labs, Bremen, Germany
2 shared publications - Ekaterina Trofimova
HSE University, 11 Pokrovsky b-r, Moscow, Russia
2 shared publications - Alessandro Ravveduto
Constructor University, Bremen, Germany
1 shared publication - Alessandro Ravveduto
Constructor Labs, Constructor University, 28759 Bremen, Germany
1 shared publication
Latest Publications
- Open Access
From Executable to Demonstrable: Synthesizing API Usage Showcases for Research Repositories
A script that runs a research repository is not the same as a script that shows how to use it. Test generation targets structural coverage, and work on executability targets whether a repository can be made to run. Neither yields what a new user of a research library needs, which is a worked example. We define demonstrativeness by three explicit predicates: in-process contact with a public non-driver symbol, use of a constructed argument, and output that depends on the returned value. We record these static predicates separately from environment construction and trial execution, preventing dependency-blocked repositories from being labelled runtime successes or failures. Reaching a library’s interface requires a target model that entry-point selection cannot express; we derive symbol-level targets by Horn clauses over signatures, exports, docstrings, and documentation references. Generated scripts are read back after every successful execution, and a vacuous script can be repaired without discarding the best executable fallback. In a paired, single-run evaluation on 90 repositories, of which 24 had buildable environments, the full configuration produced 11 passing showcases against 2 for an entry-point-only configuration and made static API contact in 15 buildable environments against 7, while both retained Tier-1 success on the same 21; exact McNemar tests on the per-repository records give and . Corpus-wide, the entry-point-only configuration attempted generation on 24 repositories and the full configuration on 89, with API contact in 7 and 70; that contrast is largely by design, since only the full configuration has a generation path in a dependency-blocked environment. Because the full configuration bundles API targets, read-back, and vacuity repair, these figures establish a system-level contrast, not the isolated causal effect of any component.Open AccessFrom Executable to Demonstrable: Synthesizing API Usage Showcases for Research Repositories
A script that runs a research repository is not the same as a script that shows how to use it. Test generation targets structural coverage, and work on executability targets whether a repository can be made to run. Neither yields what a new user of a research library needs, which is a worked example. We define demonstrativeness by three explicit predicates: in-process contact with a public non-driver symbol, use of a constructed argument, and output that depends on the returned value. We record these static predicates separately from environment construction and trial execution, preventing dependency-blocked repositories from being labelled runtime successes or failures. Reaching a library’s interface requires a target model that entry-point selection cannot express; we derive symbol-level targets by Horn clauses over signatures, exports, docstrings, and documentation references. Generated scripts are read back after every successful execution, and a vacuous script can be repaired without discarding the best executable fallback. In a paired, single-run evaluation on 90 repositories, of which 24 had buildable environments, the full configuration produced 11 passing showcases against 2 for an entry-point-only configuration and made static API contact in 15 buildable environments against 7, while both retained Tier-1 success on the same 21; exact McNemar tests on the per-repository records give and . Corpus-wide, the entry-point-only configuration attempted generation on 24 repositories and the full configuration on 89, with API contact in 7 and 70; that contrast is largely by design, since only the full configuration has a generation path in a dependency-blocked environment. Because the full configuration bundles API targets, read-back, and vacuity repair, these figures establish a system-level contrast, not the isolated causal effect of any component. - Open Access
- 12 December 2025
- Published by Association for Computing Machinery (ACM)
- p. 38-46
Agentic LLM Pipelines for Reproducible Scientific Software: Opportunities and Challenges
- 12 December 2025
- Published by Association for Computing Machinery (ACM)
- p. 38-46
Open AccessAgentic LLM Pipelines for Reproducible Scientific Software: Opportunities and Challenges
- Open Access
- 27 October 2025
- Published by Association for Computing Machinery (ACM)
- p. 91-97
A Systemic Perspective on Software Engineering
- 27 October 2025
- Published by Association for Computing Machinery (ACM)
- p. 91-97
Open AccessA Systemic Perspective on Software Engineering
- Open Access
- 13 June 2025
- Published by Association for Computing Machinery (ACM)
- p. 25-30
AI Tools for Automating Systematic Literature Reviews
- 13 June 2025
- Published by Association for Computing Machinery (ACM)
- p. 25-30
Open AccessAI Tools for Automating Systematic Literature Reviews
- Open Access
- 17 April 2025
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Access
- Vol. 13, 77493-77506
A Systematic Literature Review on Measuring Brain Activity While Reviewing Code and Paintings
In recent years, the intersection of cognitive neuroscience and software engineering has sparked significant interest, particularly in understanding developers’ mental activities. This systematic literature review (SLR) investigates the current methodologies for measuring and analyzing mental activity, particularly using EEG when reviewing code and paintings. The research addresses four key questions: (1) What methods are available to measure mental activity when reviewing code and pictures? (2) What are the methods for analyzing brain activity data especially extracted using EEG? (3) How do brain activity patterns differ when studying code and pictures obtained with EEG? and (4) Are there any differences in stress levels when reviewing code and drawing obtained with EEG? Our findings reveal various techniques for capturing and analyzing EEG data, yet highlight a significant gap in the empirical research addressing the last two questions. This underscores the need for targeted experiments to explore these specific brain activity patterns and stress level differences. These are crucial for advancing our understanding of cognitive processes in software engineering and related fields.
- 17 April 2025
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Access
- Vol. 13, 77493-77506
Open AccessA Systematic Literature Review on Measuring Brain Activity While Reviewing Code and Paintings
In recent years, the intersection of cognitive neuroscience and software engineering has sparked significant interest, particularly in understanding developers’ mental activities. This systematic literature review (SLR) investigates the current methodologies for measuring and analyzing mental activity, particularly using EEG when reviewing code and paintings. The research addresses four key questions: (1) What methods are available to measure mental activity when reviewing code and pictures? (2) What are the methods for analyzing brain activity data especially extracted using EEG? (3) How do brain activity patterns differ when studying code and pictures obtained with EEG? and (4) Are there any differences in stress levels when reviewing code and drawing obtained with EEG? Our findings reveal various techniques for capturing and analyzing EEG data, yet highlight a significant gap in the empirical research addressing the last two questions. This underscores the need for targeted experiments to explore these specific brain activity patterns and stress level differences. These are crucial for advancing our understanding of cognitive processes in software engineering and related fields.