12,156 research outputs found

    Organisational Legitimacy, Capacity and Capacity Development

    Get PDF
    The European Centre for Development Policy Management (ECDPM) has undertaken a study of capacity development, with a focus on organisational change and performance enhancement. Both individual organisations and networks of organisations have been studied with the aim of identifying important relationships among endogenous change factors (e.g. ownership, commitment and managerial style), key internal organisation variables (e.g. structures, procedures, staffing and management systems), performance and sustainability outcomes, and external environmental factors (e.g. policy frameworks, resource availability, politics, stakeholders, governance regimes, etc.).To date, the ECDPM study team has conducted 16 case studies (see Appendix). Among the findings that have emerged from several of the cases is the presence of an organisation's legitimacy as a factor contributing to successful capacity and performance. To delve in more detail into the concept of legitimacy, and to identify the implications for capacity building, ECDPM commissioned a working paper on the topic. This exploratory paper reviews the relevant literature and examines: differing definitions, types and sources of legitimacy; the links between legitimacy and organisational capacity, performance and sustainability; and management strategies for building and maintaining legitimacy. It discusses a selected set of the ECDPM cases in terms of the legitimacy concept

    Scripted GUI Testing of Android Apps: A Study on Diffusion, Evolution and Fragility

    Full text link
    Background. Evidence suggests that mobile applications are not thoroughly tested as their desktop counterparts. In particular GUI testing is generally limited. Like web-based applications, mobile apps suffer from GUI test fragility, i.e. GUI test classes failing due to minor modifications in the GUI, without the application functionalities being altered. Aims. The objective of our study is to examine the diffusion of GUI testing on Android, and the amount of changes required to keep test classes up to date, and in particular the changes due to GUI test fragility. We define metrics to characterize the modifications and evolution of test classes and test methods, and proxies to estimate fragility-induced changes. Method. To perform our experiments, we selected six widely used open-source tools for scripted GUI testing of mobile applications previously described in the literature. We have mined the repositories on GitHub that used those tools, and computed our set of metrics. Results. We found that none of the considered GUI testing frameworks achieved a major diffusion among the open-source Android projects available on GitHub. For projects with GUI tests, we found that test suites have to be modified often, specifically 5\%-10\% of developers' modified LOCs belong to tests, and that a relevant portion (60\% on average) of such modifications are induced by fragility. Conclusions. Fragility of GUI test classes constitute a relevant concern, possibly being an obstacle for developers to adopt automated scripted GUI tests. This first evaluation and measure of fragility of Android scripted GUI testing can constitute a benchmark for developers, and the basis for the definition of a taxonomy of fragility causes, and actionable guidelines to mitigate the issue.Comment: PROMISE'17 Conference, Best Paper Awar

    The Co-Evolution of Test Maintenance and Code Maintenance through the lens of Fine-Grained Semantic Changes

    Full text link
    Automatic testing is a widely adopted technique for improving software quality. Software developers add, remove and update test methods and test classes as part of the software development process as well as during the evolution phase, following the initial release. In this work we conduct a large scale study of 61 popular open source projects and report the relationships we have established between test maintenance, production code maintenance, and semantic changes (e.g, statement added, method removed, etc.). performed in developers' commits. We build predictive models, and show that the number of tests in a software project can be well predicted by employing code maintenance profiles (i.e., how many commits were performed in each of the maintenance activities: corrective, perfective, adaptive). Our findings also reveal that more often than not, developers perform code fixes without performing complementary test maintenance in the same commit (e.g., update an existing test or add a new one). When developers do perform test maintenance, it is likely to be affected by the semantic changes they perform as part of their commit. Our work is based on studying 61 popular open source projects, comprised of over 240,000 commits consisting of over 16,000,000 semantic change type instances, performed by over 4,000 software engineers.Comment: postprint, ICSME 201

    The myths and realities of Bayesian chronological modeling revealed

    Get PDF
    We review the history of Bayesian chronological modeling in archaeology and demonstrate that there has been a surge over the past several years in American archaeological applications. Most of these applications have been performed by archaeologists who are self-taught in this method because formal training opportunities in Bayesian chronological modeling are infrequently provided. We define and address misconceptions about Bayesian chronological modeling that we have encountered in conversations with colleagues and in anonymous reviews, some of which have been expressed in the published literature. Objectivity and scientific rigor is inherent in the Bayesian chronological modeling process. Each stage of this process is described in detail, and we present examples of this process in practice. Our concluding discussion focuses on the potential that Bayesian chronological modeling has for enhancing understandings of important topics

    Using grounded theory to understand software process improvement: A study of Irish software product companies

    Get PDF
    Software Process Improvement (SPI) aims to understand the software process as it is used within an organisation and thus drive the implementation of changes to that process to achieve specific goals such as increasing development speed, achieving higher product quality or reducing costs. Accordingly, SPI researchers must be equipped with the methodologies and tools to enable them to look within organisations and understand the state of practice with respect to software process and process improvement initiatives, in addition to investigating the relevant literature. Having examined a number of potentially suitable research methodologies, we have chosen Grounded Theory as a suitable approach to determine what was happening in actual practice in relation to software process and SPI, using the indigenous Irish software product industry as a test-bed. The outcome of this study is a theory, grounded in the field data, that explains when and why SPI is undertaken by the software industry. The objective of this paper is to describe both the selection and usage of grounded theory in this study and evaluate its effectiveness as a research methodology for software process researchers. Accordingly, this paper will focus on the selection and usage of grounded theory, rather than results of the SPI study itself

    Quality modeling in electronic healthcare: a study of mHealth Service

    Get PDF
    Information and communication technologies (ICTs) have the potential to radically transform health services in developing countries. Among various ICT driven health platforms, mobile health is the most promising one because of its widespread penetration and cost effective services. This paper aims to examine Quality Modeling in Electronic Healthcare by using PLS based SEM

    Getting your Accounting Right

    Get PDF

    The Right to Dream: Promising Practices Improve Odds for Latino Men and Boys

    Get PDF
    This report is organized around five experiences that define social and economic equity for men and boys of color, which in turn highlight nine priorities that require our attention and investments in order to remove structural barriers to success and allow young Latino men to see a clear path toward a positive future
    • 

    corecore