Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T20:54:10Z

Ashelby: /* Proposed Design */

== Overview ==
After the previous design document submission, we changed projects, with the suggestion and approval of our mentor and Dr. Gehringer, to a reimplementation of the UI for Teammate Review view, which has a larger scope than our previous project. The previous implementation of this UI proposed changes to not only the view files, but the controller and model files as well. This was beyond the scope of the project and complicated the integration of the UI to the existing Expertiza. Thus, our current project will focus on reimplementing the Teammate Review view isolated from other components of the current Expertiza application. Additionally, we focus on implementing a clear and user-friendly UI for both students and instructors. Following the current review display, our main display will show the numerical scores with an associated color as a heat-map.

== Previous Design ==
=== Specifications ===
*Display teammate reviews as a colormap corresponding to the numerical scores
*Students should be able to view reviews they have given to their teammates and the reviews their teammates have given them
**There should be a clear indication in the view which reviews the student is viewing (i.e. those they have given or those they have received)
*Instructors should also be able to view a student's reviews from their teammates and the reviews a student has given for their teammates
*The instructor should be able to chose whether teammate reviews are visible to the student or not by a checkbox
*An average score should be shown, for all the relevant reviews, in a clear and useful way
*There should be an anonymized view option where the names of the reviewer should not be shown

=== Design ===
The previous implementation focussed on a few main improvements to the view.
*Displaying the average score for instructors based on:
**A student's average received teammate score
**A student's average score given to teammates
*Improving the functionality of the automized view for students when selected by the instructor
**Use case diagram for the anonymized view:
[[File:uml_1.PNG|500px|UML for Anonymized]]

=== Testing ===
Main components to the testing plan included:
*Verifying the different displays for students vs. instructors
*Verifying login credentials
*Improvement in unit tests
*Addition of tests for calculating the average score
*Manual testing of the main display with the correct functionality

== Proposed Design ==

=== Specifications ===
Following the previous project specifications, our project will focus on further development to the user experience and testing.
*Intuitive Design
**User-friendly interface
**Easy to navigate
*Testing
**All the components of the UI are functioning
**Error handling
**Reliability of the UI is maintained

=== Design ===

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T20:42:22Z

Ashelby: /* Proposed Design */

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T20:38:18Z

Ashelby: /* Testing */

== Overview ==
After the previous design document submission, we changed projects, with the suggestion and approval of our mentor and Dr. Gehringer, to a reimplementation of the UI for Teammate Review view, which has a larger scope than our previous project. The previous implementation of this UI proposed changes to not only the view files, but the controller and model files as well. This was beyond the scope of the project and complicated the integration of the UI to the existing Expertiza. Thus, our current project will focus on reimplementing the Teammate Review view isolated from other components of the current Expertiza application. Additionally, we focus on implementing a clear and user-friendly UI for both students and instructors. Following the current review display, our main display will show the numerical scores with an associated color as a heat-map.

== Previous Design ==
=== Specifications ===
*Display teammate reviews as a colormap corresponding to the numerical scores
*Students should be able to view reviews they have given to their teammates and the reviews their teammates have given them
**There should be a clear indication in the view which reviews the student is viewing (i.e. those they have given or those they have received)
*Instructors should also be able to view a student's reviews from their teammates and the reviews a student has given for their teammates
*The instructor should be able to chose whether teammate reviews are visible to the student or not by a checkbox
*An average score should be shown, for all the relevant reviews, in a clear and useful way
*There should be an anonymized view option where the names of the reviewer should not be shown

=== Design ===
The previous implementation focussed on a few main improvements to the view.
*Displaying the average score for instructors based on:
**A student's average received teammate score
**A student's average score given to teammates
*Improving the functionality of the automized view for students when selected by the instructor
**Use case diagram for the anonymized view:
[[File:uml_1.PNG|500px|UML for Anonymized]]

=== Testing ===
Main components to the testing plan included:
*Verifying the different displays for students vs. instructors
*Verifying login credentials
*Improvement in unit tests
*Addition of tests for calculating the average score
*Manual testing of the main display with the correct functionality

== Proposed Design ==
Following the previous project specifications, our project will focus on reimplementing the UI for Teammate Reviews, with some additional specification.

=== Specifications ===
*Intuitive Design
**User-friendly interface
**Easy to navigate
*Testing
**All the components of the UI are functioning
**Error handling
**Reliability of the UI is maintained

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T20:38:04Z

Ashelby: /* Previous Design */

== Overview ==
After the previous design document submission, we changed projects, with the suggestion and approval of our mentor and Dr. Gehringer, to a reimplementation of the UI for Teammate Review view, which has a larger scope than our previous project. The previous implementation of this UI proposed changes to not only the view files, but the controller and model files as well. This was beyond the scope of the project and complicated the integration of the UI to the existing Expertiza. Thus, our current project will focus on reimplementing the Teammate Review view isolated from other components of the current Expertiza application. Additionally, we focus on implementing a clear and user-friendly UI for both students and instructors. Following the current review display, our main display will show the numerical scores with an associated color as a heat-map.

== Previous Design ==
=== Specifications ===
*Display teammate reviews as a colormap corresponding to the numerical scores
*Students should be able to view reviews they have given to their teammates and the reviews their teammates have given them
**There should be a clear indication in the view which reviews the student is viewing (i.e. those they have given or those they have received)
*Instructors should also be able to view a student's reviews from their teammates and the reviews a student has given for their teammates
*The instructor should be able to chose whether teammate reviews are visible to the student or not by a checkbox
*An average score should be shown, for all the relevant reviews, in a clear and useful way
*There should be an anonymized view option where the names of the reviewer should not be shown

=== Design ===
The previous implementation focussed on a few main improvements to the view.
*Displaying the average score for instructors based on:
**A student's average received teammate score
**A student's average score given to teammates
*Improving the functionality of the automized view for students when selected by the instructor
**Use case diagram for the anonymized view:
[[File:uml_1.PNG|500px|UML for Anonymized]]

=== Testing ===
Main components to the testing plan included:
*Verifying the different displays for students vs. instructors
*Verifying login credentials
*Improvement in unit tests
*Addition of tests for calculating the average score
*Manual test of the main display

== Proposed Design ==
Following the previous project specifications, our project will focus on reimplementing the UI for Teammate Reviews, with some additional specification.

=== Specifications ===
*Intuitive Design
**User-friendly interface
**Easy to navigate
*Testing
**All the components of the UI are functioning
**Error handling
**Reliability of the UI is maintained

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T20:33:32Z

Ashelby: /* Design */

== Overview ==
After the previous design document submission, we changed projects, with the suggestion and approval of our mentor and Dr. Gehringer, to a reimplementation of the UI for Teammate Review view, which has a larger scope than our previous project. The previous implementation of this UI proposed changes to not only the view files, but the controller and model files as well. This was beyond the scope of the project and complicated the integration of the UI to the existing Expertiza. Thus, our current project will focus on reimplementing the Teammate Review view isolated from other components of the current Expertiza application. Additionally, we focus on implementing a clear and user-friendly UI for both students and instructors. Following the current review display, our main display will show the numerical scores with an associated color as a heat-map.

== Previous Design ==
=== Specifications ===
*Display teammate reviews as a colormap corresponding to the numerical scores
*Students should be able to view reviews they have given to their teammates and the reviews their teammates have given them
**There should be a clear indication in the view which reviews the student is viewing (i.e. those they have given or those they have received)
*Instructors should also be able to view a student's reviews from their teammates and the reviews a student has given for their teammates
*The instructor should be able to chose whether teammate reviews are visible to the student or not by a checkbox
*An average score should be shown, for all the relevant reviews, in a clear and useful way
*There should be an anonymized view option where the names of the reviewer should not be shown

=== Design ===
The previous implementation focussed on a few main improvements to the view.
*Displaying the average score for instructors based on:
**A student's average received teammate score
**A student's average score given to teammates
*Improving the functionality of the automized view for students when selected by the instructor
**Use case diagram for the anonymized view:
[[File:uml_1.PNG|500px|UML for Anonymized]]

== Proposed Design ==
Following the previous project specifications, our project will focus on reimplementing the UI for Teammate Reviews, with some additional specification.

=== Specifications ===
*Intuitive Design
**User-friendly interface
**Easy to navigate
*Testing
**All the components of the UI are functioning
**Error handling
**Reliability of the UI is maintained

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T20:30:41Z

Ashelby: /* Design */

== Overview ==
After the previous design document submission, we changed projects, with the suggestion and approval of our mentor and Dr. Gehringer, to a reimplementation of the UI for Teammate Review view, which has a larger scope than our previous project. The previous implementation of this UI proposed changes to not only the view files, but the controller and model files as well. This was beyond the scope of the project and complicated the integration of the UI to the existing Expertiza. Thus, our current project will focus on reimplementing the Teammate Review view isolated from other components of the current Expertiza application. Additionally, we focus on implementing a clear and user-friendly UI for both students and instructors. Following the current review display, our main display will show the numerical scores with an associated color as a heat-map.

== Previous Design ==
=== Specifications ===
*Display teammate reviews as a colormap corresponding to the numerical scores
*Students should be able to view reviews they have given to their teammates and the reviews their teammates have given them
**There should be a clear indication in the view which reviews the student is viewing (i.e. those they have given or those they have received)
*Instructors should also be able to view a student's reviews from their teammates and the reviews a student has given for their teammates
*The instructor should be able to chose whether teammate reviews are visible to the student or not by a checkbox
*An average score should be shown, for all the relevant reviews, in a clear and useful way
*There should be an anonymized view option where the names of the reviewer should not be shown

=== Design ===
The previous implementation focussed on a few main improvements to the view.
*Displaying the average score for instructors based on:
**A student's average received teammate score
**A student's average score given to teammates

== Proposed Design ==
Following the previous project specifications, our project will focus on reimplementing the UI for Teammate Reviews, with some additional specification.

=== Specifications ===
*Intuitive Design
**User-friendly interface
**Easy to navigate
*Testing
**All the components of the UI are functioning
**Error handling
**Reliability of the UI is maintained

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T20:30:32Z

Ashelby: /* Design */

== Overview ==
After the previous design document submission, we changed projects, with the suggestion and approval of our mentor and Dr. Gehringer, to a reimplementation of the UI for Teammate Review view, which has a larger scope than our previous project. The previous implementation of this UI proposed changes to not only the view files, but the controller and model files as well. This was beyond the scope of the project and complicated the integration of the UI to the existing Expertiza. Thus, our current project will focus on reimplementing the Teammate Review view isolated from other components of the current Expertiza application. Additionally, we focus on implementing a clear and user-friendly UI for both students and instructors. Following the current review display, our main display will show the numerical scores with an associated color as a heat-map.

== Previous Design ==
=== Specifications ===
*Display teammate reviews as a colormap corresponding to the numerical scores
*Students should be able to view reviews they have given to their teammates and the reviews their teammates have given them
**There should be a clear indication in the view which reviews the student is viewing (i.e. those they have given or those they have received)
*Instructors should also be able to view a student's reviews from their teammates and the reviews a student has given for their teammates
*The instructor should be able to chose whether teammate reviews are visible to the student or not by a checkbox
*An average score should be shown, for all the relevant reviews, in a clear and useful way
*There should be an anonymized view option where the names of the reviewer should not be shown

