CSC/ECE 517 Fall 2015/oss E1552 NRR: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
<b>'''E1552 Refactoring dynamic_review_assignment_helper.rb and dynamic_quiz_assignment_helper.rb'''</b> | <font size="4"><b>'''E1552 Refactoring dynamic_review_assignment_helper.rb and dynamic_quiz_assignment_helper.rb'''</b></font> | ||
=='''Overview'''== | |||
===Refactoring=== | |||
Refactoring is the process of changing a software system in such a way that it does not alter the external behavior of the code yet improves its internal structure<ref>[https://books.google.com/books/about/Refactoring.html?id=HmrDHwgkbPsC&printsec=frontcover&source=kp_read_button#v=onepage&q&f=false]</ref>. It is a disciplined way to clean up code that minimizes the chances of introducing bugs. In essence when you refactor you are improving the design of the code after it has been written. | |||
There are many benefits of refactoring as follows: <ref>[http://www.cs.uni.edu/~wallingf/miscellaneous/student-papers/noborikawa-paper.pdf]</ref> | |||
* Refactoring improves the design of software. Refactoring often cleans up codes by deleting duplicates, divides a big chunk of codes into several methods, and makes the program more understandable. | |||
* Because refactoring makes a design cleaner, it helps the programmers understand codes better and see things that may have not been seen before. | |||
* Refactoring helps spot bugs since it makes the software more comprehensible. | |||
* Refactoring turns an adverse design into a good design, which allows for rapid software development. | |||
=='''References'''== | |||
<references/> | |||
Revision as of 18:54, 31 October 2015
E1552 Refactoring dynamic_review_assignment_helper.rb and dynamic_quiz_assignment_helper.rb
Overview
Refactoring
Refactoring is the process of changing a software system in such a way that it does not alter the external behavior of the code yet improves its internal structure<ref>[1]</ref>. It is a disciplined way to clean up code that minimizes the chances of introducing bugs. In essence when you refactor you are improving the design of the code after it has been written. There are many benefits of refactoring as follows: <ref>[2]</ref>
- Refactoring improves the design of software. Refactoring often cleans up codes by deleting duplicates, divides a big chunk of codes into several methods, and makes the program more understandable.
- Because refactoring makes a design cleaner, it helps the programmers understand codes better and see things that may have not been seen before.
- Refactoring helps spot bugs since it makes the software more comprehensible.
- Refactoring turns an adverse design into a good design, which allows for rapid software development.
References
<references/>