12 research outputs found

    An aspect-based traceability mechanism for domain specific languages

    No full text

    Taming the Confusion of Languages

    No full text

    TexMo: A Multi-language Development Environment

    No full text

    Variability mechanisms in software ecosystems

    No full text
    Context: Software ecosystems are increasingly popular for their economic, strategic, and technical advantages. Applica-tion platforms such as Android or iOS allow users to highly customize a system by selecting desired functionality from a large variety of assets. This customization is achieved using variability mechanisms. Objective: Variability mechanisms are well-researched in the context of software product lines. Although software ecosystems are often seen as conceptual successors, the technology that sustains their success and growth is much less understood. Our objective is to improve empirical understanding of variability mechanisms used in successful software ecosystems. Method: We analyze five ecosystems, ranging from the Linux kernel through Eclipse to Android. A qualitative analysis identifies and characterizes variability mechanisms together with their organizational context. This analysis leads to a conceptual framework that unifies ecosystem-specific aspects using a common terminology. A quantitative analysis investigates scales, growth rates, and—most importantly—dependency structures of the ecosystems. Results: In all the studied ecosystems, we identify rich dependency languages and variability descriptions that declare many direct and indirect dependencies. Indirect dependencies to abstract capabilities, as opposed to concrete variability units, are used predominantly in fast-growing ecosystems. We also find that variability models—while providing system

    Effects of nutrition therapy on growth, inflammation and metabolism in immature infants : a study protocol of a double-blind randomized controlled trial (ImNuT)

    No full text
    BACKGROUND: Current nutritional management of infants born very preterm results in significant deficiency of the essential fatty acids (FAs) arachidonic acid (ARA) and docosahexaenoic acid (DHA). The impact of this deficit on brain maturation and inflammation mediated neonatal morbidities are unknown. The aim of this study is to determine whether early supply of ARA and DHA improves brain maturation and neonatal outcomes in infants born before 29 weeks of gestation. METHODS: Infants born at Oslo University Hospital are eligible to participate in this double-blind randomized controlled trial. Study participants are randomized to receive an enteral FA supplement of either 0.4 ml/kg MCT-oil™ (medium chain triglycerides) or 0.4 ml/kg Formulaid™ (100 mg/kg of ARA and 50 mg/kg of DHA). The FA supplement is given from the second day of life to 36 weeks' postmenstrual age (PMA). The primary outcome is brain maturation assessed by Magnetic Resonance Imaging (MRI) at term equivalent age. Secondary outcomes include quality of growth, incidence of neonatal morbidities, cardiovascular health and neuro-development. Target sample size is 120 infants (60 per group), this will provide 80% power to detect a 0.04 difference in mean diffusivity (MD, mm2/sec) in major white matter tracts on MRI. DISCUSSION: Supplementation of ARA and DHA has the potential to improve brain maturation and reduce inflammation related diseases. This study is expected to provide valuable information for future nutritional guidelines for preterm infants. TRIAL REGISTRATION: Clinicaltrials.gov ID: NCT03555019 . Registered 4 October 2018- Retrospectively registered

    What Makes Agile Software Development Agile

    Get PDF
    Together with many success stories, promises such as the increase in production speed and the improvement in stakeholders\u27 collaboration have contributed to making agile a transformation in the software industry in which many companies want to take part. However, driven either by a natural and expected evolution or by contextual factors that challenge the adoption of agile methods as prescribed by their creator(s), software processes in practice mutate into hybrids over time. Are these still agile In this article, we investigate the question: what makes a software development method agile We present an empirical study grounded in a large-scale international survey that aims to identify software development methods and practices that improve or tame agility. Based on 556 data points, we analyze the perceived degree of agility in the implementation of standard project disciplines and its relation to used development methods and practices. Our findings suggest that only a small number of participants operate their projects in a purely traditional or agile manner (under 15%). That said, most project disciplines and most practices show a clear trend towards increasing degrees of agility. Compared to the methods used to develop software, the selection of practices has a stronger effect on the degree of agility of a given discipline. Finally, there are no methods or practices that explicitly guarantee or prevent agility. We conclude that agility cannot be defined solely at the process level. Additional factors need to be taken into account when trying to implement or improve agility in a software company. Finally, we discuss the field of software process-related research in the light of our findings and present a roadmap for future research
    corecore