=== Design ===
The previous implementation focussed on a few main improvements to the view.
*Displaying the average score for instructors based on
**A student's average received teammate score
**A student's average score given to teammates

== Proposed Design ==
Following the previous project specifications, our project will focus on reimplementing the UI for Teammate Reviews, with some additional specification.

=== Specifications ===
*Intuitive Design
**User-friendly interface
**Easy to navigate
*Testing
**All the components of the UI are functioning
**Error handling
**Reliability of the UI is maintained

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T20:28:13Z

Ashelby: /* Implementation */

== Overview ==
After the previous design document submission, we changed projects, with the suggestion and approval of our mentor and Dr. Gehringer, to a reimplementation of the UI for Teammate Review view, which has a larger scope than our previous project. The previous implementation of this UI proposed changes to not only the view files, but the controller and model files as well. This was beyond the scope of the project and complicated the integration of the UI to the existing Expertiza. Thus, our current project will focus on reimplementing the Teammate Review view isolated from other components of the current Expertiza application. Additionally, we focus on implementing a clear and user-friendly UI for both students and instructors. Following the current review display, our main display will show the numerical scores with an associated color as a heat-map.

== Previous Design ==
=== Specifications ===
*Display teammate reviews as a colormap corresponding to the numerical scores
*Students should be able to view reviews they have given to their teammates and the reviews their teammates have given them
**There should be a clear indication in the view which reviews the student is viewing (i.e. those they have given or those they have received)
*Instructors should also be able to view a student's reviews from their teammates and the reviews a student has given for their teammates
*The instructor should be able to chose whether teammate reviews are visible to the student or not by a checkbox
*An average score should be shown, for all the relevant reviews, in a clear and useful way
*There should be an anonymized view option where the names of the reviewer should not be shown

=== Design ===
The previous implementation focussed on a few main improvements to the view.
*Displaying the average score
**Student view
***When viewing their received teammate reviews, the average score is clearly displayed
**Instructor view
***When viewing a student, their average received and given score is displayed

== Proposed Design ==
Following the previous project specifications, our project will focus on reimplementing the UI for Teammate Reviews, with some additional specification.

=== Specifications ===
*Intuitive Design
**User-friendly interface
**Easy to navigate
*Testing
**All the components of the UI are functioning
**Error handling
**Reliability of the UI is maintained

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T20:16:36Z

Ashelby: /* Proposed Design */

== Overview ==
After the previous design document submission, we changed projects, with the suggestion and approval of our mentor and Dr. Gehringer, to a reimplementation of the UI for Teammate Review view, which has a larger scope than our previous project. The previous implementation of this UI proposed changes to not only the view files, but the controller and model files as well. This was beyond the scope of the project and complicated the integration of the UI to the existing Expertiza. Thus, our current project will focus on reimplementing the Teammate Review view isolated from other components of the current Expertiza application. Additionally, we focus on implementing a clear and user-friendly UI for both students and instructors. Following the current review display, our main display will show the numerical scores with an associated color as a heat-map.

== Previous Design ==
=== Specifications ===
*Display teammate reviews as a colormap corresponding to the numerical scores
*Students should be able to view reviews they have given to their teammates and the reviews their teammates have given them
**There should be a clear indication in the view which reviews the student is viewing (i.e. those they have given or those they have received)
*Instructors should also be able to view a student's reviews from their teammates and the reviews a student has given for their teammates
*The instructor should be able to chose whether teammate reviews are visible to the student or not by a checkbox
*An average score should be shown, for all the relevant reviews, in a clear and useful way
*There should be an anonymized view option where the names of the reviewer should not be shown

=== Implementation ===
*Instructor View:

== Proposed Design ==
Following the previous project specifications, our project will focus on reimplementing the UI for Teammate Reviews, with some additional specification.

=== Specifications ===
*Intuitive Design
**User-friendly interface
**Easy to navigate
*Testing
**All the components of the UI are functioning
**Error handling
**Reliability of the UI is maintained

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T20:16:14Z

Ashelby: /* Proposed Design */

== Overview ==
After the previous design document submission, we changed projects, with the suggestion and approval of our mentor and Dr. Gehringer, to a reimplementation of the UI for Teammate Review view, which has a larger scope than our previous project. The previous implementation of this UI proposed changes to not only the view files, but the controller and model files as well. This was beyond the scope of the project and complicated the integration of the UI to the existing Expertiza. Thus, our current project will focus on reimplementing the Teammate Review view isolated from other components of the current Expertiza application. Additionally, we focus on implementing a clear and user-friendly UI for both students and instructors. Following the current review display, our main display will show the numerical scores with an associated color as a heat-map.

== Previous Design ==
=== Specifications ===
*Display teammate reviews as a colormap corresponding to the numerical scores
*Students should be able to view reviews they have given to their teammates and the reviews their teammates have given them
**There should be a clear indication in the view which reviews the student is viewing (i.e. those they have given or those they have received)
*Instructors should also be able to view a student's reviews from their teammates and the reviews a student has given for their teammates
*The instructor should be able to chose whether teammate reviews are visible to the student or not by a checkbox
*An average score should be shown, for all the relevant reviews, in a clear and useful way
*There should be an anonymized view option where the names of the reviewer should not be shown

=== Implementation ===
*Instructor View:

== Proposed Design ==
Following the previous project specifications, our project will focus on reimplementing the UI for Teammate Reviews, with some additional specification.

=== Specifications ===
*Intuitive Design
**User-friendly interface
**Easy to navigate

=== Testing ===
*All the components of the UI are functioning
*Error handling
*Reliability of the UI is maintained

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T20:14:39Z

Ashelby: /* Proposed Design */

== Overview ==
After the previous design document submission, we changed projects, with the suggestion and approval of our mentor and Dr. Gehringer, to a reimplementation of the UI for Teammate Review view, which has a larger scope than our previous project. The previous implementation of this UI proposed changes to not only the view files, but the controller and model files as well. This was beyond the scope of the project and complicated the integration of the UI to the existing Expertiza. Thus, our current project will focus on reimplementing the Teammate Review view isolated from other components of the current Expertiza application. Additionally, we focus on implementing a clear and user-friendly UI for both students and instructors. Following the current review display, our main display will show the numerical scores with an associated color as a heat-map.

== Previous Design ==
=== Specifications ===
*Display teammate reviews as a colormap corresponding to the numerical scores
*Students should be able to view reviews they have given to their teammates and the reviews their teammates have given them
**There should be a clear indication in the view which reviews the student is viewing (i.e. those they have given or those they have received)
*Instructors should also be able to view a student's reviews from their teammates and the reviews a student has given for their teammates
*The instructor should be able to chose whether teammate reviews are visible to the student or not by a checkbox
*An average score should be shown, for all the relevant reviews, in a clear and useful way
*There should be an anonymized view option where the names of the reviewer should not be shown

=== Implementation ===
*Instructor View:

== Proposed Design ==
Following the previous project specifications, our project will focus on reimplementing the UI for Teammate Reviews.

=== Specifications ===
*Intuitive Design
**User-friendly interface
**Easy to navigate

=== Testing ===
*All the components of the UI are functioning
*Error handling
*Reliability of the UI is maintained

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T20:13:37Z

Ashelby: /* Use Case Diagram */

== Overview ==
After the previous design document submission, we changed projects, with the suggestion and approval of our mentor and Dr. Gehringer, to a reimplementation of the UI for Teammate Review view, which has a larger scope than our previous project. The previous implementation of this UI proposed changes to not only the view files, but the controller and model files as well. This was beyond the scope of the project and complicated the integration of the UI to the existing Expertiza. Thus, our current project will focus on reimplementing the Teammate Review view isolated from other components of the current Expertiza application. Additionally, we focus on implementing a clear and user-friendly UI for both students and instructors. Following the current review display, our main display will show the numerical scores with an associated color as a heat-map.

== Previous Design ==
=== Specifications ===
*Display teammate reviews as a colormap corresponding to the numerical scores
*Students should be able to view reviews they have given to their teammates and the reviews their teammates have given them
**There should be a clear indication in the view which reviews the student is viewing (i.e. those they have given or those they have received)
*Instructors should also be able to view a student's reviews from their teammates and the reviews a student has given for their teammates
*The instructor should be able to chose whether teammate reviews are visible to the student or not by a checkbox
*An average score should be shown, for all the relevant reviews, in a clear and useful way
*There should be an anonymized view option where the names of the reviewer should not be shown

=== Implementation ===
*Instructor View:

== Proposed Design ==
Following the previous project specifications, our project will focus on reimplementing the UI for Teammate Reviews.

=== Specifications ===
*Intuitive Design
**User-friendly interface
**Easy to navigate

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T20:12:39Z

Ashelby: /* Use Case Diagram */

== Overview ==
After the previous design document submission, we changed projects, with the suggestion and approval of our mentor and Dr. Gehringer, to a reimplementation of the UI for Teammate Review view, which has a larger scope than our previous project. The previous implementation of this UI proposed changes to not only the view files, but the controller and model files as well. This was beyond the scope of the project and complicated the integration of the UI to the existing Expertiza. Thus, our current project will focus on reimplementing the Teammate Review view isolated from other components of the current Expertiza application. Additionally, we focus on implementing a clear and user-friendly UI for both students and instructors. Following the current review display, our main display will show the numerical scores with an associated color as a heat-map.

== Previous Design ==
=== Specifications ===
*Display teammate reviews as a colormap corresponding to the numerical scores
*Students should be able to view reviews they have given to their teammates and the reviews their teammates have given them
**There should be a clear indication in the view which reviews the student is viewing (i.e. those they have given or those they have received)
*Instructors should also be able to view a student's reviews from their teammates and the reviews a student has given for their teammates
*The instructor should be able to chose whether teammate reviews are visible to the student or not by a checkbox
*An average score should be shown, for all the relevant reviews, in a clear and useful way
*There should be an anonymized view option where the names of the reviewer should not be shown

=== Use Case Diagram ===
The use cases were previously described for access to the "view_team" page. The diagram depicts the conditional dependence of the student's received Teammate Review display on the instructor specification.
[[File:uml_1.PNG|border|500px|UML for Anonymized]]

=== Implementation ===
*Instructor View:

== Proposed Design ==
Following the previous project specifications, our project will focus on reimplementing the UI for Teammate Reviews.

=== Specifications ===
*Intuitive Design
**User-friendly interface
**Easy to navigate

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T20:03:50Z

Ashelby: /* Use Case Diagram */

== Overview ==
After the previous design document submission, we changed projects, with the suggestion and approval of our mentor and Dr. Gehringer, to a reimplementation of the UI for Teammate Review view, which has a larger scope than our previous project. The previous implementation of this UI proposed changes to not only the view files, but the controller and model files as well. This was beyond the scope of the project and complicated the integration of the UI to the existing Expertiza. Thus, our current project will focus on reimplementing the Teammate Review view isolated from other components of the current Expertiza application. Additionally, we focus on implementing a clear and user-friendly UI for both students and instructors. Following the current review display, our main display will show the numerical scores with an associated color as a heat-map.

== Previous Design ==
=== Specifications ===
*Display teammate reviews as a colormap corresponding to the numerical scores
*Students should be able to view reviews they have given to their teammates and the reviews their teammates have given them
**There should be a clear indication in the view which reviews the student is viewing (i.e. those they have given or those they have received)
*Instructors should also be able to view a student's reviews from their teammates and the reviews a student has given for their teammates
*The instructor should be able to chose whether teammate reviews are visible to the student or not by a checkbox
*An average score should be shown, for all the relevant reviews, in a clear and useful way
*There should be an anonymized view option where the names of the reviewer should not be shown

