skip to main content
10.1145/1987875.1987881acmotherconferencesArticle/Chapter ViewAbstractPublication PagesicseConference Proceedingsconference-collections
research-article

A value-based review process for prioritizing artifacts

Published: 21 May 2011 Publication History

Abstract

As a new contribution to Value-based V&V process development, a systematic and multi-criteria process is proposed to quantitatively determine the Value-based V&V artifact priority that reviewers can follow for their reviews. This process enables reviewers to prioritize artifacts to be reviewed in a more cost-effective way based on more sophisticated and comprehensive factors, such as importance, quality risks, dependency and cost of V&V investments. Some qualitative and quantitative evidence is provided from a comparative experiment with 22 real-client e-services projects over two years of a graduate software engineering team-project course. It shows that the value-based artifact prioritization enabled reviewers to better focus on artifacts with high importance and risks, to capture issues with high impact in a timely manner, and to improve the cost-effectiveness of reviews.

References

[1]
J. Bullock, "Calculating the Value of Testing", Software Testing and Quality Engineering, May/June 2000, pp. 56--62.
[2]
P. Gerrard and N. Thompson, Risk-Based E-Business Testing, Artech House, 2002.
[3]
C. Persson and N. Yilmazturk, "Establishment of Automated Regression Testing at ABB: Industrial Experience Report on Avoiding the Pitfalls", Proceedings, ISESE 2004, IEEE, August 2004, pp. 112--121.
[4]
R. Ramler, S. Biffl, and P. Gruenbacher, "Value-Based Management of Software Testing," in S. Biffl, A. Aurum, B. Boehm, H. Erdogmus, and P. Gruenbacher, (eds.), Value-Based Software Engineering, Springer, 2005.
[5]
B. Boehm.: Value-Based Software Engineering: Overview and Agenda. In: Value-Based Software Engineering. Springer, Heidelberg (2005).
[6]
K. Lee, and B. Boehm, "Empirical Results from an Experiment on Value-Based Review (VBR) Processes," Proceedings, ISESE 2005.
[7]
B. Boehm, P. Grünbacher, and R. O. Briggs, "Developing Groupware for Requirements Negotiation: Lessons Learned", IEEE Software, May 2001, pp. 46--55.
[8]
P. Gruenbacher, S. Koszegi, and S. Biffl, "Stakeholder Value Proposition Elicitation and Reconciliation," in S. Biffl, A. Aurum, B. Boehm, H. Erdogmus, and P. Gruenbacher, (eds.), Value-Based Software Engineering, Springer, 2005.
[9]
B. Boehm and J. Lane, "Using the Incremental Commitment Model to Integrate System Acquisition, Systems Engineering, and Software Engineering," CrossTalk Journal, Volume 20, Number 10, 2007.
[10]
Instructional ICSM-Sw EPG, http://greenbay.usc.edu/IICSMSw/
[11]
J. Maranzano et al.: "Architecture Reviews: Practice and Experience," IEEE Software, March/April 2005.
[12]
M. Fagan. Advances in Software Inspections, IEEE Transactions in Software Engineering, XII:7, July 1986, pp. 744--751.
[13]
Csci-577 Bugzilla issue tracking system: http://brown.usc.edu
[14]
Value-based V&V prioritization spreadsheet, http://greenbay.usc.edu/csci577/fall2010/site/assignments/IV_V_Assign/Evaluation_of_CoreFC_Package.zip
[15]
A Value-based V&V artifact prioritization example: http://greenbay.usc.edu/csci577/fall2010/projects/team2/IIV&V/VbIIVV_CoreFCP_F10a_T02.xls
[16]
Fall 2009 Csci-577a projects: http://greenbay.usc.edu/csci577/fall2009/site/projects/index.html
[17]
Fall 2010 Csci-577a projects: http://greenbay.usc.edu/csci577/fall2010/site/projects/index.html
[18]
Fall 2009 Csci-577a assignments: http://greenbay.usc.edu/csci577/fall2009/site/assignments/index.html
[19]
Fall 2010 Csci-577a assignments: http://greenbay.usc.edu/csci577/fall2010/site/assignments/index.html
[20]
M. Fagan, "Design and code inspections to reduce errors in program development", IBM Sys. J IS(3), 1976, pp. 182--211.
[21]
V. Basili, S. Green, O. Laitenberger, F. Lanubile, F. Shull, S. Sorumgard, and M. Zelkowitz. "The empirical investigation of perspective-based reading", Intl. J. Empirical SW. Engr., 1(2) 1996, pp.133--164.
[22]
J. Li, L. Hou, Z. Qin, Q. Wang, G. Chen, "An Empirically-Based Process to Improve the Practice of Requirement Review". ICSP 2008: 135--146.
[23]
A. Porter, L. Votta, and V. Basili, "Comparing Detection Methods for software Requirement Inspection: a Replicate Experiment", IEEE Trans. Software Eng., vol 21, no 6, pp. 563--575, June 1995.
[24]
Z. Abdelrabi, E. Cantone, M. Ciolkowski, and D. Rombach, "Comparing code reading techniques applied to object oriented software frameworks with regard to effectiveness and defect detection rate", Proc, ISESE 2004, pp 239--248.
[25]
R. Conradi, and A. Wang. (eds.), "Empirical Methods and Studies in Software Engineering: Experiences from ESERNET", Springer Verlag, 2003.
[26]
T. Thelin, P. Runeson, and C. Wohlin, "Prioritized use cases as a vehicle for software inspections", Software, July/Aug 2003, pp. 30--33.

