CSC/ECE 517 Fall 2014/oss E1456 akk: Difference between revisions
Line 7: | Line 7: | ||
=Why is Refactoring Required= | =Why is Refactoring Required= | ||
*It helps in making the code more understandable | |||
*It makes the code more maintainable | |||
*To remove repetition of code | |||
=Project Overview= | =Project Overview= |
Revision as of 23:13, 29 October 2014
Refactoring Questionnaire Controller
Introduction
Questionnaire Controller interacts with the user to create and edit questionnaires such as review rubrics, teammate-feedback rubrics, quizzes, and surveys. This page provides a detailed description of Open Source Project on Expertiza for refactoring the questionnaire controller.
Why is Refactoring Required
- It helps in making the code more understandable
- It makes the code more maintainable
- To remove repetition of code
Project Overview
Classes involved
- questionnaire_controller.rb
- questionnaire_helper.rb
- advice_controller.rb
Changes made
- Functionality moved to quiz_questionnaire.rb.
- edit_advice method was not being used, so it was removed.
- save_advice moved to the advice_controller.
- copy, update_quiz, valid_quiz methods were long and have been broken up. clone_questionnaire_details was also broken up and renamed.
- Added comments to select_questionnaire_type
- Debug output (print statements) have been removed.
- Changed code to follow the global rules.
- save_new_questions, delete_questions, save_questions have been moved to a separate class.
Project Resources
UML CLass Diagram
A Subset of the UML class diagram including only the related classes for this project can be drawn as shown below.
Questionnaire Controller is the superclass of QuizQuestionnaire and all the other classes - User class, Advice class and Questionnaire classes are related model Classes to the controllers that we have modified.
Questionnaire Controller: questionnaire_controller.rb
Several methods in Questionnaire Controller class required refactoring to ensure that the change is reflected in the entire project. The names were changed to follow method naming conventions in Ruby. Deprecated code was removed and re-coded to ensure that the code worked in future version of Rails as well. Duplicate codes were commented out. Methods that are more general in the sub classes were moved to the parent class. Some methods that calculate that were colliding with other files were moved to a helper method questionnaire_helper.rb .
Sr. No. | Method Name | Changes Made | Reason For Change |
---|---|---|---|
1 |
Code Snippets
1. The quiz questionnaire related methods such as view_quiz, update_quiz, new_quiz and validate_quiz are moved to questionnaire_helper.rb to make the questionnaires_controller thin and follow global rule of thin controllers and fat models.
2. Non Restful method names changed accordingly to make them Restful.
Before
After
3. Global rule changes for using Hash - value key pair
Before Refactoring :- def delete ......... redirect_to :action => 'list', :controller => 'tree_display' ......... After Refactoring :- def delete ......... redirect_to action: 'list', controller: 'tree_display' .........
Before Refactoring :- def edit ......... redirect_to Questionnaire if @questionnaire == nil ......... redirect_to :action => 'view', :id => @questionnaire .......... redirect_to :controller => 'advice', :action => 'edit_advice', :id => params[:questionnaire][:id] .......... After Refactoring :- def edit .......... redirect_to Questionnaire if @questionnaire.eql? nil .......... redirect_to action: 'view', id: @questionnaire ........... redirect_to controller: 'advice', action: 'edit_advice', id: params[:questionnaire][:id] ..........
Before Refactoring Redundant If in def create_questionnaire :- def create_questionnaire ........ if Team.find(t.team_id, @assignment.id) if team = Team.find(t.team_id, @assignment.id) break end end ..... end After Refactoring Redundant If in def create_questionnaire :- def create_questionnaire ........ if Team.find(t.team_id, @assignment.id) #Removed unneeded If statement team = Team.find(t.team_id, @assignment.id) break end end
Before Refactoring Un-necessary Print statements in def create_questionnaire :- def create_questionnaire ....... print "=====create_questionnaire=========" ..... @successful_create = true print "=====save in create_questionnaire begin=========" save print "=====save in create_questionnaire over=========" save_choices @questionnaire.id print "=====save_choice in create_questionnaire over=========" if @successful_create == true flash[:note] = "Quiz was successfully created" end After Refactoring Un-necessary Print statements in def create_questionnaire :- def create_questionnaire ....... # print "=====create_questionnaire=========" ....... @successful_create = true # print "=====save in create_questionnaire begin=========" save # print "=====save in create_questionnaire over=========" save_choices @questionnaire.id # print "=====save_choice in create_questionnaire over=========" if @successful_create == true flash[:note] = "Quiz was successfully created" end
Before Refactoring Global rules :- def create_questionnaire ....... redirect_to :controller => 'submitted_content', :action => 'edit', :id => participant_id ....... After Refactoring Global rules :- def create_questionnaire ....... redirect_to controller: 'submitted_content', action: 'edit', id: participant_id .......
Before Refactoring Global rules :- def create_questionnaire ....... redirect_to :controller => 'tree_display', :action => 'list' ....... After Refactoring Global rules :- def create_questionnaire ....... redirect_to controller: 'tree_display', action: 'list' ........
Before Refactoring Global rules :- def create ....... redirect_to :controller => 'tree_display', :action => 'list' ....... After Refactoring Global rules :- def create ....... redirect_to controller: 'tree_display', action: 'list' .......
Before refactoring Global rules :- def update ........ redirect_to :controller => 'tree_display', :action => 'list' ........ After Refactoring Global rules :- def update ........ redirect_to controller: 'tree_display', action: 'list' .........
Before Refactoring Global rules :- def toggle_access ........ redirect_to :controller => 'tree_display', :action => 'list' end After Refactoring global rules :- def toggle_access ........ redirect_to controller: 'tree_display', action: 'list' ........
Before Refactoring Global rules :- def save ....... save_questions @questionnaire.id if @questionnaire.id != nil and @questionnaire.id > 0 ....... QuestionnaireNode.create(:parent_id => parent.id, :node_object_id => @questionnaire.id) ....... After refactoring Global rules :- def save ....... save_questions @questionnaire.id if @questionnaire.id != nil && @questionnaire.id > 0 ....... QuestionnaireNode.create(parent_id: parent.id, node_object_id: @questionnaire.id) .......
Conclusion
- Refactoring was performed as per requirements in the files questionnaire_controller.rb, and advice_controller.rb.
- The code from models cannot be moved directly to controllers, so the code was moved to the helper class questionnaire_helper.rb.
- Some methods with confusing method names have also been renamed.
References
Expertiza
Code Refactoring Wiki
Global Rules for Refactoring
Why Refactor