=== Use Case Diagram ===
The use cases were previously described for access to the "view_team" page. The diagram depicts the conditional dependence of the student's received Teammate Review display on the instructor specification.

=== Implementation ===
*Instructor View:

== Proposed Design ==
Following the previous project specifications, our project will focus on reimplementing the UI for Teammate Reviews.

=== Specifications ===
*Intuitive Design
**User-friendly interface
**Easy to navigate

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T20:03:44Z

Ashelby: /* Implementation */

== Overview ==
After the previous design document submission, we changed projects, with the suggestion and approval of our mentor and Dr. Gehringer, to a reimplementation of the UI for Teammate Review view, which has a larger scope than our previous project. The previous implementation of this UI proposed changes to not only the view files, but the controller and model files as well. This was beyond the scope of the project and complicated the integration of the UI to the existing Expertiza. Thus, our current project will focus on reimplementing the Teammate Review view isolated from other components of the current Expertiza application. Additionally, we focus on implementing a clear and user-friendly UI for both students and instructors. Following the current review display, our main display will show the numerical scores with an associated color as a heat-map.

== Previous Design ==
=== Specifications ===
*Display teammate reviews as a colormap corresponding to the numerical scores
*Students should be able to view reviews they have given to their teammates and the reviews their teammates have given them
**There should be a clear indication in the view which reviews the student is viewing (i.e. those they have given or those they have received)
*Instructors should also be able to view a student's reviews from their teammates and the reviews a student has given for their teammates
*The instructor should be able to chose whether teammate reviews are visible to the student or not by a checkbox
*An average score should be shown, for all the relevant reviews, in a clear and useful way
*There should be an anonymized view option where the names of the reviewer should not be shown

=== Use Case Diagram ===
The use cases were previously described for access to the "view_team" page. The diagram depicts the conditional dependence of the student's received Teammate Review display on the instructor specification.
[[File:Use_case_diagram_teammate_review_view.png|570px]]

=== Implementation ===
*Instructor View:

== Proposed Design ==
Following the previous project specifications, our project will focus on reimplementing the UI for Teammate Reviews.

=== Specifications ===
*Intuitive Design
**User-friendly interface
**Easy to navigate

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T20:00:23Z

Ashelby: /* Previous Design */

== Overview ==
After the previous design document submission, we changed projects, with the suggestion and approval of our mentor and Dr. Gehringer, to a reimplementation of the UI for Teammate Review view, which has a larger scope than our previous project. The previous implementation of this UI proposed changes to not only the view files, but the controller and model files as well. This was beyond the scope of the project and complicated the integration of the UI to the existing Expertiza. Thus, our current project will focus on reimplementing the Teammate Review view isolated from other components of the current Expertiza application. Additionally, we focus on implementing a clear and user-friendly UI for both students and instructors. Following the current review display, our main display will show the numerical scores with an associated color as a heat-map.

== Previous Design ==
=== Specifications ===
*Display teammate reviews as a colormap corresponding to the numerical scores
*Students should be able to view reviews they have given to their teammates and the reviews their teammates have given them
**There should be a clear indication in the view which reviews the student is viewing (i.e. those they have given or those they have received)
*Instructors should also be able to view a student's reviews from their teammates and the reviews a student has given for their teammates
*The instructor should be able to chose whether teammate reviews are visible to the student or not by a checkbox
*An average score should be shown, for all the relevant reviews, in a clear and useful way
*There should be an anonymized view option where the names of the reviewer should not be shown

=== Use Case Diagram ===
The use cases were previously described for access to the "view_team" page. The diagram depicts the conditional dependence of the student's received Teammate Review display on the instructor specification.
[[File:Use_case_diagram_teammate_review_view.png|570px]]

=== Implementation ===
*Instructor View
[[File:Teammate_Review_for_7185_new.png|570px]]

== Proposed Design ==
Following the previous project specifications, our project will focus on reimplementing the UI for Teammate Reviews.

=== Specifications ===
*Intuitive Design
**User-friendly interface
**Easy to navigate

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T19:59:05Z

Ashelby: /* Previous Design */

== Overview ==
After the previous design document submission, we changed projects, with the suggestion and approval of our mentor and Dr. Gehringer, to a reimplementation of the UI for Teammate Review view, which has a larger scope than our previous project. The previous implementation of this UI proposed changes to not only the view files, but the controller and model files as well. This was beyond the scope of the project and complicated the integration of the UI to the existing Expertiza. Thus, our current project will focus on reimplementing the Teammate Review view isolated from other components of the current Expertiza application. Additionally, we focus on implementing a clear and user-friendly UI for both students and instructors. Following the current review display, our main display will show the numerical scores with an associated color as a heat-map.

== Previous Design ==
=== Specifications ===
*Display teammate reviews as a colormap corresponding to the numerical scores
*Students should be able to view reviews they have given to their teammates and the reviews their teammates have given them
**There should be a clear indication in the view which reviews the student is viewing (i.e. those they have given or those they have received)
*Instructors should also be able to view a student's reviews from their teammates and the reviews a student has given for their teammates
*The instructor should be able to chose whether teammate reviews are visible to the student or not by a checkbox
*An average score should be shown, for all the relevant reviews, in a clear and useful way
*There should be an anonymized view option where the names of the reviewer should not be shown

=== Use Case Diagram ===
The use cases were previously described for access to the "view_team" page. The diagram depicts the conditional dependence of the student's received Teammate Review display on the instructor specification.
[[File:Use_case_diagram_teammate_review_view.png|570px]]

== Proposed Design ==
Following the previous project specifications, our project will focus on reimplementing the UI for Teammate Reviews.

=== Specifications ===
*Intuitive Design
**User-friendly interface
**Easy to navigate

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T19:58:52Z

Ashelby: /* Previous Implementation */

== Overview ==
After the previous design document submission, we changed projects, with the suggestion and approval of our mentor and Dr. Gehringer, to a reimplementation of the UI for Teammate Review view, which has a larger scope than our previous project. The previous implementation of this UI proposed changes to not only the view files, but the controller and model files as well. This was beyond the scope of the project and complicated the integration of the UI to the existing Expertiza. Thus, our current project will focus on reimplementing the Teammate Review view isolated from other components of the current Expertiza application. Additionally, we focus on implementing a clear and user-friendly UI for both students and instructors. Following the current review display, our main display will show the numerical scores with an associated color as a heat-map.

== Previous Design ==
=== Previous Specifications ===
*Display teammate reviews as a colormap corresponding to the numerical scores
*Students should be able to view reviews they have given to their teammates and the reviews their teammates have given them
**There should be a clear indication in the view which reviews the student is viewing (i.e. those they have given or those they have received)
*Instructors should also be able to view a student's reviews from their teammates and the reviews a student has given for their teammates
*The instructor should be able to chose whether teammate reviews are visible to the student or not by a checkbox
*An average score should be shown, for all the relevant reviews, in a clear and useful way
*There should be an anonymized view option where the names of the reviewer should not be shown

=== Previous Use Case Diagram ===
The use cases were previously described for access to the "view_team" page. The diagram depicts the conditional dependence of the student's received Teammate Review display on the instructor specification.
[[File:Use_case_diagram_teammate_review_view.png|570px]]

== Proposed Design ==
Following the previous project specifications, our project will focus on reimplementing the UI for Teammate Reviews.

=== Specifications ===
*Intuitive Design
**User-friendly interface
**Easy to navigate

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T19:58:27Z

Ashelby: /* Previous Implementation */

== Overview ==
After the previous design document submission, we changed projects, with the suggestion and approval of our mentor and Dr. Gehringer, to a reimplementation of the UI for Teammate Review view, which has a larger scope than our previous project. The previous implementation of this UI proposed changes to not only the view files, but the controller and model files as well. This was beyond the scope of the project and complicated the integration of the UI to the existing Expertiza. Thus, our current project will focus on reimplementing the Teammate Review view isolated from other components of the current Expertiza application. Additionally, we focus on implementing a clear and user-friendly UI for both students and instructors. Following the current review display, our main display will show the numerical scores with an associated color as a heat-map.

== Previous Implementation ==
=== Previous Specifications ===
*Display teammate reviews as a colormap corresponding to the numerical scores
*Students should be able to view reviews they have given to their teammates and the reviews their teammates have given them
**There should be a clear indication in the view which reviews the student is viewing (i.e. those they have given or those they have received)
*Instructors should also be able to view a student's reviews from their teammates and the reviews a student has given for their teammates
*The instructor should be able to chose whether teammate reviews are visible to the student or not by a checkbox
*An average score should be shown, for all the relevant reviews, in a clear and useful way
*There should be an anonymized view option where the names of the reviewer should not be shown

=== Previous Use Case Diagram ===
The use cases were previously described for access to the "view_team" page. The diagram depicts the conditional dependence of the student's received Teammate Review display on the instructor specification.
[[File:Use_case_diagram_teammate_review_view.png|570px]]

== Proposed Design ==
Following the previous project specifications, our project will focus on reimplementing the UI for Teammate Reviews.

=== Specifications ===
*Intuitive Design
**User-friendly interface
**Easy to navigate

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T19:57:48Z

Ashelby: /* Previous Implementation */

== Overview ==
After the previous design document submission, we changed projects, with the suggestion and approval of our mentor and Dr. Gehringer, to a reimplementation of the UI for Teammate Review view, which has a larger scope than our previous project. The previous implementation of this UI proposed changes to not only the view files, but the controller and model files as well. This was beyond the scope of the project and complicated the integration of the UI to the existing Expertiza. Thus, our current project will focus on reimplementing the Teammate Review view isolated from other components of the current Expertiza application. Additionally, we focus on implementing a clear and user-friendly UI for both students and instructors. Following the current review display, our main display will show the numerical scores with an associated color as a heat-map.

== Previous Implementation ==
=== Specifications ===
*Display teammate reviews as a colormap corresponding to the numerical scores
*Students should be able to view reviews they have given to their teammates and the reviews their teammates have given them
**There should be a clear indication in the view which reviews the student is viewing (i.e. those they have given or those they have received)
*Instructors should also be able to view a student's reviews from their teammates and the reviews a student has given for their teammates
*The instructor should be able to chose whether teammate reviews are visible to the student or not by a checkbox
*An average score should be shown, for all the relevant reviews, in a clear and useful way
*There should be an anonymized view option where the names of the reviewer should not be shown

=== Previous Use Case Diagram ===
The use cases were previously described for access to the "view_team" page. The diagram depicts the conditional dependence of the student's received Teammate Review display on the instructor specification.
[[File:Use_case_diagram_teammate_review_view.png|570px]]

== Proposed Design ==
Following the previous project specifications, our project will focus on reimplementing the UI for Teammate Reviews.

=== Specifications ===
*Intuitive Design
**User-friendly interface
**Easy to navigate

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T19:50:17Z

Ashelby: /* Previous Implementation */

== Overview ==
After the previous design document submission, we changed projects, with the suggestion and approval of our mentor and Dr. Gehringer, to a reimplementation of the UI for Teammate Review view, which has a larger scope than our previous project. The previous implementation of this UI proposed changes to not only the view files, but the controller and model files as well. This was beyond the scope of the project and complicated the integration of the UI to the existing Expertiza. Thus, our current project will focus on reimplementing the Teammate Review view isolated from other components of the current Expertiza application. Additionally, we focus on implementing a clear and user-friendly UI for both students and instructors. Following the current review display, our main display will show the numerical scores with an associated color as a heat-map.

