We use GoalExplorer and PermDroid to build the static GUI transition graph for 300 real-world Android apps respectively, where 100 apps are close-source apps and 200 apps are open-source apps.
Tips : OSA: open-source applications. CSA: close-source applications.
Table 1 shows the statistical information of the static GUI modeling results of 300 real-world Android apps by GoalExplorer and PermDroid
|
Tool |
GoalExplorer |
PermDroid |
||
|
Category of App |
OSA |
CSA |
OSA |
CSA |
|
Success Rate of Modeling |
78.5% |
43% |
98.5% |
100% |
|
Number of Models with Edges |
14 |
1 |
171 |
93 |
For 100 CSA, the success rate of modeling of GoalExplorer is only 43%, i.e., 43 apps are successfully modeled. Among the 43 GUI models, only one model has edges; the success rate of modeling of PermDroid is 100%, and the GUI models of 93 apps have edges.
For 200 OSA, the success rate of modeling of GoalExplorer is 78.5%, and only 14 models have edges; the success rate of PermDroid is 98.5%, and 197 apps have been successfully modeled, including 171 models with edges.
In CSA, The average number of edges of GoalExplorer is only 0.26, but that of PermDroid is 13.10. GoalExpleror takes about 30 minutes to build the GUI model, while PermDroid takes about 3.7 minutes.
For STG (State Transition Graph) generation, PermDroid is superior to GoalExplorer in terms of success rate, completeness, and efficiency.
We run the two tools on a 64-bit Windows 10 physical machine with an Intel Core i7-7700 CPU and 32GB of RAM.