OSS developers context-specific Preferred Representational systems: A initial Neurolinguistic text analysis of the Apache mailing list

Colaço, Methanias; Mendonça, Manoel; Farias, Mário André de Freitas; Henrique, Paulo

doi:10.1109/msr.2010.5463339

Cited by 6 publications

(3 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In reviewing these two streams of work, it is evident that some researchers have looked to infer the semantics of practitioners' dialogues from the text they communicated (e.g., [22,23]), while others have provided deductions based on communication frequency information [4,20]. While text analysis methods and their associated tools have been used previously to understand and predict some aspects of software development [24,25], only a few studies in this domain have considered examining software teams' internal behavioral processes as represented in their members' textual communications. This is in spite of the fact, as noted by Bacchelli et al [22], that natural language analysis techniques have proved to be effective in generating understandings of software developers' attitudes when applied to their language processes.…”

Section: The Study Of Team Communicationmentioning

confidence: 99%

Understanding the attitudes, knowledge sharing behaviors and task performance of core developers: A longitudinal study

Licorish

MacDonell

2014

Information and Software Technology

View full text Add to dashboard Cite

Context: Prior research has established that a few individuals generally dominate project communication and source code changes during software development. Moreover, this pattern has been found to exist irrespective of task assignments at project initiation. Objective: While this phenomenon has been noted, prior research has not sought to understand these dominant individuals. Previous work considering the effect of team structures on team performance has found that core communicators are the gatekeepers of their teams' knowledge, and the performance of these members was correlated with their teams' success. Building on this work, we have employed a longitudinal approach to study the way core developers' attitudes, knowledge sharing behaviors and task performance change over the course of their project, based on the analysis of repository data. Method: We first used Social Network Analysis (SNA) and standard statistical analysis techniques to identify and select artifacts from ten different software development teams. These procedures were also used to select central practitioners among these teams. We then applied psycholinguistic analysis and directed content analysis (CA) techniques to interpret the content of these practitioners' messages. Finally, we inspected these core developers' activities as recorded in system change logs at various points in time during systems' development. Results: Among our findings, we observe that core developers' attitudes and knowledge sharing behaviors were linked to their involvement in actual software development and the demands of their wider project teams. However, core developers appeared to naturally possess high levels of insightful characteristics, which became evident very early during teamwork. Conclusion: Project performance would likely benefit from strategies aimed at surrounding core developers with other competent communicators. Core developers should also be supported by a wider team who are willing to ask questions and challenge their ideas. Finally, the availability of adequate communication channels would help with maintaining positive team climate, and this is likely to mitigate the negative effects of distance during distributed developments.

show abstract

Section: The Study Of Team Communicationmentioning

confidence: 99%

Understanding the attitudes, knowledge sharing behaviors and task performance of core developers: A longitudinal study

Licorish

MacDonell

2014

Information and Software Technology

View full text Add to dashboard Cite

show abstract

“…While such methods and their associated tools have been used previously to understand and predict some aspects of software development [19], only a few studies in this domain have considered examining teams' internal behavioral processes from developers' textual communication. This is in spite of the fact, as noted by Bacchelli et al [17], that natural language analysis techniques have proved to be effective in generating understanding of software developers' language processes.…”

Section: Theoretical Background Related Work and Research Questionsmentioning

confidence: 99%

What Can Developers' Messages Tell Us? A Psycholinguistic Analysis of Jazz Teams' Attitudes and Behavior Patterns

Licorish

MacDonell

2013

2013 22nd Australian Software Engineering Conference

View full text Add to dashboard Cite

Reports that communication and behavioral issues contribute to inadequately performing software teams have fuelled a wealth of research aimed at understanding the human processes employed during software development. The increasing level of interest in human issues is particularly relevant for agile and global software development approaches that emphasize the importance of people and their interactions during projects. While mature analysis techniques in behavioral psychology have been recommended for studying such issues, particularly when using archives and artifacts, these techniques have rarely been used in software engineering research. We utilize these techniques under an embedded case study approach to examine whether IBM Rational Jazz practitioners' behaviors change over project duration and whether certain tasks affect teams' attitudes and behaviors. We found highest levels of project engagement at project start and completion, as well as increasing levels of team collectiveness as projects progressed. Additionally, Jazz practitioners were most insightful and perceptive at the time of project scoping. Further, Jazz teams' attitudes and behaviors varied in line with the nature of the tasks they were performing. We explain these findings and discuss their implications for software project governance and tool design.

show abstract

“…Colaço Júnior et al 11 describe that the way that software engineers process resources like diagrams and nonconventional visualization metaphors impacts on the success of that processing for both, text and diagrams. The article points out that other studies do not evaluate what types of representational systems (RS) are the preferred by software engineers.…”

Section: Related Workmentioning

confidence: 99%

Multimedia resources as a support for requirements engineering and software maintenance

Santos

Júnior

Andrade

2020

J Software Evolu Process

View full text Add to dashboard Cite

Textual documentations are frequently used in the software development process to outline features and behaviors of an application. For some people, textual descriptions may not be enough to understand what is being developed. In this scenario, multimedia resources appear as an option for software documentation, providing other ways to observe and interpret information.ObjectiveTo identify and characterize the approaches and techniques which promote the use of multimedia in requirements engineering (RE) to support software development and maintenance.MethodA systematic mapping was conducted to find the primary studies in the literature and collect evidence for directing future research.ResultsOnly 27.66% of the approaches found validated their solutions through controlled experiments, showing the need to increase the use of scientific method in this area, with replications of studies that will allow to evaluating if other researchers independently will come up with the same results. In this context, the approaches/techniques identified were TRECE, MURMER, Wiki System Multimedia, Storytelling, Virtual World Environment, VisionCatcher, PRESTO4U, ReqVidA, CrowdRE, AVW, The Software Cinema Technique, Dolli Project, UTOPIA, and approaches without explicit names, which, as a rule, use multimedia resources as an additional support.ConclusionsThere was a favorable consensus regarding the use of multimedia in RE. The selected studies demonstrated to be favorable to the adoption of media to persist and store the requirements of a system. Moreover, multimedia resources can improve the process of understanding the code and decrease evolution and maintenance costs.General terms are design, documentation, experimentation, human factors, multimedia, reliability, software engineering, verification, and security.

show abstract

OSS developers context-specific Preferred Representational systems: A initial Neurolinguistic text analysis of the Apache mailing list

Cited by 6 publications

References 12 publications

Understanding the attitudes, knowledge sharing behaviors and task performance of core developers: A longitudinal study

Understanding the attitudes, knowledge sharing behaviors and task performance of core developers: A longitudinal study

What Can Developers' Messages Tell Us? A Psycholinguistic Analysis of Jazz Teams' Attitudes and Behavior Patterns

Multimedia resources as a support for requirements engineering and software maintenance

Contact Info

Product

Resources

About