== Previous Implementation ==
=== Specifications ===
*Display teammate reviews as a colormap corresponding to the numerical scores
*Students should be able to view reviews they have given to their teammates and the reviews their teammates have given them
**There should be a clear indication in the view which reviews the student is viewing (i.e. those they have given or those they have received)
*Instructors should also be able to view a student's reviews from their teammates and the reviews a student has given for their teammates
*The instructor should be able to chose whether teammate reviews are visible to the student or not by a checkbox
*An average score should be shown, for all the relevant reviews, in a clear and useful way
*There should be an anonymized view option where the names of the reviewer should not be shown

=== Previous Use Case Diagram ===
[[File:Use_case_diagram_teammate_review_view.png|570px]]

== Proposed Design ==
Following the previous project specifications, our project will focus on reimplementing the UI for Teammate Reviews.

=== Specifications ===
*Intuitive Design
**User-friendly interface
**Easy to navigate

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T19:48:47Z

Ashelby: /* Previous Implementation */

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T19:33:02Z

Ashelby: /* Previous Implementation */

== Overview ==
After the previous design document submission, we changed projects, with the suggestion and approval of our mentor and Dr. Gehringer, to a reimplementation of the UI for Teammate Review view, which has a larger scope than our previous project. The previous implementation of this UI proposed changes to not only the view files, but the controller and model files as well. This was beyond the scope of the project and complicated the integration of the UI to the existing Expertiza. Thus, our current project will focus on reimplementing the Teammate Review view isolated from other components of the current Expertiza application. Additionally, we focus on implementing a clear and user-friendly UI for both students and instructors. Following the current review display, our main display will show the numerical scores with an associated color as a heat-map.

== Previous Implementation ==
Previously, the project specifications included:
*Display teammate reviews as a colormap corresponding to the numerical scores
*Students should be able to view reviews they have given to their teammates and the reviews their teammates have given them
**There should be a clear indication in the view which reviews the student is viewing (i.e. those they have given or those they have received)
*Instructors should also be able to view a student's reviews from their teammates and the reviews a student has given for their teammates
*The instructor should be able to chose whether teammate reviews are visible to the student or not by a checkbox
*An average score should be shown, for all the relevant reviews, in a clear and useful way
*There should be an anonymized view option where the names of the reviewer should not be shown

== Proposed Design ==
Following the previous project specifications, our project will focus on reimplementing the UI for Teammate Reviews.

=== Specifications ===
*Intuitive Design
**User-friendly interface
**Easy to navigate

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T19:23:15Z

Ashelby: /* Previous Implementation */

== Overview ==
After the previous design document submission, we changed projects, with the suggestion and approval of our mentor and Dr. Gehringer, to a reimplementation of the UI for Teammate Review view, which has a larger scope than our previous project. The previous implementation of this UI proposed changes to not only the view files, but the controller and model files as well. This was beyond the scope of the project and complicated the integration of the UI to the existing Expertiza. Thus, our current project will focus on reimplementing the Teammate Review view isolated from other components of the current Expertiza application. Additionally, we focus on implementing a clear and user-friendly UI for both students and instructors. Following the current review display, our main display will show the numerical scores with an associated color as a heat-map.

== Previous Implementation ==
Previously, the project specifications included:
*Display teammate reviews as a colormap corresponding to the numerical scores
*Students should be able to view reviews they have given to their teammates and the reviews their teammates have given them
**There should be a clear indication in the view which reviews the student is viewing (i.e. those they have given or those they have received)
*Instructors should also be able to view a student's reviews from their teammates and the reviews a student has given for their teammates
**A colormap should also be used to display the scores
*The instructor should be able to chose whether teammate reviews are visible to the student or not by a checkbox
*An average score should be shown, for all the relevant reviews, in a clear and useful way
*There should be an anonymized view option where the names of the reviewer should not be shown

== Proposed Design ==
Following the previous project specifications, our project will focus on reimplementing the UI for Teammate Reviews.

=== Specifications ===
*Intuitive Design
**User-friendly interface
**Easy to navigate

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T18:58:17Z

Ashelby:

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T18:56:11Z

Ashelby:

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T18:55:13Z

Ashelby:

= Overview =
After the previous design document submission, we changed projects, with the suggestion and approval of our mentor and Dr. Gehringer, to a reimplementation of the UI for Teammate Review view, which has a larger scope than our previous project. The previous implementation of this UI proposed changes to not only the view files, but the controller and model files as well. This was beyond the scope of the project and complicated the integration of the UI to the existing Expertiza. Thus, our current project will focus on reimplementing the Teammate Review view isolated from other components of the current Expertiza application. Additionally, we focus on implementing a clear and user-friendly UI for both students and instructors. Following the current review display, our main display will show the numerical scores with an associated color as a heat-map.

= Previous Implementation =
Previously, the project specifications included:
*Show reviews for the student separately from reviews by the student
*In the instructor view, there should be a checkbox that allows the instructor to chose whether teammate reviews are visible to the student
*An average score should be shown from all the relevant reviews
*There should be an anonymized view option where the names of the reviewer should not be shown

= Proposed Design =
Following the previous project specifications, our project will focus on reimplementing the UI for Teammate Reviews.

Specifications
*Intuitive Design

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T18:52:27Z

Ashelby:

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T18:50:17Z

Ashelby:

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T18:49:34Z

Ashelby:

= Overview =
After the previous design document submission, we changed projects, with the suggestion and approval of our mentor and Dr. Gehringer, to a reimplementation of the UI for Teammate Review view, which has a larger scope than our previous project. The previous implementation of this UI proposed changes to not only the view files, but the controller and model files as well. This was beyond the scope of the project and complicated the integration of the UI to the existing Expertiza. Thus, this current project will focus on reimplementing the Teammate Review view isolated from other components of the current Expertiza application. Additionally, we focus on implementing a clear and user-friendly UI for both students and instructors. Following the current review display, our main display will show the numerical scores with an associated color as a heat-map.

= Previous Implementation =
Previously, the project specifications included:
*Show reviews for the student separately from reviews by the student
*In the instructor view, there should be a checkbox that allows the instructor to chose whether teammate reviews are visible to the student
*An average score should be shown from all the relevant reviews
*There should be an anonymized view option where the names of the reviewer should not be shown

= Proposed Design =
Following the previous project specifications, our project will focus on reimplementing the UI for Teammate Reviews.

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T18:27:38Z

Ashelby:

= Overview =
After the previous design document submission, we changed projects, with the suggestion and approval of our mentor and Dr. Gehringer, to a reimplementation of the UI for Teammate Review view, which has a larger scope than our previous project. The previous implementation of this UI proposed changes to not only the view files, but the controller and model files as well. This was beyond the scope of the project and complicated the integration of the UI to the existing Expertiza.

= Previous Implementation =
Previously, the project specifications included:
*Show reviews for the student separately from reviews by the student
*In the instructor view, there should be a checkbox that allows the instructor to chose whether teammate reviews are visible to the student
*An average score should be shown from all the relevant reviews
*There should be an anonymized view option where the names of the reviewer should not be shown

= Proposed Design =
Following the previous project specifications, our project will focus on reimplementing the UI for Teammate Reviews.

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T18:22:06Z

Ashelby: /* Previous Implementation */

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T18:20:34Z

Ashelby:

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T18:20:13Z

Ashelby:

=== Overview ===
After the previous design document submission, we changed projects, with the suggestion and approval of our mentor and Dr. Gehringer, to a reimplementation of the UI for Teammate Review view, which has a larger scope than our previous project. The previous implementation of this UI proposed changes to not only the view files, but the controller and model files as well. This was beyond the scope of the project and complicated the integration of the UI to the existing Expertiza.

=== Previous Implementation ===
Previously, the project specifications included:
*Show reviews for the student separately from reviews by the student
*In the instructor view, there should be a checkbox that allows the instructor to chose whether teammate views are visible to the student
*An average score should be shown from all the relevant reviews
*There should be an anonymized view option where the names of the reviewer should not be shown

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T18:13:30Z

Ashelby:

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T18:04:15Z

Ashelby:

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T16:13:31Z

Ashelby:

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T16:12:59Z

Ashelby:

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T16:06:33Z

Ashelby: /* Overview */

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T16:06:18Z

Ashelby:

CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View

2024-12-02T16:05:40Z

Ashelby: Created page with "=== Overview === This project will create a modern, responsive TypeScript and ReactJS interface for the Report Review page within Expertiza. It aims to present instructors with a summary of student reviews for each assignment. The design will prioritize simplicity and usability, providing instructors with a clear and effective way to review student feedback."

CSC/ECE 517 Fall 2024

2024-12-02T16:05:02Z

Ashelby:

