Full Text:   <1333>

Summary:  <738>

CLC number: TP311

On-line Access: 2016-08-05

Received: 2015-05-18

Revision Accepted: 2015-10-27

Crosschecked: 2016-07-20

Cited: 0

Clicked: 3257

Citations:  Bibtex RefMan EndNote GB/T7714

 ORCID:

Saif Ur Rehman Khan

http://orcid.org/0000-0002-9643-6858

-   Go to

Article info.
Open peer comments

Frontiers of Information Technology & Electronic Engineering  2016 Vol.17 No.8 P.750-765

http://doi.org/10.1631/FITEE.1500162


RePizer: a framework for prioritization of software requirements


Author(s):  Saif Ur Rehman Khan, Sai Peck Lee, Mohammad Dabbagh, Muhammad Tahir, Muzafar Khan, Muhammad Arif

Affiliation(s):  Department of Software Engineering, Faculty of Computer Science and Information Technology, University of Malaya, Kuala Lumpur 50603, Malaysia; more

Corresponding email(s):   saif_rehman@siswa.um.edu.my

Key Words:  Software requirements, Requirements prioritization techniques, Prioritization framework, Planning game, Analytical hierarchy process


Saif Ur Rehman Khan, Sai Peck Lee, Mohammad Dabbagh, Muhammad Tahir, Muzafar Khan, Muhammad Arif. RePizer: a framework for prioritization of software requirements[J]. Frontiers of Information Technology & Electronic Engineering, 2016, 17(8): 750-765.

@article{title="RePizer: a framework for prioritization of software requirements",
author="Saif Ur Rehman Khan, Sai Peck Lee, Mohammad Dabbagh, Muhammad Tahir, Muzafar Khan, Muhammad Arif",
journal="Frontiers of Information Technology & Electronic Engineering",
volume="17",
number="8",
pages="750-765",
year="2016",
publisher="Zhejiang University Press & Springer",
doi="10.1631/FITEE.1500162"
}

%0 Journal Article
%T RePizer: a framework for prioritization of software requirements
%A Saif Ur Rehman Khan
%A Sai Peck Lee
%A Mohammad Dabbagh
%A Muhammad Tahir
%A Muzafar Khan
%A Muhammad Arif
%J Frontiers of Information Technology & Electronic Engineering
%V 17
%N 8
%P 750-765
%@ 2095-9184
%D 2016
%I Zhejiang University Press & Springer
%DOI 10.1631/FITEE.1500162

TY - JOUR
T1 - RePizer: a framework for prioritization of software requirements
A1 - Saif Ur Rehman Khan
A1 - Sai Peck Lee
A1 - Mohammad Dabbagh
A1 - Muhammad Tahir
A1 - Muzafar Khan
A1 - Muhammad Arif
J0 - Frontiers of Information Technology & Electronic Engineering
VL - 17
IS - 8
SP - 750
EP - 765
%@ 2095-9184
Y1 - 2016
PB - Zhejiang University Press & Springer
ER -
DOI - 10.1631/FITEE.1500162


Abstract: 
The standard software development life cycle heavily depends on requirements elicited from stakeholders. Based on those requirements, software development is planned and managed from its inception phase to closure. Due to time and resource constraints, it is imperative to identify the high-priority requirements that need to be considered first during the software development process. Moreover, existing prioritization frameworks lack a store of historical data useful for selecting the most suitable prioritization technique of any similar project domain. In this paper, we propose a framework for prioritization of software requirements, called RePizer, to be used in conjunction with a selected prioritization technique to rank software requirements based on defined criteria such as implementation cost. RePizer assists requirements engineers in a decision-making process by retrieving historical data from a requirements repository. RePizer also provides a panoramic view of the entire project to ensure the judicious use of software development resources. We compared the performance of RePizer in terms of expected accuracy and ease of use while separately adopting two different prioritization techniques, planning game (PG) and analytical hierarchy process (AHP). The results showed that RePizer performed better when used in conjunction with the PG technique.

The authors proposed RePizer a requirements prioritization framework, that starting from a list of requirements and a prioritization technique is able to rank the requirements. Then the authors reported a case study and an empirical evaluation of their proposal in order to show how the framework can be applied in real cases and its effectiveness.

RePizer:一种软件需求排序架构

