Personality requirements in requirement engineering of web development: A systematic literature review

Askarinejadamiri, Zahra

doi:10.1109/icwr.2016.7498465

Cited by 11 publications

(6 citation statements)

References 29 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…decision support systems [26]), human aspects (e.g. personality [27], culture [28]), and even empirical methods [29]. Here, we discuss a few secondary studies that target requirements quality.…”

Section: Introductionmentioning

confidence: 99%

Empirical research on requirements quality: a systematic mapping study

et al. 2022

View full text Add to dashboard Cite

Research has repeatedly shown that high-quality requirements are essential for the success of development projects. While the term “quality” is pervasive in the field of requirements engineering and while the body of research on requirements quality is large, there is no meta-study of the field that overviews and compares the concrete quality attributes addressed by the community. To fill this knowledge gap, we conducted a systematic mapping study of the scientific literature. We retrieved 6905 articles from six academic databases, which we filtered down to 105 relevant primary studies. The primary studies use empirical research to explicitly define, improve, or evaluate requirements quality. We found that empirical research on requirements quality focuses on improvement techniques, with very few primary studies addressing evidence-based definitions and evaluations of quality attributes. Among the 12 quality attributes identified, the most prominent in the field are ambiguity, completeness, consistency, and correctness. We identified 111 sub-types of quality attributes such as “template conformance” for consistency or “passive voice” for ambiguity. Ambiguity has the largest share of these sub-types. The artefacts being studied are mostly referred to in the broadest sense as “requirements”, while little research targets quality attributes in specific types of requirements such as use cases or user stories. Our findings highlight the need to conduct more empirically grounded research defining requirements quality, using more varied research methods, and addressing a more diverse set of requirements types.

show abstract

Section: Introductionmentioning

confidence: 99%

Empirical research on requirements quality: a systematic mapping study

et al. 2022

View full text Add to dashboard Cite

show abstract

“…Personality impacts have been extensively studied in software teams [61], including impact on requirements engineering [62], coding and pair programming [63], and testing [64]. The impact of personality on multi-disciplinary teams, especially those involved in DI solution development, is little explored to date [65].…”

Section: Literature Related To Findingsmentioning

confidence: 99%

Dealing with Data Challenges when Delivering Data-Intensive Software Solutions

Graetsch¹,

Khalajzadeh²,

Shahin³

et al. 2022

Preprint

View full text Add to dashboard Cite

The predicted increase in demand for data-intensive solution development is driving the need for software, data, and domain experts to effectively collaborate in multi-disciplinary data-intensive software teams (MDSTs). We conducted a socio-technical grounded theory study through interviews with 24 practitioners in MDSTs to better understand the challenges these teams face when delivering data-intensive software solutions. The interviews provided perspectives across different types of roles including domain, data and software experts, and covered different organisational levels from team members, team managers to executive leaders. We found that the key concern for these teams is dealing with data-related challenges. In this paper, we present the theory of dealing with data challenges to explain the challenges faced by MDSTs including gaining access to data, aligning data, understanding data, and resolving data quality issues; the context in and condition under which these challenges occur, the causes that lead to the challenges, and the related consequences such as having to conduct remediation activities, inability to achieve expected outcomes and lack of trust in the delivered solutions. We also identified contingencies or strategies applied to address the challenges including high-level strategic approaches such as implementing data governance, implementing new tools and techniques such as data quality visualisation and monitoring tools, as well as building stronger teams by focusing on people dynamics, communication skill development and cross-skilling. Our findings have direct implications for practitioners and researchers to better understand the landscape of data challenges and how to deal with them.

show abstract

“…This framework can save efforts in requirement elicitation process as compared to other techniques. Askarinejadamiri [24] Studied and focused on effective personality in the field of web development during requirement elicitation. They proposed that web development has some relationship of human personality with RE and there is more that can be identified as other human aspects in RE process.…”

Section: Related Workmentioning

confidence: 99%

Role of Human Aspects on the process of Software Requirement Elicitation

Rizvi¹,

Yang²,

Mahmood³

2022

IJEME

View full text Add to dashboard Cite

Requirement elicitation(RE) process requires collaboration with people of different backgrounds and expertise. Collaboration between diverse teams such as developers, testers, designers, requirement engineers, and stakeholders makes requirement elicitation process highly human dependent. The main goal of this research is to find out the role and importance of "human aspects" such as domain knowledge, motivation, communication skills, gender, age personality, attitude, geographical distribution, emotions, and cultural diversity in requirement elicitation activities. The purpose of this study is to identify the industrial perspectives of key human aspects that will help organizations to carry out RE-related activities more effectively. To fulfill that purpose, we surveyed 165 software practitioners and elicited the industrial perspective through their responses. Practitioner's data revealed that requirement elicitation activities are highly human-dependent, 90% of practitioners were of the view that the success of requirement engineering activities depends on the individuals engaged in those activities. Software practitioner's data revealed that domain knowledge (84%), motivation (68%), communication skills (61%), and personality (41%) are the highly important aspect for the individual engaged in requirement engineering activities. Furthermore, the data revealed that the correctness (73%) of identified requirements is a highly important factor in measuring the performance of the person involved in the RE process. Simultaneously, the clarity (78%) and the completeness (75%) of identified requirements are also important. Our results suggest that the individual engaged in the requirement engineering process should have the social and collaborative (89%), enthusiastic (94%), altruistic (kind, generous, trustworthy, and helpful) (67%) qualities to be able to carry out RE activities effectively. Our survey suggests that the practitioners may consider the findings of this research appropriately when forming, managing teams, and conducting software requirement elicitation activities.

show abstract

Personality requirements in requirement engineering of web development: A systematic literature review

Cited by 11 publications

References 29 publications

Empirical research on requirements quality: a systematic mapping study

Empirical research on requirements quality: a systematic mapping study

Dealing with Data Challenges when Delivering Data-Intensive Software Solutions

Role of Human Aspects on the process of Software Requirement Elicitation

Contact Info

Product

Resources

About