* [[CSC/ECE 517 Fall 2024 - E2450. Refactor assignments_controller.rb]]
* [[CSC/ECE 517 Fall 2024 - E2451. Reimplement feedback_response_map.rb]]
* [[CSC/ECE 517 Fall 2024 - E2452. Refactor review_mapping_controller.rb]]
* [[CSC/ECE 517 Fall 2024 - E2453. Refactor review_mapping_helper.rb]]
* [[CSC/ECE 517 Fall 2024 - E2454. Refactor student_task.rb]]
* [[CSC/ECE 517 Fall 2024 - E2455. Refactor sign_up_sheet_controller.rb]]
* [[CSC/ECE 517 Fall 2024 - E2456. Refactor teams_user.rb]]
* [[CSC/ECE 517 Fall 2024 - E2456. Refactor teams_user.rb (Phase 2 - Design Document)]]
* [[CSC/ECE 517 Fall 2024 - E2457. GitHub metrics integration]]
* [[CSC/ECE 517 Fall 2024 - E2458. User management and users table]]
* [[CSC/ECE 517 Fall 2024 - E2459. View for results of bidding]]
* [[CSC/ECE 517 Fall 2024 - E2460 Mentor-Meeting Management]]
* [[CSC/ECE 517 Fall 2024 - E2461. UI for Courses]]
* [[CSC/ECE 517 Fall 2024 - E2461. UI and Backend for Courses]]
* [https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2024_-_E2462._UI_for_Questionnaires CSC/ECE 517 Fall 2024 - E2462. UI for Questionnaire.rb]
* [https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2024_-_E2463_Implement_Front_End_for_Student_Task_List CSC/ECE 517 Fall 2024 - E2463. UI for Student Task List]
* [[CSC/ECE 517 Fall 2024 - E2464 UI for Project Topics (was: Sign_up_Topics)]]
* [[CSC/ECE 517 Fall 2024 - E2465. UI for Institutions and Notification]]
* [[CSC/ECE 517 Fall 2024 - E2466. UI for Impersonate User]]
* [[CSC/ECE 517 Fall 2024 - E2467. UI for View Submissions]]
* [[CSC/ECE 517 Fall 2024 - E2468. Reimplement due_date]]
* [[CSC/ECE 517 Fall 2024 - E2469. Reimplement grades/view_team]]
* [[CSC/ECE 517 Fall 2024 - E2470. Reimplement grades_controller]]
* [[CSC/ECE 517 Fall 2024 - E2471. Reimplement logger]]
* [[CSC/ECE 517 Fall 2024 - E2472. Reimplement responses_controller.rb]]
* [[CSC/ECE 517 Fall 2024 - E2473. Reimplement sign up topic.rb as project topic.rb]]
* [[CSC/ECE 517 Fall 2024 - E2474. Reimplement student_quizzes_controller.rb]]
* [[CSC/ECE 517 Fall 2024 - E2475. Reimplement student_task view]]
* [[CSC/ECE 517 Fall 2024 - E2476. Reimplement student_teams_controller.rb]]
* [[CSC/ECE 517 Fall 2024 - E2477. Reimplement suggestion_controller.rb]]
* [[CSC/ECE 517 Fall 2024 - E2478. Reimplement the Question hierarchy as Item hierarchy]]
* [[CSC/ECE 517 Fall 2024 - E2479. Reimplement teams_users_controller.rb]]
* [[CSC/ECE 517 Fall 2024 - E2480. Implement testing for new Bookmarks Controller]]
* [[CSC/ECE 517 Fall 2024 - E2481 Reimplement response_map.rb]]
* [[CSC/ECE 517 Fall 2024 - E2482. Reimplement heatgrid for reviews]]
* [[CSC/ECE 517 Fall 2024 - E2483. Reimplement Notification Controller and Model]]
* [[CSC/ECE 517 Fall 2024 - E2484. Reimplement participants_controller.rb]]
* [[CSC/ECE 517 Fall 2024 - E2485. Allow reviewers to bid on what to review]]
* [[CSC/ECE 517 Fall 2024 - E2486.Reimplement deadline_rights and deadline_types]]
* [[CSC/ECE 517 Fall 2024 - E2487. Reimplement authorization_helper.rb]]
* [[CSC/ECE 517 Fall 2024 - E2488 Reimplementation of Add TA to course]]
* [[CSC/ECE 517 Fall 2024 - E2489. Create a UI for Assignment Edit page "Etc" tab in ReactJS]]
* [[CSC/ECE 517 Fall 2024 - E2491.UI for View assignments in Courses view]]
* [[CSC/ECE 517 Fall 2024 - E2492. UI for View submissions/assign grades (except heatgrid)]]
* [[CSC/ECE 517 Fall 2024 - E2493. UI for Assign Reviewers]]
* [[CSC/ECE 517 Fall 2024 - E2494. UI for Report Review for Assignment]]
* [[CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View]]
* [[CSC/ECE 517 Fall 2024 - G2401 Refactor Graphql API endpoint for contribution metrics]]
* [[CSC/ECE 517 Fall 2024 - G2402 Refactor Graphql API endpoint for repositories]]

CSC/ECE 517 Fall 2024

2024-12-02T15:56:25Z

Ashelby:

* [[CSC/ECE 517 Fall 2024 - E2450. Refactor assignments_controller.rb]]
* [[CSC/ECE 517 Fall 2024 - E2451. Reimplement feedback_response_map.rb]]
* [[CSC/ECE 517 Fall 2024 - E2452. Refactor review_mapping_controller.rb]]
* [[CSC/ECE 517 Fall 2024 - E2453. Refactor review_mapping_helper.rb]]
* [[CSC/ECE 517 Fall 2024 - E2454. Refactor student_task.rb]]
* [[CSC/ECE 517 Fall 2024 - E2455. Refactor sign_up_sheet_controller.rb]]
* [[CSC/ECE 517 Fall 2024 - E2456. Refactor teams_user.rb]]
* [[CSC/ECE 517 Fall 2024 - E2456. Refactor teams_user.rb (Phase 2 - Design Document)]]
* [[CSC/ECE 517 Fall 2024 - E2457. GitHub metrics integration]]
* [[CSC/ECE 517 Fall 2024 - E2458. User management and users table]]
* [[CSC/ECE 517 Fall 2024 - E2459. View for results of bidding]]
* [[CSC/ECE 517 Fall 2024 - E2460 Mentor-Meeting Management]]
* [[CSC/ECE 517 Fall 2024 - E2461. UI for Courses]]
* [[CSC/ECE 517 Fall 2024 - E2461. UI and Backend for Courses]]
* [https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2024_-_E2462._UI_for_Questionnaires CSC/ECE 517 Fall 2024 - E2462. UI for Questionnaire.rb]
* [https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2024_-_E2463_Implement_Front_End_for_Student_Task_List CSC/ECE 517 Fall 2024 - E2463. UI for Student Task List]
* [[CSC/ECE 517 Fall 2024 - E2464 UI for Project Topics (was: Sign_up_Topics)]]
* [[CSC/ECE 517 Fall 2024 - E2465. UI for Institutions and Notification]]
* [[CSC/ECE 517 Fall 2024 - E2466. UI for Impersonate User]]
* [[CSC/ECE 517 Fall 2024 - E2467. UI for View Submissions]]
* [[CSC/ECE 517 Fall 2024 - E2468. Reimplement due_date]]
* [[CSC/ECE 517 Fall 2024 - E2469. Reimplement grades/view_team]]
* [[CSC/ECE 517 Fall 2024 - E2470. Reimplement grades_controller]]
* [[CSC/ECE 517 Fall 2024 - E2471. Reimplement logger]]
* [[CSC/ECE 517 Fall 2024 - E2472. Reimplement responses_controller.rb]]
* [[CSC/ECE 517 Fall 2024 - E2473. Reimplement sign up topic.rb as project topic.rb]]
* [[CSC/ECE 517 Fall 2024 - E2474. Reimplement student_quizzes_controller.rb]]
* [[CSC/ECE 517 Fall 2024 - E2475. Reimplement student_task view]]
* [[CSC/ECE 517 Fall 2024 - E2476. Reimplement student_teams_controller.rb]]
* [[CSC/ECE 517 Fall 2024 - E2477. Reimplement suggestion_controller.rb]]
* [[CSC/ECE 517 Fall 2024 - E2478. Reimplement the Question hierarchy as Item hierarchy]]
* [[CSC/ECE 517 Fall 2024 - E2479. Reimplement teams_users_controller.rb]]
* [[CSC/ECE 517 Fall 2024 - E2480. Implement testing for new Bookmarks Controller]]
* [[CSC/ECE 517 Fall 2024 - E2481 Reimplement response_map.rb]]
* [[CSC/ECE 517 Fall 2024 - E2482. Reimplement heatgrid for reviews]]
* [[CSC/ECE 517 Fall 2024 - E2483. Reimplement Notification Controller and Model]]
* [[CSC/ECE 517 Fall 2024 - E2484. Reimplement participants_controller.rb]]
* [[CSC/ECE 517 Fall 2024 - E2485. Allow reviewers to bid on what to review]]
* [[CSC/ECE 517 Fall 2024 - E2486.Reimplement deadline_rights and deadline_types]]
* [[CSC/ECE 517 Fall 2024 - E2487. Reimplement authorization_helper.rb]]
* [[CSC/ECE 517 Fall 2024 - E2488 Reimplementation of Add TA to course]]
* [[CSC/ECE 517 Fall 2024 - E2489. Create a UI for Assignment Edit page "Etc" tab in ReactJS]]
* [[CSC/ECE 517 Fall 2024 - E2491.UI for View assignments in Courses view]]
* [[CSC/ECE 517 Fall 2024 - E2492. UI for View submissions/assign grades (except heatgrid)]]
* [[CSC/ECE 517 Fall 2024 - E2493. UI for Assign Reviewers]]
* [[CSC/ECE 517 Fall 2024 - E2494. UI for Report Review for Assignment]]
* [[CSC/ECE 517 Fall 2024 - G2401 Refactor Graphql API endpoint for contribution metrics]]
* [[CSC/ECE 517 Fall 2024 - G2402 Refactor Graphql API endpoint for repositories]]

CSC/ECE 517 Fall 2024

2024-12-02T15:55:43Z

Ashelby:

* [[CSC/ECE 517 Fall 2024 - E2450. Refactor assignments_controller.rb]]
* [[CSC/ECE 517 Fall 2024 - E2451. Reimplement feedback_response_map.rb]]
* [[CSC/ECE 517 Fall 2024 - E2452. Refactor review_mapping_controller.rb]]
* [[CSC/ECE 517 Fall 2024 - E2453. Refactor review_mapping_helper.rb]]
* [[CSC/ECE 517 Fall 2024 - E2454. Refactor student_task.rb]]
* [[CSC/ECE 517 Fall 2024 - E2455. Refactor sign_up_sheet_controller.rb]]
* [[CSC/ECE 517 Fall 2024 - E2456. Refactor teams_user.rb]]
* [[CSC/ECE 517 Fall 2024 - E2456. Refactor teams_user.rb (Phase 2 - Design Document)]]
* [[CSC/ECE 517 Fall 2024 - E2457. GitHub metrics integration]]
* [[CSC/ECE 517 Fall 2024 - E2458. User management and users table]]
* [[CSC/ECE 517 Fall 2024 - E2459. View for results of bidding]]
* [[CSC/ECE 517 Fall 2024 - E2460 Mentor-Meeting Management]]
* [[CSC/ECE 517 Fall 2024 - E2461. UI for Courses]]
* [[CSC/ECE 517 Fall 2024 - E2461. UI and Backend for Courses]]
* [https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2024_-_E2462._UI_for_Questionnaires CSC/ECE 517 Fall 2024 - E2462. UI for Questionnaire.rb]
* [https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2024_-_E2463_Implement_Front_End_for_Student_Task_List CSC/ECE 517 Fall 2024 - E2463. UI for Student Task List]
* [[CSC/ECE 517 Fall 2024 - E2464 UI for Project Topics (was: Sign_up_Topics)]]
* [[CSC/ECE 517 Fall 2024 - E2465. UI for Institutions and Notification]]
* [[CSC/ECE 517 Fall 2024 - E2466. UI for Impersonate User]]
* [[CSC/ECE 517 Fall 2024 - E2467. UI for View Submissions]]
* [[CSC/ECE 517 Fall 2024 - E2468. Reimplement due_date]]
* [[CSC/ECE 517 Fall 2024 - E2469. Reimplement grades/view_team]]
* [[CSC/ECE 517 Fall 2024 - E2470. Reimplement grades_controller]]
* [[CSC/ECE 517 Fall 2024 - E2471. Reimplement logger]]
* [[CSC/ECE 517 Fall 2024 - E2472. Reimplement responses_controller.rb]]
* [[CSC/ECE 517 Fall 2024 - E2473. Reimplement sign up topic.rb as project topic.rb]]
* [[CSC/ECE 517 Fall 2024 - E2474. Reimplement student_quizzes_controller.rb]]
* [[CSC/ECE 517 Fall 2024 - E2475. Reimplement student_task view]]
* [[CSC/ECE 517 Fall 2024 - E2476. Reimplement student_teams_controller.rb]]
* [[CSC/ECE 517 Fall 2024 - E2477. Reimplement suggestion_controller.rb]]
* [[CSC/ECE 517 Fall 2024 - E2478. Reimplement the Question hierarchy as Item hierarchy]]
* [[CSC/ECE 517 Fall 2024 - E2479. Reimplement teams_users_controller.rb]]
* [[CSC/ECE 517 Fall 2024 - E2480. Implement testing for new Bookmarks Controller]]
* [[CSC/ECE 517 Fall 2024 - E2481 Reimplement response_map.rb]]
* [[CSC/ECE 517 Fall 2024 - E2482. Reimplement heatgrid for reviews]]
* [[CSC/ECE 517 Fall 2024 - E2483. Reimplement Notification Controller and Model]]
* [[CSC/ECE 517 Fall 2024 - E2484. Reimplement participants_controller.rb]]
* [[CSC/ECE 517 Fall 2024 - E2485. Allow reviewers to bid on what to review]]
* [[CSC/ECE 517 Fall 2024 - E2486.Reimplement deadline_rights and deadline_types]]
* [[CSC/ECE 517 Fall 2024 - E2487. Reimplement authorization_helper.rb]]
* [[CSC/ECE 517 Fall 2024 - E2488 Reimplementation of Add TA to course]]
* [[CSC/ECE 517 Fall 2024 - E2489. Create a UI for Assignment Edit page "Etc" tab in ReactJS]]
* [[CSC/ECE 517 Fall 2024 - E2491.UI for View assignments in Courses view]]
* [[CSC/ECE 517 Fall 2024 - E2492. UI for View submissions/assign grades (except heatgrid)]]
* [[CSC/ECE 517 Fall 2024 - E2493. UI for Assign Reviewers]]
* [[CSC/ECE 517 Fall 2024 - E2494. UI for Teammate Review View]]
* [[CSC/ECE 517 Fall 2024 - G2401 Refactor Graphql API endpoint for contribution metrics]]
* [[CSC/ECE 517 Fall 2024 - G2402 Refactor Graphql API endpoint for repositories]]

