37th Annual Hawaii International Conference on System Sciences, 2004. Proceedings of The 2004
DOI: 10.1109/hicss.2004.1265711
|View full text |Cite
|
Sign up to set email alerts
|

What makes a code review trustworthy?

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
15
0

Year Published

2005
2005
2017
2017

Publication Types

Select...
4
1
1

Relationship

1
5

Authors

Journals

citations
Cited by 15 publications
(15 citation statements)
references
References 8 publications
0
15
0
Order By: Relevance
“…Since that time it has played an important role in the life cycle of numerous projects. When done properly, it may help spreading knowledge among developers and encouraging the emergence of code standards for the project (Nelson and Schumann 2004). It also affects the final quality of the project as better code review coverage results in less post-release defects (McIntosh et al 2014).…”
Section: Background and Related Workmentioning
confidence: 99%
See 2 more Smart Citations
“…Since that time it has played an important role in the life cycle of numerous projects. When done properly, it may help spreading knowledge among developers and encouraging the emergence of code standards for the project (Nelson and Schumann 2004). It also affects the final quality of the project as better code review coverage results in less post-release defects (McIntosh et al 2014).…”
Section: Background and Related Workmentioning
confidence: 99%
“…According to the law, a reviewer who scrutinizes a code lying outside his/her knowledge focuses on unimportant details (Rigby and Storey 2011). Furthermore, according to Nelson and Schumann (2004), it is difficult for all reviewers to spot performance problems, race conditions or synchronization issues. Fortunately, some automated tools may aid developers in such cases (Nelson and Schumann 2004).…”
Section: Background and Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…Examples of such mistakes include use of undeclared variables, use of un-initialized variables, out-ofbound array referencing, wrong input of formal parameters in subroutine calls, use of inconsistent data type, and performing mixed-mode computations. A rich body of checklists, coding standards, and literature about this topic has been published [20]. Code review also examines the code to verify that comments are well used throughout and that the program contains no dead or unreachable code.…”
Section: Tools For Automated Static Analysismentioning
confidence: 99%
“…Typical examples include buffer overrun errors, uninitialized variables, or synchronisation problems in distributed system. Table 1 shows a list of important coding error classes for safety-critical software (from [5]). For each error class, the importance to find such bugs (proportional to the risk), as well as the difficulty to locate such errors in the text is given.…”
Section: Errors and Risks In Autonomous Systemsmentioning
confidence: 99%