This document provides an overview and status update of tools that visualize risks and potential project delays in the software testing lifecycle. The tools include a Quality Dashboard and SRGC App. They collect and analyze test data to predict project quality and risk levels in advance. Currently, the tools import daily report data, display risk levels for various projects, and project managers can identify projects that may need attention. Going forward, the presenters want the two tools to better collaborate by predicting completion dates and proposing additional testing where needed.

1. 
STLC（ソフトウェア・テスト・ライフサイクル）における
リスクとプロジェクトの遅延を表示するツール
30th Mar 2022
Cayetano Clint, Chihiro Kudo
Rakuten Group, Inc.
Test Engineers Meet up #4

2. 2
Agenda
1. Self introduction
2. Overview
3. Why we need this tools
4. How achieve
5. System architecture?
6. Current operation status
7. Next step

3. 3
Self-introduction / 自己紹介
Chihiro Kudo | Gray
Nagasaki city
University of Miyazaki
Scuba Diving,Tea, Photography
Twitter：@kudo_chihiro

4. 4
About me
Clint Cayetano
• Joined Rakuten in September 2016
• Around 15 years in Product Development and Quality
Assurance
• Around 8 years experience inTest Automation
• Likes to travel, read books & articles

5. 5
Overview
Click and Jump
“Quality Dashboard” “SRGC App”

6. 6
Overview
Click and Jump
“Quality Dashboard” “SRGC App”
Visualize

7. 7
Overview
Click and Jump
“Quality Dashboard” “SRGC App”
Visualize Predict

8. 8
Agenda
1. Self introduction
2. Overview
3. Why we need this tools
4. How achieve
5. System architecture?
6. Current operation status
7. Next step

9. 9
Why we need this tools
Stakeholders
Project A Project B
Project D
Project C
Project F
Project E
Product risks tend not to surface
and are often found late

10. 10
Why we need this tools
Stakeholders
Project A Project B
Project D
Project C
Project F
Project E
It’s not easy to understand the
product risk for each projects

11. 11
Why we need this tools
Stakeholders
Project A Project B
Project D
Project C
Project F
Project E
Difficult to handle in advance
It’s not easy to understand the
product risk for each projects

12. 12
If the product risk is visible Project A Project B
Project D
Project C
Project F
Project E
On Schedule
High Risk
Delayed
Stakeholders
On Schedule
On Schedule
On Schedule

13. 13
If the product risk is visible Project A Project B
Project D
Project C
Project F
Project E
Easy to grasp the product risk!!
High Risk
Delayed
Stakeholders
On Schedule On Schedule
On Schedule
On Schedule

14. 14
If the product risk is visible Project A Project B
Project D
Project C
Project F
Project E
High Risk
Delayed
On Schedule On Schedule
On Schedule
On Schedule
Stakeholders
Detect signs of product risk
and take the initiative
Easy to grasp the product risk!!

15. 15
Visualize and predict the status of PRJ using data and analysis methods! !!
Quality Dashboard + SRGC
Predict Project Quality in advance
Test Data
Analysis methods

16. 16
Agenda
1. Self introduction
2. Overview
3. Why this tools needed
4. How achieve
5. System architecture?
6. Current operation status
7. Next step

17. 17
システムの全体図
Daily Report QA Data base
Quality Dashboard + SRGC
Overview of QD + SRGC + QD Database + Daily Report

18. 18
以前のテスト実績報告形式
部署 D
MicrosoftTeams
Email
Viber
報告フォーマット
なし
部署 A
部署 B
部署 C

19. 19
一元管理されたデータストアが存在しない
部署 D
MicrosoftTeams
Email
Viber
報告フォーマット
なし
部署 A
部署 B
部署 C
No Unified Data store

20. 20
データを一元的に集約したい
部署 D
MicrosoftTeams
Email
Viber
報告フォーマット
なし
部署 A
部署 B
部署 C

21. 21
報告フォーマットの統一
部署 D
JIRA
部署 A
部署 B
部署 C
JIRA
JIRA JIRA

22. 22
報告フォーマットの統一
部署 D
部署 A
部署 B
部署 C
Easy to collect data
JIRA JIRA
JIRA JIRA

23. 23
データ収集と蓄積
Daily Report （JIRA） QA Data base
※Detail data