CSC/ECE 517 Fall 2024 - E2494. UI for Report Review for Assignment

2024-11-13T15:30:28Z

Ashelby:

===Overview===
This project will create a modern, responsive TypeScript and ReactJS interface for the Report Review page within Expertiza. It aims to present instructors with a summary of student reviews for each assignment. The design will prioritize simplicity and usability, providing instructors with a clear and effective way to review student feedback.

==1. Objective and Goals==
Develop a TypeScript and React-based UI for the Report Review page, accessible only to instructors, which will be responsive, intuitive, and efficient.

Key Goals:
1.Deliver an organized and clean display of student review summaries.
2.Create a responsive design adaptable to various screen sizes and devices.
3.Implement robust error handling for reliable data display and ensure usability across the application.

==2. Scope==
- Report Review Summary: Display individual review summaries per student for instructors, incorporating filtering and search functionalities to facilitate navigation.

- Role-Based Access Control (RBAC): Limit access to this page strictly to instructors, ensuring students cannot view the review summary.

==3. System Architecture==
The system architecture will use ReactJS with a focus on component reusability, TypeScript for type safety, and enhanced role-based access control. Components will communicate with the backend through RESTful APIs.

==4. Technical Specifications and Design Patterns==
4.1 Component Design and Structure
The Report Review UI will include modular components for scalability, reusability, and role-based access control.

Core Components for Report Review UI:

ReviewSummaryList: Displays a summary list of student reviews for a specific assignment.
ReviewDetail: Shows detailed information for each review, accessible upon selecting a summary.
ErrorBoundary: Wraps components to catch and display errors related to data fetching and rendering.

4.2 Role Management System
Role management will ensure only instructors can access the Report Review page. Key elements include:

Role Enumeration (ROLE Enum): Define roles like INSTRUCTOR to control access to the Report Review UI.
Centralized Authentication Context (AuthContext): Store and provide role information globally. This enables easy role checks, such as AuthContext.hasPermission('view_reviews'), to control access based on user roles.
Conditional Rendering: Use AuthContext to ensure only users with the INSTRUCTOR role can view the ReviewSummaryList.

4.3 Application of Design Patterns
Container-Presenter Pattern:

Purpose: Separate data-fetching logic from display logic for easier maintenance.
Application: A container component (e.g., ReviewSummaryPageContainer) will handle data fetching and pass the data to presentational components like ReviewSummaryList.
Benefits: Clear separation of concerns makes components more readable and easier to test.

Error Handling Pattern with Error Boundaries:

Purpose: Capture and manage errors for smoother user experience and reliability.
Application: Use an ErrorBoundary component to handle errors within the ReviewSummaryList and ReviewDetail components.
Benefits: Improves reliability by ensuring unexpected errors do not disrupt the entire page.

4.4 TypeScript for Static Typing
TypeScript will be used throughout to enforce strict typing, reduce errors, and improve code readability. Custom types/interfaces, such as ReviewSummary, will define expected data structures for better integration with the backend API.

4.5 Testing Strategy
Unit Tests:

Components like ReviewDetail and ErrorBoundary will have unit tests to ensure error handling and data display work as expected.

Integration Tests:

Verify that data flows correctly between components, especially between ReviewSummaryList and ReviewDetail.

End-to-End Tests:

Simulate instructor interactions to ensure only authorized users can access the review data, validating user flows from review list to detailed view.

== Team ==
===Mentor===
* Sahil Sawant

=== Members ===
* Arlee Shelby (ashelby@ncsu.edu)
* Aryan Tapkire (atapkir@ncsu.edu)
* Haojie Zhou (hzhou33@ncsu.edu)

==Links ==
*Github Repository:
*Pull Request:

==References==
[1]https://wiki.expertiza.ncsu.edu/index.php?title=Main_Page

[2]https://github.com/expertiza/reimplementation-front-end

[3]https://github.com/expertiza/reimplementation-back-end

[4]https://wiki.expertiza.ncsu.edu/index.php?title=Sign_up_topics

CSC/ECE 517 Fall 2024 - E2464 UI for Project Topics (was: Sign up Topics)

2024-10-29T23:01:01Z

Ashelby: /* Links */

==Background==
Expertiza is an open-source course management web application, built with Ruby on Rails, that is maintained by students and teaching staff across NC State and other universities. Additionally, Expertiza is used as a platform to help students learn how to work collaboratively and contribute to large applications concurrent with best practices and object oriented design and development.

For our project in particular, we were tasked with building a new user interface for a new Project Topics page with React.js and Typescript. The page's main function is to display all the project topics for an assignment, with relevant information displayed with respect to the user, student or administrators/instructor. This was previously implemented as a Sign up Topics page, which we use as a template for our current implementation. If you would like to learn more about Expertiza, please check the Expertiza wiki[1], or the GitHub pages [2],[3].

==Previous: Sign up Topics==
Previously, the user interface display for assignment topics was implemented as a Sign up Topics page. The main component of the display included a table showing all topics for a particular assignment. The student view displayed the topics id, the number of available slots, and number of teams of the waitlist as table columns: Topic ID, Topic name(s), Available Slots, and Num. on waitlist. The student view also implemented a display for a signed in student's current selected or assigned topic by an indication of a yellow highlight over their topic in the associated row in the topics table, and in text at the top of the page under the page header.
*Student View:
[[File:SignupTopics-StudentView.jpeg|800px]]

The admin/instructor view also displayed all topics for an associated project, with two additional columns, one indicating the number of slots available: Num. of slots, and another: Checkbox which allowed topics to be selected. Additionally, admin/instructors were able to view the teams associated with a given topic in the Topic name(s) column by the usernames of the team's members in smaller text under the topic name. The admin/instructor page also displayed a list of checkboxes above the table with fields associated with the assignment topic features. The checkboxes indicate attributes of the assignment settings attribute.
*Instructor View:
[[File:SignupTopics-InstructorView.jpeg|900px]]

==Design==
For our implementation, we were tasked with creating a new user interface for assignment topics using the dynamic rendering capabilities of React.js and Typescript. We used the previous implementation as a model for our design.
===Specifications===
*Intuitive Design:
**User-friendly interface
**Easy to navigate
**Enough spacing to ensure all the fetched information is being displayed in an orderly and clean fashion
*Responsive Design:
**Hold design across multiple devices (mobile, laptop, tablet) and screen sizes (fullscreen, windowed)
*Error Handling:
**Take in consideration of possible data errors (invalid data, missing data)
*Testing:
**All the components of the UI are functioning
**Error handling
**Reliability of the UI is maintained

===Overview===
For our design, we used test data in order to simulate the responsiveness and integration with real data. The test data is set up following the Assignments and Topics specifications, from [4]. We also used modular React styling components to keep the number of files we modified minimal and aimed to restrict the impact of our implementation to other parts of the application small. Because the current Expertiza front end has components and pages that are being developed, we added our new Project Topics page as a new link on the application header, labled Topics, which can be accessed at all times.
====Files Changed====
To provide access to our new Project Topics page, we added a new route and header to the following files, as well as updated the README.md file with instructions to add a user. We use the added user to view and test the student view. The current Expertiza application already has an admin user implemented which we used to test the admin/instructor display.
*src/App.tsx
*src/layout/Header.tsx
*README.md

====Files Created====
Our main implementation can be found in the following files, which we created for the new Project Topics page.
*src/pages/ProjectTopics
*src/pages/ProjectTopics/ProjectTopics/testData.js
*src/pages/ProjectTopics/ProjectTopics.module.css
*src/pages/ProjectTopics/ProjectTopics.tsx

===Implementation===
The main component of our design is a table, resembling the display of the previous implementation, which serves as the component for which students and admin/instructors can view all topics. Additionally, due to parts of the current Expertiza front-end being developed, we also included an Assignment select component, so that our implementation and UI could be well tested within realistic assignment conditions and easily integrated to the current application.
====Student Display====
Additionally, for the student display, we implemented a feature which allows for students to view their selected and/or assigned topics. We implemented this with a visual indicator and a selection checkbox. Following the previous Sign up Topics page, we added a visual indicator in the topics table and we chose to implement this with a gold start next to the Topic ID. We made this choice following the design specifications and with the aim of clarifying the intent of the visual marker. We designed the student selection checkbox to enhance the previously implemented text describing the student's current topic. This implementation enables the student user to more clearly obtain their current topic selection and provides a more engaging experience.

[[File:ProjectTopics-NewStudentView.jpeg|1200px]]

====Admin/instructor Display====
For the Admin/instructor display, we also implemented an Assignment Topic Settings feature as a set of checkboxes, as in the previous implementation. This component is auto-filled with the set attributes of the Assignment settings in the test data, which allows for further testing. As such, we ensure that this feature can be integrated with the current structure of Assignments and displays the associated features in a user friendly way for admin/instructors. We also allow for the display of selected teams for each topic by the associated team members, below the Topic Name(s) column, much like the previous implementation. This component can be further integrated with the back-end development of ProjectTopics.

[[File:ProjectTopics-NewAdminView.jpeg|1200px]]

== Team ==
===Mentor===
* Sahil Sawant

=== Members ===
* Arlee Shelby (ashelby@ncsu.edu)
* Aryan Tapkire (atapkir@ncsu.edu)
* Haojie Zhou (hzhou33@ncsu.edu)

==Links ==
*Github Repository: https://github.com/arlee-shelby/reimplementation-front-end
*Pull Request: https://github.com/expertiza/reimplementation-front-end/pull/64

==References==
[1]https://wiki.expertiza.ncsu.edu/index.php?title=Main_Page

[2]https://github.com/expertiza/reimplementation-front-end

[3]https://github.com/expertiza/reimplementation-back-end

[4]https://wiki.expertiza.ncsu.edu/index.php?title=Sign_up_topics

CSC/ECE 517 Fall 2024 - E2464 UI for Project Topics (was: Sign up Topics)

2024-10-29T22:57:55Z

