Exploration and Exploitation of Developers' Sentimental Variations in Software Engineering

2016 ◽  
Vol 4 (4) ◽  
pp. 35-55 ◽  
Author(s):  
Md Rakibul Islam ◽  
Minhaz F. Zibran
Keyword(s):  
Software Engineering ◽  
Empirical Study ◽  
Software Development ◽  
Open Source ◽  
Emotional Awareness ◽  
Exploration And Exploitation ◽  
Software Artifacts ◽  
Bug Fixing ◽  
Different Types

Software development is highly dependent on human efforts and collaborations, which are immensely affected by emotions. This paper presents a quantitative empirical study of the emotional variations in different types of development activities (e.g., bug-fixing tasks), development periods (i.e., days and times) and in projects of different sizes involving teams of variant sizes. The study also includes an in-depth investigation of emotions' impacts on software artifacts (i.e., commit messages) and exploration of scopes for exploiting emotional variations in software engineering activities. This work is based on careful analyses of emotions in more than 490 thousand commit comments across 50 open-source projects. The findings from this work add to our understanding of the role of emotions in software development, and expose scopes for exploitation of emotional awareness in improved task assignments and collaborations.

Exploration and Exploitation of Developers' Sentimental Variations in Software Engineering

2021 ◽  
pp. 1889-1910
Author(s):  
Md Rakibul Islam ◽  
Minhaz F. Zibran
Keyword(s):  
Software Engineering ◽  
Empirical Study ◽  
Software Development ◽  
Open Source ◽  
Emotional Awareness ◽  
Exploration And Exploitation ◽  
Software Artifacts ◽  
Bug Fixing ◽  
Different Types

Software development is highly dependent on human efforts and collaborations, which are immensely affected by emotions. This paper presents a quantitative empirical study of the emotional variations in different types of development activities (e.g., bug-fixing tasks), development periods (i.e., days and times) and in projects of different sizes involving teams of variant sizes. The study also includes an in-depth investigation of emotions' impacts on software artifacts (i.e., commit messages) and exploration of scopes for exploiting emotional variations in software engineering activities. This work is based on careful analyses of emotions in more than 490 thousand commit comments across 50 open-source projects. The findings from this work add to our understanding of the role of emotions in software development, and expose scopes for exploitation of emotional awareness in improved task assignments and collaborations.

scholarly journals Modding as an Open Source Approach to Extending Computer Game Systems

2013 ◽  
pp. 177-188
Author(s):  
Walt Scacchi
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Open Source ◽  
Open Source Software ◽  
Computer Game ◽  
Game Studies ◽  
The World ◽  
The Subject ◽  
Closed Source

This paper examines what is known about the role of open source software development within the world of game mods and modding practices. Game modding has become a leading method for developing games by customizing or creating Open Source Software extensions to game software in general, and particularly to proprietary closed source software games. What, why, and how OSS and closed source software come together within an application system is the subject for this study. Observational and qualitative is used to highlight current practices and issues that can be associated with software engineering and game studies foundations with multiple examples of different game mods and modding practices are identified throughout this study.

scholarly journals EMPIRICAL STUDY OF THE INFLUENCE OF SECONDARY OBJECT AND SPATIAL IMAGERY ON A LITERARY TEXT TRANSLATION

2021 ◽  
pp. 266-273
Author(s):  
Алексей Григорьевич Шипулин
Keyword(s):  
Experimental Data ◽  
Empirical Study ◽  
Negative Correlation ◽  
Literary Text ◽  
Mental Images ◽  
Spatial Imagery ◽  
Low Level ◽  
Different Types ◽  
Moderate Negative Correlation

Статья посвящена исследованию влияния вторичных образов различного типа на перевод художественного текста. Результаты эксперимента подтверждают ведущую роль предметных образов для нахождения адекватных решений. Также показано наличие умеренной обратной корреляции между уровнем образного мышления в целом и количеством неадекватных трансформаций в переводе. Выявлено негативное влияние на результаты перевода низкого пространственного воображения. The article aims to investigate the influence of different types of secondary mental images on literary text translation. Our experimental data confirm a stone role of object imagery for finding adequate translation solutions, as well as suggest a moderate negative correlation between individual imagery scores and the number of inadequate translation solutions. A low level of spatial imagery may negatively affect the translator’s choices.

Is Modeling a Treatment for the Weakness of Software Engineering?

2017 ◽  
pp. 1977-1994
Author(s):  
Janis Osis ◽  
Erika Asnina
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Mathematical Formalism ◽  
Separation Of Concerns ◽  
Model Driven ◽  
Topological Modeling ◽  
System Functioning ◽  
Mathematical Accuracy ◽  
The Way

Experts' opinions exist that the way software is built is primitive. The role of modeling as a treatment for Software Engineering (SE) became more important after the appearance of Model-Driven Architecture (MDA). The main advantage of MDA is architectural separation of concerns that showed the necessity of modeling and opened the way for Software Development (SD) to become engineering. However, this principle does not demonstrate its whole potential power in practice, because of a lack of mathematical accuracy in the initial steps of SD. The question about the sufficiency of modeling in SD is still open. The authors believe that SD, in general, and modeling, in particular, based on mathematical formalism in all its stages together with the implemented principle of architectural separation of concerns can become an important part of SE in its real sense. They introduce such mathematical formalism by means of topological modeling of system functioning.

Is Modeling a Treatment for the Weakness of Software Engineering?

2018 ◽  
pp. 310-327
Author(s):  
Janis Osis ◽  
Erika Asnina
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Mathematical Formalism ◽  
Separation Of Concerns ◽  
Model Driven ◽  
Topological Modeling ◽  
System Functioning ◽  
Mathematical Accuracy ◽  
The Way

