282 research outputs found

    A four stage approach towards speeding GitHub OSS development

    Get PDF
    Many open source software (OSS) project creators adopt GitHub as their chosen online repository. They seek out others within the global OSS community of developers. Such community developers are then encouraged to add their capabilities, ideas and coding into a creator’s developing OSS project. A structural equation modelling study of three top OSS programming languages deploys GitHub’s operational elements as a four stage directional suite of (1) dependent, (2) intermediaries, and (3) independent elements. It shows a project’s activity levels can be enhanced when additional project contributions are effectively stage-wise pursued. A staged development approach helps creators understand the process of attracting OSS developers into a creator’s GitHub project

    The Impact of Agile Methodology on Software Team’s Work-Related Well-Being

    Get PDF
    Agile methodology is people-oriented.However, little evidence demonstrates the methodology effectiveness on humanistic aspects.Work-related well-being is measured to what extent the agile methodology can give impact on anxiety, contentment, depression, and enthusiasm level among software engineering (SE) teams.This paper aims to investigate empirically the effect of agile methodology on software development team’s work-related well-being.To achieve this goal, a comparison study was carried out in an academic setting. A quantitative approach using statistical analysis was used to investigate the effect. Results showed that agile does not significantly affect work-related well-being.Nonetheless, the team that is able to apply the agile practices as closely as possible experienced higher level of enthusiasm during software project.This study provides additional empirical data in software engineering research and practices specifically on human aspects.Further investigation needs to be carried out on the software projects with higher task complexity

    Annual Report, 2013-2014

    Get PDF
    Beginning in 2004/2005- issued in online format onl

    Action-based recommendation in pull-request development

    Get PDF
    Pull requests (PRs) selection is a challenging task faced by integrators in pull-based development (PbD), with hundreds of PRs submitted on a daily basis to large open-source projects. Managing these PRs manually consumes integrators' time and resources and may lead to delays in the acceptance, response, or rejection of PRs that can propose bug fixes or feature enhancements. On the one hand, well-known platforms for performing PbD, like GitHub, do not provide built-in recommendation mechanisms for facilitating the management of PRs. On the other hand, prior research on PRs recommendation has focused on the likelihood of either a PR being accepted or receive a response by the integrator. In this paper, we consider both those likelihoods, this to help integrators in the PRs selection process by suggesting to them the appropriate actions to undertake on each specific PR. To this aim, we propose an approach, called CARTESIAN (aCceptance And Response classificaTion-based requESt IdentificAtioN) modeling the PRs recommendation according to PR actions. In particular, CARTESIAN is able to recommend three types of PR actions: accept, respond, and reject. We evaluated CARTESIAN on the PRs of 19 popular GitHub projects. The results of our study demonstrate that our approach can identify PR actions with an average precision and recall of about 86%. Moreover, our findings also highlight that CARTESIAN outperforms the results of two baseline approaches in the task of PRs selection

    Blinded by Simplicity: Locating the Social Dimension in Software Development Process Literature

    Get PDF
    The software development process is a complex human, intellectual and labor-intensive activity and human related factors have shown to be the most significant contributors to software system failures. Lacking the ability to identify or quantify these factors, software practitioners will not learn from the failures caused by them. Although, social factors give rise to high failure rates in software development projects they tend to be ignored. Business continues as usual. The inability for software engineers to attain a holistic and inclusive approach will leave the social dimension out and undermine the realization of a fully sustainable software development process.This paper builds on the master’s thesis with the same title completed in December 2019 at Stockholm University. The thesis demonstrates how research literature on software development processes addresses (or not) the social dimension of sustainability from a holistic point of view. The results indicate that the practice of dealing holistically with complexity including the social dimension is still underdeveloped. Further research is suggested regarding the development of adequate supporting tools, social skills, and managerial attitudes and behaviors

    Annual Report, 2017-2018

    Get PDF

    NIAS Annual Report 2022-2023

    Get PDF
    • …
    corecore