Towards a process for architectural modelling in agile software development
Proceedings of the joint ACM SIGSOFT conference -- QoSA and ACM SIGSOFT symposium -- ISARCS on Quality of software architectures -- QoSA and architecting critical systems -- ISARCS
Prioritisation of software requirements using grey relational analysis
International Journal of Computer Applications in Technology
A systematic literature review of software requirements prioritization research
Information and Software Technology
| Hi-index | 0.00 |
A software projects is bounded by number of constraints such as time, features, budget and resources. The needs & expectations of the customer are dynamic and depend on the various factors which keep changing. In order find out their relevance [24], to increase the customer satisfaction [23], planning the release of new prototype or version the requirements [16] prioritization have gained importance and have became an essential characteristic of requirements [24]. This is also important when there are strict constraints on schedule & resources one must negotiate & prioritize the most essential features to be incorporated as to make project successful. In industrial projects, there are many requirements which keep on increasing as the projects undergo development, so prioritization is must [23, 24, 26, 27] but often it is dropped because of large number of growing requirements need more number of comparisons. "Yet there has been little progress to date, either theoretical or practical, on the mechanisms for prioritizing software requirements [2]."[1]. This paper encourages the industry to prioritize requirement, with help of B-Tree method in which the number of comparison required by the proposed method can be kept low.