CSC/ECE 517 Fall 2014/final E1471 asuv

From Expertiza_Wiki
Jump to navigation Jump to search

Information Display and Student Interaction

Introduction

Background

Scope

Purpose

Approach

As the project was originally assigned to students two years ago, the functionality is mostly complete. The main concern is that, as the project was completed 2 years ago (in December 2012), it was made for an older version of rails.

General Approach

Our general approach to the project would be as follows:

  • Run the current project with rails 4
  • Check the functionality to find out the incompatible parts
  • Refactor the parts of code that do not function as expected and port them to rails 4 specification
  • After making sure everything runs, refactor the entire code to make sure it follows the global code rules.

Specific Approach

The specific approach to each of the two functionality is as follows:

Better display for assignments

Dashboard for students

Testing

Files involved

Dashboard for students

  • Model
  • ScoreCache.rb
  • View
  • grades\view_my_scored.html.erb
  • Controller
  • grades_controller.rb, review_mapping_controller.rb,response_controller.rb
  • Database tables
  • Assignments,Participants, score_caches, response_maps,responses


Sr. No. Method Name Comment
1 getParticipantEntriesInAssignmentList(assignmentList) This method is responsible for calculating the leaderboard of all the participants associated with assignments in given assignment list.
2 extractPersonalAchievements(csHash, courseIdList, userId) This method is responsible for calculating personal aggregated score. It also calculates the ranking of currently logged in user against total users associated with the same set of courses as that of current user.
3 addEntryToCSHash(qtypeHash, qtype, userid, csEntry, courseid) This method is called internally from Leaderboard.getParticipantEntriesInAssignmentList . This method aggregates score of a user grouped by course id, further grouped by questionnaire type.

Functionality of each file

Use case

UML diagram