scholarly journals Intercultural Communication and Management Factors and Their Impact to the Process of Global Software Development for Virtual and Non-Virtual Teams

2014 ◽  
Vol 6 (1) ◽  
pp. 5-16
Author(s):  
Germinal Isern

Abstract This position paper presents the factors involved in the successful software development and what is the impact of some methodologies like Agile in this process. Global software development projects may be a total success or an anticipated disaster for simple reasons that usually have nothing to do with the technology involved, with the time differences, or the product being built, but because of subtle intercultural factors. How do the language, the race, the gender, the religion, and the location affects the software development process from analysis and design to implementation, testing and maintenance? Do all these factors impact in the same way if we are working with a local team, and offshore development team or even a global virtual team? Is any specific software development methodology better suited for your particular case? How could you decide what’s the better approach? What will be the results and what our goals? The issues at stake are not superficial matters of the ways how people dress, or how clear do they speak in our local language, or what they like to eat, or their small daily behaviors, but are based in the fundamental differences in the systems of values that govern our lives. So institutions, corporations and global companies have to raise the level of awareness of their employees worldwide on the cultural differences, through various programs for intercultural or diversity training. But this poor model of cultural awareness is not enough to overcome some of the obstacles that intercultural differences bring to the table. So this paper will list and describe this important intercultural factors that directly impact in the software development process and how certain software development methodologies could be used in order to have a more systematic look or set of guidelines that would allow the team managers to evaluate and to decide how theuse of each one of these software development methodologies for local teams, non local teams and virtual teams will affect positively or negatively the outcomes of software development practices.

Sensors ◽  
2021 ◽  
Vol 21 (10) ◽  
pp. 3480
Author(s):  
Walter Takashi Nakamura ◽  
Iftekhar Ahmed ◽  
David Redmiles ◽  
Edson Oliveira ◽  
David Fernandes ◽  
...  

The success of a software application is related to users’ willingness to keep using it. In this sense, evaluating User eXperience (UX) became an important part of the software development process. Researchers have been carrying out studies by employing various methods to evaluate the UX of software products. Some studies reported varied and even contradictory results when applying different UX evaluation methods, making it difficult for practitioners to identify which results to rely upon. However, these works did not evaluate the developers’ perspectives and their impacts on the decision process. Moreover, such studies focused on one-shot evaluations, which cannot assess whether the methods provide the same big picture of the experience (i.e., deteriorating, improving, or stable). This paper presents a longitudinal study in which 68 students evaluated the UX of an online judge system by employing AttrakDiff, UEQ, and Sentence Completion methods at three moments along a semester. This study reveals contrasting results between the methods, which affected developers’ decisions and interpretations. With this work, we intend to draw the HCI community’s attention to the contrast between different UX evaluation methods and the impact of their outcomes in the software development process.


Author(s):  
Andreza Vieira ◽  
Franklin Ramalho

The Model-Driven Development (MDD) approach shifts the focus on code to models in the software development process. In MDD, model transformations are elements that play an important role. MDD-based projects evolve along their lifecycle in a way that changes in their transformations are frequent. Before applying changes it is important to measure their impacts within the transformation. However, currently no technique helps practitioners in this direction. We propose an approach to measure the change impact in ATL model transformations. Based on static analysis, it detects the elements impacted by a change and calculates the change impact value through three metrics we defined. By using our approach, practitioners can (i) save effort and development time since the elements impacted with the change are automatically detected and (ii) better schedule and prioritize changes according to the impact value. To empirically evaluate our approach we conducted a case study.


Author(s):  
Rory O’Connor ◽  
Shuib Basri

This article identifies the effect of team dynamics in the context of software development teams and its impact on software process improvement (SPI) activities in very small companies, in order to understand the relationship between these two variables. Most software development work is done by teams of software engineers working together in a collaborative manner to execute a software development process. Although there is much literature examining software process and how to improve it, less attention has been paid to the issues of team-working and specifically the impact of team dynamics on the software development process. Team dynamics is the term used to define how people work and interact together in teams. Teamwork is more effective with the existence of positive team dynamic, as it encourages a better working environment with satisfied, fulfilled employees who will in turn be more productive. This paper presents the results of a research study of team dynamics in very small software development companies and its impact on the software development process and software process improvement activities.


UML class model is an essential element of today's software development process. In modern software development methodologies, it is considered a key contributor in every phase of software development. It may be automatically converted into other UML models and even in programming code. However, the erroneous model generates other erroneous models. The model verification technique checks the presence of error in the UML class model. This paper's main objective is to introduce a technique for the completely automatic and expressive transformation of the UML class model's qualified association into ontology. Because the current verification method does not support the transformation and verification of qualified associations. Later on, the ontology-based reasoning method is presented to verify qualified associations and their constraints.


Sign in / Sign up

Export Citation Format

Share Document