An Approach for Requirement Prioritization Using B-Tree

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.

[1]  Nenad Medvidovic,et al.  Dimensions of Concerns in Requirements Negotiation and Architecture Modeling 1 , 2000 .

[2]  Martin Höst,et al.  An analytical model for requirements selection quality evaluation in product software development , 2003, Proceedings. 11th IEEE International Requirements Engineering Conference, 2003..

[3]  Mamoru Maekawa,et al.  Need-based requirements change management , 2001, Proceedings. Eighth Annual IEEE International Conference and Workshop On the Engineering of Computer-Based Systems-ECBS 2001.

[4]  E. Capaldi,et al.  The organization of behavior. , 1992, Journal of applied behavior analysis.

[5]  Daniel M. Berry,et al.  The importance of ignorance in requirements engineering , 1995, J. Syst. Softw..

[6]  Björn Regnell,et al.  A hierarchical use case model with graphical representation , 1996, Proceedings IEEE Symposium and Workshop on Engineering of Computer-Based Systems.

[7]  Martin Höst,et al.  An Industrial Case Study on Distributed Prioritisation in Market-Driven Requirements Engineering for Packaged Software , 2001, Requirements Engineering.

[8]  Dar-Biau Liu,et al.  Metrics for requirements engineering , 1995, J. Syst. Softw..

[9]  Didar Zowghi,et al.  The Three Cs of Requirements : Consistency , Completeness , and Correctness , 2002 .

[10]  Rudolf Bayer,et al.  Symmetric binary B-Trees: Data structure and maintenance algorithms , 1972, Acta Informatica.

[11]  Ronald L. Rivest,et al.  Introduction to Algorithms , 1990 .

[12]  Armin Eberlein,et al.  Requirements engineering for time-to-market projects , 2002, Proceedings Ninth Annual IEEE International Conference and Workshop on the Engineering of Computer-Based Systems.

[13]  Naveed Ikram The management of risk in information systems development , 2000 .

[14]  Donald E. Knuth,et al.  Sorting and Searching , 1973 .

[15]  Björn Regnell,et al.  Market-driven requirements engineering processes for software products - a report on current practices , 2003 .

[16]  Björn Regnell,et al.  Visualization of Agreement and Satisfaction in Distributed Prioritization of Market Requirements , 2000 .

[17]  Marjo Kauppinen,et al.  Requirements Prioritization Challenges in Practice , 2004, PROFES.

[18]  Paul Grünbacher Collaborative requirements negotiation with EasyWinWin , 2000, Proceedings 11th International Workshop on Database and Expert Systems Applications.

[19]  Alfred V. Aho,et al.  The Design and Analysis of Computer Algorithms , 1974 .

[20]  Sebastián Uchitel,et al.  Incremental elaboration of scenario-based specifications and behavior models using implied scenarios , 2004, TSEM.

[21]  Alfred V. Aho,et al.  The design and analysis of algorithms , 1974 .

[22]  Paul Grünbacher,et al.  Complementing XP with Requirements Negotiation , 2002 .

[23]  Lester Oscar Lobo,et al.  Analysis and Evaluation of Methods for Activities in the Expanded Requirements Generation Model (x-RGM) , 2004 .

[24]  Nick Kanopoulos,et al.  Reducing the Time to Market Through Rapid Prototyping - Guest Editors' Introduction , 1995, Computer.

[25]  Leonidas J. Guibas,et al.  A dichromatic framework for balanced trees , 1978, 19th Annual Symposium on Foundations of Computer Science (sfcs 1978).

[26]  Claes Wohlin,et al.  An evaluation of methods for prioritizing software requirements , 1998, Inf. Softw. Technol..

[27]  Jawed I. A. Siddiqi,et al.  Requirements Engineering: The Emerging Wisdom , 1996, IEEE Softw..

[28]  Brian A. Malloy,et al.  AN APPROACH TO AUTOMATE REQUIREMENTS ELICITATION AND SPECIFICATION , 2003 .

[29]  Dewayne E. Perry,et al.  Software architects in practice: handling requirements , 2006, CASCON.