An Approach for Managing Large-Sized Software Requirements During Prioritization
Muhammad Huzaifa Yaseen, Aida Mustapha, Noraini Ibrahim
Abstract
Muhammad Huzaifa Yaseen, Aida Mustapha, Noraini Ibrahim
Abstract
Requirements prioritization is very vital and difficult phase during requirement management phase of software engineering. Prioritization of small size requirements is not big issue and many techniques are suggested by researchers and available to prioritize small set of requirements but issues arise when we consider large set of software requirements. In this study, an approach is presented to reduce number of comparisons during prioritizing large requirements. Through analytic hierarchy process (AHP), first two modules were compared directly for prioritization and then all functional requirements (FRs) belong to these two modules were compared with one another and at the end the results of both comparisons were compared and it was concluded that rather than comparing all FRs together it is better to compare only major user requirements (URs) to which these FRs belong in order to reduce number of comparisons.
OpenAlex reports 29 citations for this work. Citation counts describe recorded attention and do not establish research quality.
A contribution statement is not available in the OpenAlex record.
Method details are not available in the OpenAlex metadata.
Findings are not separately available in the OpenAlex metadata.
Limitations are not available in the OpenAlex metadata.
Application details are not available in the OpenAlex metadata.
Requirements prioritization is very vital and difficult phase during requirement management phase of software engineering. Prioritization of small size requirements is not big issue and many techniques are suggested by researchers and available to prioritize small set of requirements but issues arise when we consider large set of software requirements. In this study, an approach is presented to reduce number of comparisons during prioritizing large requirements. Through analytic hierarchy process (AHP), first two modules were compared directly for prioritization and then all functional requirements (FRs) belong to these two modules were compared with one another and at the end the results of both comparisons were compared and it was concluded that rather than comparing all FRs together it is better to compare only major user requirements (URs) to which these FRs belong in order to reduce number of comparisons.
Key concepts: Requirement prioritization, Prioritization, Computer science, Software requirements, Requirements engineering, Requirements analysis, Requirements management, Analytic hierarchy process