CSC/ECE 517 Fall 2016/E1680. Improve survey functionality - Revision history

Smohapa3: /* Distribution of results */

2016-12-13T22:15:54Z

Distribution of results

← Older revision		Revision as of 22:15, 13 December 2016
Line 34:		Line 34:

	[[File:Class_diagram_new.PNG \| center]]		[[File:Class_diagram_new.PNG \| center]]

	~~=== '''Distribution of results''' ===~~

	* There is a page to see the distribution of results for any question (e.g., how many people answered “1”, how many answered “2”, etc.).
	* This page will not only be designed for surveys, but also for other types of questionnaires (E.g. this view be able to show the score distribution for a question in other types of questionnaires, no matter whether it is a survey question like “how much do you like the course?” or a peer-review question like “how well did the author test the code?”)
	~~<br>~~

	~~The required page for this implementation would look like this:~~

	~~[[File:Distribution_of_results.PNG]]~~


	* Our page to see the distribution of results for any question would render a similar Bar graph showing the no of people who answered a choice amongst the options.
	* The vertical axis would show the no of people.
	* The horizontal axis will show the possible answers to the question.
	* To implement this in Expertise we can use JQPlot Rails or some other graph plotting plugin.

	~~The ''JQuery'' code might look like~~
	~~[[File:Code_snippet.PNG]]~~

	* We will have to integrate the Jquery plugin and create a .erb file in views which will have similar
	* Jquery code to render a bar graph based on the data provided.

	==='''Taking the survey'''===		==='''Taking the survey'''===

Scyadav at 04:04, 3 December 2016

2016-12-03T04:04:45Z

← Older revision		Revision as of 04:04, 3 December 2016
Line 11:		Line 11:
	<br>		<br>
	The three kinds of surveys in this project are:		The three kinds of surveys in this project are:
	*1. Survey questionnaire		*1. Assignment Survey questionnaire
	*2. Global survey questionnaire		*2. Global survey questionnaire
	*3. Course evaluation questionnaire		*3. Course evaluation questionnaire
Line 22:		Line 22:
	* We should use the same code to display the existing survey responses as to display the responses in peer reviews.		* We should use the same code to display the existing survey responses as to display the responses in peer reviews.
	* For each course or assignment, the admin/instructor should be able to create a survey and have some (or all) of the participants receive the survey.		* For each course or assignment, the admin/instructor should be able to create a survey and have some (or all) of the participants receive the survey.
	* When a user is assigned to take part in a survey, a survey_participant record should be created for that user in the participants table.
	==='''Existing Models, Views and Controllers'''===		==='''Existing Models, Views and Controllers'''===
	Survey questionnaire, Global Survey questionnaire and ~~course_evaluation_questionnaire~~ are the existing models which are subclasses of questionnaire. Their		Assignment Survey questionnaire, Global Survey questionnaire and Course Evaluation Questionnaire are the existing models which are subclasses of questionnaire. Their display types are survey, global survey and course evaluation respectively. The controller file present currently is survey_controller.rb.
	display types are survey, global survey and course evaluation respectively. The controller file present currently is survey_controller.rb.

	=='''Proposed Design'''==		=='''Proposed Design'''==
	==='''Structure'''===		==='''Structure'''===
	In the design we have three kinds of survey-		In the design we have three kinds of survey-
	* ~~survey_questionnaire~~		* assignment_survey_questionnaire
	* global_survey_questionnaire		* global_survey_questionnaire
	* course_evaluation_questionnaire		* course_evaluation_questionnaire

Scyadav: /* Views */

2016-12-03T03:08:05Z

Views

← Older revision		Revision as of 03:08, 3 December 2016
Line 96:		Line 96:
	*app/views/survey_response/		*app/views/survey_response/
	*app/views/survey		*app/views/survey


	=='''New Implementation'''==		=='''New Implementation'''==

Scyadav: /* Responses */

2016-12-03T03:06:40Z

Responses

← Older revision		Revision as of 03:06, 3 December 2016
Line 153:		Line 153:
	reviewee_id is same as object_id		reviewee_id is same as object_id

	[[File:CompleteFlow.~~PNG~~]]		[[File: CompleteFlow.png]]


	=='''Testing'''==		=='''Testing'''==

Scyadav: /* Testing using UI */

2016-12-03T03:03:23Z

Testing using UI

← Older revision		Revision as of 03:03, 3 December 2016
Line 163:		Line 163:
	2. Click on Manage -> Questionnaires-> Survey / Global Survey/ Course evaluation.<br>		2. Click on Manage -> Questionnaires-> Survey / Global Survey/ Course evaluation.<br>
	3. Create a new Survey/ Global Survey/ Course evaluation filling in the parameters asked for.<br>		3. Create a new Survey/ Global Survey/ Course evaluation filling in the parameters asked for.<br>
			<br>
	[[File:Procedure expertiza.PNG]]		[[File:Procedure expertiza.PNG]]

Scyadav at 03:02, 3 December 2016

2016-12-03T03:02:30Z

