Regression Testing-Based Requirement Prioritization of Mobile Applications
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 engineer...
Ausführliche Beschreibung
Gespeichert in:
| Autor*in: |
Gupta, Varun [verfasserIn] Chauhan, D. S. [author] Dutta, Kamlesh [author] |
|---|
| Format: |
E-Artikel |
|---|---|
| Sprache: |
Englisch |
| Erschienen: |
2012 |
|---|
| Schlagwörter: |
|---|
| Umfang: |
Online-Ressource |
|---|
| Reproduktion: |
IGI Global InfoSci Journals Archive 2000 - 2012 |
|---|---|
| Übergeordnetes Werk: |
In: International journal of systems and service-oriented engineering - Hershey, Pa : IGI Global, 2010, 3(2012), 4, Seite 20-39 |
| Übergeordnetes Werk: |
volume:3 ; year:2012 ; number:4 ; pages:20-39 |
| Links: |
|---|
| DOI / URN: |
10.4018/jssoe.2012100102 |
|---|
| Katalog-ID: |
NLEJ244503249 |
|---|
| LEADER | 01000caa a22002652 4500 | ||
|---|---|---|---|
| 001 | NLEJ244503249 | ||
| 003 | DE-627 | ||
| 005 | 20240202180242.0 | ||
| 007 | cr uuu---uuuuu | ||
| 008 | 150605s2012 xx |||||o 00| ||eng c | ||
| 024 | 7 | |a 10.4018/jssoe.2012100102 |2 doi | |
| 035 | |a (DE-627)NLEJ244503249 | ||
| 035 | |a (VZGNL)10.4018/jssoe.2012100102 | ||
| 040 | |a DE-627 |b ger |c DE-627 |e rakwb | ||
| 041 | |a eng | ||
| 100 | 1 | |a Gupta, Varun |e verfasserin |4 aut | |
| 245 | 1 | 0 | |a Regression Testing-Based Requirement Prioritization of Mobile Applications |
| 264 | 1 | |c 2012 | |
| 300 | |a Online-Ressource | ||
| 336 | |a nicht spezifiziert |b zzz |2 rdacontent | ||
| 337 | |a nicht spezifiziert |b z |2 rdamedia | ||
| 338 | |a nicht spezifiziert |b zu |2 rdacarrier | ||
| 520 | |a 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 | ||
| 533 | |f IGI Global InfoSci Journals Archive 2000 - 2012 | ||
| 650 | 4 | |a Mobile Applications | |
| 650 | 4 | |a Regression Testing | |
| 650 | 4 | |a Requirement Prioritization | |
| 650 | 4 | |a Ripple Effects | |
| 650 | 4 | |a Software Application | |
| 700 | 1 | |a Chauhan, D. S. |e author |4 aut | |
| 700 | 1 | |a Dutta, Kamlesh |e author |4 aut | |
| 773 | 0 | 8 | |i In |t International journal of systems and service-oriented engineering |d Hershey, Pa : IGI Global, 2010 |g 3(2012), 4, Seite 20-39 |h Online-Ressource |w (DE-627)NLEJ244419558 |w (DE-600)2703819-1 |x 1947-3060 |7 nnns |
| 773 | 1 | 8 | |g volume:3 |g year:2012 |g number:4 |g pages:20-39 |
| 856 | 4 | 0 | |u http://services.igi-global.com/resolvedoi/resolve.aspx?doi=10.4018/jssoe.2012100102 |m X:IGIG |x Verlag |z Deutschlandweit zugänglich |
| 856 | 4 | 2 | |u http://services.igi-global.com/resolvedoi/resolve.aspx?doi=10.4018/jssoe.2012100102&buylink=true |q text/html |y Abstract |z Deutschlandweit zugänglich |
| 912 | |a ZDB-1-GIS | ||
| 912 | |a GBV_NL_ARTICLE | ||
| 951 | |a AR | ||
| 952 | |d 3 |j 2012 |e 4 |h 20-39 | ||
| author_variant |
v g vg d s c ds dsc k d kd |
|---|---|
| matchkey_str |
article:19473060:2012----::ersinetnbsdeurmnpirtztoo |
| hierarchy_sort_str |
2012 |
| publishDate |
2012 |
| allfields |
10.4018/jssoe.2012100102 doi (DE-627)NLEJ244503249 (VZGNL)10.4018/jssoe.2012100102 DE-627 ger DE-627 rakwb eng Gupta, Varun verfasserin aut Regression Testing-Based Requirement Prioritization of Mobile Applications 2012 Online-Ressource nicht spezifiziert zzz rdacontent nicht spezifiziert z rdamedia nicht spezifiziert zu rdacarrier 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 IGI Global InfoSci Journals Archive 2000 - 2012 Mobile Applications Regression Testing Requirement Prioritization Ripple Effects Software Application Chauhan, D. S. author aut Dutta, Kamlesh author aut In International journal of systems and service-oriented engineering Hershey, Pa : IGI Global, 2010 3(2012), 4, Seite 20-39 Online-Ressource (DE-627)NLEJ244419558 (DE-600)2703819-1 1947-3060 nnns volume:3 year:2012 number:4 pages:20-39 http://services.igi-global.com/resolvedoi/resolve.aspx?doi=10.4018/jssoe.2012100102 X:IGIG Verlag Deutschlandweit zugänglich http://services.igi-global.com/resolvedoi/resolve.aspx?doi=10.4018/jssoe.2012100102&buylink=true text/html Abstract Deutschlandweit zugänglich ZDB-1-GIS GBV_NL_ARTICLE AR 3 2012 4 20-39 |
| spelling |
10.4018/jssoe.2012100102 doi (DE-627)NLEJ244503249 (VZGNL)10.4018/jssoe.2012100102 DE-627 ger DE-627 rakwb eng Gupta, Varun verfasserin aut Regression Testing-Based Requirement Prioritization of Mobile Applications 2012 Online-Ressource nicht spezifiziert zzz rdacontent nicht spezifiziert z rdamedia nicht spezifiziert zu rdacarrier 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 IGI Global InfoSci Journals Archive 2000 - 2012 Mobile Applications Regression Testing Requirement Prioritization Ripple Effects Software Application Chauhan, D. S. author aut Dutta, Kamlesh author aut In International journal of systems and service-oriented engineering Hershey, Pa : IGI Global, 2010 3(2012), 4, Seite 20-39 Online-Ressource (DE-627)NLEJ244419558 (DE-600)2703819-1 1947-3060 nnns volume:3 year:2012 number:4 pages:20-39 http://services.igi-global.com/resolvedoi/resolve.aspx?doi=10.4018/jssoe.2012100102 X:IGIG Verlag Deutschlandweit zugänglich http://services.igi-global.com/resolvedoi/resolve.aspx?doi=10.4018/jssoe.2012100102&buylink=true text/html Abstract Deutschlandweit zugänglich ZDB-1-GIS GBV_NL_ARTICLE AR 3 2012 4 20-39 |
| allfields_unstemmed |
10.4018/jssoe.2012100102 doi (DE-627)NLEJ244503249 (VZGNL)10.4018/jssoe.2012100102 DE-627 ger DE-627 rakwb eng Gupta, Varun verfasserin aut Regression Testing-Based Requirement Prioritization of Mobile Applications 2012 Online-Ressource nicht spezifiziert zzz rdacontent nicht spezifiziert z rdamedia nicht spezifiziert zu rdacarrier 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 IGI Global InfoSci Journals Archive 2000 - 2012 Mobile Applications Regression Testing Requirement Prioritization Ripple Effects Software Application Chauhan, D. S. author aut Dutta, Kamlesh author aut In International journal of systems and service-oriented engineering Hershey, Pa : IGI Global, 2010 3(2012), 4, Seite 20-39 Online-Ressource (DE-627)NLEJ244419558 (DE-600)2703819-1 1947-3060 nnns volume:3 year:2012 number:4 pages:20-39 http://services.igi-global.com/resolvedoi/resolve.aspx?doi=10.4018/jssoe.2012100102 X:IGIG Verlag Deutschlandweit zugänglich http://services.igi-global.com/resolvedoi/resolve.aspx?doi=10.4018/jssoe.2012100102&buylink=true text/html Abstract Deutschlandweit zugänglich ZDB-1-GIS GBV_NL_ARTICLE AR 3 2012 4 20-39 |
| allfieldsGer |
10.4018/jssoe.2012100102 doi (DE-627)NLEJ244503249 (VZGNL)10.4018/jssoe.2012100102 DE-627 ger DE-627 rakwb eng Gupta, Varun verfasserin aut Regression Testing-Based Requirement Prioritization of Mobile Applications 2012 Online-Ressource nicht spezifiziert zzz rdacontent nicht spezifiziert z rdamedia nicht spezifiziert zu rdacarrier 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 IGI Global InfoSci Journals Archive 2000 - 2012 Mobile Applications Regression Testing Requirement Prioritization Ripple Effects Software Application Chauhan, D. S. author aut Dutta, Kamlesh author aut In International journal of systems and service-oriented engineering Hershey, Pa : IGI Global, 2010 3(2012), 4, Seite 20-39 Online-Ressource (DE-627)NLEJ244419558 (DE-600)2703819-1 1947-3060 nnns volume:3 year:2012 number:4 pages:20-39 http://services.igi-global.com/resolvedoi/resolve.aspx?doi=10.4018/jssoe.2012100102 X:IGIG Verlag Deutschlandweit zugänglich http://services.igi-global.com/resolvedoi/resolve.aspx?doi=10.4018/jssoe.2012100102&buylink=true text/html Abstract Deutschlandweit zugänglich ZDB-1-GIS GBV_NL_ARTICLE AR 3 2012 4 20-39 |
| allfieldsSound |
10.4018/jssoe.2012100102 doi (DE-627)NLEJ244503249 (VZGNL)10.4018/jssoe.2012100102 DE-627 ger DE-627 rakwb eng Gupta, Varun verfasserin aut Regression Testing-Based Requirement Prioritization of Mobile Applications 2012 Online-Ressource nicht spezifiziert zzz rdacontent nicht spezifiziert z rdamedia nicht spezifiziert zu rdacarrier 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 IGI Global InfoSci Journals Archive 2000 - 2012 Mobile Applications Regression Testing Requirement Prioritization Ripple Effects Software Application Chauhan, D. S. author aut Dutta, Kamlesh author aut In International journal of systems and service-oriented engineering Hershey, Pa : IGI Global, 2010 3(2012), 4, Seite 20-39 Online-Ressource (DE-627)NLEJ244419558 (DE-600)2703819-1 1947-3060 nnns volume:3 year:2012 number:4 pages:20-39 http://services.igi-global.com/resolvedoi/resolve.aspx?doi=10.4018/jssoe.2012100102 X:IGIG Verlag Deutschlandweit zugänglich http://services.igi-global.com/resolvedoi/resolve.aspx?doi=10.4018/jssoe.2012100102&buylink=true text/html Abstract Deutschlandweit zugänglich ZDB-1-GIS GBV_NL_ARTICLE AR 3 2012 4 20-39 |
| language |
English |
| source |
In International journal of systems and service-oriented engineering 3(2012), 4, Seite 20-39 volume:3 year:2012 number:4 pages:20-39 |
| sourceStr |
In International journal of systems and service-oriented engineering 3(2012), 4, Seite 20-39 volume:3 year:2012 number:4 pages:20-39 |
| format_phy_str_mv |
Article |
| institution |
findex.gbv.de |
| topic_facet |
Mobile Applications Regression Testing Requirement Prioritization Ripple Effects Software Application |
| isfreeaccess_bool |
false |
| container_title |
International journal of systems and service-oriented engineering |
| authorswithroles_txt_mv |
Gupta, Varun @@aut@@ Chauhan, D. S. @@aut@@ Dutta, Kamlesh @@aut@@ |
| publishDateDaySort_date |
2012-01-01T00:00:00Z |
| hierarchy_top_id |
NLEJ244419558 |
| id |
NLEJ244503249 |
| language_de |
englisch |
| fullrecord |
<?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>01000caa a22002652 4500</leader><controlfield tag="001">NLEJ244503249</controlfield><controlfield tag="003">DE-627</controlfield><controlfield tag="005">20240202180242.0</controlfield><controlfield tag="007">cr uuu---uuuuu</controlfield><controlfield tag="008">150605s2012 xx |||||o 00| ||eng c</controlfield><datafield tag="024" ind1="7" ind2=" "><subfield code="a">10.4018/jssoe.2012100102</subfield><subfield code="2">doi</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-627)NLEJ244503249</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(VZGNL)10.4018/jssoe.2012100102</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-627</subfield><subfield code="b">ger</subfield><subfield code="c">DE-627</subfield><subfield code="e">rakwb</subfield></datafield><datafield tag="041" ind1=" " ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Gupta, Varun</subfield><subfield code="e">verfasserin</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">Regression Testing-Based Requirement Prioritization of Mobile Applications</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="c">2012</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">Online-Ressource</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="a">nicht spezifiziert</subfield><subfield code="b">zzz</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="a">nicht spezifiziert</subfield><subfield code="b">z</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="a">nicht spezifiziert</subfield><subfield code="b">zu</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="520" ind1=" " ind2=" "><subfield code="a">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</subfield></datafield><datafield tag="533" ind1=" " ind2=" "><subfield code="f">IGI Global InfoSci Journals Archive 2000 - 2012</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Mobile Applications</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Regression Testing</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Requirement Prioritization</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Ripple Effects</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Software Application</subfield></datafield><datafield tag="700" ind1="1" ind2=" "><subfield code="a">Chauhan, D. S.</subfield><subfield code="e">author</subfield><subfield code="4">aut</subfield></datafield><datafield tag="700" ind1="1" ind2=" "><subfield code="a">Dutta, Kamlesh</subfield><subfield code="e">author</subfield><subfield code="4">aut</subfield></datafield><datafield tag="773" ind1="0" ind2="8"><subfield code="i">In</subfield><subfield code="t">International journal of systems and service-oriented engineering</subfield><subfield code="d">Hershey, Pa : IGI Global, 2010</subfield><subfield code="g">3(2012), 4, Seite 20-39</subfield><subfield code="h">Online-Ressource</subfield><subfield code="w">(DE-627)NLEJ244419558</subfield><subfield code="w">(DE-600)2703819-1</subfield><subfield code="x">1947-3060</subfield><subfield code="7">nnns</subfield></datafield><datafield tag="773" ind1="1" ind2="8"><subfield code="g">volume:3</subfield><subfield code="g">year:2012</subfield><subfield code="g">number:4</subfield><subfield code="g">pages:20-39</subfield></datafield><datafield tag="856" ind1="4" ind2="0"><subfield code="u">http://services.igi-global.com/resolvedoi/resolve.aspx?doi=10.4018/jssoe.2012100102</subfield><subfield code="m">X:IGIG</subfield><subfield code="x">Verlag</subfield><subfield code="z">Deutschlandweit zugänglich</subfield></datafield><datafield tag="856" ind1="4" ind2="2"><subfield code="u">http://services.igi-global.com/resolvedoi/resolve.aspx?doi=10.4018/jssoe.2012100102&buylink=true</subfield><subfield code="q">text/html</subfield><subfield code="y">Abstract</subfield><subfield code="z">Deutschlandweit zugänglich</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">ZDB-1-GIS</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_NL_ARTICLE</subfield></datafield><datafield tag="951" ind1=" " ind2=" "><subfield code="a">AR</subfield></datafield><datafield tag="952" ind1=" " ind2=" "><subfield code="d">3</subfield><subfield code="j">2012</subfield><subfield code="e">4</subfield><subfield code="h">20-39</subfield></datafield></record></collection>
|
| series2 |
IGI Global InfoSci Journals Archive 2000 - 2012 |
| author |
Gupta, Varun |
| spellingShingle |
Gupta, Varun misc Mobile Applications misc Regression Testing misc Requirement Prioritization misc Ripple Effects misc Software Application Regression Testing-Based Requirement Prioritization of Mobile Applications |
| authorStr |
Gupta, Varun |
| ppnlink_with_tag_str_mv |
@@773@@(DE-627)NLEJ244419558 |
| format |
electronic Article |
| delete_txt_mv |
keep |
| author_role |
aut aut aut |
| collection |
NL |
| remote_str |
true |
| illustrated |
Not Illustrated |
| issn |
1947-3060 |
| topic_title |
Regression Testing-Based Requirement Prioritization of Mobile Applications Mobile Applications Regression Testing Requirement Prioritization Ripple Effects Software Application |
| topic |
misc Mobile Applications misc Regression Testing misc Requirement Prioritization misc Ripple Effects misc Software Application |
| topic_unstemmed |
misc Mobile Applications misc Regression Testing misc Requirement Prioritization misc Ripple Effects misc Software Application |
| topic_browse |
misc Mobile Applications misc Regression Testing misc Requirement Prioritization misc Ripple Effects misc Software Application |
| format_facet |
Elektronische Aufsätze Aufsätze Elektronische Ressource |
| format_main_str_mv |
Text Zeitschrift/Artikel |
| carriertype_str_mv |
zu |
| hierarchy_parent_title |
International journal of systems and service-oriented engineering |
| hierarchy_parent_id |
NLEJ244419558 |
| hierarchy_top_title |
International journal of systems and service-oriented engineering |
| isfreeaccess_txt |
false |
| familylinks_str_mv |
(DE-627)NLEJ244419558 (DE-600)2703819-1 |
| title |
Regression Testing-Based Requirement Prioritization of Mobile Applications |
| ctrlnum |
(DE-627)NLEJ244503249 (VZGNL)10.4018/jssoe.2012100102 |
| title_full |
Regression Testing-Based Requirement Prioritization of Mobile Applications |
| author_sort |
Gupta, Varun |
| journal |
International journal of systems and service-oriented engineering |
| journalStr |
International journal of systems and service-oriented engineering |
| lang_code |
eng |
| isOA_bool |
false |
| recordtype |
marc |
| publishDateSort |
2012 |
| contenttype_str_mv |
zzz |
| container_start_page |
20 |
| author_browse |
Gupta, Varun Chauhan, D. S. Dutta, Kamlesh |
| container_volume |
3 |
| physical |
Online-Ressource |
| format_se |
Elektronische Aufsätze |
| author-letter |
Gupta, Varun |
| doi_str_mv |
10.4018/jssoe.2012100102 |
| author2-role |
author |
| title_sort |
regression testing-based requirement prioritization of mobile applications |
| title_auth |
Regression Testing-Based Requirement Prioritization of Mobile Applications |
| 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 |
| abstractGer |
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 |
| abstract_unstemmed |
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 |
| collection_details |
ZDB-1-GIS GBV_NL_ARTICLE |
| container_issue |
4 |
| title_short |
Regression Testing-Based Requirement Prioritization of Mobile Applications |
| url |
http://services.igi-global.com/resolvedoi/resolve.aspx?doi=10.4018/jssoe.2012100102 http://services.igi-global.com/resolvedoi/resolve.aspx?doi=10.4018/jssoe.2012100102&buylink=true |
| remote_bool |
true |
| author2 |
Chauhan, D. S. Dutta, Kamlesh |
| author2Str |
Chauhan, D. S. Dutta, Kamlesh |
| ppnlink |
NLEJ244419558 |
| mediatype_str_mv |
z |
| isOA_txt |
false |
| hochschulschrift_bool |
false |
| doi_str |
10.4018/jssoe.2012100102 |
| up_date |
2024-07-06T08:06:52.194Z |
| _version_ |
1803816232232681472 |
| fullrecord_marcxml |
<?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>01000caa a22002652 4500</leader><controlfield tag="001">NLEJ244503249</controlfield><controlfield tag="003">DE-627</controlfield><controlfield tag="005">20240202180242.0</controlfield><controlfield tag="007">cr uuu---uuuuu</controlfield><controlfield tag="008">150605s2012 xx |||||o 00| ||eng c</controlfield><datafield tag="024" ind1="7" ind2=" "><subfield code="a">10.4018/jssoe.2012100102</subfield><subfield code="2">doi</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-627)NLEJ244503249</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(VZGNL)10.4018/jssoe.2012100102</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-627</subfield><subfield code="b">ger</subfield><subfield code="c">DE-627</subfield><subfield code="e">rakwb</subfield></datafield><datafield tag="041" ind1=" " ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Gupta, Varun</subfield><subfield code="e">verfasserin</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">Regression Testing-Based Requirement Prioritization of Mobile Applications</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="c">2012</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">Online-Ressource</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="a">nicht spezifiziert</subfield><subfield code="b">zzz</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="a">nicht spezifiziert</subfield><subfield code="b">z</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="a">nicht spezifiziert</subfield><subfield code="b">zu</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="520" ind1=" " ind2=" "><subfield code="a">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</subfield></datafield><datafield tag="533" ind1=" " ind2=" "><subfield code="f">IGI Global InfoSci Journals Archive 2000 - 2012</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Mobile Applications</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Regression Testing</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Requirement Prioritization</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Ripple Effects</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Software Application</subfield></datafield><datafield tag="700" ind1="1" ind2=" "><subfield code="a">Chauhan, D. S.</subfield><subfield code="e">author</subfield><subfield code="4">aut</subfield></datafield><datafield tag="700" ind1="1" ind2=" "><subfield code="a">Dutta, Kamlesh</subfield><subfield code="e">author</subfield><subfield code="4">aut</subfield></datafield><datafield tag="773" ind1="0" ind2="8"><subfield code="i">In</subfield><subfield code="t">International journal of systems and service-oriented engineering</subfield><subfield code="d">Hershey, Pa : IGI Global, 2010</subfield><subfield code="g">3(2012), 4, Seite 20-39</subfield><subfield code="h">Online-Ressource</subfield><subfield code="w">(DE-627)NLEJ244419558</subfield><subfield code="w">(DE-600)2703819-1</subfield><subfield code="x">1947-3060</subfield><subfield code="7">nnns</subfield></datafield><datafield tag="773" ind1="1" ind2="8"><subfield code="g">volume:3</subfield><subfield code="g">year:2012</subfield><subfield code="g">number:4</subfield><subfield code="g">pages:20-39</subfield></datafield><datafield tag="856" ind1="4" ind2="0"><subfield code="u">http://services.igi-global.com/resolvedoi/resolve.aspx?doi=10.4018/jssoe.2012100102</subfield><subfield code="m">X:IGIG</subfield><subfield code="x">Verlag</subfield><subfield code="z">Deutschlandweit zugänglich</subfield></datafield><datafield tag="856" ind1="4" ind2="2"><subfield code="u">http://services.igi-global.com/resolvedoi/resolve.aspx?doi=10.4018/jssoe.2012100102&buylink=true</subfield><subfield code="q">text/html</subfield><subfield code="y">Abstract</subfield><subfield code="z">Deutschlandweit zugänglich</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">ZDB-1-GIS</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_NL_ARTICLE</subfield></datafield><datafield tag="951" ind1=" " ind2=" "><subfield code="a">AR</subfield></datafield><datafield tag="952" ind1=" " ind2=" "><subfield code="d">3</subfield><subfield code="j">2012</subfield><subfield code="e">4</subfield><subfield code="h">20-39</subfield></datafield></record></collection>
|
| score |
7.397252 |