scholarly journals Analysing Time-Stamped Co-Editing Networks in Software Development Teams using git2net

2021 ◽  
Vol 26 (4) ◽  
Author(s):  
Christoph Gote ◽  
Ingo Scholtes ◽  
Frank Schweitzer
Keyword(s):  
Software Engineering ◽  
Computational Social Science ◽  
Software Project ◽  
High Resolution Data ◽  
Software Repositories ◽  
Fine Grained ◽  
Development Teams ◽  
History Of ◽  
Software Development Teams ◽  
Advance Theory

AbstractData from software repositories have become an important foundation for the empirical study of software engineering processes. A recurring theme in the repository mining literature is the inference of developer networks capturing e.g. collaboration, coordination, or communication from the commit history of projects. Many works in this area studied networks of co-authorship of software artefacts, neglecting detailed information on code changes and code ownership available in software repositories. To address this issue, we introduce , a scalable software that facilitates the extraction of fine-grained co-editing networks in large repositories. It uses text mining techniques to analyse the detailed history of textual modifications within files. We apply our tool in two case studies using repositories of multiple Open Source as well as a proprietary software project. Specifically, we use data on more than 1.2 million commits and more than 25,000 developers to test a hypothesis on the relation between developer productivity and co-editing patterns in software teams. We argue that opens up an important new source of high-resolution data on human collaboration patterns that can be used to advance theory in empirical software engineering, computational social science, and organisational studies.

scholarly journals Design Thinking: Challenges for Software Requirements Elicitation

Information ◽  
2019 ◽  
Vol 10 (12) ◽  
pp. 371 ◽  
Author(s):  
Hugo Ferreira Martins ◽  
Antônio Carvalho de Oliveira Junior ◽  
Edna Dias Canedo ◽  
Ricardo Ajax Dias Kosloski ◽  
Roberto Ávila Paldês ◽  
...  
Keyword(s):  
Design Thinking ◽  
Requirements Elicitation ◽  
Software Requirements ◽  
Agile Methods ◽  
Software Project ◽  
Functional Requirements ◽  
Use Of Data ◽  
Development Teams ◽  
Software Development Teams ◽  
User Workshop

Agile methods fit well for software development teams in the requirements elicitation activities. It has brought challenges to organizations in adopting the existing traditional methods, as well as new ones. Design Thinking has been used as a requirements elicitation technique and immersion in the process areas, which brings the client closer to the software project team and enables the creation of better projects. With the use of data triangulation, this paper brings a literature review that collected the challenges in software requirements elicitation in agile methodologies and the use of Design Thinking. The result gave way to a case study in a Brazilian public organization project, via user workshop questionnaire with 20 items, applied during the study, in order to identify the practice of Design Thinking in this context. We propose here an overview of 13 studied challenges, from which eight presented strong evidence of contribution (stakeholders involvement, requirements definition and validation, schedule, planning, requirement details and prioritization, and interdependence), three presented partial evidence of contribution and two were not eligible for conclusions (non-functional requirements, use of artifacts, and change of requirements). The main output of this work is to present an analysis of the use of Design Thinking to see if it fits properly to be used as a means of solving the challenges of elicitation of software requirements when using agile methods.

scholarly journals Beyond Subjectiviness: Assessing Abilities and Preferences to Create Software Development Teams

2021 ◽  
Author(s):  
Lucas Alves ◽  
Vinícius Ricardo ◽  
Laerte Xavier
Keyword(s):  
Genetic Algorithm ◽  
Software Engineering ◽  
Software Development ◽  
Interpersonal Relationships ◽  
Human Error ◽  
Project Managers ◽  
Specific Task ◽  
Development Teams ◽  
Software Development Teams ◽  
Performance Issues

The creation of software development teams that are affected by performance issues is a problem frequently observed in companies in the software development market. This process is commonly done through subjective methodologies. Such methodologies can be influenced by interpersonal relationships and susceptible to human error. This paper proposes a quantitative and data-oriented alternative to the process of forming workgroups through the use of a genetic algorithm capable of optimizing collaborator’s abilities and preferences when executing a specific task within a project. As a result, we show that the use of such genetic algorithm is able to create teams similar to the teams assembled by the project managers of companies in the industry of software engineering. Therefore, the ability of genetic algorithm on supporting the process of develoment teams assembly becomes evident.