24. 24
データの取得と利用
QA Data base
API
Quality Dashboard + SRGC

25. 25
Agenda
1. Self introduction
2. Overview
3. Why this tools needed
4. How achieve
5. System architecture?
6. Current operation status
7. Next step

26. 26
システムの全体図
Daily Report QA Data base
Quality Dashboard + SRGC
Overview of QD + SRGC + QD Database + Daily Report

27. 27
QA Data Access + SRGC & Quality Dashboard View Tech Stack
Database
MySQL
Rest API
Spring-boot
View
Express (Node.js)
Kanboard (PHP)

28. 28
システムの全体図
Daily Report QA Data base
Quality Dashboard + SRGC
Overview of QD + SRGC + QD Database + Daily Report

29. 29
Data Import (1)
QA members create daily report in the ticket management system.
Ticket
Management
QA
Daily Report

30. 30
Data Import (2)
To be able to successfully import data, the data should have standard format that is
followed by all reporters.

31. 31
Data Import (3)
These reports are imported daily and stored in QA report database
QA Data DB
Ticket
Management
QA Data API
Import Data
C
R
U
D
TIME SCHEDULED TASK
4 AM Import daily report data from ticket management system

32. 32
Data Import (4)
New threshold data will be automatically created. Default: 5
QA Data DB
Ticket
Management
QA Data API
Import Data
C
R
U
D
TIME SCHEDULED TASK
4 AM Import daily report data from ticket management system
5 AM Create threshold data for new products

33. 33
Data Flow
The master data imported from ticket management system is preserved in database and
APIs consume those original data
QA Data DB
Ticket
Management
QA QA Data API SRGCViewer
Quality Dashboard
Daily Report Import Data Get Project Data
C
R
U
D

34. 34
システムの全体図
Daily Report QA Data base
Quality Dashboard + SRGC
Overview of QD + SRGC + QD Database + Daily Report

35. 35
Quality Dashboardの全体図
Apache
PHP API
Update batch
PHP Front
Http Server
Get Latest QA data
Update QD info

36. 36
Quality Dashboardのリスクレベル表示
Normal Project（Green）
※Exceed threshold
※Already delayed
※On schedule and not exceed threshold

37. 37
How to judge the risk level
企業秘密！❤️
I'm sorry ... I’d like to skip explanation on this time

38. 38
システムの全体図
Daily Report QA Data base
Quality Dashboard + SRGC
Overview of QD + SRGC + QD Database + Daily Report

39. 39
SRGC View
We use 3 formula to generate the graph in SRGCView page of the project.
By combining then project threshold value and daily bug report using configurable
parameters, the graph is displayed.
Type Formula Parameters
Logistic Curve y=a/(1+b*EXP(-c*x)) 3
Gompertz Curve y=a*EXP(-b*c^x) 3
Delayed-S Shaped Curve y=a*(1-(1+b*x)*EXP(-b*x)) 2
DEPT – PRODUCT (Threshold: 5)
Product
Sample Graph

40. 40
Agenda
1. Self introduction
2. Overview
3. Why this tools needed
4. How achieve
5. System architecture?
6. Current operation status
7. Next step

41. 41
Current operation status
Stakeholders
Project A Project B
Project D
Project C
Project F
Project E
No Issue!! No Issue!!
High Risk No Issue!!
Delayed No Issue!!
Project PICs
Pay attention to the status of each PRJ
and pick it up in the Daily MTG of each
team.

42. 42
Stakeholders
Current operation status Project A Project B
Project D
Project C
Project F
Project E
Pay attention to the status of each PRJ
and pick it up in the Daily MTG of each
team.
No Issue!! No Issue!!
High Risk No Issue!!
Delayed No Issue!!
Project PICs
Can take the initiative in the PRJs
that have signs of product risk

43. 43
Agenda
1. Self introduction
2. Overview
3. Why this tools needed
4. How achieve
5. System architecture?
6. Current operation status
7. Next step

44. 44
Next step
Click and Jump
CollaborateTwo tools
“Quality Dashboard” “SRGC App”

45. 45
Image of what we want to do next
“Quality Dashboard” “SRGC App”
Click and Jump
予測収束日
今日はこことして
追加テストの提案
本来の実施完了予定日
追加テストが必要！
実施完了予定日をX日過ぎそう！

46. 46
Thank You!!!