guiding identification of missing scenarios for dynamic feature location

4
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

Upload: shinpei-hayashi

Post on 19-Mar-2017

959 views

Category:

Software


2 download

TRANSCRIPT

Page 1: Guiding Identification of Missing Scenarios for Dynamic Feature Location

Guiding Identificationof Missing Scenarios

for Dynamic Feature Location

Shinpei Hayashi,†1

Hiroshi Kazato,†2

Takashi Kobayashi,†1

Tsuyoshi Oshima,†3

Katsuyuki Natsukawa,†3

Takashi Hoshino,†3 andMotoshi Saeki†1

†1 Tokyo Institute of Technology†2 NTT DATA CORPORATION†3 NTT Software Innovation Center

Page 2: Guiding Identification of Missing Scenarios for Dynamic Feature Location

Dynamic Feature Locationl Specifying modules based on the execution profiles

obtained using scenarios– Lack of scenarios leads to insufficient results

Feature implementation

Scen

ario

1Sc

enar

io2

Missingnon-invokedmodules

Found

Page 3: Guiding Identification of Missing Scenarios for Dynamic Feature Location

Finding Clues for New Scenariosl Which unexplored call dependencies ( )

should we focus on for preparing new scenarios?

Problem:

??

?? ?

?

??

?

?

Page 4: Guiding Identification of Missing Scenarios for Dynamic Feature Location

Prioritization Deps. by Metricsl Measuring the potential impact of unexplored

dependencies– NODU(dep): number of outgoing unexplored deps. = 5

dep

Incomingmodules/dependencies

(reaching/using d)

Outgoingmodules/dependencies(reached/used by d)

Solution:

1

2

34

5