Ashelby: /* Previous: Sign up Topics */

==Background==
Expertiza is an open-source course management web application, built with Ruby on Rails, that is maintained by students and teaching staff across NC State and other universities. Additionally, Expertiza is used as a platform to help students learn how to work collaboratively and contribute to large applications concurrent with best practices and object oriented design and development.

For our project in particular, we were tasked with building a new user interface for a new Project Topics page with React.js and Typescript. The page's main function is to display all the project topics for an assignment, with relevant information displayed with respect to the user, student or administrators/instructor. This was previously implemented as a Sign up Topics page, which we use as a template for our current implementation. If you would like to learn more about Expertiza, please check the Expertiza wiki[1], or the GitHub pages [2],[3].

==Previous: Sign up Topics==
Previously, the user interface display for assignment topics was implemented as a Sign up Topics page. The main component of the display included a table showing all topics for a particular assignment. The student view displayed the topics id, the number of available slots, and number of teams of the waitlist as table columns: Topic ID, Topic name(s), Available Slots, and Num. on waitlist. The student view also implemented a display for a signed in student's current selected or assigned topic by an indication of a yellow highlight over their topic in the associated row in the topics table, and in text at the top of the page under the page header.
*Student View:
[[File:SignupTopics-StudentView.jpeg|800px]]

The admin/instructor view also displayed all topics for an associated project, with two additional columns, one indicating the number of slots available: Num. of slots, and another: Checkbox which allowed topics to be selected. Additionally, admin/instructors were able to view the teams associated with a given topic in the Topic name(s) column by the usernames of the team's members in smaller text under the topic name. The admin/instructor page also displayed a list of checkboxes above the table with fields associated with the assignment topic features. The checkboxes indicate attributes of the assignment settings attribute.
*Instructor View:
[[File:SignupTopics-InstructorView.jpeg|900px]]

==Design==
For our implementation, we were tasked with creating a new user interface for assignment topics using the dynamic rendering capabilities of React.js and Typescript. We used the previous implementation as a model for our design.
===Specifications===
*Intuitive Design:
**User-friendly interface
**Easy to navigate
**Enough spacing to ensure all the fetched information is being displayed in an orderly and clean fashion
*Responsive Design:
**Hold design across multiple devices (mobile, laptop, tablet) and screen sizes (fullscreen, windowed)
*Error Handling:
**Take in consideration of possible data errors (invalid data, missing data)
*Testing:
**All the components of the UI are functioning
**Error handling
**Reliability of the UI is maintained

===Overview===
For our design, we used test data in order to simulate the responsiveness and integration with real data. The test data is set up following the Assignments and Topics specifications, from [4]. We also used modular React styling components to keep the number of files we modified minimal and aimed to restrict the impact of our implementation to other parts of the application small. Because the current Expertiza front end has components and pages that are being developed, we added our new Project Topics page as a new link on the application header, labled Topics, which can be accessed at all times.
====Files Changed====
To provide access to our new Project Topics page, we added a new route and header to the following files, as well as updated the README.md file with instructions to add a user. We use the added user to view and test the student view. The current Expertiza application already has an admin user implemented which we used to test the admin/instructor display.
*src/App.tsx
*src/layout/Header.tsx
*README.md

====Files Created====
Our main implementation can be found in the following files, which we created for the new Project Topics page.
*src/pages/ProjectTopics
*src/pages/ProjectTopics/ProjectTopics/testData.js
*src/pages/ProjectTopics/ProjectTopics.module.css
*src/pages/ProjectTopics/ProjectTopics.tsx

===Implementation===
The main component of our design is a table, resembling the display of the previous implementation, which serves as the component for which students and admin/instructors can view all topics. Additionally, due to parts of the current Expertiza front-end being developed, we also included an Assignment select component, so that our implementation and UI could be well tested within realistic assignment conditions and easily integrated to the current application.
====Student Display====
Additionally, for the student display, we implemented a feature which allows for students to view their selected and/or assigned topics. We implemented this with a visual indicator and a selection checkbox. Following the previous Sign up Topics page, we added a visual indicator in the topics table and we chose to implement this with a gold start next to the Topic ID. We made this choice following the design specifications and with the aim of clarifying the intent of the visual marker. We designed the student selection checkbox to enhance the previously implemented text describing the student's current topic. This implementation enables the student user to more clearly obtain their current topic selection and provides a more engaging experience.

[[File:ProjectTopics-NewStudentView.jpeg|1200px]]

====Admin/instructor Display====
For the Admin/instructor display, we also implemented an Assignment Topic Settings feature as a set of checkboxes, as in the previous implementation. This component is auto-filled with the set attributes of the Assignment settings in the test data, which allows for further testing. As such, we ensure that this feature can be integrated with the current structure of Assignments and displays the associated features in a user friendly way for admin/instructors. We also allow for the display of selected teams for each topic by the associated team members, below the Topic Name(s) column, much like the previous implementation. This component can be further integrated with the back-end development of ProjectTopics.

[[File:ProjectTopics-NewAdminView.jpeg|1200px]]

== Team ==
===Mentor===
* Sahil Sawant

=== Members ===
* Arlee Shelby (ashelby@ncsu.edu)
* Aryan Tapkire (atapkir@ncsu.edu)
* Haojie Zhou (hzhou33@ncsu.edu)

==Links ==
*Github Repository: https://github.com/arlee-shelby/reimplementation-front-end

==References==
[1]https://wiki.expertiza.ncsu.edu/index.php?title=Main_Page

[2]https://github.com/expertiza/reimplementation-front-end

[3]https://github.com/expertiza/reimplementation-back-end

[4]https://wiki.expertiza.ncsu.edu/index.php?title=Sign_up_topics

CSC/ECE 517 Fall 2024 - E2464 UI for Project Topics (was: Sign up Topics)

2024-10-29T22:57:46Z

Ashelby: /* Previous: Sign up Topics */

==Background==
Expertiza is an open-source course management web application, built with Ruby on Rails, that is maintained by students and teaching staff across NC State and other universities. Additionally, Expertiza is used as a platform to help students learn how to work collaboratively and contribute to large applications concurrent with best practices and object oriented design and development.

For our project in particular, we were tasked with building a new user interface for a new Project Topics page with React.js and Typescript. The page's main function is to display all the project topics for an assignment, with relevant information displayed with respect to the user, student or administrators/instructor. This was previously implemented as a Sign up Topics page, which we use as a template for our current implementation. If you would like to learn more about Expertiza, please check the Expertiza wiki[1], or the GitHub pages [2],[3].

==Previous: Sign up Topics==
Previously, the user interface display for assignment topics was implemented as a Sign up Topics page. The main component of the display included a table showing all topics for a particular assignment. The student view displayed the topics id, the number of available slots, and number of teams of the waitlist as table columns: Topic ID, Topic name(s), Available Slots, and Num. on waitlist. The student view also implemented a display for a signed in student's current selected or assigned topic by an indication of a yellow highlight over their topic in the associated row in the topics table, and in text at the top of the page under the page header.
*Student View:
[[File:SignupTopics-StudentView.jpeg|800px]]

The admin/instructor view also displayed all topics for an associated project, with two additional columns, one indicating the number of slots available: Num. of slots, and another: Checkbox which allowed topics to be selected. Additionally, admin/instructors were able to view the teams associated with a given topic in the Topic name(s) column by the usernames of the team's members in smaller text under the topic name. The admin/instructor page also displayed a list of checkboxes above the table with fields associated with the assignment topic features. The checkboxes indicate attributes of the assignment settings attribute.
*Instructor View:
[[File:SignupTopics-InstructorView.jpeg|600px]]

==Design==
For our implementation, we were tasked with creating a new user interface for assignment topics using the dynamic rendering capabilities of React.js and Typescript. We used the previous implementation as a model for our design.
===Specifications===
*Intuitive Design:
**User-friendly interface
**Easy to navigate
**Enough spacing to ensure all the fetched information is being displayed in an orderly and clean fashion
*Responsive Design:
**Hold design across multiple devices (mobile, laptop, tablet) and screen sizes (fullscreen, windowed)
*Error Handling:
**Take in consideration of possible data errors (invalid data, missing data)
*Testing:
**All the components of the UI are functioning
**Error handling
**Reliability of the UI is maintained

===Overview===
For our design, we used test data in order to simulate the responsiveness and integration with real data. The test data is set up following the Assignments and Topics specifications, from [4]. We also used modular React styling components to keep the number of files we modified minimal and aimed to restrict the impact of our implementation to other parts of the application small. Because the current Expertiza front end has components and pages that are being developed, we added our new Project Topics page as a new link on the application header, labled Topics, which can be accessed at all times.
====Files Changed====
To provide access to our new Project Topics page, we added a new route and header to the following files, as well as updated the README.md file with instructions to add a user. We use the added user to view and test the student view. The current Expertiza application already has an admin user implemented which we used to test the admin/instructor display.
*src/App.tsx
*src/layout/Header.tsx
*README.md

====Files Created====
Our main implementation can be found in the following files, which we created for the new Project Topics page.
*src/pages/ProjectTopics
*src/pages/ProjectTopics/ProjectTopics/testData.js
*src/pages/ProjectTopics/ProjectTopics.module.css
*src/pages/ProjectTopics/ProjectTopics.tsx

===Implementation===
The main component of our design is a table, resembling the display of the previous implementation, which serves as the component for which students and admin/instructors can view all topics. Additionally, due to parts of the current Expertiza front-end being developed, we also included an Assignment select component, so that our implementation and UI could be well tested within realistic assignment conditions and easily integrated to the current application.
====Student Display====
Additionally, for the student display, we implemented a feature which allows for students to view their selected and/or assigned topics. We implemented this with a visual indicator and a selection checkbox. Following the previous Sign up Topics page, we added a visual indicator in the topics table and we chose to implement this with a gold start next to the Topic ID. We made this choice following the design specifications and with the aim of clarifying the intent of the visual marker. We designed the student selection checkbox to enhance the previously implemented text describing the student's current topic. This implementation enables the student user to more clearly obtain their current topic selection and provides a more engaging experience.

[[File:ProjectTopics-NewStudentView.jpeg|1200px]]

====Admin/instructor Display====
For the Admin/instructor display, we also implemented an Assignment Topic Settings feature as a set of checkboxes, as in the previous implementation. This component is auto-filled with the set attributes of the Assignment settings in the test data, which allows for further testing. As such, we ensure that this feature can be integrated with the current structure of Assignments and displays the associated features in a user friendly way for admin/instructors. We also allow for the display of selected teams for each topic by the associated team members, below the Topic Name(s) column, much like the previous implementation. This component can be further integrated with the back-end development of ProjectTopics.

[[File:ProjectTopics-NewAdminView.jpeg|1200px]]

== Team ==
===Mentor===
* Sahil Sawant

=== Members ===
* Arlee Shelby (ashelby@ncsu.edu)
* Aryan Tapkire (atapkir@ncsu.edu)
* Haojie Zhou (hzhou33@ncsu.edu)

==Links ==
*Github Repository: https://github.com/arlee-shelby/reimplementation-front-end

==References==
[1]https://wiki.expertiza.ncsu.edu/index.php?title=Main_Page

[2]https://github.com/expertiza/reimplementation-front-end

[3]https://github.com/expertiza/reimplementation-back-end

[4]https://wiki.expertiza.ncsu.edu/index.php?title=Sign_up_topics

