Campus Event Calendar
Event Entry
What and Who
Token Based Risk-Classification of Software Components
Melih Demir
IMPRS
Talk
AG 1, AG 2, AG 3, AG 4, AG 5
MPI Audience
Note: We use this to send email in the morning.
Date, Time and Location
Tuesday, 13 December 2005
13:00
60 Minutes
46.1 - MPII
0.24
Saarbrücken
Abstract
It is always desirable to deliver a software product to the end user with
the least number of defects. For that purpose, it is important to know in
which components more effort should be spent, in other words which
components are more likely to contain defects. Such components should be
considered as "risky" and examined more carefully.
Our approach uses tokens derived from source code and aims to identify
relations between source code and the risk of components as measured by
post release failures.
the least number of defects. For that purpose, it is important to know in
which components more effort should be spent, in other words which
components are more likely to contain defects. Such components should be
considered as "risky" and examined more carefully.
Our approach uses tokens derived from source code and aims to identify
relations between source code and the risk of components as measured by
post release failures.
Contact
Kerstin Meyer-Ross
9325-226
--email hidden
passcode not visible
logged in users only
Friederike Gerndt, 12/06/2005 12:16 -- Created document.