¥¼¥ß¥Ê¡¼¥ëȯɽ

Æü»þ: 9·î28Æü(¿å)1¸Â¡Ê9:20-10:50¡Ë


²ñ¾ì: L£±

»Ê²ñ: Æ£ËÜ ¤Þ¤Ê¤È
°ì¥ÎÀ¥ ÃÒ¹À 1551010: M, 2²óÌÜȯɽ ¥½¥Õ¥È¥¦¥§¥¢¹©³Ø ¾¾ËÜ ·ò°ì,°ÂËÜ ·Ä°ì,Ȫ ½¨ÌÀ
title: Removing Self-Admitted Technical Debt with Gamification
abstract:
Technical debt is a metaphor that has been used to express non-optimal solutions of software development, for example, incomplete implementation, requiring rework, producing errors, or a temporary workaround. Although it can accelerate development in the short term, it lowers maintainability of the software in the long term. Self-admitted technical debt is a kind of technical debt that is intentionally introduced into source code with keywords such as "TODO" or "FIXME". Self-admitted technical debt can be seen in many Open Source Software (OSS) projects, and may make development of them slow by lowering maintainability. Therefore, self-admitted technical debt should be removed early after it is introduced. In this study, I develop a system that assists removing self-admitted technical debt with visualization and gamification. The system visualizes the directory structure of the source files as a city on web browser, and makes source code¥æs building with self-admitted technical debt obvious. The system also shows the ranking of the number of removed self-admitted technical debt by each developer, and motivates developers to remove them by stimulating a competition.
language of the presentation:Japanese
 
¾®Ìî ·ò°ì 1551028: M, 2²óÌÜȯɽ ¥½¥Õ¥È¥¦¥§¥¢¹©³Ø ¾¾ËÜ ·ò°ì,°ÂËÜ ·Ä°ì,°Ë¸¶ ¾´µª
title: Identification of an acceptable developers for code-review requests
abstract: Open Source Software (OSS) developers are often different from their expertise, background, and lifestyle among individuals. They could contribute their interest tasks to develop OSS. While they sometimes get a request task such as a bug-fix and a code-review from the other OSS project members, those tasks are not necessarily mandatory. The goal of my study proposes an approach to identify a developer who will accept the requests. Through my case study using Qt project, my study found that a developer is likely to contribute a review-request for the module which the developer has reviewed.
language of the presentation: Japanese
 
Æ£ÎÓ Âçµ£ 1551091: M, 2²óÌÜȯɽ ¥½¥Õ¥È¥¦¥§¥¢¹©³Ø ¾¾ËÜ ·ò°ì,°ÂËÜ ·Ä°ì,¹ÓËÒ ±Ñ¼£,°Ë¸¶ ¾´µª

Toward understanding the condition of library to introduce them

- A Case Study of Apache Software Foundation -


Software developers often use Open Source Software (OSS) libraries to reduce costs and import the latest technology. Many of those OSS libraries are developed and released in Github. The newest version does not always have high quality, because OSS projects aim to release the software as soon as possible and expect to be reviewed the software by many user. Hence, users need to find reliable library from past releases. I conduct an empirical study to identify reliable library.