BEGIN:VCALENDAR
VERSION:2.0
METHOD:PUBLISH
X-WR-CALNAME:Events of FSE 2014
PRODID:-//Generated by Conference Publishing//EN
BEGIN:VEVENT
CREATED:20231026T144647Z
DTSTAMP:20231026T144647Z
DTSTART;TZID=Asia/Hong_Kong:20141117T090000
DTEND;TZID=Asia/Hong_Kong:20141117T100000
SUMMARY:Invited Talk 1
LOCATION:Meeting Room 4
DESCRIPTION:Invited Talk 1\n\n
UID:oomo0EeVee
ORGANIZER:ConfPub
CATEGORIES:Conference Program Event
END:VEVENT
BEGIN:VEVENT
CREATED:20231026T144647Z
DTSTAMP:20231026T144647Z
DTSTART;TZID=Asia/Hong_Kong:20141117T100000
DTEND;TZID=Asia/Hong_Kong:20141117T103000
SUMMARY:Technical Presentations 1
LOCATION:Meeting Room 4
DESCRIPTION:Technical Presentations 1\n\n\n\nSoftware crashes are severe ma
 nifestations of software faults. Especially\, software crashes in productio
 n software usually result in bad user experiences. Therefore\, crashing fau
 lts mostly are required to be fixed with a high priority. Diagnosing crashi
 ng faults on production software is non-trivial\, due to the characteristic
 s of production environment. In general\, it is required to address two maj
 or challenges. First\, crash reports in production software are usually num
 erous\, since production software is used by a large number of end users in
  various environments and configurations. Especially\, a single fault may m
 anifest as different crash reports\, which makes the prioritizing debugging
  and understanding faults difficult. Second\, deployed software is required
  to run with minimal overhead and cannot afford a heavyweight instrumentati
 on approach to collect program execution information. Furthermore\, end use
 rs require that the logged information should not reveal sensitive producti
 on data. This thesis contributes for developing crashing fault diagnosis to
 ols that can be used in production environment.\n
UID:pho0Ahtaek
ORGANIZER:ConfPub
CATEGORIES:Conference Program Event
END:VEVENT
BEGIN:VEVENT
CREATED:20231026T144647Z
DTSTAMP:20231026T144647Z
DTSTART;TZID=Asia/Hong_Kong:20141117T110000
DTEND;TZID=Asia/Hong_Kong:20141117T123000
SUMMARY:Technical Presentations 2
LOCATION:Meeting Room 4
DESCRIPTION:Technical Presentations 2\n\nIntegrating Approaches for Feature
  Implementation\n\n\n\nNumerical Program Analysis and Testing\n\n\n\nTracea
 bility and Model Checking to Support Safety Requirement Verification\n\n\n\
 nDealing with Uncertainty in Verification of Nondeterministic Systems\n\n\n
 \n
UID:einoh4aeMe
ORGANIZER:ConfPub
CATEGORIES:Conference Program Event
END:VEVENT
BEGIN:VEVENT
CREATED:20231026T144647Z
DTSTAMP:20231026T144647Z
DTSTART;TZID=Asia/Hong_Kong:20141117T140000
DTEND;TZID=Asia/Hong_Kong:20141117T153000
SUMMARY:Technical Presentations 3
LOCATION:Meeting Room 4
DESCRIPTION:Technical Presentations 3\n\nStatic Analysis Driven Performance
  and Energy Testing\n\n\n\nAutonomous Compliance Monitoring of Non-function
 al Properties\n\n\n\nDetecting\, Isolating\, and Enforcing Dependencies amo
 ng and within Test Cases\n\n\n\nImproving the Software Testing Skills of No
 vices during Onboarding through Social Transparency\n\n\n\n
UID:zoh2Thah8l
ORGANIZER:ConfPub
CATEGORIES:Conference Program Event
END:VEVENT
BEGIN:VEVENT
CREATED:20231026T144647Z
DTSTAMP:20231026T144647Z
DTSTART;TZID=Asia/Hong_Kong:20141117T160000
DTEND;TZID=Asia/Hong_Kong:20141117T163000
SUMMARY:Technical Presentations 4
LOCATION:Meeting Room 4
DESCRIPTION:Technical Presentations 4\n\n\n\nSoftware conflicts arising bec
 ause of conflicting changes are a regular occurrence and delay projects. Wo
 rkspace awareness tools have been proposed to facilitate task coordination 
 among developers\, enabling them to identify potential conflicts early\, wh
 ile conflicts are still easy to resolve. However\, these tools have limitat
 ions\, as they identify conflicts after conflicts have already occurred and
  therefore\, are unable to prevent developers’ time and effort spent in res
 olving the conflicts. The goal of this Ph.D. research is to: (1) characteri
 ze the distribution of conflicts\, their frequency and the factors within a
  project that affects the distribution and frequency of conflicts\, (2) des
 ign and implement a conflict minimization technique that proactively identi
 fies potential conflicts by analyzing developers’ tasks and avoids them by 
 scheduling tasks in a conflict minimal manner and (3) evaluate the proposed
  approach using historic data from OSS projects and through user evaluation
 s. Thus far\, we have implemented our approach and evaluated it with histor
 ic data from four OSS projects and through simulated data.\n
UID:zang0cheeJ
ORGANIZER:ConfPub
CATEGORIES:Conference Program Event
END:VEVENT
BEGIN:VEVENT
CREATED:20231026T144647Z
DTSTAMP:20231026T144647Z
DTSTART;TZID=Asia/Hong_Kong:20141117T163000
DTEND;TZID=Asia/Hong_Kong:20141117T173000
SUMMARY:Invited Talk 2
LOCATION:Meeting Room 4
DESCRIPTION:Invited Talk 2\n\n
UID:Taechai9bo
ORGANIZER:ConfPub
CATEGORIES:Conference Program Event
END:VEVENT
END:VCALENDAR