CSC/ECE 517 Spring 2024 - E2444 Implement Frontend for the Review: Difference between revisions

From Expertiza_Wiki
Jump to navigation Jump to search
No edit summary
Line 52: Line 52:
4. Below is the Flow-Chart for the entire process.
4. Below is the Flow-Chart for the entire process.
<br/>
<br/>
[[File: Reviewer_Control_Flow_E2444.jpeg | 1000px| center]]
[[File: Reviewer_Control_Flow_E2444.jpeg | 500px| center]]
<p style="text-align: center;">Figure 2: Flow-Chart of the "View Review" and "Email Author" functional requirements</p>
<p style="text-align: center;">Figure 2: Flow-Chart of the "View Review" and "Email Author" functional requirements</p>



Revision as of 02:14, 9 April 2024

Overview of Expertiza

Expertiza, constructed using Ruby on Rails, is an open-source learning management system that offers a diverse array of features. These include the ability to generate assignments, tests, assignment teams, courses, reviews for the assignments, etc. Notably, it excels in providing a comprehensive peer review system, fostering thorough feedback within teams and among group members. The central focus of the project revolves around enhancing the frontend components related to the Review. A specific challenge being tackled involves the reimplementation of the current non-Typescript Review Page to incorporate Typescript and React. Consequently, the team's task is to craft the User Interface for these components using React.js and Typescript.

Introduction

The main objective of this project is to reimplement the front end for the Review view page within Expertiza.

Problem Statement

The following tasks were required for the reimplementation :

  1. Frontend Reimplementation: Reimplement the frontend of the Review page in React.js and Typescript which is currently in Ruby.
  2. Seeding of Databse File There should be seeding of 1 file to simulate the review given by a user which will reflect in the Review UI page.
  3. Removal of Unused Elements: Remove any unused elements such as URLs, color legends, etc., to streamline the interface.
  4. Improve UI: We aim to improve user experience and interface efficiency by developing a refreshed front end using React JS and TypeScript.

Project 4 - DESIGN DOC

Design Patterns

Composite Design Pattern:

By nesting and composing elements like Show-Review, Email etc and others, we can effectively design our Review component by utilising the Composite Design Pattern.

DRY Principle:

We want to reduce redundancy by using React's functionality to reuse pre-existing components like Show-Review and Email, in line with the DRY Principle.

Provider Pattern:

Our goal is to apply the Provider Pattern to React's Context API so that props can propagate naturally throughout the component hierarchy without requiring explicit prop drilling.

Observer Pattern:

Our goal is to take advantage of the Observer Pattern by using hooks like useEffect and useState along with React's Context API to manage component state and side effects efficiently.

HOC Pattern:

Routing for new pages can be made more efficient by using the Higher-Order Component pattern, or HOC Pattern. This entails creating functions that take an input component and provide a changed component with routing functionality.

Mediator Pattern:

Our goal is to apply the Mediator Pattern in light of the discrepancy between frontend requirements and backend data structures. With this method, we can easily change data as needed to ensure that it is consistent and compatible with the rest of our program.

Design

The designs provided are for the existing Reviews Page, which has already been implemented. Our goal is to replicate these designs for the new components mentioned earlier in the project. This involves creating similar visual elements, layouts, and functionalities for these new components to maintain consistency and coherence across the application.

Existing Review Page

Figure 1: Existing Review page within Expertiza

Reimplementation To Be Done

1. Our task is to reimplement the exact Review page which is currently in Ruby language to React and Typescript languages respectively.
2. With that, we will also be making the UI a little more responsive and improving the experience.
3. We will be seeding a database file which will read the Reviews from that file to display it in the front-end.
4. Below is the Flow-Chart for the entire process.

Figure 2: Flow-Chart of the "View Review" and "Email Author" functional requirements

Test Plan

Since the changes revolve around UI implementation, the features need to be manually checked on the web pages.

  1. Component Rendering: Ensure that all components from the original Ruby frontend are properly re-implemented in React.js and Typescript.
  2. Styling Consistency: Verify that the new front-end maintains consistent styling with the rest of the application.
  3. Functionality Testing: Test all interactive elements such as buttons, and input fields to ensure they work as expected.
  4. Responsive Design: Check the responsiveness of the new front-end on different screen sizes and devices.
  5. Show "Email Author" Link: Ensure that "Email Author" Link is there in the reimplemented React page so that the Review can be mailed to him/her.
  6. Seeding the Database Functionality: Ensure that the Reviews are correctly read from a sample Database by seeding it correctly.
  7. Interface Efficiency: Check if the new frontend enhances interface efficiency by being more intuitive and user-friendly.

Important Links

  • GitHub repo [1]
  • Pull Request to be merged before starting this project [2]

Team

Mentor
  • Riya Gori
Members
  • Mitesh Agarwal (unityid: magarwa3)
  • Shubham Loya (unityid: ssloya)
  • Gwen Mason (unityid: cpmason)