Guiding Identification of Missing Scenarios for Dynamic Feature Location
0 likes28,857 views
1) The document discusses identifying missing scenarios for dynamic feature location which involves specifying modules based on execution profiles obtained from scenarios. A lack of scenarios can lead to insufficient results. 2) It proposes finding clues for new scenarios by prioritizing which unexplored call dependencies to focus on for preparing additional scenarios. This is done by measuring the potential impact of unexplored dependencies using metrics like the number of outgoing unexplored dependencies. 3) The aim is to help guide the identification of missing scenarios that could provide more complete feature location results.
1 of 4
Download to read offline
More Related Content
Ad
Viewers also liked (10)
Ad
Similar to Guiding Identification of Missing Scenarios for Dynamic Feature Location (11)
More from Institute of Science Tokyo (9)
Recently uploaded (20)
Guiding Identification of Missing Scenarios for Dynamic Feature Location
- 1. Guiding Identification of Missing Scenarios for Dynamic Feature Location Shinpei Hayashi,†1 Hiroshi Kazato,†2 Takashi Kobayashi,†1 Tsuyoshi Oshima,†3 Katsuyuki Natsukawa,†3 Takashi Hoshino,†3 and Motoshi Saeki†1 †1 Tokyo Institute of Technology †2 NTT DATA CORPORATION †3 NTT Software Innovation Center
- 2. Dynamic Feature Location l Specifying modules based on the execution profiles obtained using scenarios – Lack of scenarios leads to insufficient results Feature implementation Scenario 1 Scenario 2 Missing non-invoked modules Found
- 3. Finding Clues for New Scenarios l Which unexplored call dependencies ( ) should we focus on for preparing new scenarios? Problem: ? ? ? ? ? ? ?? ? ?
- 4. Prioritization Deps. by Metrics l Measuring the potential impact of unexplored dependencies – NODU(dep): number of outgoing unexplored deps. = 5 dep Incoming modules/dependencies (reaching/using d) Outgoing modules/dependencies (reached/used by d) Solution: 1 2 3 4 5