概要:标准的软件开发周期很大程度上取决于利益相关方的需求。软件开发全程围绕需求设计和管理。考虑到时间和资源的限制,必须分清哪些是必须首先考虑的高优先级需求。已有的需求排序架构缺少对历史数据的记录,而这些历史数据有助于从类似项目中方便地选取最适合的需求排序技术。本文中,我们提出一种名为RePizer的软件需求排序架构,该架构与一种选定的需求排序技术联合使用,可以基于给定标准(如开发成本),为软件需求优先级排序。RePizer通过从需求库提取历史数据,为软件需求工程师决策提供协助。此外,RePizer提供了对整个项目的全景式视角,以确保对资源的审慎使用。基于RePizer架构,采用已有的两种需求排序技术:计划博弈(planning game, PG)和层级分析(analytical hierarchy process, AHP),分别比较各自的预期准确度和易用程度。结果表明,采用计划博弈时,RePizer性能更佳。
关键词:软件需求;需求排序技术;排序架构;计划博弈;层级分析

Darkslateblue:Affiliate; Royal Blue:Author; Turquoise:Article

Reference

[1]Achimugu, P., Selamat, A., Ibrahim, R., et al., 2014. A systematic literature review of software requirements prioritization research. Inform. Softw. Technol., 56(6):568-585.

[2]Ahl, V., 2005. An Experimental Comparison of Five Prioritization Methods—Investigating Ease of Use, Accuracy and Scalability. MS Thesis, Blekinge Institute of Technology, Ronneby, Sweden.

[3]Arias, T.B.C., America, P., Avgeriou, P., 2011. Defining and documenting execution viewpoints for a large and complex software-intensive system. J. Syst. Softw., 84(9): 1447-1461.

[4]Avesani, P., Bazzanella, C., Perini, A., et al., 2004. Supporting the requirements prioritization process: a machine learning approach. Proc. 16th Int. Conf. on Software Engineering and Knowledge Engineering, p.306-311.

[5]Bebensee, T., van de Weerd, I., Brinkkemper, S., 2010. Binary priority list for prioritizing software requirements. LNCS, 6182:67-78.

[6]Beck, K., 2000. Extreme Programming Explained: Embrace Change. Addison-Wesley Longman Publishing Co., Inc., Boston, MA, USA.

[7]Berander, P., 2007. Evolving Prioritization for Software Product Management. PhD Thesis, Blekinge Institute of Technology, Sweden.

[8]Berander, P., Andrews, A., 2005. Requirements prioritization. In: Aurum, A., Wohlin, C. (Eds.), Engineering and Managing Software Requirements. Springer, p.69-94.

[9]Berander, P., Jönsson, P., 2006. Hierarchical cumulative voting (HCV)—prioritization of requirements in hierarchies. Int. J. Softw. Eng. Knowl. Eng., 16(6):819-849.

[10]Bourque, P., Fairley, R.E., 2014. Guide to the Software Engineering Body of Knowledge (SWEBOK®), Version 3.0. IEEE Computer Society Press, Piscataway, New Jersey.

[11]Brackett, J.W., 1990. Software Requirements. Technical Report, No. SEI-CM-19-1.2. Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA, USA.

[12]Creswell, J.W., 2013. Research Design: Qualitative, Quantitative, and Mixed Methods Approaches (4th Ed.). Sage Publications.

[13]Dabbagh, M., Lee, S.P., 2013. A consistent approach for prioritizing system quality attributes. Proc. 14th ACIS Int. Conf. on Software Engineering, Artificial Intelligence, Networking and Parallel/Distributed Computing, p.317-322.

[14]Dabbagh, M., Lee, S.P., 2014. An approach for integrating the prioritization of functional and nonfunctional requirements. Sci. World J., Article ID 737626.

[15]Dabbagh, M., Lee, S.P., 2015. An approach for prioritizing NFRs according to their relationship with FRs. Lect. Notes Softw. Eng., 3(1):1-5.

[16]Dabbagh, M., Lee, S.P., Parizi, R.M., 2014. Application of hybrid assessment method for priority assessment of functional and non-functional requirements. Proc. Int. Conf. on Information Science and Applications, p.1-4.

[17]Danesh, A.S., Mortazavi, S.M., Danesh, S.Y.S., 2009. Requirements prioritization in on-line banking systems using value-oriented framework. Int. Conf. on Computer Technology and Development, p.158-161.

[18]Daneva, M., Damian, D., Marchetto, A., et al., 2014. Empirical research methodologies and studies in requirements engineering: how far did we come J. Syst. Softw., 95:1-9.

[19]Dominguez, J., 2009. The Curious Case of the Chaos Report 2009. Available from http://www.projectsmart.co.uk/the-curious-case-of-the-chaos-report-2009.html

[20]Firesmith, D., 2004. Prioritizing requirements. J. Obj. Technol., 3(8):35-47.

[21]Gorschek, T., 2006. Requirements Engineering Supporting Technical Product Management. PhD Thesis, Blekinge Institute of Technology, Sweden.

[22]Karlsson, J., Ryan, K., 1997. A cost-value approach for prioritizing requirements. IEEE Softw., 14(5):67-74.

