Oct 2026· Naunyn-Schmiedeberg s Archives of Pharmacology· 24 references
Abstract
Abstract Electronic flashcards are popular among medical students, although their real-world effectiveness, and staff resources required to develop tailored decks, is not well understood. The Institute of Experimental and Clinical Pharmacology, Toxicology and Pharmacology of Natural Products at the Ulm University Medical Center, Germany, created 1007 flashcards on 228 drugs aligned to the local and national curriculum using the Anki flashcard software. The time needed for card development was documented. Medical students participated in an observational study over four semesters and were encouraged to use the cards alongside established study materials for exam preparation in clinical pharmacology. Exams concluded either a lecture-based course focusing on declarative knowledge, or concluded a seminar-based course focusing on case-based application. A survey assessed usage patterns and helpfulness of flashcards and other study materials, demographics, and self-rated general academic performance. Pseudonymous codes linked survey responses to individual exam scores. Flashcard use was reported by 38.4% of participants overall, with higher use when preparing for lecture-based exams than for seminar-based exams. In total, 83.3% of users considered the cards helpful. Participants with lower self-rated general academic performance were more likely to use flashcards. Flashcard users scored lower in the exam than non-users, but this association was no longer significant after adjusting for self-rated general academic performance. Flashcard development took on average 7 min per card. These findings suggest that academically weaker students, and students preparing for exams testing declarative knowledge, may prefer flashcards. Given the substantial staff time required, and the lacking benefit of our flashcard-decks, the decision to tailor curriculum-aligned flashcards should be made cautiously.
This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.
P. Abrahamsson, O. Salo, Jussi Ronkainen et al.· arXiv.org· 727 citations· ⚡54
The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.
M. Pikkarainen, Jukka Haikara, O. Salo et al.· Empirical Software Engineeri...· 401 citations· ⚡48
The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.
Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al.· Information and Software Tec...· 394 citations· ⚡54
The results show that the embedded industry has been able to apply agile methods in its development processes and that the appreciation of the agile methods and their individual practices appears to increase once adopted and applied in practice.
O. Salo, P. Abrahamsson· IET Software· 238 citations· ⚡9
Consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts are found.
D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al.· Journal of Systems and Softw...· 236 citations· ⚡13
The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed, which helped develop an agile development approach for mobile application development.
P. Abrahamsson, Antti Hanhineva, H. Hulkko et al.· Conference on Object-Oriente...· 225 citations· ⚡18
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduOct 6, 2026
Writing as a participant and researcher, PhD student JS Tan SM ’22 has co-authored a new book about the rise of tech worker protests and the employer backlash that followed.
Requirements in large systems rarely exist in isolation. Their meaning depends on the wider project context - other requirements, policies, decisions, tests, and implementation details. That becomes especially important when AI is used for review, because spotting a possible conflict or gap is only the beginning. ReqSpace explores how AI, visualisation, and connected project context can help reviewers understand those findings, trace the relationships behind them, and focus on the questions that…
AI is making software generation faster, but speed does not remove the need for expertise. As more work is delegated to AI, tacit knowledge may become one of the most important human advantages in software engineering. The post Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering appeared first on GPT-Lab.
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.