Abstract Accessible tools for pharmacokinetic education and routine clinical pharmacokinetic analysis remain limited. Commercial software carries licensing costs and on the other hand existing open-source alternatives lack integrated workflows spanning study planning through bioequivalence assessment and are not user-friendly. We developed NCA Assistant, a browser-based application for non-compartmental pharmacokinetic analysis, bioequivalence testing, and power and sample size calculations within a single platform designed for pharmacokinetic research and teaching. NCA Assistant was designed with Anthropic Claude AI as coding assistant, with multi-expert prompting. The app was developed in R/Shiny with a hub-based architecture connecting six workflow modules. Core computations rely on established R packages for non-compartmental analysis, power and sample size calculations and analysis of variance. For the interface, there was an emphasis for transparency through interactive visualization, configurable analysis settings and exportable audit trails. The application supports extravascular and intravenous dosing scenarios, handles both single-subject and batch analyses and accommodates standard crossover, replicate, and parallel bioequivalence designs.A dedicated visualization module generates publication-ready concentration–time plots. Features include interactive terminal half-life review with point selection override and configurable thresholds for elimination half-life calculation. A validation package, consisting of draft validation documents and a validation script, accompanies the application and is supplied in the supplemental materials. NCA Assistant provides an accessible entry point for pharmacokinetic data analysis suitable for graduate training and routine clinical pharmacology applications, with extensibility for use in more regulated environments.
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.