← Older revision		Revision as of 03:02, 3 December 2016
Line 152:		Line 152:
	reviewed_object_id is assignment_id or course_id depending upon the previous conditional output.		reviewed_object_id is assignment_id or course_id depending upon the previous conditional output.
	reviewee_id is same as object_id		reviewee_id is same as object_id

			[[File:CompleteFlow.PNG]]

Scyadav at 02:59, 3 December 2016

2016-12-03T02:59:17Z

← Older revision		Revision as of 02:59, 3 December 2016
Line 63:		Line 63:
	* The response_controller can be used to make sure that the survey can be taken only once by each user, depending upon the survey type and the users who are allowed to access (can be listed using 'action_allowed?'). The answers can be saved using the 'saving' method. Also, the responses can be viewed once, the survey is submitted.		* The response_controller can be used to make sure that the survey can be taken only once by each user, depending upon the survey type and the users who are allowed to access (can be listed using 'action_allowed?'). The answers can be saved using the 'saving' method. Also, the responses can be viewed once, the survey is submitted.

	==='''Adding Participants to the survey:'''===		==='''Adding Participants to the survey'''===

	* Instructor or admin both can add survey for any course or assignment		* Instructor or admin both can add survey for any course or assignment
Line 69:		Line 69:
	* The creator would be able to select the participants based on the scope of the survey, that is, all the students or all the Expertiza users or specific group of people.		* The creator would be able to select the participants based on the scope of the survey, that is, all the students or all the Expertiza users or specific group of people.

	==='''Adding all the global questionnaire questions:'''===		==='''Adding all the global questionnaire questions'''===

	* There would be a generic set of questions which will be included in global_survey_questionnaire.		* There would be a generic set of questions which will be included in global_survey_questionnaire.

Scyadav at 02:58, 3 December 2016

2016-12-03T02:58:50Z

@@ Line 96: / Line 96: @@
 *app/views/survey_response/
 *app/views/survey
@@ Line 165: / Line 152: @@
    reviewed_object_id is assignment_id or course_id depending upon the previous conditional output.
    reviewee_id is same as object_id

Scyadav: /* Distribution of results */

2016-12-03T02:57:23Z

Distribution of results

Scyadav: /* Structure */

2016-12-03T02:56:13Z

Structure

← Older revision		Revision as of 02:56, 3 December 2016
Line 29:		Line 29:
	=='''Proposed Design'''==		=='''Proposed Design'''==
	==='''Structure'''===		==='''Structure'''===
	In ~~our~~ design we have three kinds of survey-		In the design we have three kinds of survey-
	* survey_questionnaire		* survey_questionnaire
	* global_survey_questionnaire		* global_survey_questionnaire
	* course_evaluation_questionnaire		* course_evaluation_questionnaire
	These models should be made as subclasses of the class survey. By using the concept of polymorphism, survey is made a subclass of survey_questionnaire as many kinds of survey_questionnaire can exist and by using polymorphism, the code can be made more efficient. Survey_questionnaire is then a subclass of questionnaire. Complete refactoring is needed as the existing code is inefficient.		These models should be made as subclasses of the class questionnaire. Complete refactoring is needed as the existing code is inefficient.

	[[File:Class_diagram_new.PNG \| center]]		[[File:Class_diagram_new.PNG \| center]]

← Older revision		Revision as of 02:57, 3 December 2016
Line 39:		Line 39:
	=== '''Distribution of results''' ===		=== '''Distribution of results''' ===

	* There ~~will be~~ a page to see the distribution of results for any question (e.g., how many people answered “1”, how many answered “2”, etc.).		* There is a page to see the distribution of results for any question (e.g., how many people answered “1”, how many answered “2”, etc.).
	* This page will not only be designed for surveys, but also for other types of questionnaires (E.g. this view be able to show the score distribution for a question in other types of questionnaires, no matter whether it is a survey question like “how much do you like the course?” or a peer-review question like “how well did the author test the code?”)		* This page will not only be designed for surveys, but also for other types of questionnaires (E.g. this view be able to show the score distribution for a question in other types of questionnaires, no matter whether it is a survey question like “how much do you like the course?” or a peer-review question like “how well did the author test the code?”)
	<br>		<br>
	~~'''Proposed Implementation'''~~

	The required page for this implementation would look like this:		The required page for this implementation would look like this:
Line 49:		Line 48:


	* Our page to see the distribution of results for any question would render a similar Bar graph		* Our page to see the distribution of results for any question would render a similar Bar graph showing the no of people who answered a choice amongst the options.
	* showing the no of people who answered a choice amongst the options.
	* The vertical axis would show the no of people.		* The vertical axis would show the no of people.
	* The horizontal axis will show the possible answers to the question.		* The horizontal axis will show the possible answers to the question.
	* To implement this in Expertise we can use JQPlot Rails or some other graph plotting plugin.		* To implement this in Expertise we can use JQPlot Rails or some other graph plotting plugin.

	The ''JQuery'' code might look like		The ''JQuery'' code might look like
	[[File:Code_snippet.PNG]]		[[File:Code_snippet.PNG]]