Regression Testing-Based Requirement Prioritization of Mobile Applications

Varun Gupta, D. S. Chauhan and Kamlesh Dutta
Additional contact information
Varun Gupta: Department of Computer Science & Engineering, Jawaharlal Nehru Govt. Engineering College, Sundernagar, Himachal Pradesh, India
D. S. Chauhan: Uttarakhand Technical University, Dehradun, Uttarakhand, India
Kamlesh Dutta: Department of CSE, National Institute of Technology, Hamirpur, Himachal Pradesh, India

International Journal of Systems and Service-Oriented Engineering (IJSSOE), 2012, vol. 3, issue 4, 20-39

Abstract: Mobile software application development process must be matured enough to handle the challenges (especially market related) associated with the development of high quality mobile software development. Ever increasing number of both mobile users and mobile applications had presented software engineers with the challenge of satisfying billions of users with high quality software applications to be delivered within deadline and budgets. Always there had been a lot of pressure to develop complex software categorized by thousands of requirements, under resource constrained environment. Requirement prioritization is one of the activities undertaken by software engineer to deliver partial software product to its customers such that most important requirements are implemented in the earliest releases. During next releases some changed and pending requirements are implemented, an activity that generates ripple effects. Such ripple effects need to be tested by executing modified source code against test cases of previous releases (regression testing). Regression testing is a very effortful activity that requires a software tester to select test cases that have high fault detection capability, execute the modified code against selected test cases and performing debugging. This regression testing activity can be lowered to the maximum extend by considering dependencies between requirements during the time of requirement prioritization. Thus requirement prioritization will be carried out not only against aspects like cost, time, risks, business values etc but against dependencies also. The aim is to implement almost all dependent highest priority requirements in current release so that implementation of new requirements is unlikely to have ripple effects. Changes in requirements might not be related to variable usage and definition and might not involve a change in functionality. In such cases there is no need to select already executed test cases of previous versions. Module dependencies can lead to test case selections of previous versions if changes of requirement lead to ripple effects. This paper aims to implement highest priority requirements such that regression testing is performed to minimum thereby improving development process of mobile applications. The proposed technique had been successfully evaluated on Android based notification software application that meets the specification of Aakash tablets.

Date: 2012
References: Add references at CitEc
Citations:

Downloads: (external link)
http://services.igi-global.com/resolvedoi/resolve. ... 018/jssoe.2012100102 (application/pdf)

Related works:
This item may be available elsewhere in EconPapers: Search for items with the same title.

Export reference: BibTeX RIS (EndNote, ProCite, RefMan) HTML/Text

Persistent link: https://EconPapers.repec.org/RePEc:igg:jssoe0:v:3:y:2012:i:4:p:20-39

Access Statistics for this article

International Journal of Systems and Service-Oriented Engineering (IJSSOE) is currently edited by Wuhui Chen

More articles in International Journal of Systems and Service-Oriented Engineering (IJSSOE) from IGI Global
Bibliographic data for series maintained by Journal Editor ().