Masahiro Taga

Masahiro Taga

Auto-generated profile, based on publicly available information

Masahiro Taga

E-Seikatsu Co., Ltd., Tokyo, Japan

Research Focus & Metrics

Academic Career Length

10Years (2017-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
1 January 2021 in International Journal of Software Engineering and Knowledge Engineering
Verified
Journal Article
Open access
YWYasuhiro Watanabe
Yasuhiro Watanabe
Hironori WashizakiHironori Washizaki
Hironori Washizaki
YFYoshiaki Fukazawa
Yoshiaki Fukazawa
KHKiyoshi Honda
Kiyoshi Honda
MTMasahiro Taga
Masahiro Taga
TSTakayoshi Suzuki
Takayoshi Suzuki
Business-to-Business (B-to-B) software development companies develop services to satisfy their customers’ requirements. Developers should prioritize customer satisfaction because customers greatly influence agile software development. However, satisfying current customer’s requirements may not fulfill actual users or future customers’ requirements because customers’ requirements are not always derived from actual users. To reconcile these differences, developers should identify conflicts in their strategic plan. This plan should consider current commitments to end users and their intentions as well as employ a data-driven approach to adapt to rapid market changes. A persona models an end user representation in human-centered design. Although previous works have applied personas to software development and proposed data-driven software engineering frameworks with gap analysis between the effectiveness of commitments and expectations, the significance of developers’ commitment and quantitative decision-making are not considered. Developers often do not achieve their business goal due to conflicts. Hence, the target of commitments should be validated. To address these issues, we propose Data-Driven Persona Retrospective (DDR) to help developers plan future releases. DDR, which includes the Persona Significance Index (PerSI) to reflect developers’ commitments to end users’ personas, helps developers identify a gap between developers’ commitments to personas and expectations. In addition, DDR identifies release situations with conflicts based on PerSI. Specifically, we define four release cases, which include different situations and issues, and provide a method to determine the release case based on PerSI. Then we validate the release cases and their determinations through a case study involving a Japanese cloud application and discuss the effectiveness of DDR.

14 April 2024
Verified
Conference Paper
Open access
RSRie Sera
Rie Sera
Hironori WashizakiHironori Washizaki
Hironori Washizaki
JCJunyan Chen
Junyan Chen
YFYoshiaki Fukazawa
Yoshiaki Fukazawa
MTMasahiro Taga
Masahiro Taga
KHKiyoshi Honda
Kiyoshi Honda
Persona --- fictional user profiles --- are used to identify user requirements in software engineering. However, methods targeting revisions, especially for existing B2B services, remain sparse. This paper proposes a method that integrates several models, including k-means clustering, term frequency-inverse document frequency (TF-IDF), and generative AI. Users' behavior tendencies, pain points, and other attributes are output solely from clickstream log data, bypassing the traditional survey-based approaches of previous studies. Clickstreams are vectorized and categorized, whereas users are further analyzed on the basis of time and content of their clickstreams. A case study was conducted with evaluations carried out both quantitatively and qualitatively. The results suggest that, although some parameters still need improvement, fairly rated persona outcomes were attained.

1 October 2017
Verified
Conference Paper
Closed access
KHKiyoshi Honda
Kiyoshi Honda
Hironori WashizakiHironori Washizaki
Hironori Washizaki
YFYoshiaki Fukazawa
Yoshiaki Fukazawa
MTMasahiro Taga
Masahiro Taga
AMAkira Matsuzaki
Akira Matsuzaki
TSTakayoshi Suzuki
Takayoshi Suzuki
Monitoring the results of software reliability growth models (SRGMs) helps evaluate project's situations. SRGMs are used to measure the reliability of software by analyzing the relations between the number of detected bugs and the detected time to predict the number of remaining bugs within the software. For example, development managers apply a SRGM to the number of detected bugs and the detected time to predict the number of remaining bugs. Sometimes the SRGM results cause managers to make incorrect decisions because the results are temporary snapshots that change as a development progresses. We propose a method to help evaluate a project's qualities by monitoring the results of SRGM applications. We collected the number of detected bugs and the detected time in the test phases for cloud services provided by e-Seikatsu Co., Ltd. to real estate businesses. The datasets contain about 34 cloud service features. The evaluation found that our method provides correct answers for 29 features and incorrect answers for 5 features.