Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2022 - E2277. Further Refactoring questionnaires controller.rb

2022-12-06T03:06:55Z

Penaman:

==Introduction==
This page gives a description of the changes made related to the CRUD operations related to the questionnaire of the Expertiza-based OSS project.

===Expertiza Background ===
Expertiza is a web application where students can submit and peer-review learning objects (articles, codes, websites, etc). Instructors add and grade the assignments submitted by students to Expertiza. Students can be assigned in teams based on their selection of the topics. It has functionalities such as peer reviews in which students can provide feedback on others' work which helps peer in better developing the project. The National Science Foundation supports it.

== Problems Encountered ==

This project builds on E2257. That project focused only on simplifying the methods in questionnaires_controller, while this project's objective is wider. It involves looking at any code related to the questionnaire and performing bug fixes, refactoring and cleanup. This code also introduces the changes made in E2257, as PR related to that required some changes to be made before merging. This was done as some of the current changes build upon changes made in the previous round.

 Suggestion provided in the documentation of the problem 
* Use of temporary variables instead of instance variables wherever possible to narrow their scope.
* question.rb contains a large number of constants. Make explicit comments on their usage, and remove them if not used.
* Since a controller should only create objects of one type the questions_controller could be introduced to create and edit questions moving the logic of dealing with individual questions into a separate controller and improving the separation of responsibility.

 What we have considered 
*Checked the flow of the code, by adding comments to figure out unused functions.
*Check for unused constants.
*Checked code climate issues found.
*Found bugs where expected behaviour wasn't happening.

Since this is an important piece of code with usage at a lot of places we had to be very careful with making changes. We were able to fix most of the bugs and issues we found, but there still exist a few that we didn't have enough time to fix. These have been added to future work so that it can be easier for anyone who picks up the project.

 The issues we have handled are as follows: 
*Presence of many unused functions in the questionnaire questionnaire_controller.rb
*Presence of many unused constants in the model questions.rb
*Unable to update questionnaire parameters.
*Error in the logic used to assign sequence numbers to questions in a questionnaire.
*High severity issue in the way questionnaire and question objects are created (Code Climate)
*Updates made to issues fixed in E2257

==Files Changed==

*app/controllers/questionnaires_controller.rb
*app/models/question.rb
*app/helpers/questionnaire_helper.rb
*app/views/questionnaires/_questionnaire.html.erb
*spec/controllers/questionnaires_controller_spec.rb

== Files Added ==
*app/helpers/question_helper.rb

==Implementation==

* Creating an object of the required questionnaire type is currently performed using Object.const_get, based on user input values. This is a very bad approach (Severity: Critical) according to CodeClimate reports, thus we aim to look at alternative approaches to create an object of the required questionnaire type using Factory Design pattern.
* As discussed before try to move the save functionality out of questionnaire_controller, and into questions_controller. Call it from there where ever needed.
* The questionnaire apparently has a lot of items and not just questions, thus try to rename the usages of questions to items.
* The code has been cleaned many times and functionalities have been moved around a lot, which has made the code messy with a lot of dead code. Have a closer look at each functionality and flow, add comments to each of them (eg. create_node) and remove unnecessary code (eg. many constants).
===Flowchart===

The following will be the process carried out to move the save functionality from questionnaires_controller into questions_controller. But we will also be be using it on every other functionality in both the controllers just to make sure they are at the right places.

[[File:flowchart2277.jpg]]

==Testing==

''''' Testing Plan '''''
# Since we are removing the use of 'Object.const_get' we ran the tests again to see that it is functioning properly.

=== RSPEC Test Cases ===
The current version of expertiza included tests for the questionnaire_controller and qeustions_controller. we plan to modify a few of these tests so that it fits the changes that we have proposed.

To run the tests, run the following commands from the expertiza directory
<pre>
rspec ./spec/controllers/questionnaires_controller_spec.rb
</pre>
<pre>
rspec ./spec/controllers/questions_controller_spec.rb
</pre>

===Manual Testing===

''''' Testing as Instructor'''''
# Login as Instructor.
# Click on Questionnaires.
# Choose a topic and create a new questionnaire.
# Check the save functionality.
# Add a new question to the questionnaire and check the save question functionality.
# delete a question and check if it's reflected properly.

==SOLID Principle==

