Proceedings of the XXXI Brazilian Symposium on Software Engineering 2017
DOI: 10.1145/3131151.3131161
|View full text |Cite
|
Sign up to set email alerts
|

Investigating the Effectiveness of Peer Code Review in Distributed Software Development

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

4
19
0

Year Published

2019
2019
2024
2024

Publication Types

Select...
4
3

Relationship

0
7

Authors

Journals

citations
Cited by 18 publications
(23 citation statements)
references
References 31 publications
4
19
0
Order By: Relevance
“…This category involves factors i.e. team organization, team strategies, team culture, team, and team drive [8], [9], [11], [16], [32], [52], [48], [40], [53].…”
Section: B Knowledge Sharing Factors In Mcrmentioning
confidence: 99%
See 3 more Smart Citations
“…This category involves factors i.e. team organization, team strategies, team culture, team, and team drive [8], [9], [11], [16], [32], [52], [48], [40], [53].…”
Section: B Knowledge Sharing Factors In Mcrmentioning
confidence: 99%
“…Although MCR has addressed many shortcomings of Fagan's code inspections and is developed to improve software and code quality through extensive knowledge sharing among MCR team members [6], [8], [9], [11], [12], however, the MCR generates waiting waste due to poor knowledge sharing [5], [8], [13], [14], [15], [16], [17], [18].…”
Section: Introductionmentioning
confidence: 99%
See 2 more Smart Citations
“…Situational software engineering ensures the software engineers' sustainability [9], [11], [15]. The previous work established that researchers have highlighted the significance of situational factors identification and attention has been given on the identification of situational factors in software requirement and for software development [3], [8], [9], [10], [11], [12], however, little indication is available concerning to Modern Code Review (MCR) [30], [31], [32], [33], [34]. It results in the unavailability of situational guidelines that can help software engineers to increase their competency for the identification of situational factors.…”
Section: Introductionmentioning
confidence: 99%