Knowledge at Work in Software Development

2005 ◽  
pp. 312-342
Author(s):  
Luca Iandoli ◽  
Giuseppe Zollo
Keyword(s):  
Knowledge Management ◽  
Software Development ◽  
Management Practices ◽  
Field Analysis ◽  
Software Project ◽  
Software Life Cycle ◽  
Software Applications ◽  
Development Teams ◽  
Software Development Teams ◽  
Methodological Aspects

Knowledge management practices in software development and engineering have been focused mainly on knowledge sharing and maintenance whereas less attention has been devoted to knowledge elicitation and codification issues. In this chapter we present a methodology based on causal mapping for the investigation and management of knowledge created and elaborated by software development teams in the production of new software applications. The chapter focuses on the early stages of the process when development teams have to make a choice regarding the software life cycle model that best fits, given constraints concerning ambiguity of the requirements, risks, costs evaluation and scheduling. A step-by-step application of the proposed methodology to a case study in a software company is presented to provide the reader with examples drawn from the field analysis and illustrates critical methodological aspects. Implications for knowledge management in software project development are then outlined and discussed.

scholarly journals THE AWARENESS NETWORK OF MONITORING AND DISPLAYING ACTIONS OF SOCIAL NETWORKS

2015 ◽  
pp. 95-97
Author(s):  
B.DEENA DIVYA NAYOMI ◽  
FAROOQ MOHAMMED ◽  
V. SANDEEP ◽  
TAMKEEN FATIMA
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Work Practices ◽  
Organizational Setting ◽  
Software Developers ◽  
Social Actors ◽  
Development Teams ◽  
The Social ◽  
Software Development Teams ◽  
Ethnographic Data

The concept of awareness plays a pivotal role in research in Computer-Supported Cooperative Work. Recently, Software Engineering researchers interested in the collaborative nature of software development have explored the implications of this concept in the design of software development tools. A critical aspect of awareness is the associated coordinative work practices of displaying and monitoring actions. This aspect concerns how colleagues monitor one another’s actions to understand how these actions impact their own work and how they display their actions in such a way that others can easily monitor them while doing their own work. we focus on an additional aspect of awareness: the identification of the social actors who should be monitored and the actors to whom their actions should be displayed. We address this aspect by presenting software developers’ work practices based on ethnographic data from three different software development teams. In addition, we illustrate how these work practices are influenced by different factors, including the organizational setting, the age of the project, and the software architecture. We discuss how our results are relevant for both CSCW and Software Engineering researchers.

scholarly journals Adoption challenges of CI/CD methodology in software development teams

2021 ◽  
Author(s):  
Maneka Rajasinghe
Keyword(s):  
Software Engineering ◽  
Sri Lanka ◽  
Process Optimization ◽  
Cost Effective ◽  
Agile Development ◽  
Sri Lankan ◽  
It Industry ◽  
Development Teams ◽  
Continuous Delivery ◽  
Software Development Teams

<p>Continuous Integration and Continuous Delivery (CI/CD) is one of the widely discussed topics in the recent information technology (IT) world within the software engineering and delivery sectors. CI/CD is an Agile based DevOps methodology in software engineering that has proven to help improved quality and efficiency in the software delivery process which results in cost effective and low risk business solutions. With the growing demand in the global IT industry specifically in the DevOps based software engineering, estimated to reach $8 billion by 2022, up from $3.9 billion in 2017 [1], we commonly see that more focus is now being given to process optimization to attain efficiencies. Sri Lanka has always been one of the topmost sought-after destinations for outsourced IT labor in the world and currently employs 115, 000 skilled IT professionals [2] and it is important to include the advancements to process optimization to gain better results and keep up that momentum going. CI/CD being classified in the international IT market an improvement as such, the adoption of CI/CD and its perceived impact among Sri Lankan IT teams were researched. The literature review carried out did not provide much detail based on statistical evidence to understand the current adoption of CI/CD as well as the degree to which it is adopted among the IT teams specific to the Sri Lankan context. If CI/CD is adopted within Sri Lanka already, although undocumented, it was also important to understand what factors impact the adoption rate. Agile development methodologies are often adaptable to suit the best working solutions for teams, companies and even industries, hence there can be major inapplicability when it comes to studying a global set of factors from different contexts impacting the Sri Lankan teams. Building from this, the three top factors stated in international literature, team factors, stakeholder buy-in and complexity were studied, specifically within the Sri Lankan context to evaluate their impact on CI/CD adoption. </p>