[23]Khan, S.U.R., Rehman, I.U., Malik, S.U.R., 2009. The impact of test case reduction and prioritization on software testing effectiveness. Int. Conf. on Emerging Technologies, p.416-421.

[24]Lauesen, S., 2002. Software Requirements: Styles and Techniques. Addison-Wesley Professional.

[25]Leffingwell, D., Widrig, D., 2003. Managing Software Requirements: a Unified Approach. Addison-Wesley.

[26]Lehtola, L., 2006. Providing Value by Prioritizing Requirements Throughout Product Development: State of Practice and Suitability of Prioritization Methods. PhD Thesis, Helsinki University of Technology, Finland.

[27]Lehtola, L., Kauppinen, M., 2006. Suitability of requirements prioritization methods for market-driven software product development. Softw. Process Improv. Pract., 11(1):7-19.

[28]Library of Congress Portals Applications Interest Group (LCPAIG), 2003. Functional Requirements for an Open-URL Resolver for the Library of Congress. Available from http://www.loc.gov/catdir/lcpaig/openurl_requirements_20031104.pdf

[29]Likert, R., 1932. A technique for the measurement of attitudes. Arch. Psychol., 22:1-55.

[30]Liu, X.Q., Veera, C.S., Sun, Y., et al., 2004. Priority assessment of software requirements from multiple perspectives. 28th Annual Int. Computer Software and Applications Conf., p.410-415.

[31]Mead, N., 2006. Requirements Prioritization Introduction. Software Engineering Institute Web Publication, Carnegie Mellon University, Pittsburgh, USA.

[32]Mohammadi, S., Nikkhahan, B., Sohrabi, S., 2008. An analytical survey of “on-site customer” practice in extreme programming. Int. Symp. on Computer Science and Its Applications, p.1-6.

[33]Moisiadis, F., 2002. The fundamentals of prioritising requirements. Proc. Systems Engineering, Test and Evaluation Conf., p.109-119.

[34]Otero, C.E., Dell, E., Qureshi, A., et al., 2010. A quality-based requirement prioritization framework using binary inputs. 4th Asia Int. Conf. on Mathematical/Analytical Modelling and Computer Simulation, p.187-192.

[35]Perini, A., Ricca, F., Susi, A., 2009. Tool-supported requirements prioritization: comparing the AHP and CBRank methods. Inform. Softw. Technol., 51(6):1021-1032.

[36]Perini, A., Susi, A., Avesani, P., 2013. A machine learning approach to software requirements prioritization. IEEE Trans. Softw. Eng., 39(4):445-461.

[37]Ramzan, M., Jaffar, M.A., Iqbal, M.A., et al., 2009. Value based fuzzy requirement prioritization and its evaluation framework. Proc. 4th IEEE Int. Conf. on Innovative Computing, Information and Control, p.1464-1468.

[38]Ramzan, M., Jaffar, M.A., Shahid, A.A., 2011. Value based intelligent requirement prioritization (VIRP): expert driven fuzzy logic based prioritization technique. Int. J. Innov. Comput. Inform. Contr., 7(3):1017-1038.

[39]Ribeiro, R.A., Moreira, A.M., van den Broek, P., et al., 2011. Hybrid assessment method for software engineering decisions. Dec. Supp. Syst., 51(1):208-219.

[40]Saaty, T.L., 2008. Decision making with the analytic hierarchy process. Int. J. Serv. Sci., 1(1):83-98.

[41]Sadiq, M., Shahid, M., Ahmad, S., 2010. Adding threat during software requirements elicitation and prioritization. Int. J. Comput. Appl., 1(9):50-54.

[42]Siegel, S., Castellan, N.J., 1988. Nonparametric Statistics for the Behavioral Sciences (2nd Ed.). McGraw-Hill.

[43]Sommerville, I., 2010. Software Engineering (9th Ed.). Pearson.

[44]Tahriri, F., Dabbagh, M., Ale Ebrahim, N., 2014. Supplier assessment and selection using fuzzy analytic hierarchy process in a steel manufacturing company. J. Sci. Res. Rep., 3(10):1319-1338.

[45]Wiegers, K., Beatty, J., 2013. Software Requirements (3rd Ed.). Microsoft Press.

[46]Wohlin, C., Runeson, P., Höst, M., et al., 2012. Experimentation in Software Engineering. Springer Science & Business Media.

[47]Young, R.R., 2004. The Requirements Engineering Handbook. Artech House, Norwood, MA, USA.

Open peer comments: Debate/Discuss/Question/Opinion

<1>

Please provide your name, email address and a comment





Journal of Zhejiang University-SCIENCE, 38 Zheda Road, Hangzhou 310027, China
Tel: +86-571-87952783; E-mail: cjzhang@zju.edu.cn
Copyright © 2000 - Journal of Zhejiang University-SCIENCE