Context. Prioritization is essential part of requirements engineering, software release planning and many other software engineering disciplines. Cumulative Voting (CV) is known as relatively simple method for prioritizing requirements on a ratio scale. Historically, CV has been applied in decision making in government elections, corporate governance, and forestry. CV prioritization results are special type of data - compositional data. Any analysis of CV results must take into account the compositional nature of the CV results. Objectives. The purpose of this study is to aid decision making by collecting knowledge on the empirical use of CV and developing a method for detecting prioritization items with equal priority. Methods. We present a systematic literature review of CV and CV result analysis methods. The review is based on search in electronic databases and snowball sampling of the primary studies. Relevant studies are selected based on titles, abstracts, and full text inspection. Additionally, we propose Equality of Cumulative Votes (ECV) { a CV result analysis method that identifies prioritization items with equal priority. Results. CV has been used in not only in requirements prioritization and release planning but also in software process improvement, change impact analysis, model drive software development, etc. The review has resulted in a collection of state of the practice studies and CV result analysis methods. CV results can be analysed to detect stakeholder satisfaction and disagreement, see how the priorities differ among prioritization perspectives and stakeholder groups. ECV has been applied to 27 prioritization cases from 14 studies and has identified nine groups of equal items in three studies. Conclusions. We believe that collected studies and CV result analysis methods can help the adoption of CV prioritization method. The evaluation of ECV indicates that it is able to detect prioritization items with equal priority.

Prioritization of software requirements is an important part of the requirements engineering process within the industry of software development. There are many different methods for achieving the most optimal order of software requirements, a list that shows in what order the requirements should be implemented. This degree project utilizes the SMT-based solver Z3 for an interactive prioritization algorithm. Previous studies have shown good results with another SMT-based solver called Yices. With the newer Z3 from Microsoft, the results have been improved further, and the tool is based on Python, and the framework for Z3 is called Z3PY. Experiments have been conducted on a set of different software requirements derived from a project in the healthcare industry and show that the Z3 solution is, in general, improving the requirements prioritization compared to other mentioned solutions in the study that has been tested on the same set of requirements. Results show that the Z3 solution outperformed the other SMT-based solution Yices by 2-4% regarding disagreement and by 3% regarding average distance. The results are significantly improved based on an ANOVA test with a p-value <= 0.05.

Background and Motivation. Requirements engineering is decision intensiveand involves many roles and stakeholders. As humans are often subjective in theirdecision-making and biased by subjective criteria, we are interested in exploring howthis impacts requirements prioritization. Each requirements prioritization techniquehas its advantages and limitations to use on software products for single/multiplepurposes in the software field. Understanding how human aspects affect requirementsprioritization remains greatly unexplored. Objectives. This thesis aims to understand how human factors impact requirementsprioritization. The primary goal is to address and understand the various human as-pects that affect people when they make decisions. The secondary goal is to identifyvarious human aspects that receive more attention while prioritizing requirements. Methods. Systematic Literature Review (SLR) and survey were chosen as the re-search methods for this thesis. A snowballing method was used to extract empiricalresearch papers that were used for implementing the survey questionnaire. Each em-pirical paper from snowballing method has identified some human aspects throughone or more prioritization techniques and prioritization criteria. Using these humanaspects as input a survey questionnaire is designed for gaining insights on occur-rences/experiences of these human aspects in a large organization of Agile practi-tioners. Results. From the literature review, we identified 21 papers through the snow-balling method. And we identified more than two human aspects from each SLRpaper that impact requirements prioritization that were grouped into 11 categories.We also discovered many requirements prioritization techniques and their criteriawhere we included the top 15 RP techniques, 11 human aspects, and 17 RP cri-teria in the web-based survey questionnaire that were extracted through the SLRapproach. Our survey respondents considered the human aspects as very importantare Domain Knowledge of Individuals/ Stakeholders/ Analysts; Ability to consid-er/understand multiple perspectives; Ability to build/reach Consensus; Cognitiveskills and Limitations; Group Cohesion/ Team Maturity; and Accept Diversity as-pects as having the largest impact when prioritizing requirements. We have alsodiscovered that Emotions/ Emotional Cohesion which is also rated by the surveyrespondents as very important and is having the least impact as a human aspectwhen prioritizing requirements. Conclusions. Our study focus on the human aspects in requirements prioritizationmethod, the actual human aspects are least graded and human behavior that is con-sidered as an human aspect is highly graded by the practitioners in the survey. So aclear map is needed to identify the human aspect bias for requirements prioritizationand the results of this study can be helpful to all the researchers who want to carryour research on requirements prioritization in relation with human aspects.

Context This thesis verifies a method developed on alignment issues in different data points and is useful to validate the method in those data points. To find the alignment/misalignment problems occurring within the stakeholders in a company is done through surveys using Hierarchical Cumulative Voting (HCV). This paper presents a case study to explain the importance of alignment between the stakeholders to achieve quality. Time, scope and cost are given higher priority leaving quality as it is hard to measure. To maintain quality in a software product is a major challenge in most of the software organizations. Stakeholders play a major role in software development. Without the alignment and common understanding between the stakeholders, it is highly difficult to achieve successful software project with good quality. The reasons for misalignment/alignment between the stakeholders are being explained clearly in this thesis based on the interviews and the survey conducted in software development companies under the novelty of case study. Objectives To evaluate the usefulness of alignment approach in different data points, to achieve product quality, for understanding the reasons for misalignment and to provide common approach for aligning we need to know the actual aligning priorities given by the stakeholders. We have one method for aligning and we want to see how actual alignment is different in different data points. To find the reasons for different stakeholders’ groups focusing on different quality attributes and to manage quality that helps in aligning quality requirements in future. Methods In order to know the importance of quality, prioritization of requirements and about the alignment problem we have conducted the literature review. To understand the problem and to know the reasons for misalignment in the companies we have conducted a case study in which we interviewed 8 employees from a company and to know the individual ranking of quality attributes we also made use of surveys in which 17 individuals from two companies had participated. Results We have identified the reasons for misalignment using interviews in one company and the individual priorities given to different quality attributes through surveys in two different companies. The qualities are prioritized by the stakeholder groups in the surveys and these are used to calculate the alignment/misalignment between the groups using spearman rank correlation which pointed that there are some disagreements between the stakeholder groups. Conclusions This paper explains the results obtained from a case study for determining the alignment/misalignment between different stakeholder groups and the reasons for this situation. Through surveys we found that there is a strong disagreement between the stakeholders in one company and partial agreement in the other company with respect to priorities they assign to individual qualities and the reasons behind this are obtained through interviews. The reasons for misalignment are lack of common understandings between the stakeholders, less discussion on quality requirement, undocumented priorities, no importance given to quality and others. / This Thesis work is about Software Product Quality and how it is achieved through alignment between the people in understanding the requirements. / 0763138272, 0739849383