CSC/ECE 517 Fall 2015/oss E1569 JNR: Difference between revisions
No edit summary |
No edit summary |
||
| Line 6: | Line 6: | ||
=Refactoring= | =Refactoring= | ||
Refactoring is a process designed to change code without modifying the functionality. Refactoring can improve the readability and the logical design of the software, making sure everything is in the right place and has the right name. This allows code to be understood more quickly by a developer, which shortens the time it takes to develop new features. | [https://en.wikipedia.org/wiki/Code_refactoring Refactoring] is a process designed to change code without modifying the functionality. Refactoring can improve the readability and the logical design of the software, making sure everything is in the right place and has the right name. This allows code to be understood more quickly by a developer, which shortens the time it takes to develop new features. | ||
= References= | = References= | ||
<references/> | <references/> | ||
Revision as of 03:56, 31 October 2015
E1569: Refactoring ReviewMappingController
This page provides a description of our Expertiza based OSS project, which aimed at refactoring the ReviewMappingController.
Introduction
Expertiza is an Open Source software tool developed at NC State University. It is used to facilitate assignment and course management. It is primarily intended to facilitate assignments being peer reviewed. It is written as a Ruby on Rails application, thus functioning natively in a web environment. It can be cloned from GitHub.
Refactoring
Refactoring is a process designed to change code without modifying the functionality. Refactoring can improve the readability and the logical design of the software, making sure everything is in the right place and has the right name. This allows code to be understood more quickly by a developer, which shortens the time it takes to develop new features.
References
<references/>