CSC/ECE 517 Fall 2024 - E2464 UI for Project Topics (was: Sign up Topics)

2024-10-29T22:56:03Z

Ashelby: /* Admin/instructor Display */

==Background==
Expertiza is an open-source course management web application, built with Ruby on Rails, that is maintained by students and teaching staff across NC State and other universities. Additionally, Expertiza is used as a platform to help students learn how to work collaboratively and contribute to large applications concurrent with best practices and object oriented design and development.

For our project in particular, we were tasked with building a new user interface for a new Project Topics page with React.js and Typescript. The page's main function is to display all the project topics for an assignment, with relevant information displayed with respect to the user, student or administrators/instructor. This was previously implemented as a Sign up Topics page, which we use as a template for our current implementation. If you would like to learn more about Expertiza, please check the Expertiza wiki[1], or the GitHub pages [2],[3].

==Previous: Sign up Topics==
Previously, the user interface display for assignment topics was implemented as a Sign up Topics page. The main component of the display included a table showing all topics for a particular assignment. The student view displayed the topics id, the number of available slots, and number of teams of the waitlist as table columns: Topic ID, Topic name(s), Available Slots, and Num. on waitlist. The student view also implemented a display for a signed in student's current selected or assigned topic by an indication of a yellow highlight over their topic in the associated row in the topics table, and in text at the top of the page under the page header.
*Student View:
[[File:SignupTopics-StudentView.jpeg|500px]]

The admin/instructor view also displayed all topics for an associated project, with two additional columns, one indicating the number of slots available: Num. of slots, and another: Checkbox which allowed topics to be selected. Additionally, admin/instructors were able to view the teams associated with a given topic in the Topic name(s) column by the usernames of the team's members in smaller text under the topic name. The admin/instructor page also displayed a list of checkboxes above the table with fields associated with the assignment topic features. The checkboxes indicate attributes of the assignment settings attribute.
*Instructor View:
[[File:SignupTopics-InstructorView.jpeg|600px]]

==Design==
For our implementation, we were tasked with creating a new user interface for assignment topics using the dynamic rendering capabilities of React.js and Typescript. We used the previous implementation as a model for our design.
===Specifications===
*Intuitive Design:
**User-friendly interface
**Easy to navigate
**Enough spacing to ensure all the fetched information is being displayed in an orderly and clean fashion
*Responsive Design:
**Hold design across multiple devices (mobile, laptop, tablet) and screen sizes (fullscreen, windowed)
*Error Handling:
**Take in consideration of possible data errors (invalid data, missing data)
*Testing:
**All the components of the UI are functioning
**Error handling
**Reliability of the UI is maintained

===Overview===
For our design, we used test data in order to simulate the responsiveness and integration with real data. The test data is set up following the Assignments and Topics specifications, from [4]. We also used modular React styling components to keep the number of files we modified minimal and aimed to restrict the impact of our implementation to other parts of the application small. Because the current Expertiza front end has components and pages that are being developed, we added our new Project Topics page as a new link on the application header, labled Topics, which can be accessed at all times.
====Files Changed====
To provide access to our new Project Topics page, we added a new route and header to the following files, as well as updated the README.md file with instructions to add a user. We use the added user to view and test the student view. The current Expertiza application already has an admin user implemented which we used to test the admin/instructor display.
*src/App.tsx
*src/layout/Header.tsx
*README.md

====Files Created====
Our main implementation can be found in the following files, which we created for the new Project Topics page.
*src/pages/ProjectTopics
*src/pages/ProjectTopics/ProjectTopics/testData.js
*src/pages/ProjectTopics/ProjectTopics.module.css
*src/pages/ProjectTopics/ProjectTopics.tsx

===Implementation===
The main component of our design is a table, resembling the display of the previous implementation, which serves as the component for which students and admin/instructors can view all topics. Additionally, due to parts of the current Expertiza front-end being developed, we also included an Assignment select component, so that our implementation and UI could be well tested within realistic assignment conditions and easily integrated to the current application.
====Student Display====
Additionally, for the student display, we implemented a feature which allows for students to view their selected and/or assigned topics. We implemented this with a visual indicator and a selection checkbox. Following the previous Sign up Topics page, we added a visual indicator in the topics table and we chose to implement this with a gold start next to the Topic ID. We made this choice following the design specifications and with the aim of clarifying the intent of the visual marker. We designed the student selection checkbox to enhance the previously implemented text describing the student's current topic. This implementation enables the student user to more clearly obtain their current topic selection and provides a more engaging experience.

[[File:ProjectTopics-NewStudentView.jpeg|1200px]]

====Admin/instructor Display====
For the Admin/instructor display, we also implemented an Assignment Topic Settings feature as a set of checkboxes, as in the previous implementation. This component is auto-filled with the set attributes of the Assignment settings in the test data, which allows for further testing. As such, we ensure that this feature can be integrated with the current structure of Assignments and displays the associated features in a user friendly way for admin/instructors. We also allow for the display of selected teams for each topic by the associated team members, below the Topic Name(s) column, much like the previous implementation. This component can be further integrated with the back-end development of ProjectTopics.

[[File:ProjectTopics-NewAdminView.jpeg|1200px]]

== Team ==
===Mentor===
* Sahil Sawant

=== Members ===
* Arlee Shelby (ashelby@ncsu.edu)
* Aryan Tapkire (atapkir@ncsu.edu)
* Haojie Zhou (hzhou33@ncsu.edu)

==Links ==
*Github Repository: https://github.com/arlee-shelby/reimplementation-front-end

==References==
[1]https://wiki.expertiza.ncsu.edu/index.php?title=Main_Page

[2]https://github.com/expertiza/reimplementation-front-end

[3]https://github.com/expertiza/reimplementation-back-end

[4]https://wiki.expertiza.ncsu.edu/index.php?title=Sign_up_topics

CSC/ECE 517 Fall 2024 - E2464 UI for Project Topics (was: Sign up Topics)

2024-10-29T22:54:16Z

Ashelby: /* Implementation */

==Background==
Expertiza is an open-source course management web application, built with Ruby on Rails, that is maintained by students and teaching staff across NC State and other universities. Additionally, Expertiza is used as a platform to help students learn how to work collaboratively and contribute to large applications concurrent with best practices and object oriented design and development.

For our project in particular, we were tasked with building a new user interface for a new Project Topics page with React.js and Typescript. The page's main function is to display all the project topics for an assignment, with relevant information displayed with respect to the user, student or administrators/instructor. This was previously implemented as a Sign up Topics page, which we use as a template for our current implementation. If you would like to learn more about Expertiza, please check the Expertiza wiki[1], or the GitHub pages [2],[3].

==Previous: Sign up Topics==
Previously, the user interface display for assignment topics was implemented as a Sign up Topics page. The main component of the display included a table showing all topics for a particular assignment. The student view displayed the topics id, the number of available slots, and number of teams of the waitlist as table columns: Topic ID, Topic name(s), Available Slots, and Num. on waitlist. The student view also implemented a display for a signed in student's current selected or assigned topic by an indication of a yellow highlight over their topic in the associated row in the topics table, and in text at the top of the page under the page header.
*Student View:
[[File:SignupTopics-StudentView.jpeg|500px]]

The admin/instructor view also displayed all topics for an associated project, with two additional columns, one indicating the number of slots available: Num. of slots, and another: Checkbox which allowed topics to be selected. Additionally, admin/instructors were able to view the teams associated with a given topic in the Topic name(s) column by the usernames of the team's members in smaller text under the topic name. The admin/instructor page also displayed a list of checkboxes above the table with fields associated with the assignment topic features. The checkboxes indicate attributes of the assignment settings attribute.
*Instructor View:
[[File:SignupTopics-InstructorView.jpeg|600px]]

==Design==
For our implementation, we were tasked with creating a new user interface for assignment topics using the dynamic rendering capabilities of React.js and Typescript. We used the previous implementation as a model for our design.
===Specifications===
*Intuitive Design:
**User-friendly interface
**Easy to navigate
**Enough spacing to ensure all the fetched information is being displayed in an orderly and clean fashion
*Responsive Design:
**Hold design across multiple devices (mobile, laptop, tablet) and screen sizes (fullscreen, windowed)
*Error Handling:
**Take in consideration of possible data errors (invalid data, missing data)
*Testing:
**All the components of the UI are functioning
**Error handling
**Reliability of the UI is maintained

===Overview===
For our design, we used test data in order to simulate the responsiveness and integration with real data. The test data is set up following the Assignments and Topics specifications, from [4]. We also used modular React styling components to keep the number of files we modified minimal and aimed to restrict the impact of our implementation to other parts of the application small. Because the current Expertiza front end has components and pages that are being developed, we added our new Project Topics page as a new link on the application header, labled Topics, which can be accessed at all times.
====Files Changed====
To provide access to our new Project Topics page, we added a new route and header to the following files, as well as updated the README.md file with instructions to add a user. We use the added user to view and test the student view. The current Expertiza application already has an admin user implemented which we used to test the admin/instructor display.
*src/App.tsx
*src/layout/Header.tsx
*README.md

====Files Created====
Our main implementation can be found in the following files, which we created for the new Project Topics page.
*src/pages/ProjectTopics
*src/pages/ProjectTopics/ProjectTopics/testData.js
*src/pages/ProjectTopics/ProjectTopics.module.css
*src/pages/ProjectTopics/ProjectTopics.tsx

===Implementation===
The main component of our design is a table, resembling the display of the previous implementation, which serves as the component for which students and admin/instructors can view all topics. Additionally, due to parts of the current Expertiza front-end being developed, we also included an Assignment select component, so that our implementation and UI could be well tested within realistic assignment conditions and easily integrated to the current application.
====Student Display====
Additionally, for the student display, we implemented a feature which allows for students to view their selected and/or assigned topics. We implemented this with a visual indicator and a selection checkbox. Following the previous Sign up Topics page, we added a visual indicator in the topics table and we chose to implement this with a gold start next to the Topic ID. We made this choice following the design specifications and with the aim of clarifying the intent of the visual marker. We designed the student selection checkbox to enhance the previously implemented text describing the student's current topic. This implementation enables the student user to more clearly obtain their current topic selection and provides a more engaging experience.

[[File:ProjectTopics-NewStudentView.jpeg|1200px]]

====Admin/instructor Display====
For the Admin/instructor display, we also implemented an Assignment Topic Settings feature as a set of checkboxes, as in the previous implementation. This component is auto-filled with the set attributes of the Assignment settings in the test data, which allows for further testing. As such, we ensure that this feature can be integrated with the current structure of Assignments and displays the associated features in a user friendly way for admin/instructors.

[[File:ProjectTopics-NewAdminView.jpeg|1200px]]

== Team ==
===Mentor===
* Sahil Sawant

=== Members ===
* Arlee Shelby (ashelby@ncsu.edu)
* Aryan Tapkire (atapkir@ncsu.edu)
* Haojie Zhou (hzhou33@ncsu.edu)

==Links ==
*Github Repository: https://github.com/arlee-shelby/reimplementation-front-end

==References==
[1]https://wiki.expertiza.ncsu.edu/index.php?title=Main_Page

[2]https://github.com/expertiza/reimplementation-front-end

[3]https://github.com/expertiza/reimplementation-back-end

[4]https://wiki.expertiza.ncsu.edu/index.php?title=Sign_up_topics