DSpace Repository

How are IF-Conditional Statements Fixed Through Peer

Show simple item record

dc.contributor.author UEDA, Yuki
dc.contributor.author IHARA, Akinori
dc.contributor.author ISHIO, Takash
dc.contributor.author HIRAO, Toshiki
dc.contributor.author MATSUMOTO, ,Kenichi
dc.date.accessioned 2019-04-04T06:57:28Z
dc.date.available 2019-04-04T06:57:28Z
dc.date.issued 2018-11-01
dc.identifier.issn 0916-8532
dc.identifier.uri http://hdl.handle.net/10061/13129
dc.description.abstract Peer code review is key to ensuring the absence of software defects. To reduce review costs, software developers adopt code convention checking tools that automatically identify maintainability issues in source code. However, these tools do not always address the maintainability issue for a particular project. The goal of this study is to understand how code review fixes conditional statement issues, which are the most frequent changes in software development. We conduct an empirical study to understand if-statement changes through code review. Using review requests in the Qt and OpenStack projects, we analyze changes of the if-conditional statements that are (1) requested to be reviewed, and are (2) revised through code review. We find the most frequently changed symbols are “( )”, “.”, and “!”. We also find project-specific fixing patterns for improving code readability by association rule mining. For example “!” operator is frequently replaced with a function call. These rules are useful for improving a coding convention checker tailored for the projects. ja_JP
dc.language.iso en ja_JP
dc.publisher The Institute of Electronics, Information and Communication Engineers ja_JP
dc.rights c 2018 The Institute of Electronics, Information and Communication Engineers ja_JP
dc.subject codeReview ja_JP
dc.subject code readability ja_JP
dc.subject if statement ja_JP
dc.title How are IF-Conditional Statements Fixed Through Peer ja_JP
dc.type.nii Journal Article ja_JP
dc.contributor.transcription ウエダ, ユウキ
dc.contributor.transcription イハラ, アキノリ
dc.contributor.transcription イシオ, タカシ
dc.contributor.transcription ヒラオ, トシキ
dc.contributor.transcription マツモト, ケンイチ
dc.contributor.alternative 上田, 裕己
dc.contributor.alternative 伊原, 彰紀
dc.contributor.alternative 石尾, 隆
dc.contributor.alternative 平尾, 俊貴
dc.contributor.alternative 松本, 健一
dc.identifier.fulltexturl https://www.jstage.jst.go.jp/article/transinf/E101.D/11/E101.D_2018EDP7004/_article ja_JP
dc.textversion publisher ja_JP
dc.identifier.abstracturl https://www.jstage.jst.go.jp/article/transinf/E101.D/11/E101.D_2018EDP7004/_article#article-overiew-abstract-wrap ja_JP
dc.identifier.ncid AA10826272 ja_JP
dc.identifier.jtitle IEICE Transactions on Information and Systems ja_JP
dc.identifier.volume E101.D ja_JP
dc.identifier.issue 11 ja_JP
dc.identifier.spage 2720 ja_JP
dc.identifier.epage 2729 ja_JP
dc.relation.doi info:doi/10.1587/transinf.2018EDP7004 ja_JP
dc.identifier.NAIST-ID 85626190 ja_JP
dc.identifier.NAIST-ID 82040478 ja_JP
dc.identifier.NAIST-ID 74653577 ja_JP
dc.identifier.NAIST-ID 84367317 ja_JP
dc.identifier.NAIST-ID 73292310 ja_JP

Files in this item

This item appears in the following Collection(s)

Show simple item record

Search DSpace

Advanced Search


My Account