Cited By

View all
  • (2018)Hazard Relation DiagramsRequirements Engineering10.1007/s00766-017-0267-923:2(291-329)Online publication date: 1-Jun-2018
  • (2015)Supporting the Validation of Adequacy in Requirements-Based Hazard MitigationsRequirements Engineering: Foundation for Software Quality10.1007/978-3-319-16101-3_2(17-32)Online publication date: 14-Mar-2015
  • (2013)Improving scenario testing process by adding value-based prioritization: an industrial case studyProceedings of the 2013 International Conference on Software and System Process10.1145/2486046.2486061(78-87)Online publication date: 18-May-2013
  • Show More Cited By

Recommendations

Comments

Information & Contributors

Information

Published In

cover image ACM Other conferences
ICSSP '11: Proceedings of the 2011 International Conference on Software and Systems Process
May 2011
256 pages
ISBN:9781450307307
DOI:10.1145/1987875
Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]

Publisher

Association for Computing Machinery

New York, NY, United States

Publication History

Published: 21 May 2011

Permissions

Request permissions for this article.

Check for updates

Author Tags

  1. review
  2. validation
  3. value-based software engineering
  4. verification

Qualifiers

  • Research-article

Conference

ICSSP '11

Contributors

Other Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

  • Downloads (Last 12 months)4
  • Downloads (Last 6 weeks)0
Reflects downloads up to 02 Mar 2025

Other Metrics

Citations

Cited By

View all
  • (2018)Hazard Relation DiagramsRequirements Engineering10.1007/s00766-017-0267-923:2(291-329)Online publication date: 1-Jun-2018
  • (2015)Supporting the Validation of Adequacy in Requirements-Based Hazard MitigationsRequirements Engineering: Foundation for Software Quality10.1007/978-3-319-16101-3_2(17-32)Online publication date: 14-Mar-2015
  • (2013)Improving scenario testing process by adding value-based prioritization: an industrial case studyProceedings of the 2013 International Conference on Software and System Process10.1145/2486046.2486061(78-87)Online publication date: 18-May-2013
  • (undefined)Value-Based Software Engineering: A Systematic Mapping StudySSRN Electronic Journal10.2139/ssrn.4148149

View Options

Login options

View options

PDF

View or Download as a PDF file.

PDF

eReader

View online with eReader.

eReader

Figures

Tables

Media

Share

Share

Share this Publication link

Share on social media