Prioritization of Software Functional Requirements: Spanning Tree based Approach

Abstract

Requirements prioritization shows significant role during effective implementation of requirements. Prioritization of requirements is not easy process particularly when requirements are large in size. The current methods of prioritization face limitations as the current prioritization techniques for functional requirements rely on the responses of stakeholders instead of prioritizing requirements on the basis of internal dependencies of one requirement on other requirements. Moreover, there is need to classify requirements on the basis of their importance i.e. how much they are needed for other requirements or dependent on other requirements. Requirements are first represented with spanning trees and then prioritized. Suggested spanning tree based approach is evaluated on requirements of ODOO ERP. Requirements are assigned to four developers. Time estimation with and without prioritization are calculated. The difference in time estimation with prioritization and without prioritization shows the significance of prioritization of functional requirements.

Practices for Effective Software Project Management in Global Software Development: A Systematic Literature Review

“…Requirement Engineering (RE) deals with all aspects of software requirements from requirements collection to requirements implementation in systematic way [1] [2]. RE consist of different phases.…”

Validation of Practices for Effective Communication during Requirements Elicitation in Global Software Development

“…Requirement Engineering (RE) deals with all aspects of software requirements from requirements collection to requirements implementation in systematic and discipline way [1][2] [3]. RE consist of different phases.…”

Using Interdependencies for the Prioritization and Reprioritization of Requirements in Incremental Development

“…This can be done by the use of spanning tree architecture in order to eliminate the redundant comparisons, consequently, reducing the total number of comparison. On the other hand, it is not efficient when the number of requirements is large [10]. Numerical assignment (grouping) which provides a scale to all requirements based on separating them into different groups.…”