scholarly journals Adoption challenges of CI/CD methodology in software development teams

2021 ◽  
Author(s):  
Maneka Rajasinghe
Keyword(s):  
Software Engineering ◽  
Sri Lanka ◽  
Process Optimization ◽  
Cost Effective ◽  
Agile Development ◽  
Sri Lankan ◽  
It Industry ◽  
Development Teams ◽  
Continuous Delivery ◽  
Software Development Teams

<p>Continuous Integration and Continuous Delivery (CI/CD) is one of the widely discussed topics in the recent information technology (IT) world within the software engineering and delivery sectors. CI/CD is an Agile based DevOps methodology in software engineering that has proven to help improved quality and efficiency in the software delivery process which results in cost effective and low risk business solutions. With the growing demand in the global IT industry specifically in the DevOps based software engineering, estimated to reach $8 billion by 2022, up from $3.9 billion in 2017 [1], we commonly see that more focus is now being given to process optimization to attain efficiencies. Sri Lanka has always been one of the topmost sought-after destinations for outsourced IT labor in the world and currently employs 115, 000 skilled IT professionals [2] and it is important to include the advancements to process optimization to gain better results and keep up that momentum going. CI/CD being classified in the international IT market an improvement as such, the adoption of CI/CD and its perceived impact among Sri Lankan IT teams were researched. The literature review carried out did not provide much detail based on statistical evidence to understand the current adoption of CI/CD as well as the degree to which it is adopted among the IT teams specific to the Sri Lankan context. If CI/CD is adopted within Sri Lanka already, although undocumented, it was also important to understand what factors impact the adoption rate. Agile development methodologies are often adaptable to suit the best working solutions for teams, companies and even industries, hence there can be major inapplicability when it comes to studying a global set of factors from different contexts impacting the Sri Lankan teams. Building from this, the three top factors stated in international literature, team factors, stakeholder buy-in and complexity were studied, specifically within the Sri Lankan context to evaluate their impact on CI/CD adoption. </p>

scholarly journals Individual differences limit predicting well-being and productivity using software repositories: a longitudinal industrial study

2021 ◽  
Vol 26 (5) ◽  
Author(s):  
Miikka Kuutila ◽  
Mika Mäntylä ◽  
Maëlick Claes ◽  
Marko Elovainio ◽  
Bram Adams
Keyword(s):  
Individual Differences ◽  
Fixed Effects ◽  
Prediction Models ◽  
Well Being ◽  
Software Project ◽  
Structured Interviews ◽  
Software Developers ◽  
Software Repositories ◽  
Generalized Linear Mixed Effects ◽  
Individualized Prediction

AbstractReports of poor work well-being and fluctuating productivity in software engineering have been reported in both academic and popular sources. Understanding and predicting these issues through repository analysis might help manage software developers’ well-being. Our objective is to link data from software repositories, that is commit activity, communication, expressed sentiments, and job events, with measures of well-being obtained with a daily experience sampling questionnaire. To achieve our objective, we studied a single software project team for eight months in the software industry. Additionally, we performed semi-structured interviews to explain our results. The acquired quantitative data are analyzed with generalized linear mixed-effects models with autocorrelation structure. We find that individual variance accounts for most of the R2 values in models predicting developers’ experienced well-being and productivity. In other words, using software repository variables to predict developers’ well-being or productivity is challenging due to individual differences. Prediction models developed for each developer individually work better, with fixed effects R2 value of up to 0.24. The semi-structured interviews give insights into the well-being of software developers and the benefits of chat interaction. Our study suggests that individualized prediction models are needed for well-being and productivity prediction in software development.

Sign in / Sign up

Export Citation Format

Share Document