Experts' opinions exist that the way software is built is primitive. The role of modeling as a treatment for Software Engineering (SE) became more important after the appearance of Model-Driven Architecture (MDA). The main advantage of MDA is architectural separation of concerns that showed the necessity of modeling and opened the way for Software Development (SD) to become engineering. However, this principle does not demonstrate its whole potential power in practice, because of a lack of mathematical accuracy in the initial steps of SD. The question about the sufficiency of modeling in SD is still open. The authors believe that SD, in general, and modeling, in particular, based on mathematical formalism in all its stages together with the implemented principle of architectural separation of concerns can become an important part of SE in its real sense. They introduce such mathematical formalism by means of topological modeling of system functioning.

Theory Driven Modeling as the Core of Software Development

2021 ◽  
pp. 88-107
Author(s):  
Janis Osis ◽  
Erika Nazaruka (Asnina)
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Separation Of Concerns ◽  
Model Driven ◽  
The Core ◽  
Engineering Discipline ◽  
Topological Modeling ◽  
System Functioning ◽  
Mathematical Accuracy

Some experts opine that software is built in a primitive way. The role of modeling as a treatment for the weakness of software engineering became more important when the principles of Model Driven Architecture (MDA) appeared. Its main advantage is architectural separation of concerns. It showed the necessity of modeling and opened the way for software development to become an engineering discipline. However, this principle does not demonstrate its whole potential power in practice because of lack of mathematical accuracy in the very initial steps of software development. The sufficiency of modeling in software development is still disputable. The authors believe that software development in general (and modeling in particular) based on mathematical formalism in all of its stages and together with the implemented principle of architectural separation of concerns can become an important part of software engineering in its real sense. They propose the formalism by topological modeling of system functioning as the first step towards engineering.

Bug Fixing Practices within Free/Libre Open Source Software Development Teams

2009 ◽  
pp. 1079-1110 ◽  
Author(s):  
Kevin Crowston ◽  
Barbara Scozzi
Keyword(s):  
Software Development ◽  
Open Source ◽  
Open Source Software ◽  
Tracking System ◽  
Distributed Teams ◽  
Distributed Software ◽  
Bug Fixing ◽  
Development Teams ◽  
Bulletin Boards ◽  
Software Development Teams

Free/Libre open source software (FLOSS, e.g., Linux or Apache) is primarily developed by distributed teams. Developers contribute from around the world and coordinate their activity almost exclusively by means of email and bulletin boards, yet some how profit from the advantages and evade the challenges of distributed software development. In this article we investigate the structure and the coordination practices adopted by development teams during the bug-fixing process, which is considered one of main areas of FLOSS project success. In particular, based on a codification of the messages recorded in the bug tracking system of four projects, we identify the accomplished tasks, the adopted coordination mechanisms, and the role undertaken by both the FLOSS development team and the FLOSS community. We conclude with suggestions for further research.

Bug Fixing Practices within Free/Libre Open Source Software Development Teams

2009 ◽  
pp. 797-828
Author(s):  
Kevin Crowston ◽  
Barbara Scozzi
Keyword(s):  
Software Development ◽  
Open Source ◽  
Open Source Software ◽  
Tracking System ◽  
Distributed Teams ◽  
Distributed Software ◽  
Bug Fixing ◽  
Development Teams ◽  
Bulletin Boards ◽  
Software Development Teams

Free/Libre open source software (FLOSS, e.g., Linux or Apache) is primarily developed by distributed teams. Developers contribute from around the world and coordinate their activity almost exclusively by means of email and bulletin boards, yet some how profit from the advantages and evade the challenges of distributed software development. In this article we investigate the structure and the coordination practices adopted by development teams during the bug-fixing process, which is considered one of main areas of FLOSS project success. In particular, based on a codification of the messages recorded in the bug tracking system of four projects, we identify the accomplished tasks, the adopted coordination mechanisms, and the role undertaken by both the FLOSS development team and the FLOSS community. We conclude with suggestions for further research.

Comparing Software Bugs in Clone and Non-clone Code: An Empirical Study

2017 ◽  
Vol 27 (09n10) ◽  
pp. 1507-1527
Author(s):  
Judith F. Islam ◽  
Manishankar Mondal ◽  
Chanchal K. Roy ◽  
Kevin A. Schneider
Keyword(s):  
High Risk ◽  
Empirical Study ◽  
Software Development ◽  
Comparative Study ◽  
Software Maintenance ◽  
Statistical Significance ◽  
Ongoing Debate ◽  
Software Bugs ◽  
Bug Fixing

Code cloning is a recurrent operation in everyday software development. Whether it is a good or bad practice is an ongoing debate among researchers and developers for the last few decades. In this paper, we conduct a comparative study on bug-proneness in clone code and non-clone code by analyzing commit logs. According to our inspection of thousands of revisions of seven diverse subject systems, the percentage of changed files due to bug-fix commits is significantly higher in clone code compared with non-clone code. We perform a Mann–Whitney–Wilcoxon (MWW) test to show the statistical significance of our findings. In addition, the possibility of occurrence of severe bugs is higher in clone code than in non-clone code. Bug-fixing changes affecting clone code should be considered more carefully. Finally, our manual investigation shows that clone code containing if-condition and if–else blocks has a high risk of having severing bugs. Changes to such types of clone fragments should be done carefully during software maintenance. According to our findings, clone code appears to be more bug-prone than non-clone code.

Sign in / Sign up

Export Citation Format

Share Document