BEGIN:VCALENDAR
VERSION:2.0
CALSCALE:GREGORIAN
PRODID:iCalendar-Ruby
BEGIN:VEVENT
CATEGORIES:Lecture or Presentation
DESCRIPTION:Using code smells to shape code evolution and robustness in lar
 ge development efforts\n\nAs the complexity of software has increased\, sof
 tware development has evolved from being predominantly performed by small g
 roups of collocated developers to large groups of geographically distribute
 d developers. To successfully work on complex and distributed projects\, de
 velopers need to continuously discuss design decisions and the complexities
  associated with ever-evolving requirements or face increasing amounts of “
 technical debt” in the form of design decisions that don’t hold up and resu
 lt in sub-optimal code. One measure of technical debt is code smell\, a ter
 m used to describe bad design decisions in code\, such as overly complex st
 ructures\, poor compartmentalization of functionality\, etc. Code smells ha
 ve been associated with long-term maintainability problems\, and have also 
 been shown to negatively impact overall quality (buginess) of the software.
  Most of the previous research on code smells has focused on detecting and 
 categorizing different smells. However\, there is little research into how 
 code smell could affect the collaborative development process or software q
 uality. If code smells are not taken care of\, they can effectively mask bu
 gs\, increase the time to find or fix bugs\, and generally the time and eff
 ort needed to perform any future changes to the code. Though code smells ar
 e well-established in the academic literature\, code smells are rarely used
  outside of academic circles. According to a study\, 32% of software develo
 pers don’t know what code smells are\, or how they can be used to evaluate 
 code. My research is to investigate the relationship between code smells\, 
 bugs and code evaluation which in turn can be used by collaborative softwar
 e development teams to make better design decisions and write better code.\
 n\nMajor Advisor: Carlos Jensen\nCommittee: Margaret Burnett\nCommittee: An
 ita Sarma\nCommittee: Arash Termehchy\nGCR: Margaret L Niess
DTEND:20181128T230000Z
DTSTAMP:20260412T194127Z
DTSTART:20181128T210000Z
GEO:44.567164;-123.278692
LOCATION:Kelley Engineering Center\, 1126
SEQUENCE:0
SUMMARY:PhD Preliminary Oral Exam – Umme Ayda Mannan
UID:tag:localist.com\,2008:EventInstance_4116105
URL:https://events.oregonstate.edu/event/phd_preliminary_oral_exam_umme_ayd
 a_mannan
END:VEVENT
END:VCALENDAR
