|
|
| Line 1: |
Line 1: |
| Expertiza Project Writeup
| |
| Madhavbhai Hitendrabhai Bhatt, Randal William Myers, and Sai Krishna Panakanti
| |
| Advisor: Ferry Pramudianto, fferry@ncsu.edu
| |
|
| |
|
| Abstract: Our group addresses “E1720: UI issues/fixes” from the assignment sheet for the Spring 2017 semester and North Carolina State University.
| |
|
| |
| What was wrong with Expertiza:
| |
| Historically, we have created courses without specifying the institution. Now with the data warehouse storing institution for each course, this is undesirable.
| |
| If an assignment is completed, no one can sign up for topics or drop topics. Yet a completely blank "Actions" column on the signup sheet still appears. It would be better if the column did not appear.
| |
| Currently when admin/instructor tries to delete an assignment, there is no alert/confirmation shown. This is risky. We need to add a confirmation step to avoid losing data.
| |
| It would be nice to include feature updates for the users of Expertiza when major features are added or changed.
| |
|
| |
| What needed to be done at the beginning:
| |
| Issue #702: Add another institution_id to course table and The Create Course page needs to be fixed to tell the creator to specify the institution (course/_course.html.erb).
| |
| Issue #316:Remove "Actions" column on signup sheet in a completed assignment (sign_up_sheet/list.html.erb).
| |
| Issue #295: Add a confirmation on deleting an assignment on the admin screen (tree_display/actions/_shared_actions.html.rb).
| |
| Issue #256: Add a one-time notification at the top of the page which links to an article on the details of the change (it might make sense to put a javascript module in the site_controllers/index.html.rb and let other pages call this).
| |
|
| |
| What was done to address each issue:
| |
| Issue #702: We used scaffolding to create a model, view and controller for institutions.
| |
| Issue #316: .
| |
| Issue #295: .
| |
| Issue #256: .
| |
|
| |
| Test Plan:
| |