Ideation and Design Team Live Review

[AniCricKet]

Overview

For this mini-project, our team has decided to build a project focused on cars, specifically the electric cars offered by known brands such as BMW, Chevrolet, Tesla, and Lucid as we move into a more alternative fuel source for our automobiles.

Build a virtual car website where users can explore different types of cars, view details, and “customize” their virtual cars. The application will have both frontend and backend components.

Backend

1. Deployment of Backend and rebuilding whenever changes are made to spring
2. Image Database: Using an image database in order to display images as APIs don't include information about each car's look Reference
3. Car Classes: Implement classes for different types of cars with inheritance. For instance, you can have classes for sedans, SUVs, sports cars, etc., each inheriting from a common Car class.
4. Database: Use a simple database to store information about available cars, their specifications, and customization options.
5. Sorting Algorithm: Implement a sorting algorithm to sort cars based on various criteria, such as type, brand, or price.

Frontend

1. Car Display: Create an attractive frontend where users can see the available cars, their images, and specifications.
2. Maximize use of Layouts and Includes in order to provide blogs and use of timebox
3. Building the Tables for Each Company: Being able to display different information about each vehicle

Integration

1. API Endpoints: Develop API endpoints on the backend to handle fetching the list of available cars, details of a specific car, and customization options.
2. Communication: Use AJAX or Fetch API to communicate between the frontend and backend, ensuring real-time updates when users customize their virtual cars.
3. Random Car Generator: Implement a feature that generates random cars with varying specifications, making the showroom dynamic and interesting.

Vehicles

BMW: i4, i5, i7, and iX Chevrolet: Bolt EV, Bolt EUV, Blazer EV, Equinox EV, Silverado EV Tesla: Cybertruck, , Model S, Model 3, Model X, Model Y, and Roadster Lucid: Air, Air Sapphire, and Gravity

Frontend Wireframe This will be updated throughout the duration of the project to assist our frontend developer complete the task accurately

[rohinsood]

Things Done Well:

• Clear Project Scope: The overview provides a concise and clear description of the mini-project, focusing on building a virtual car website with both frontend and backend components.
• Backend Implementation: Adequate consideration for the backend, including deployment procedures, image database usage, car classes with inheritance, and a simple database for storing car information.
• Frontend Planning: Thoughtful planning for the frontend, emphasizing an attractive display, efficient use of layouts, and integration of API endpoints for real-time updates.
• Company-Specific Information: Specific details for each car brand, including the vehicles offered, add depth to the project, enhancing user experience.

Areas for Improvement:

• Clarification on Sorting Algorithm: The mention of implementing a sorting algorithm is vague. Specify the type of sorting algorithm (e.g., quicksort, mergesort) and clarify its purpose (sorting by type, brand, or price).
• Wireframe Details: The frontend wireframe section could be enhanced by providing more specific details or examples, ensuring better guidance for the frontend developer.
• Communication Protocol: Specify whether AJAX or Fetch API will be used for communication between the frontend and backend, ensuring consistency and clarity in the development process.

Score: 0.93/1

[jm1021]

There needs to be more focus on sorting and abstraction in the project

[AniCricKet]

Sorting and Abstraction Revisions (Input from Mort and ChatGPT):

Backend:

3. Car Classes:

   • Enhance the abstraction by introducing an abstract class or interface for Car and then derive specific car types (sedans, SUVs, sports cars) from it. This can promote code reusability and maintainability.

4. Sorting Algorithm:

   • Implement a flexible sorting service that allows dynamic sorting based on user preferences. Allow users to choose and combine sorting criteria such as brand, type, and price.

   public interface CarSortService {
      List<Car> sortCars(List<Car> cars, SortCriteria criteria);
   }

   • Create an enum for SortCriteria to represent various sorting options.

Frontend:

3. Tables for Each Company:

   • Abstract the rendering of car details by creating a reusable component that takes a Car object as input. This way, you can easily extend it for different car types.

   // CarDetailsComponent.jsx
   const CarDetailsComponent = ({ car }) => {
      // Render car details based on the car object
   }

Integration:

2. Communication:

   • Abstract the communication with the backend by creating a service or utility for handling API requests. This can encapsulate the details of API calls and responses.

   // ApiClient.js
   class ApiClient {
      static async fetchCars() {
          // Handle the API call to retrieve cars
      }
   
      // Other API methods...
   }

Additional Considerations:

• Implement a generic search and filter functionality that allows users to search for cars based on various criteria (e.g., brand, type) on the frontend.

• Utilize dependency injection in the backend for services such as sorting and database access to make the components loosely coupled.

• Explore design patterns like Strategy Pattern for sorting to make it more extensible.

• Consider incorporating a frontend state management library (e.g., Redux for React) to manage the state of sorting preferences and other user interactions.

These modifications should enhance the focus on sorting and abstraction in your project, making the codebase more modular and adaptable to changes.

[Krishiv111]

Success Points

• Great Ideation and collaboration display
• great frontend model and display
• good frontend planning and implementation of cars and models
• good plan for backend

Feedback

• Need to have a clear sorting and iteration abstraction
• more emphasis on how backend will work to be linked to be frontend. Score: 0.93/1