Intra-jaw versus inter-jaw mini-implant anchored total maxillary arch distalization compared with extraction-based en-masse retraction in adult class II division 1 malocclusion patients: A randomized controlled trial.
Aug 2026· International Orthodontics· Vol 24 4, pp.
101233
· 0 citations· 59 references
Medicine
TL;DR
Both TMAD methods are effective alternatives to extraction-based treatment, and intra-jaw and inter-jaw TMAD better preserved anterior torque and occlusal plane stability.
Abstract
Background
This study aimed to compare the efficacy of intra-jaw and inter-jaw mini-implant-anchored total-maxillary-arch distalization (TMAD) versus premolar extraction for treating Class II Division 1 malocclusion.
Methods
This randomized parallel-group controlled trial included Forty-one patients with Class II Division 1 malocclusion aged between 16 and 30 years were randomly assigned in a 1:1:1 allocation ratio to three groups: intra-jaw TMAD (buccal TADs between U5 and U6; mean age±SD: 22.0±3.7 years), inter-jaw TMAD (skeletally anchored Class II elastics with TADs between L6 and L7; mean age±SD: 19.0±2.6 years), and a control group (premolar extraction with alveolar TADs between U5 and U6; mean age±SD: 21.4±2.7 years). Dentoalveolar, skeletal, and soft-tissue changes were evaluated using dental casts and cephalograms before treatment (T0), at the end of the alignment and levelling phase (T1), and at the end of active treatment (achieving Class I canine relationship with normal overjet; T2. Block randomization and outcome assessor blinding were employed. Statistical analysis was performed using SPSS software. Comparisons between groups and within groups were performed using ANOVA or non-parametric equivalents, followed by appropriate post-hoc tests with Bonferroni correction when required.
Results
Forty-one patients completed the study. Intra-Jaw TMAD, Inter-Jaw TMAD, and extraction treatments showed significant overjet reduction (4.1±0.6, 4.1±0.7, 4.6±1 respectively) and canine correction (3.7±0.9, 3.5±1.1, 4±0.8 respectively) with no significant intergroup differences. However, palatal incisor tipping was significantly lower in the intra-jaw group (5.2̊±1.8) compared to the inter-jaw (8̊±2.6) and control (11̊±2.8) groups. Skeletally, TMAD groups exhibited slight mandibular downward rotation, while the control group showed minor forward rotation. The maxillary-mandibular plane angle (MM) increased in intra-jaw and inter-jaw TMAD groups (1̊±0.7, 1.5̊±0.7 with P-values of 0.001,<0.001, respectively) but decreased in the control (1̊±0.8, P=0.04). The control group showed a more pronounced nasolabial angle increase (12.5̊±3.8) compared to intra-jaw and inter-jaw TMAD groups (8.5̊±2.6, 10̊±1.6, with P-values<0.001).
Conclusions
Both TMAD methods are effective alternatives to extraction-based treatment. Intra-jaw TMAD better preserved anterior torque and occlusal plane stability. While extraction treatment produced greater soft tissue changes and reduced intermolar width, TMAD increased width and induced distobuccal molar rotation.
TRIAL REGISTRATION
Clinical Trials.gov (Identifier: NCT04814173). Registered on the 20th of May 2022.
Agile - denoting "the quality of being agile, readiness for motion, nimbleness, activity, dexterity in motion" - software development methods are attempting to offer an answer to the eager business community asking for lighter weight along with faster and nimbler software development processes. This is especially the case with the rapidly growing and volatile Internet software industry as well as for the emerging mobile application environment. The new agile methods have evoked substantial amount of literature and debates. However, academic research on the subject is still scarce, as most of existing publications are written by practitioners or consultants. The aim of this publication is to begin filling this gap by systematically reviewing the existing literature on agile software development methodologies. This publication has three purposes. First, it proposes a definition and a classification of agile software development approaches. Second, it analyses ten software development methods that can be characterized as being "agile" against the defined criterion. Third, it compares these methods and highlights their similarities and differences. Based on this analysis, future research needs are identified and discussed.
P. Abrahamsson, O. Salo, Jussi Ronkainen et al.· arXiv.org· 728 citations· ⚡54
Context: Software startups are newly created companies with no operating history and fast in producing cutting-edge technologies. These companies develop software under highly uncertain conditions, tackling fast-growing markets under severe lack of resources. Therefore, software startups present a unique combination of characteristics which pose several challenges to software development activities. Objective: This study aims to structure and analyze the literature on software development in startup companies, determining thereby the potential for technology transfer and identifying software development work practices reported by practitioners and researchers. Method: We conducted a systematic mapping study, developing a classification schema, ranking the selected primary studies according their rigor and relevance, and analyzing reported software development work practices in startups. Results: A total of 43 primary studies were identified and mapped, synthesizing the available evidence on software development in startups. Only 16 studies are entirely dedicated to software development in startups, of which 10 result in a weak contribution (advice and implications (6); lesson learned (3); tool (1)). Nineteen studies focus on managerial and organizational factors. Moreover, only 9 studies exhibit high scientific rigor and relevance. From the reviewed primary studies, 213 software engineering work practices were extracted, categorized and analyzed. Conclusion: This mapping study provides the first systematic exploration of the state-of-art on software startup research. The existing body of knowledge is limited to a few high quality studies. Furthermore, 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 growing literature on affect among software developers mostly reports on the linkage between happiness, software quality, and developer productivity. Understanding happiness and unhappiness in all its components -- positive and negative emotions and moods -- is an attractive and important endeavor. Scholars in industrial and organizational psychology have suggested that understanding happiness and unhappiness could lead to cost-effective ways of enhancing working conditions, job performance, and to limiting the occurrence of psychological disorders. Our comprehension of the consequences of (un)happiness among developers is still too shallow, being mainly expressed in terms of development productivity and software quality. In this paper, we study what happens when developers are happy and unhappy while developing software. Qualitative data analysis of responses given by 317 questionnaire participants identified 42 consequences of unhappiness and 32 of happiness. We found consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts. Our classification scheme, available as open data enables new happiness research opportunities of cause-effect type, and it can act as a guideline for practitioners for identifying damaging effects of unhappiness and for fostering happiness on the job.
D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al.· Journal of Systems and Softw...· 236 citations· ⚡13
Mobile phones have been closed environments until recent years. The change brought by open platform technologies such as the Symbian operating system and Java technologies has opened up a significant business opportunity for anyone to develop application software such as games for mobile terminals. However, developing mobile applications is currently a challenging task due to the specific demands and technical constraints of mobile development. Furthermore, at the moment very little is known about the suitability of the different development processes for mobile application development. Due to these issues, we have developed an agile development approach called Mobile-D. The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed.
P. Abrahamsson, Antti Hanhineva, H. Hulkko et al.· Conference on Object-Oriente...· 225 citations· ⚡18
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduAug 17, 2026
A USAF cadet and a Lincoln Laboratory researcher found AI chatbots can help nontechnical service members produce viable software applications for their unique problems.