SOLID is a set of rules that guide us on how to achieve that in object-oriented programming. Using SOLID guidelines you can avoid bad design in your code and give a well-structured architecture to your design. Bad design leads to an inflexible and brittle codebase, a simple and small change can result in bugs with bad design.

We implemented the single responsibility principle to divide the questionnaires_controller into questionnaires and questions controller thus ensuring that each controller does only one job.

==Factory Design pattern==

In Factory pattern, we create object without exposing the creation logic to the client and refer to newly created object using a common interface.

We implemented the factory design pattern to create questionnaire objects based on the type selected by the user. We implemented similar approach for creation of question objects as well.

==References==

* [https://github.com/kailash1998s/expertiza GitHub]

* [https://github.com/expertiza/expertiza/pull/2492 github PR]

* [https://www.rubyguides.com/2015/12/ruby-refactoring/ Introduction to Refactoring in Ruby]

* [http://rspec.info/documentation/3.8/rspec-core/ Rspec Documentation]

==Team Members==

* [mailto:aumasan@ncsu.edu Ashwin Shankar Umasankar]
* [mailto:ksingar2@ncsu.edu Kailash Singaravelu]
* [mailto:penaman@ncsu.edu Pujitha Enamandala]

CSC/ECE 517 Fall 2022 - E2257: Refactor questionnaires controller.rb

2022-10-27T01:40:11Z

Penaman:

==Introduction==
<nowiki>In Expertiza, Questionnaire is the superclass for all kinds of questionnaires and rubrics—rubrics for evaluating submissions and teammate contributions, and taking quizzes and surveys. All of these are subclasses of Questionnaire. questionnaires_controller.rb is charged with creating, displaying, and managing Questionnaires. Because it is used so widely, malfunctions could cause bugs in many parts of the system; hence it is especially important that the code be clear.</nowiki>

==Issues Fixed==
# Removed create_questionnaire
# Split create method into smaller self-documenting methods.
# QuizQuestionnaire check
# Refactor add_new_questions method
# Remove redundant variables in QuestionnairesController

==Files Changed==
*app/controllers/questionnaires_controller.rb
*spec/controllers/questionnaires_controller_spec.rb
*app/models/question.rb

==Changes==
===Fix #1===
The <code>create_questionnnaires</code> method was present but its related functionality had been removed. Some kind of link to it is still present in one of the initial migrations which was populating a database to show values for a drop-down that is no longer in use. Thus ended up removing the function and its corresponding test cases.

===Fix #2===
The <code>create</code> method itself is 49 lines long. This is much too long to be viewable at a glance. Thus the method was broken into <code>adding_question_variables</code> and <code>create_node</code> method so that they are clear enough to be self-documenting.
<nowiki>
def create
if params[:questionnaire][:name].blank?
flash[:error] = 'A rubric or survey must have a title.'
redirect_to controller: 'questionnaires', action: 'new', model: params[:questionnaire][:type], private: params[:questionnaire][:private]
else
questionnaire_private = params[:questionnaire][:private] == 'true'
display_type = params[:questionnaire][:type].split('Questionnaire')[0]
begin
@questionnaire = Object.const_get(params[:questionnaire][:type]).new if Questionnaire::QUESTIONNAIRE_TYPES.include? params[:questionnaire][:type]
rescue StandardError
flash[:error] = $ERROR_INFO
end
begin
# Zhewei: Right now, the display_type in 'questionnaires' table and name in 'tree_folders' table are not consistent.
# In the future, we need to write migration files to make them consistency.
# E1903 : We are not sure of other type of cases, so have added a if statement. If there are only 5 cases, remove the if statement
if %w[AuthorFeedback CourseSurvey TeammateReview GlobalSurvey AssignmentSurvey BookmarkRating].include?(display_type)
display_type = display_type.split(/(?=[A-Z])/).join('%')
end
# setting the object variables
adding_question_variables(questionnaire_private, display_type)
# Create node
create_node()
rescue StandardError
flash[:error] = $ERROR_INFO
end
redirect_to controller: 'questionnaires', action: 'edit', id: @questionnaire.id
end
end</nowiki>

----

<nowiki>
# Assigns corrresponding variables to questionnaire object.
def adding_question_variables(prv,display)
@questionnaire.private = prv
@questionnaire.name = params[:questionnaire][:name]
@questionnaire.instructor_id = session[:user].id
@questionnaire.min_question_score = params[:questionnaire][:min_question_score]
@questionnaire.max_question_score = params[:questionnaire][:max_question_score]
@questionnaire.type = params[:questionnaire][:type]
@questionnaire.display_type = display
@questionnaire.instruction_loc = Questionnaire::DEFAULT_QUESTIONNAIRE_URL
@questionnaire.save
end
</nowiki>

----

<nowiki>
# Creates tree node
def create_node()
tree_folder = TreeFolder.where(['name like ?', @questionnaire.display_type]).first
parent = FolderNode.find_by(node_object_id: tree_folder.id)
QuestionnaireNode.create(parent_id: parent.id, node_object_id: @questionnaire.id, type: 'QuestionnaireNode')
flash[:success] = 'You have successfully created a questionnaire!'
end
</nowiki>

===Fix #3===
There are three checks for whether a questionnaire is a QuizQuestionnaire. Testing the class of an object is always suspect, though, in a controller, which has to control a whole hierarchy of objects, it is not necessarily wrong. However, they probably aren’t necessary. 2 of them seem to have been removed already and the only remaining check was in create_questionnaire, thus it got removed while applying Fix #1.

===Fix #4===

According to the code climate, it was suggested that usage of <code>each_key</code> is preferable instead of <code>keys.each</code> . Rubocop suggests this due to performance. Using large sets of data is where this becomes noticeable. Chaining methods is going to be slower than using the built-in method (in this case) which accomplishes the task with a single special enumerator.

<nowiki>
params[:question].keys.each do |question_key|
</nowiki>

<nowiki>
params[:question].each_key do |question_key|
</nowiki>

===Fix #5===

According to the code climate, it was suggested that the use of parentheses around a method call should be avoided.

<nowiki>
display_type = (display_type.split(/(?=[A-Z])/)).join('%')
</nowiki>

<nowiki>
display_type = display_type.split(/(?=[A-Z])/).join('%')
</nowiki>

===Fix #6===

The add_new_questions method has string literal values like 'Strongly agree', 'Strongly disagree', '50, 3', '0|1|2|3|4|5' for max_label, min_label, size and alternatives. The literals are removed by introducing constants in question.rb.
<nowiki>
if question.is_a? ScoredQuestion
question.weight = params[:question][:weight]
question.max_label = 'Strongly agree'
question.min_label = 'Strongly disagree'
end

question.size = '50, 3' if question.is_a? Criterion
question.size = '50, 3' if question.is_a? Cake
question.alternatives = '0|1|2|3|4|5' if question.is_a? Dropdown
question.size = '60, 5' if question.is_a? TextArea
question.size = '30' if question.is_a? TextField

</nowiki>

<nowiki>
if question.is_a? ScoredQuestion
question.weight = params[:question][:weight]
question.max_label = Question::MAX_LABEL
question.min_label = Question::MIN_LABEL
end

if Question::SIZES.key?(question.class.name)
question.size = Question::SIZES[question.class.name]
end
if Question::ALTERNATIVES.key?(question.class.name)
question.alternatives = Question::ALTERNATIVES[question.class.name]
end
</nowiki>

===Fix #7===

The add_new_questions and save_all_questions methods have reduntant variable defined called questionnaire_id. The variable declaration is redundant as we can access it using params[:id].

<nowiki>
questionnaire_id = params[:id] unless params[:id].nil?
num_of_existed_questions = Questionnaire.find(questionnaire_id).questions.size
</nowiki>

<nowiki>
num_of_existed_questions = Questionnaire.find(params[:id]).questions.size
</nowiki>

=== Future scope ===

===Project Mentor===

Edward Gehringer (efg@ncsu.edu)

===Team Member===

Ashwin Shankar Umasankar [[(aumasan@ncsu.edu)]]

Kailash Singaravelu [[(ksingar2@ncsu.edu)]]

Pujitha Enamandala [[(penaman@ncsu.edu)]]

===Reference===
#[http://152.7.177.154:8080/ VCL link]
#[https://github.com/Ashwinshankar98/expertiza Github Repo]
#[https://github.com/expertiza/expertiza/pull/2470 Github Pull Request]
#[https://github.com/expertiza/expertiza Expertiza on GitHub]
#[http://wikis.lib.ncsu.edu/index.php/Expertiza Expertiza Project Documentation Wiki]
#[https://codeclimate.com/github/expertiza/expertiza/app/controllers/questionnaires_controller.rb CodeClimate Documentation]

CSC/ECE 517 Fall 2022 - E2257: Refactor questionnaires controller.rb

2022-10-27T00:54:19Z

Penaman:

==Introduction==
<nowiki>In Expertiza, Questionnaire is the superclass for all kinds of questionnaires and rubrics—rubrics for evaluating submissions and teammate contributions, and taking quizzes and surveys. All of these are subclasses of Questionnaire. questionnaires_controller.rb is charged with creating, displaying, and managing Questionnaires. Because it is used so widely, malfunctions could cause bugs in many parts of the system; hence it is especially important that the code be clear.</nowiki>

==Issues Fixed==
# Removed create_questionnaire
# Refactor create method ( usage of local variable instead of instance variables)
# QuizQuestionnaire check
# Refactor add_new_questions method
# Remove reduntant variables in QuestionnairesController

==Files Changed==
*app/controllers/questionnaires_controller.rb
*spec/controllers/questionnaires_controller_spec.rb
*app/models/question.rb

==Changes==
===Fix #1===
The <code>create_questionnnaires</code> method was present but its related functionality had been removed. Some kind of link to it is still present in one of the initial migrations which was populating a database to show values for a drop-down that is no longer in use. Thus ended up removing the function and its corresponding test cases.

===Fix #2===
The instance variable <code>@questionnaire</code> is converted to local <code>questionnaire</code> object to reduce its scope. Since in any other method <code>@questionnaire</code> object is initialized again.
<nowiki>
def create
if params[:questionnaire][:name].blank?
flash[:error] = 'A rubric or survey must have a title.'
redirect_to controller: 'questionnaires', action: 'new', model: params[:questionnaire][:type], private: params[:questionnaire][:private]
else
questionnaire_private = params[:questionnaire][:private] == 'true'
display_type = params[:questionnaire][:type].split('Questionnaire')[0]
begin
questionnaire = Object.const_get(params[:questionnaire][:type]).new if Questionnaire::QUESTIONNAIRE_TYPES.include? params[:questionnaire][:type]
rescue StandardError
flash[:error] = $ERROR_INFO
end
begin
questionnaire.private = questionnaire_private
questionnaire.name = params[:questionnaire][:name]
questionnaire.instructor_id = session[:user].id
questionnaire.min_question_score = params[:questionnaire][:min_question_score]
questionnaire.max_question_score = params[:questionnaire][:max_question_score]
questionnaire.type = params[:questionnaire][:type]
# Zhewei: Right now, the display_type in 'questionnaires' table and name in 'tree_folders' table are not consistent.
# In the future, we need to write migration files to make them consistency.
# E1903 : We are not sure of other type of cases, so have added a if statement. If there are only 5 cases, remove the if statement
if %w[AuthorFeedback CourseSurvey TeammateReview GlobalSurvey AssignmentSurvey BookmarkRating].include?(display_type)
display_type = (display_type.split(/(?=[A-Z])/)).join('%')
end
questionnaire.display_type = display_type
questionnaire.instruction_loc = Questionnaire::DEFAULT_QUESTIONNAIRE_URL
questionnaire.save
# Create node
tree_folder = TreeFolder.where(['name like ?', questionnaire.display_type]).first
parent = FolderNode.find_by(node_object_id: tree_folder.id)
QuestionnaireNode.create(parent_id: parent.id, node_object_id: questionnaire.id, type: 'QuestionnaireNode')
flash[:success] = 'You have successfully created a questionnaire!'
rescue StandardError
flash[:error] = $ERROR_INFO
end
redirect_to controller: 'questionnaires', action: 'edit', id: questionnaire.id
end
end</nowiki>

===Fix #3===
There are three checks for whether a questionnaire is a QuizQuestionnaire. Testing the class of an object is always suspect, though, in a controller, which has to control a whole hierarchy of objects, it is not necessarily wrong. However, they probably aren’t necessary. 2 of them seem to have been removed already and the only remaining check was in create_questionnaire, thus it got removed while applying Fix #1.

===Fix #4===

According to the code climate, it was suggested that usage of <code>each_key</code> is preferable instead of <code>keys.each</code> . Rubocop suggests this due to performance. Using large sets of data is where this becomes noticeable. Chaining methods is going to be slower than using the built-in method (in this case) which accomplishes the task with a single special enumerator.

<nowiki>
params[:question].keys.each do |question_key|
</nowiki>

<nowiki>
params[:question].each_key do |question_key|
</nowiki>

===Fix #5===

According to the code climate, it was suggested that the use of parentheses around a method call should be avoided.

<nowiki>
display_type = (display_type.split(/(?=[A-Z])/)).join('%')
</nowiki>

<nowiki>
display_type = display_type.split(/(?=[A-Z])/).join('%')
</nowiki>

===Fix #6===

The add_new_questions method has string literal values like 'Strongly agree', 'Strongly disagree', '50, 3', '0|1|2|3|4|5' for max_label, min_label, size and alternatives. String literals are removed by introducing constants in question.rb.

<nowiki>
if question.is_a? ScoredQuestion
question.weight = params[:question][:weight]
question.max_label = Question::MAX_LABEL
question.min_label = Question::MIN_LABEL
end

if Question::SIZES.key?(question.class.name)
question.size = Question::SIZES[question.class.name]
end
if Question::ALTERNATIVES.key?(question.class.name)
question.alternatives = Question::ALTERNATIVES[question.class.name]
end
</nowiki>

===Fix #7===

The add_new_questions and save_all_questions methods have reduntant variable defined called questionnaire_id. The variable declaration is redundant as we can access it using params[:id].

=== Future scope ===

===Project Mentor===

Edward Gehringer (efg@ncsu.edu)

===Team Member===

Ashwin Shankar Umasankar [[(aumasan@ncsu.edu)]]

Kailash Singaravelu [[(ksingar2@ncsu.edu)]]

Pujitha Enamandala [[(penaman@ncsu.edu)]]

===Reference===
#[http://152.7.177.154:8080/ VCL link]
#[https://github.com/Ashwinshankar98/expertiza Github Repo]
#[https://github.com/expertiza/expertiza/pull/2470 Github Pull Request]
#[https://github.com/expertiza/expertiza Expertiza on GitHub]
#[http://wikis.lib.ncsu.edu/index.php/Expertiza Expertiza Project Documentation Wiki]
#[https://codeclimate.com/github/expertiza/expertiza/app/controllers/questionnaires_controller.rb CodeClimate Documentation]

CSC/ECE 517 Fall 2022 - E2257: Refactor questionnaires controller.rb

2022-10-27T00:52:06Z

Penaman:

==Introduction==
<nowiki>In Expertiza, Questionnaire is the superclass for all kinds of questionnaires and rubrics—rubrics for evaluating submissions and teammate contributions, and taking quizzes and surveys. All of these are subclasses of Questionnaire. questionnaires_controller.rb is charged with creating, displaying, and managing Questionnaires. Because it is used so widely, malfunctions could cause bugs in many parts of the system; hence it is especially important that the code be clear.</nowiki>

==Issues Fixed==
# Removed create_questionnaire
# Refactor create method ( usage of local variable instead of instance variables)
# QuizQuestionnaire check
# Refactor add_new_questions method

==Files Changed==
*app/controllers/questionnaires_controller.rb
*spec/controllers/questionnaires_controller_spec.rb
*app/models/question.rb

==Changes==
===Fix #1===
The <code>create_questionnnaires</code> method was present but its related functionality had been removed. Some kind of link to it is still present in one of the initial migrations which was populating a database to show values for a drop-down that is no longer in use. Thus ended up removing the function and its corresponding test cases.

===Fix #2===
The instance variable <code>@questionnaire</code> is converted to local <code>questionnaire</code> object to reduce its scope. Since in any other method <code>@questionnaire</code> object is initialized again.
<nowiki>
def create
if params[:questionnaire][:name].blank?
flash[:error] = 'A rubric or survey must have a title.'
redirect_to controller: 'questionnaires', action: 'new', model: params[:questionnaire][:type], private: params[:questionnaire][:private]
else
questionnaire_private = params[:questionnaire][:private] == 'true'
display_type = params[:questionnaire][:type].split('Questionnaire')[0]
begin
questionnaire = Object.const_get(params[:questionnaire][:type]).new if Questionnaire::QUESTIONNAIRE_TYPES.include? params[:questionnaire][:type]
rescue StandardError
flash[:error] = $ERROR_INFO
end
begin
questionnaire.private = questionnaire_private
questionnaire.name = params[:questionnaire][:name]
questionnaire.instructor_id = session[:user].id
questionnaire.min_question_score = params[:questionnaire][:min_question_score]
questionnaire.max_question_score = params[:questionnaire][:max_question_score]
questionnaire.type = params[:questionnaire][:type]
# Zhewei: Right now, the display_type in 'questionnaires' table and name in 'tree_folders' table are not consistent.
# In the future, we need to write migration files to make them consistency.
# E1903 : We are not sure of other type of cases, so have added a if statement. If there are only 5 cases, remove the if statement
if %w[AuthorFeedback CourseSurvey TeammateReview GlobalSurvey AssignmentSurvey BookmarkRating].include?(display_type)
display_type = (display_type.split(/(?=[A-Z])/)).join('%')
end
questionnaire.display_type = display_type
questionnaire.instruction_loc = Questionnaire::DEFAULT_QUESTIONNAIRE_URL
questionnaire.save
# Create node
tree_folder = TreeFolder.where(['name like ?', questionnaire.display_type]).first
parent = FolderNode.find_by(node_object_id: tree_folder.id)
QuestionnaireNode.create(parent_id: parent.id, node_object_id: questionnaire.id, type: 'QuestionnaireNode')
flash[:success] = 'You have successfully created a questionnaire!'
rescue StandardError
flash[:error] = $ERROR_INFO
end
redirect_to controller: 'questionnaires', action: 'edit', id: questionnaire.id
end
end</nowiki>

===Fix #3===
There are three checks for whether a questionnaire is a QuizQuestionnaire. Testing the class of an object is always suspect, though, in a controller, which has to control a whole hierarchy of objects, it is not necessarily wrong. However, they probably aren’t necessary. 2 of them seem to have been removed already and the only remaining check was in create_questionnaire, thus it got removed while applying Fix #1.

===Fix #4===

According to the code climate, it was suggested that usage of <code>each_key</code> is preferable instead of <code>keys.each</code> . Rubocop suggests this due to performance. Using large sets of data is where this becomes noticeable. Chaining methods is going to be slower than using the built-in method (in this case) which accomplishes the task with a single special enumerator.

<nowiki>
params[:question].keys.each do |question_key|
</nowiki>

<nowiki>
params[:question].each_key do |question_key|
</nowiki>

===Fix #5===

According to the code climate, it was suggested that the use of parentheses around a method call should be avoided.

<nowiki>
display_type = (display_type.split(/(?=[A-Z])/)).join('%')
</nowiki>

<nowiki>
display_type = display_type.split(/(?=[A-Z])/).join('%')
</nowiki>

===Fix #6===

The add_new_questions method has string literal values like 'Strongly agree', 'Strongly disagree', '50, 3', '0|1|2|3|4|5' for max_label, min_label, size and alternatives. String literals are removed by introducing constants.

<nowiki>
if question.is_a? ScoredQuestion
question.weight = params[:question][:weight]
question.max_label = Question::MAX_LABEL
question.min_label = Question::MIN_LABEL
end

if Question::SIZES.key?(question.class.name)
question.size = Question::SIZES[question.class.name]
end
if Question::ALTERNATIVES.key?(question.class.name)
question.alternatives = Question::ALTERNATIVES[question.class.name]
end
</nowiki>

===Fix #7===

The add_new_questions and save_all_questions method has a reduntant variable defined called questionnaire_id. The variable declaration is redundant as we can access it using params[:id].

=== Future scope ===

===Project Mentor===

Edward Gehringer (efg@ncsu.edu)

===Team Member===

Ashwin Shankar Umasankar [[(aumasan@ncsu.edu)]]

Kailash Singaravelu [[(ksingar2@ncsu.edu)]]

Pujitha Enamandala [[(penaman@ncsu.edu)]]

===Reference===
#[http://152.7.177.154:8080/ VCL link]
#[https://github.com/Ashwinshankar98/expertiza Github Repo]
#[https://github.com/expertiza/expertiza/pull/2470 Github Pull Request]
#[https://github.com/expertiza/expertiza Expertiza on GitHub]
#[http://wikis.lib.ncsu.edu/index.php/Expertiza Expertiza Project Documentation Wiki]
#[https://codeclimate.com/github/expertiza/expertiza/app/controllers/questionnaires_controller.rb CodeClimate Documentation]