REQUIREMENTS PRIORITIZATION

Software Requirements Prioritization



Abstract

The article presents a valuation of discrete methods for prioritizing software requirement. Prioritization is a vital necessity towards making the right choice for software production. A variety of characteristics of functionality are measured, like importance, risk, cost, and many more. Prioritization judgments are taken by stakeholders, as well as requirements engineer, customer representatives, user representatives, architects, system testers, and subject matter experts. Other stakeholders that also require being concerned in desires prioritization include operators, maintainers, safety engineers, security analysts, and any others that have an important stake in the preparation of requirements execution.

Keywords: Requirements, prioritising; evaluation.

Software Requirements Prioritization

Introduction

In everyday life, when we buy software products they are so many things to consider. We think about the brand, size, texture, longevity and durability. There are so many competitors in the world these days, so everyone, applies something new and unique when producing their own software. For example in the computer gaming industry, competitors such as Electronic Arts and Rockstar Games constantly compete in their high end ultra modern interactive games constantly creating something different to dwarf their counterparts. When these gaming companies are developing these software's they have to think in mind of if the software meets the consumer's needs, is cost effective, could be done on a time scale and nor run into a problem in production.

Onion Diagram

Saunders et al (2007) defined epistemology as the study of the nature of knowledge. He explains that this study focus on analysing nature of knowledge in relation to justification and belief. This concept also deals with the production of knowledge, as well as scepticism about knowledge claims. The following paper follows the inductive research approach in this paper.

Research Method

This research is going to utilize the qualitative method of research. The data in the study has been collected through the "secondary" methodology and has been used to perform the investigation. The "secondary" analysis has also been done through researching, studying and reproducing the literature from various articles, journals, cases and available literature.

Data Collection Method

The majority of variables are secondary data extracted from existing obstetrical databases such as Sage, EBSCOhost, and other online libraries including Babson Library.

Validity of Finding

This research focuses on the up to date journals and publications for the following research.

Finding/Results

The feature of software merchandise is essentially determined by the capability, to assure the requirements of consumers and clients (B. Bergman et al 2003). Software needs have been of considerable significance in software expansion; however, there has been little growth to date, either hypothetical or practical, on the methods for prioritizing software requirements.

Similarly, if it does not match the customer requirements and undesirable software implemented whether the product is checked and tested million times, the final result depends on the customer choice, and that the product will not implemented. Now, the main function of prioritization that assists to recognize the most critical needs required to in shape customer and stakeholders fulfilment.

Prioritization has an improvement over competitors, stable, ordered plan, value, cost and time taken to complete the ...