Oct 2026· Acta Crystallographica Section C Structural Chemistry· 0 citations
Medicine
Abstract
With checkCIF the IUCr has created a unique platform for the validation and archiving of the result of a small-molecule crystal structure study. That information, supplied in CIF (crystallographic information file) format, should include not only the numerical results of that study but also much of the supporting experimental data and details of the procedures used during the structural investigation. This not only allows for a proper validation of a structure report but also provides an option for a future re-evaluation or use of the data for an unrelated study. The experimental data might be difficult to obtain again or even unique. George Sheldrick's SHELX software was an early adopter of CIF and with that has played a major role in the success of the IUCr validation effort. IUCr/checkCIF initially started out with tests that check for the completeness of the supplied data, along with tests that check whether their values are within the expected range. Currently, the PLATON software carries out most of the tests in the IUCr/checkCIF software framework. Validation issues are reported as a set of ALERTS along with a short clarification. All ALERT messages should be inspected, addressed with a correction where applicable or a short explanation of a special situation. Some ALERT messages are informative but do not necessarily need a comment. More detailed information about a reported issue, such as warnings about missed twinning, missed additional symmetry or voids, might be obtained with a locally installed version of the PLATON software using the same tools on which those ALERTS are based. As an example of this, the use of the PLATON/TwinRotMat tool for the detection of twinning is discussed along with some details about the underlying algorithm. Three twinning examples are presented, covering merohedral, pseudomerohedral and non-merohedral twins, to illustrate the additional twinning information that can be obtained beyond what is shown as an ALERT in the IUCr/checkCIF report.
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.