Exploring prioritization through systematic literature surveys and case studies <s> Synthesis of literature findings <s> Requirements prioritization is recognized as an important but challenging activity in software product development. For a product to be successful, it is crucial to find the right balance among competing quality requirements. Although literature offers many methods for requirements prioritization, the research on prioritization of quality requirements is limited. This study identifies how quality requirements are prioritized in practice at 11 successful companies developing software intensive systems. We found that ad-hoc prioritization and priority grouping of requirements are the dominant methods for prioritizing quality requirements. The results also show that it is common to use customer input as criteria for prioritization but absence of any criteria was also common. The results suggests that quality requirements by default have a lower priority than functional requirements, and that they only get attention in the prioritizing process if decision-makers are dedicated to invest specific time and resources on QR prioritization. The results of this study may help future research on quality requirements to focus investigations on industry-relevant issues. <s> BIB001 </s> Exploring prioritization through systematic literature surveys and case studies <s> Synthesis of literature findings <s> Requirement prioritization creates an implementation ordering of large wishes of diverse stakeholders of software systems. It results in delivering software functionality in increments. Implementation of new or changed requirements in each increment at code level, might affect other parts of source code representing other implemented requirements. New requirements need to be tested along with testing the affected parts of code (regression testing). To investigate the impact of requirement prioritization on regression testing, a multilayered hybrid regression testing approach was employed on unsuccessful and successful versions of the same embedded type project. Results indicate that regression testing of evolving software is directly related to the effectiveness of the requirement prioritization process and assigned priorities. By improving requirement prioritization process, correctness of priorities enhances, thereby improving regression testing process of evolving software. Keywords: Requirement Prioritization, Regression Testing, Impact Analysis, Fault Detection Rate. <s> BIB002
The papers extracted from literature are discussed in previous section and summarized in Tables 3 and 4 . The extraction must be synthesized so as to generate answers to the four research questions ("Research questions"). RQ 1. How is the area of reprioritization treated with respect to the area of prioritization? All the extracted papers are related to reprioritization activity, with few giving conceptual models and the remaining presenting new techniques. Conceptual models and new techniques establish the difference between reprioritization and prioritization. The papers given in Table 3 do not highlight the problems that confront the reprioritization activities. Possible unidentified problems could be as follows: • The conceptual models are silent on considering already prioritized requirements for reprioritization. BIB002 reported that there is a direct impact between requirement prioritization and regression testing. To achieve the objective of lesser costs attributable to minimization of regression testing, the requirement priorities should reflect the current market trends. • The conceptual models are silent on reprioritization involving a change in priorities of decision aspects. This is due to the finding of  that decision aspects are subjected to reprioritization to have accuracy in implementation set of the requirements. • Reprioritization should focus on the views of developers as many non functional requirements are better prioritized by the developers rather than the clients. BIB001 , after the analysis of eleven software developing firms, reported that prioritization of quality requirements are a neglected activity. Quality requirements are taken as low priority requirements and the main stress is on implementing functional ones. • The reprioritization techniques must focus on minimizing the reprioritization efforts. An increase in the efforts mean increase in delivery time and costs. An increase in the values of these parameters is not acceptable in either bespoke and market driven developments. The reprioritization techniques have to execute on the larger set of inputs, than those operated in earlier increment. The reprioritization process should be able to handle large number of Table 3 Literature work of papers related to conceptual models S. no. Paper reference Findings and deliverable