Extractive Summarization of Development Emails
Extractive Summarization of Development Emails
Extractive Summarization of Development Emails
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
While for strace thread type follows the one <strong>of</strong> natural language thread type.<br />
Figure 4. Average test result for STRACE thread-type<br />
Perhaps such a behavior is due to the fact that people tend to underline always the same things in pieces <strong>of</strong><br />
source code: class names and method signatures. We thought that this happens because they do not represent machine<br />
instructions, but only the functionality <strong>of</strong> the piece <strong>of</strong> code they contain. On the contrary, in case <strong>of</strong> natural<br />
language, a human subject is able to better interpret the text and everyone can build a personal opinion about the<br />
weight <strong>of</strong> every sentence.<br />
Referring to the post-test questionnaire, the participants had to write for every question an integer vote between 1<br />
and 5, with the corresponding extreme values indicated in the question itself. We discovered that on average people<br />
did not find summarizing thread from a system more difficult than from the other, but they found the division<br />
into essential and optional sentences harder for System A rather than System B. This is an interesting aspect to be<br />
inspected: is this task really harder for ArgoUML, or the results are due to the fact that such system was required to<br />
be summarized first and so participants were still unaccustomed to this job?<br />
Figure 5. Average on answers to question “How difficult was it to summarize emails by sentences?" [1 = “very easy", 5 = “very<br />
hard"]<br />
Figure 6. Average on answers to question “How difficult was it to divide sentences into essential and optional?" [1 = “very<br />
easy", 5 = “very hard"]<br />
16