skip to main content
10.1145/1806799.1806882acmconferencesArticle/Chapter ViewAbstractPublication PagesicseConference Proceedingsconference-collections
research-article

An empirical analysis of team review approaches for teaching quality software development

Published: 01 May 2010 Publication History

Abstract

Reviews are an integral part of the software development process. They are one of the key methodologies that undergraduates study in order to develop quality software. Despite their importance, reviews are rarely used in software engineering projects at the baccalaureate level. This paper demonstrates results from a study conducted on students at baccalaureate level enrolled in a one-semester software engineering course at the National University of Computer and Emerging Sciences -- Foundation for Advancement of Science and Technology (NUCES-FAST) in Pakistan. The objectives of the study are: to determine how the various team review techniques help to educate students about the importance of the review process and find which technique is more suitable for teaching reviews to undergraduates. Two variations on team review are proposed: Similar Domain Review (SDR) and Cross-Domain Review (CDR) without author. The paper presents a comparison of the proposed and existing team review techniques and measures their effectiveness in terms of defect detection. The results show that the proposed variation SDR is more effective in defect detection than CDR (with/without author). Another interesting result is that the proposed CDR-without author is better than CDR with author (the existing team review approach). Also, early defect detection enabled students to incorporate changes and improve the software quality.

References

[1]
Bailey, D., Conn, T., Hanks, B. and Werner, L. 2003. Can we influence students' attitudes about inspections? Can we measure a change in attitude? In Proceedings of the 16th Conference on Software Engineering Education and Training (CSEET). IEEE, (Mar. 2003), 260--267.
[2]
Clark, N. 2004. Peer testing in software engineering projects. In Proceedings of the 6th Conference on Australasian Computing Education - Volume 30 (Dunedin, New Zealand). R. Lister and A. Young, Eds. ACM International Conference Proceeding Series, vol. 57. Australian Computer Society, Darlinghurst, Australia, 41--48.
[3]
Collofello, J. S. 1987. Teaching technical reviews in a one-semester software engineering course. In Proceedings of the 18th SIGCSE Technical Symposium on Computer Science Education (Missouri, United States, February 19--20, 1987). SIGCSE '87. ACM, New York, NY, 222--227.
[4]
Collofello, J. S. 1988. The Software Technical Review Process. Curriculum Module SEI-CM-3-1.5, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, Pa.
[5]
Cross, J. A. 1988. Support Materials for the Software Technical Review Process. Support Materials SEI-SM-3-1.0, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, Pa.
[6]
Deimel, L. 1991. Scenes of Software Inspection Video Dramatizations for the Classroom. Software Engineering Institute, Carnegie Mellon University.
[7]
Fagan, M. E. 1976. Design and Code Inspections to Reduce Errors in Program Development. IBM Systems Journal, 15, 182--211.
[8]
Fagan, M. E. 1986. Advances in Software Inspections. IEEE Software SE-12, 744--751.
[9]
http://www.tol.oulu.fi/users/ilkka.tervonen/WChecklist.pdf
[10]
Humphery, W. S. 1989. Managing the Software Process. Addison-Wesley Publishing.
[11]
Institute of Electrical and Electronic Engineers. Standard for Software Reviews and Audits. (Jun 1989) ANSI/IEEE Std 1028--1988.
[12]
Institute of Electrical and Electronic Engineers. Recommended Practice for Software Requirements Specifications, (Dec 1993) IEEE Std 830--1993.
[13]
Kan, S. 2002. Metrics and Models in Software Quality Engineering. Addison-Wesley Publishing.
[14]
Laitenberger, O. and DeBaud, J. 2000. An encompassing life cycle centric survey of software inspection. J. Syst. Softw. 50, 1 (Jan. 2000), 5--31.
[15]
Neil, D. O. 2001. Peer Reviews, Encyclopedia of Software Engineering, Wiley, New York.
[16]
Pressman, R. S. 2001. Software Engineering a Practitioner's Approach. McGraw Hill International.
[17]
Reil, A. J. 2002. Object-Oriented Design Heuristics, Addison Wesley.
[18]
R. S. Pressman & Associates, Inc http://www.rspa.com/checklists/index.html
[19]
Sullivan, S. L. 1994. Reciprocal Peer Reviews. In ACM SIGCSE Bulletin 26, 1, (Mar. 1994), 314--318.
[20]
Wiegers, K. E. 2002. Peer Reviews in Software: A Practical Guide. Addison-Wesley Professional.
[21]
Yourdon, E. 1989. Structured Walkthroughs. 4th Ed. Englewood Cliffs, N.J.: Yourdon Press.
[22]
Zeller, A. 2000. Making students read and review code. In Proceedings of the 5th Annual SIGCSE/SIGCUE Iticseconference on innovation and Technology in Computer Science Education (Helsinki, Finland, July 11--13, 2000). ITiCSE '00. ACM, New York, NY, 89--92.

Cited By

View all
  • (2012)The Effect of Checklist in Code Review for Inexperienced StudentsProceedings of the 2012 IEEE 25th Conference on Software Engineering Education and Training10.1109/CSEET.2012.22(120-124)Online publication date: 17-Apr-2012

Recommendations

Comments

Information & Contributors

Information

Published In

cover image ACM Conferences
ICSE '10: Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1
May 2010
627 pages
ISBN:9781605587196
DOI:10.1145/1806799
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]

Sponsors

Publisher

Association for Computing Machinery

New York, NY, United States

Publication History

Published: 01 May 2010

Permissions

Request permissions for this article.

Check for updates

Qualifiers

  • Research-article

Conference

ICSE '10
Sponsor:

Acceptance Rates

Overall Acceptance Rate 276 of 1,856 submissions, 15%

Upcoming Conference

ICSE 2025

Contributors

Other Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

  • Downloads (Last 12 months)5
  • Downloads (Last 6 weeks)1
Reflects downloads up to 05 Mar 2025

Other Metrics

Citations

Cited By

View all
  • (2012)The Effect of Checklist in Code Review for Inexperienced StudentsProceedings of the 2012 IEEE 25th Conference on Software Engineering Education and Training10.1109/CSEET.2012.22(120-124)Online publication date: 17-Apr-2012

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