Upgrade to Pro — share decks privately, control downloads, hide ads and more …

CS 373 Final Project Presentation

CS 373 Final Project Presentation

CS 373 Final Project Presentation for Group 4.

Mrityunjay Mishra

July 17, 2021
Tweet

Other Decks in Education

Transcript

  1. Meet the Team Mrityunjay Mishra Architect and Full Stack Developer

    Nalin Mahajan Backend Developer Vineeth Bandi Frontend Developer James Dong Frontend Developer
  2. Motivation • Lack of easily accessible NBA information for data-based

    objectives ◦ We aggregate data that is spread across different sources and compile it for easy digestions and reuse • Fans can easily use this website to track information about their favorite players, teams, or even specifics about a game ◦ Current solutions require multiple searches or access to not easily accessible data • Provided a good opportunity to practice intuitive design elements and create a visually appealing website
  3. Frontend Design • Component-based frontend architecture for a faster and

    more dynamic UI • Page-based presentation for familiarity with users • Grid based layout for responsiveness • Media-first design thinking for a more immersive experience App.js Navbar.js Home.js Teams.js Players.js Games.js Sources.js About.js TeamInstance.js PlayerInstance.js GameInstance.js
  4. Self Critique • What did we do well? • What

    did we learn? • What can we do better? • What puzzles us? Icon by Freepik from flaticon
  5. What did we do well? User Interface • User friendly

    • Intuitive • Lightweight design • Efficient component-driven architecture • Responsive design Backend API Design • Simple to use • Easy design based on path parameters • Rich options through query capabilities • Modular approach driving efficiency Database Design • Enabled a 3-tier architecture for security • Normalization Rich & Relevant Information • DB scrape got the most relevant and up-to-date information for NBA • We provide latest news using the ESPN API
  6. What can we do better? • Implement sorting with chaining

    • Implement a more intuitive UI for our chained filtering • Implement a more efficient algorithm for multi-word search • Implement better security for our API • Construct a more appealing UI for the Games page • Add more relevant media
  7. What puzzles us? Automated Q/A testing for frontend • How

    to leverage Selenium • How to leverage RobotFramework • Any other technologies? How to efficiently test database setup/design? How to use teams and other Agile concepts with Gitlab?
  8. Provider Critique - BookSleuth • What did they do well?

    • What did we learn from their website? • What can they do better? • What puzzles us about their website?
  9. What did they do well? Simple and Intuitive User Interface

    • Eye-appealing splash page • Simple navigation • Consistent UI / layout Modern approach to design thinking • Very simple and easy to use sorting / filtering options Easy to use and well documented API
  10. What can we learn from their website? • It is

    possible to create a simplified UI for an already established functionality ◦ Such as filtering and sorting • Using pre-established UI standards can make the UI more intuitive and easy to follow • Consistency in the UI can lead to a better user experience • Material UI can also be used for developing a more eye-appealing and responsive design
  11. What can they do better? More vibrant color palette along

    with a bigger font size for a better user experience Add more immersive media, such as videos More modularity in backend architecture (ex. query parsing could be modularized from main)
  12. What puzzles us about their website? • List of works/books

    could not be organized by genre, which made it a little difficult to find books of a specific genre • Content formatting on the frontend could be inconsistent from time to time, which led to some confusion ◦ For example, the works instance page • How the Wikimedia REST API was used in their website