Advances in software inspections
IEEE Transactions on Software Engineering
Teaching technical reviews in a one-semester software engineering course
SIGCSE '87 Proceedings of the eighteenth SIGCSE technical symposium on Computer science education
Structured walkthroughs: 4th edition
Structured walkthroughs: 4th edition
Managing the software process
SIGCSE '94 Proceedings of the twenty-fifth SIGCSE symposium on Computer science education
An encompassing life cycle centric survey of software inspection
Journal of Systems and Software
Making students read and review code
Proceedings of the 5th annual SIGCSE/SIGCUE ITiCSEconference on Innovation and technology in computer science education
Peer reviews in software: a practical guide
Peer reviews in software: a practical guide
Metrics and Models in Software Quality Engineering
Metrics and Models in Software Quality Engineering
Software Engineering: A Practitioner's Approach
Software Engineering: A Practitioner's Approach
Can We Influence Students' Attitudes About Inspections? Can We Measure a Change in Attitude?
CSEET '03 Proceedings of the 16th Conference on Software Engineering Education and Training
Peer testing in Software Engineering Projects
ACE '04 Proceedings of the Sixth Australasian Conference on Computing Education - Volume 30
Design and code inspections to reduce errors in program development
IBM Systems Journal
Hi-index | 0.00 |
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.