docs: add subject and audit files

subjects/java/Buy01/README.md

@@ -0,0 +1,86 @@
+## Microservices with Angular
+
+### Objectives
+
+Develop an end-to-end e-commerce platform with Spring Boot microservices and Angular. The platform should support user registration (either as a client or seller), authentication, product CRUD functionality exclusively for sellers, and media management for product images.
+
+### Instructions
+
+#### 1. Microservices Setup
+
+- Set up your microservice architecture. Consider **Spring Cloud Eureka** for service discovery and **Docker** for containerization.
+
+#### 2. Enhanced Database Design
+
+```mermaid
+classDiagram
+    User "1" -- "n" Product : Sells
+    Product "1" -- "n" Media : Contains
+    User : +String id
+    User : +String name
+    User : +String email
+    User : +String password
+    User : +String role (client/seller)
+    User : +String avatar
+    Product : +String id
+    Product : +String name
+    Product : +String description
+    Product : +Double price
+    Product : +Int quantity
+    Product : +String userId
+    Media : +String id
+    Media : +String imagePath
+    Media : +String productId
+```
+
+#### 3. API Development Enhancement
+
+- **User Microservice**:
+    - Users can register as clients or sellers, with sellers having the option to upload an avatar.
+    - Authentication and profile management functions should be available.
+
+- **Product Microservice**:
+    - CRUD operations for products, with only authenticated sellers being able to create/update/delete their products.
+    - Products should support an associated list of images.
+
+- **Media Microservice**:
+    - Handle media uploads with a size limit of 2MB.
+    - Ensure only legitimate image files are uploaded.
+
+#### 4. Front-end Development with Angular
+
+- **Sign-In/Up Pages**: Implement authentication views. Sellers should have the option to upload/update their avatar.
+- **Seller Product Management**: A dashboard where sellers can manage their products, including uploading images.
+- **Product Listing**: A simple view to display all products without filtering or search capabilities.
+- **Media Management**: A dedicated view for sellers to manage and upload media specifically for their products. Ensure appropriate file size and type validation.
+
+#### 5. Authentication & Authorization
+
+- Implement role-based authentication.
+- Use **Spring Security** with **JWT** or **OAuth2** to distinguish between clients and sellers, ensuring only sellers can manage products and their associated media.
+
+#### 6. Error Handling and Validation
+
+- Provide feedback for incorrect file types or when exceeding the upload size limit.
+- Handle cases like a client trying to add a product or a seller trying to modify another seller's product.
+- Provide validation for all forms in the application.
+
+#### 7. Security Measures
+
+- **HTTPS Encryption**: Always use HTTPS to encrypt data in transit. Consider tools like **Let's Encrypt** for free SSL certificates.
+- **Sensitive Information Protection**: Protect sensitive user information. Passwords and other details should never be exposed in API responses.
+- **Password Security**: Use **Spring Security** to hash and salt passwords before saving them in the MongoDB database.
+- **Access Control**: Ensure only the seller who created a product can modify or delete it and manage its media.
+
+### Testing
+
+Emphasize testing:
+- Role-based functionalities.
+- Media upload constraints.
+- Authentication flows.
+- Data integrity for product and media management by sellers.
+
+### Resources
+[Spring Boot Microservices Guide](https://spring.io/guides/tutorials/rest/)
+[Spring Cloud Eureka Service Discovery Client Setup](https://www.baeldung.com/spring-cloud-netflix-eureka)  
+[Let's Encrypt for ssl(HTTPS)](https://letsencrypt.org/getting-started/)

subjects/java/Buy01/audit/README.md

@@ -0,0 +1,53 @@
+#### Initial Setup & Access
+
+##### Download the project and initiate it. Try accessing the web pages and the API endpoints using a web browser and tools like Postman.
+
+###### Does the application run seamlessly, and are you able to interact with its functionalities?
+
+#### User & Product CRUD Operations
+
+##### Examine the CRUD operations for Users (both client and seller) and Products.
+
+###### Are CRUD operations for Users and Products correctly implemented, and does each user role have the appropriate access levels?
+
+#### Authentication & Role Validation
+
+##### Sign up as a client and a seller. Afterwards, test functionalities specific to each role.
+
+###### Does the authentication system work, and do the operations respect the user roles (seller vs client)?
+
+#### Media Upload & Product Association
+
+##### As a seller, attempt to upload media for a product and ensure it adheres to the given size and type constraints.
+
+###### Can media be uploaded effectively, and are the constraints enforced? Are products correctly associated with these media?
+
+#### Frontend Interaction
+
+##### Explore the sign-in/up pages, seller product management page, product listing, and media upload page for products.
+
+###### Are all the frontend pages functioning as expected, and is the user experience intuitive?
+
+#### Security
+
+##### Analyze for the specified security measures like hashed passwords, input validation, protection of sensitive data, and HTTPS usage.
+
+###### Are the mentioned security practices appropriately enforced?
+
+#### Code Quality and Standards
+
+##### Evaluate the backend code for appropriate usage of Spring and other related annotations.
+
+###### Are the Spring Boot, MongoDB, and other relevant annotations used correctly throughout the application?
+
+#### Frontend Implementation
+
+##### Investigate the frontend codebase, especially the Angular components, services, and modules.
+
+###### Is the Angular code structured efficiently, and are components, services, and modules effectively utilized?
+
+#### Error Handling & Edge Cases
+
+##### Attempt actions that might cause errors, such as registering with an existing email, uploading invalid media formats, or exceeding the media size limit.
+
+###### Does the application gracefully handle these errors, providing useful feedback to the user?