Programs are not only a tool for the simplification or automation of everyday tasks; they also represent a significant time and money investment. A program's life may span years, or even decades, which creates certain risks for the stakeholders involved. To mitigate the risks associated with these legacy systems, software renovation can be undertaken. Software renovation can be described as a series of processes and/or tools used to modernize a legacy system, thereby preserving and maintaining the investment it represents while decreasing the risks associated with it. In this thesis, the focus is on renovation of software created by in-house development. A series of case studies will be examined to demonstrate basic renovation strategies, including the formation of goals for a renovation and exploring trade-offs between robustness, performance, and usability.
","abstract_html":"<p>Programs are not only a tool for the simplification or automation of everyday tasks; they also represent a significant time and money investment. A program's life may span years, or even decades, which creates certain risks for the stakeholders involved. To mitigate the risks associated with these legacy systems, software renovation can be undertaken. Software renovation can be described as a series of processes and/or tools used to modernize a legacy system, thereby preserving and maintaining the investment it represents while decreasing the risks associated with it. In this thesis, the focus is on renovation of software created by in-house development. A series of case studies will be examined to demonstrate basic renovation strategies, including the formation of goals for a renovation and exploring trade-offs between robustness, performance, and usability.</p>","abstract_has_math":false,"creators":["Horton, Brian"],"institution":null,"degree_name":"M.S.","degree_level":"Thesis-Restricted","degree_discipline":"Computer Science","degree_department":null,"school":null,"contributors":["Tu, Shengru","Nino, Jaime","Roussev, Vassil"],"advisors":[],"committee_chairs":[],"committee_members":[],"year":2010,"date_issued":"2010-12-17T08:00:00Z","date_published":"2010-12-17T08:00:00Z","updated_at":"2026-07-24T05:28:04Z","subjects":["Methodologies","Code Design","Programming Paradigms","Maintenance"],"languages":[],"rights":[],"rights_urls":[],"identifier_entries":[]},"links":{"outbound_url":"https://scholarworks.uno.edu/td/112","outbound_label":"Repository record","outbound_source":"dc:identifier"},"metadata_groups":[{"id":"people","label":"People","entries":[{"key":"dc:contributor","label":"Contributor","values":["Tu, Shengru","Nino, Jaime","Roussev, Vassil"]},{"key":"dc:creator","label":"Author","values":["Horton, Brian"]}]},{"id":"academic_context","label":"Academic Context","entries":[{"key":"thesis:degree_discipline","label":"Discipline","values":["Computer Science"]},{"key":"thesis:degree_level","label":"Degree Level","values":["Thesis-Restricted"]},{"key":"thesis:degree_name","label":"Degree Name","values":["M.S."]}]},{"id":"subjects_keywords","label":"Subjects and Keywords","entries":[{"key":"dc:subject","label":"Dc Subject","values":["Methodologies","Code Design","Programming Paradigms","Maintenance"]}]},{"id":"identifiers","label":"Identifiers","entries":[{"key":"dc:identifier","label":"Identifier","values":["https://scholarworks.uno.edu/td/112"]}]},{"id":"additional","label":"Additional Metadata","entries":[{"key":"dc:description.abstract","label":"Abstract","values":["Programs are not only a tool for the simplification or automation of everyday tasks; they also represent a significant time and money investment. A program's life may span years, or even decades, which creates certain risks for the stakeholders involved. To mitigate the risks associated with these legacy systems, software renovation can be undertaken. Software renovation can be described as a series of processes and/or tools used to modernize a legacy system, thereby preserving and maintaining the investment it represents while decreasing the risks associated with it. In this thesis, the focus is on renovation of software created by in-house development. A series of case studies will be examined to demonstrate basic renovation strategies, including the formation of goals for a renovation and exploring trade-offs between robustness, performance, and usability.
"]},{"key":"dc:title","label":"Title","values":["Software Renovation: An In-house Perspective with Case Studies"]}]}],"canonical_facts":{"dc:contributor":["Tu, Shengru","Nino, Jaime","Roussev, Vassil"],"dc:creator":["Horton, Brian"],"dc:description.abstract":["Programs are not only a tool for the simplification or automation of everyday tasks; they also represent a significant time and money investment. A program's life may span years, or even decades, which creates certain risks for the stakeholders involved. To mitigate the risks associated with these legacy systems, software renovation can be undertaken. Software renovation can be described as a series of processes and/or tools used to modernize a legacy system, thereby preserving and maintaining the investment it represents while decreasing the risks associated with it. In this thesis, the focus is on renovation of software created by in-house development. A series of case studies will be examined to demonstrate basic renovation strategies, including the formation of goals for a renovation and exploring trade-offs between robustness, performance, and usability.
"],"dc:identifier":["https://scholarworks.uno.edu/td/112"],"dc:subject":["Methodologies","Code Design","Programming Paradigms","Maintenance"],"dc:title":["Software Renovation: An In-house Perspective with Case Studies"],"thesis:degree_discipline":["Computer Science"],"thesis:degree_level":["Thesis-Restricted"],"thesis:degree_name":["M.S."]},"updated_at":"2026-07-24T05:28:04Z"}