A study of emotions in requirements engineering.

Proceedings of: 3rd World Summit on the Knowledge Society (WKKS 2010), September 22-24, 2010, Corfu (Greece)Requirements engineering (RE) is a crucial activity in software development projects. This phase in the software development cycle is knowledge intensive, and thus, human capital intensive. From the human point of view, emotions play an important role in behavior and can even act as behavioral motivators. Thus, if we consider that RE represents a set of knowledge-intensive tasks, which include acceptance and negotiation activities, then the emotional factor represents a key element in these issues. However, the emotional factor in RE has not received the attention it deserves. This paper aims to integrate the stakeholder’s emotions into the requirement process, proposing to catalogue them like any other factor in the process such as clarity or stability. Results show that high arousal and low pleasure levels are predictors of high versioning requirements.Publicad

Using the affect grid to measure emotions in software requirements engineering

Computer systems are designed and used by humans. And human being is characterized, among other things, by emotions. Giving this fact, the process of designing and developing computer systems is, like any other facet in our lives, driven by emotions. Requirements engineering is one of the main phases in software development. In Requirements engineering, several tasks include acceptance and negotiation activities in which the emotional factor represents a key role. This paper presents a study based on the application of affect grid by Russell in requirements engineering main stakeholders: developers and users. Results show that high arousal and low pleasure levels in the process are predictors of conflictive requirements.Publicad

ELICA: An Automated Tool for Dynamic Extraction of Requirements Relevant Information

Requirements elicitation requires extensive knowledge and deep understanding of the problem domain where the final system will be situated. However, in many software development projects, analysts are required to elicit the requirements from an unfamiliar domain, which often causes communication barriers between analysts and stakeholders. In this paper, we propose a requirements ELICitation Aid tool (ELICA) to help analysts better understand the target application domain by dynamic extraction and labeling of requirements-relevant knowledge. To extract the relevant terms, we leverage the flexibility and power of Weighted Finite State Transducers (WFSTs) in dynamic modeling of natural language processing tasks. In addition to the information conveyed through text, ELICA captures and processes non-linguistic information about the intention of speakers such as their confidence level, analytical tone, and emotions. The extracted information is made available to the analysts as a set of labeled snippets with highlighted relevant terms which can also be exported as an artifact of the Requirements Engineering (RE) process. The application and usefulness of ELICA are demonstrated through a case study. This study shows how pre-existing relevant information about the application domain and the information captured during an elicitation meeting, such as the conversation and stakeholders' intentions, can be captured and used to support analysts achieving their tasks.Comment: 2018 IEEE 26th International Requirements Engineering Conference Workshop

Consequences of Unhappiness While Developing Software

The growing literature on affect among software developers mostly reports on the linkage between happiness, software quality, and developer productivity. Understanding the positive side of happiness -- positive emotions and moods -- is an attractive and important endeavor. Scholars in industrial and organizational psychology have suggested that also studying the negative side -- unhappiness -- could lead to cost-effective ways of enhancing working conditions, job performance, and to limiting the occurrence of psychological disorders. Our comprehension of the consequences of (un)happiness among developers is still too shallow, and is mainly expressed in terms of development productivity and software quality. In this paper, we attempt to uncover the experienced consequences of unhappiness among software developers. Using qualitative data analysis of the responses given by 181 questionnaire participants, we identified 49 consequences of unhappiness while doing software development. We found detrimental consequences on developers' mental well-being, the software development process, and the produced artifacts. Our classification scheme, available as open data, will spawn new happiness research opportunities of cause-effect type, and it can act as a guideline for practitioners for identifying damaging effects of unhappiness and for fostering happiness on the job.Comment: 6 pages. To be presented at the Second International Workshop on Emotion Awareness in Software Engineering, colocated with the 39th International Conference on Software Engineering (ICSE'17). Extended version of arXiv:1701.02952v2 [cs.SE

Web-based virtual learning environment (EmoViLe) with emotive interface feature

This study attempts to obtain the user requirements for the EmoViLe during the data collection and to identify the user requirement for the EmoViLE. This VLE will be benefited to the student by improving the user experience and increasing their engagement when using the VLE, and lecturer in helping them to understand their student better and to come out with a better future plan for their learning assessment. The methodology in doing this study are Phase 1 which involved the initial study on the previous work, Phase 2 is the data collection on the user requirement, Phase 3 which involves the design process of the VLE, Phase 4 is the development phase of the VLE and Phase 5 is the testing on the prototype of the VLE. The expected outcome is a prototype of the VLE with the emotive interface feature that can contribute for the improvement and betterment on teaching and learning process between students and lecturer.Keywords: emotions; virtual learning environment; web-based teaching; web-based learning dashboard; Kansei engineering