{"_id":"6693c4941c11a258c8906e5d","userId":"6397fe5fbfe53e713a1c10d8","title":"GFTA - Education Platform An Ideation","desc":"## 1. Overview GFTA-EP\nDi era transformasi digital dan AI, proses pembelajaran modern harus didukung oleh **ekosistem layanan IT** yang mempercepat pengalaman belajar siswa dan memberikan kesempatan untuk mengembangkan diri dengan berbagai kompetensi yang diinginkan. GFTA (GFT Academy) merencanakan pengembangan suatu platform edukasi yang memberikan fasilitas layanan utama personal learning experience tercatat dalam aplikasi utama eportofolio. Dengan tema \"**pembelajaran sepanjang hayat**\" maka layanan ini diupayakan dapat digunakan oleh siapa saja yang ingin mempunyai digital learning. Porfolio sebagai home app akan diintegrasikan dengan berbagai layanan edukasi dan terintegrasi dengan aplikasi berbasis edukasi lainnya seperti, LMS (Learning Management System), Micro Credential, bahkan memungkinkan untuk diintegrasikan dengan platform lainnya seperti keuangan maupun ecommerce.\n\nPengembangan dilakukan bertahap dengan konsep MVP (Minimum Viable Product) yang diterapkan pada refactoring 1 dari beberapa aplikasi yang telah ada antara lain:\n1. Portfolio https://portfolio.gft.academy/\n2. Project Management https://cpm.lambdasolusi.co.id/\n3. Teaching Factory Management System\n\nTarget yang diberikan pada refactoring 1 antara lain:\n1. Integrasi MVP dari ketiga aplikasi tersebut pada suatu platform SAAS (Software As A Service) sebagai layanan multi platform dan multi tenance\n2. Mempersiapkan Cluster Infrastruktur sebagai GFTA Education Platform yang dapat memberikan layanan skalabilitas secara horizontal\n3. Mempertimbangkan kapabilitas sistem enterprise yang dikembangkan sebagai layanan edukasi berbasis platform.\n4. Teknologi yang digunakan adalah Collaborative Content Workspaces.\n\nDari ketiga aplikasi ini diatur untuk menjadi ekosistem baru sebagai education platform berbasis layanan IT modern yang dikembangkan dengan konsep Multi Platform Multi Tenant. Dan sangat memungkinkan untuk ditambahkan dengan tren-tren perkembangan dunia edukasi seperti Micro Credential yang mensupport ekosistem ini.\n\n## 2. Context System GFTA-EP\n>GFTA Education Platform (GFTA-EP) adalah Ekosistem aplikasi IT pada konteks edukasi (terutama higher education) yang fokus pada porfolio pengalaman pembelajaran siswa berbasis pada kolaborasi. Suatu platform yang dikembangkan dengan arsitektur Multi Tenant pada layanan sistem multi platform SAAS (Software As A Service).\n\n```mermaid\ngraph TD\n A[Universitas] -->|Mengakses| B[Mahasiswa]\n A -->|Mengatur kelas| C[Dosen]\n A -->|Melihat kemajuan anak| D[Orang Tua]\n\n B -->|Belajar| E[Modul Pembelajaran Kredensial]\n C -->|Melacak & Menilai| E\n D -->|Memantau| E\n\n E -->|Video Pembelajaran| F1[Video Pembelajaran]\n E -->|Latihan Interaktif| F2[Latihan Interaktif]\n E -->|Artikel dan Bacaan| F3[Artikel dan Bacaan]\n E -->|Rekomendasi AI| F4[AI Rekomendasi]\n E -->|API Integrasi| F5[API Integrasi]\n\n F1 -->|Menyediakan Konten| G[Analitik]\n F2 -->|Menyediakan Latihan| G\n F3 -->|Menyediakan Artikel| G\n F4 -->|Memberikan Rekomendasi| G\n F5 -->|Menghubungkan Sistem| G\n\n G -->|Menghasilkan Laporan| H1[Dashboard Siswa]\n G -->|Memberikan Wawasan| H2[Dashboard Dosen]\n G -->|Memberikan Informasi| H3[Dashboard Orang Tua]\n\n G -->|Menyimpan Data| I1[DB Mahasiswa]\n G -->|Menyimpan Data| I2[DB Dosen]\n G -->|Menyimpan Data| I3[DB Orang Tua]\n G -->|Menyimpan Data| I4[DB Konten]\n\n subgraph Infrastruktur Teknologi\n I1\n I2\n I3\n I4\n J[Server Backend]\n K[Frontend Interface]\n end\n\n I1 --> J\n I2 --> J\n I3 --> J\n I4 --> J\n J --> K\n\n subgraph Alat Analitik\n H1\n H2\n H3\n end\n\n subgraph Modul Pembelajaran\n F1\n F2\n F3\n F4\n F5\n end\n```\nPada context system di atas kapabilitas utama terletak pada ***Modul Pembelajaran Kredensial*** dan ***Modul Analitik***. Dengan 3 aktor utama yaitu Universitas, Mahasiswa, Dosen, dan Orang tua. Universitas mengelola pembelajaran kredensial dan sekaligus memberikan analisis kemajuan pembelajaran mahasiswa berdasarkan porfolio akademik selama kuliah. Mahasiswa dapat mengakses pembelajaran secara mandiri dan Orang tua dapat memantau perkembangan kemajuan pembelajaran mahasiswa.\n\nPengembangan desain selanjutnya adalah Kapabilitas porfolio mahasiswa dan pembelajaran kredensial diintegrasikan pada desain sistem berbasis Microservice. Modul Porfolio merupakan layanan bagi mahasiswa untuk mengekspose pembelajaranya dengan membuat post, artikel, aktivitas, project, dan badge. 2 Modul services yaitu **Analytics Services** dan **Porfolio Services** dibuat independent pada desain untuk memungkinkan berinteraksi dengan API external (data-data akademik formal dari sistem resmi di Universitas). Untuk Frontend didesain dengan multi platform baik layanan web maupun mobile.\n\n```mermaid\ngraph TD\n subgraph Frontend\n A1[Web Application]\n A2[Mobile Application]\n end\n\n subgraph Microservices\n B1[Authentication Service]\n B2[User Profile Service]\n C1[Content Delivery Service]\n C2[Exercise Service]\n C3[Article Service]\n C4[AI Recommendation Service]\n D1[Analytics Service]\n E1[Portfolio Service]\n end\n\n subgraph Databases\n G1[User DB]\n G2[Content DB]\n G3[Exercise DB]\n G4[Article DB]\n G5[Portfolio DB]\n G6[Analytics DB]\n end\n\n A1 -->|Uses| B1\n A2 -->|Uses| B1\n B1 --> B2\n\n A1 -->|Accesses| C1\n A2 -->|Accesses| C1\n\n C1 --> C2\n C1 --> C3\n C1 --> C4\n C4 -->|Integrates with| H1[External APIs]\n\n B2 --> G1\n C1 --> G2\n C2 --> G3\n C3 --> G4\n E1 --> G5\n D1 --> G6\n\n B2 --> D1\n C1 --> D1\n C2 --> D1\n C3 --> D1\n E1 --> D1\n\n subgraph Portfolio Services\n E1\n end\n\n subgraph Analytics Services\n D1\n end\n```\nContent Delivery Service pada platform edukasi dapat diturunkan menjadi Course Management Service sebagai contoh MOOC atau pun pembelajaran independent, Microcredential.\n\nUntuk referensi Kolaborasi sistem antara UDEMY + GFT ACADEMY + CLICKUP ditunjukkan pada Gambar di bawah ini. Kapabilitas dari context system terletak pada Course Management Service, Authentication Service, Portfolio Service, dan Project Management Service. AI Service pada gambar sebaiknya dipisahkan sebagai support (enabler) dari context system - education platform. Mengacu pada konsep FullStack maka Frontend dapat ditambahkan Student Panel dan Admin Panel.\n\n\n```mermaid\ngraph TD\n style A1 fill:#f9f,stroke:#333,stroke-width:2px;\n style A2 fill:#f9f,stroke:#333,stroke-width:2px;\n style B1 fill:#ff9,stroke:#333,stroke-width:2px;\n style B2 fill:#ff9,stroke:#333,stroke-width:2px;\n style C1 fill:#9f9,stroke:#333,stroke-width:2px;\n style C2 fill:#9f9,stroke:#333,stroke-width:2px;\n style C3 fill:#9f9,stroke:#333,stroke-width:2px;\n style C4 fill:#9f9,stroke:#333,stroke-width:2px;\n style C5 fill:#9f9,stroke:#333,stroke-width:2px;\n style C6 fill:#9f9,stroke:#333,stroke-width:2px;\n style E1 fill:#99f,stroke:#333,stroke-width:2px;\n style E2 fill:#99f,stroke:#333,stroke-width:2px;\n style E3 fill:#99f,stroke:#333,stroke-width:2px;\n style D1 fill:#f99,stroke:#333,stroke-width:2px;\n style D2 fill:#f99,stroke:#333,stroke-width:2px;\n style D3 fill:#f99,stroke:#333,stroke-width:2px;\n style P1 fill:#ffb6c1,stroke:#333,stroke-width:2px;\n style P2 fill:#ffb6c1,stroke:#333,stroke-width:2px;\n style P3 fill:#ffb6c1,stroke:#333,stroke-width:2px;\n style G1 fill:#ccf,stroke:#333,stroke-width:2px;\n style G2 fill:#ccf,stroke:#333,stroke-width:2px;\n style G3 fill:#ccf,stroke:#333,stroke-width:2px;\n style G4 fill:#ccf,stroke:#333,stroke-width:2px;\n style G5 fill:#ccf,stroke:#333,stroke-width:2px;\n style G6 fill:#ccf,stroke:#333,stroke-width:2px;\n style G7 fill:#ccf,stroke:#333,stroke-width:2px;\n style G8 fill:#ccf,stroke:#333,stroke-width:2px;\n style G9 fill:#ccf,stroke:#333,stroke-width:2px;\n style A3 fill:#f4a460,stroke:#333,stroke-width:2px;\n style A4 fill:#f4a460,stroke:#333,stroke-width:2px;\n\n subgraph Frontend\n A1[Web Application]\n A2[Mobile Application]\n A3[Student Panel]\n A4[Admin Panel]\n end\n\n B1[Authentication Service]\n B2[User Profile Service]\n C1[Course Management Service]\n C2[Lesson Management Service]\n C3[Instructor Management Service]\n C4[AI Recommendation Service]\n C5[Quiz and Assignment Service]\n C6[Certification Service]\n E1[Portfolio Service]\n E2[Portfolio Management Service]\n E3[Portfolio Presentation Service]\n D1[Analytics Service]\n D2[Learning Analytics Service]\n D3[Portfolio Analytics Service]\n P1[Project Management Service]\n P2[Task Management Service]\n P3[Collaboration Service]\n\n subgraph Databases\n G1[User DB]\n G2[Course DB]\n G3[Lesson DB]\n G4[Instructor DB]\n G5[Quiz DB]\n G6[Certification DB]\n G7[Portfolio DB]\n G8[Analytics DB]\n G9[Project DB]\n end\n\n A1 -->|Uses| B1\n A2 -->|Uses| B1\n A3 -->|Uses| B1\n A4 -->|Uses| B1\n B1 --> B2\n\n A1 -->|Accesses| C1\n A2 -->|Accesses| C1\n A3 -->|Accesses| C1\n A4 -->|Accesses| C1\n\n C1 --> C2\n C1 --> C3\n C1 --> C4\n C1 --> C5\n C1 --> C6\n C4 -->|Integrates with| H1[External APIs]\n\n B2 --> G1\n C1 --> G2\n C2 --> G3\n C3 --> G4\n C5 --> G5\n C6 --> G6\n\n B2 --> D1\n C1 --> D2\n C2 --> D2\n C3 --> D2\n C5 --> D2\n C6 --> D2\n\n E1 -->|Accesses| G7\n E1 --> E2\n E1 --> E3\n \n E2 --> D3\n E3 --> D3\n \n D3 -->|Accesses| G8\n\n P1 -->|Accesses| G9\n P1 --> P2\n P1 --> P3\n P2 --> D1\n P3 --> D1\n\n subgraph Backend\n B1\n B2\n C1\n C2\n C3\n C4\n C5\n C6\n E1\n E2\n E3\n D1\n D2\n D3\n P1\n P2\n P3\n end\n\n subgraph Databases\n G1\n G2\n G3\n G4\n G5\n G6\n G7\n G8\n G9\n end\n```\n## 3. Container Level\nEducation platform sebagai suatu ekosistem layanan IT yang berskala enterprise memerlukan desain pada beberapa level arsitektur baik software, data, maupun teknologi yang akan digunakan. Pertimbangan EA (Enterprise Architecture) menjadi pilihan utama untuk ekosistem ini. Kapabilitas sistem yang skalable, fleksible, fault tolerant, dan reliable digunakan sebagai pertimbangan utama dalam menentukan spesifikasi GFTA-EP.\n\nSpesifikasi Deskripsi GFTA Education PLatform :\n| Deskripsi | Spesifikasi |\n| --- | --- |\n| Teknologi | Collaborative Content Workspaces |c\n| Cluster PE | GFTA Cluster dengan minimum requirement|\n| Tipe Aplikasi | Multi Platform - Multi Tenant |\n| Arsitektur software | Wajib Microservices |\n| Referensi Apps : | ClickuP.com, Confluence by Attlasian http://office.gft.academy |\n\nSalah satu arsitektur yang diinginkan adalah multi platform seamless user experience dengan mengharuskan mobile development sebagai bagian dari ekosistem. Dengan demikian desain container yang digunakan harus mempertimbangkan kebutuhan native multi platform dengan konsep full stack.\n\nKonsep desain arsitektur Microservice sangat mempengaruhi pengelolaan komputasi pada infrastruktur virtualisasi (container level).\n## 4. Component Level\nPada component level bagian yang terpenting adalah framework teknis terutama Fullstack dengan pemisahan komponen-komponen Front End dan Back End. Untuk Back end menerapkan API spesification pada kapabilitas yang terdiri dari komponen microservice.\n### 4.1 Course Management Service API Specification\n\n

\n \n

\n\n

\n \n\n\n**Base URL:** `/api/courses`\n\n#### Course Management Endpoints\n\n| Method | Endpoint | Description | Request Parameters | Request Body | Response |\n|---|---|---|---|---|---|\n| GET | / | Get a list of all courses | `page`, `limit` | | 200 OK, array of course objects |\n| GET | /{course_id} | Get details of a specific course | | | 200 OK, course object |\n| POST | / | Create a new course | | Course JSON object | 201 Created, course object |\n| PUT | /{course_id} | Update details of a specific course | | Updated course JSON object | 200 OK, updated course object |\n| DELETE | /{course_id} | Delete a specific course | | | 204 No Content |\n\n#### Lesson Management Endpoints\n\n| Method | Endpoint | Description | Request Parameters | Request Body | Response |\n|--------|---------------------------------|-----------------------------------------------|------------------------------------|-------------------------------|------------------------------------|\n| GET | /{course_id}/lessons | Get a list of lessons in a specific course | `page`, `limit` | | 200 OK, array of lesson objects |\n| GET | /{course_id}/lessons/{lesson_id}| Get details of a specific lesson | | | 200 OK, lesson object |\n| POST | /{course_id}/lessons | Add a lesson to a specific course | | Lesson JSON object | 201 Created, lesson object |\n| PUT | /{course_id}/lessons/{lesson_id}| Update details of a specific lesson | | Updated lesson JSON object | 200 OK, updated lesson object |\n| DELETE | /{course_id}/lessons/{lesson_id}| Delete a specific lesson from a course | | | 204 No Content |\n\n\n### Request Drivent\nInteraksi antar service umumnya menggunakan request driven yang berarti memerlukan response secara sinkron. Dengan mempertimbangkan fault tolerant yang cukup tinggi dan terjadi ketergantungan antar service jika menggunakan pattern ini, maka perlu pertimbangan lain untuk skalabilitas dan independensi dari setiap service yang ada pada sistem. Request driven lebih mudah untuk digunakan memahami bagaimana suatu sistem berinteraksi. Komunikasi antar service melibatkan state yang perlu dipertimbangkan. Kombinasi stateless dan statefull merupakan pilihan yang tepat untuk menentukan raliabilitas dari kinerja sistem.\n\n```mermaid\nsequenceDiagram\n participant User\n participant EnrollmentService\n participant CourseService\n participant NotificationService\n participant ProgressService\n\n User->>EnrollmentService: POST /enrollments (course_id, user_id)\n EnrollmentService->>CourseService: GET /courses/{course_id} (check availability)\n CourseService-->>EnrollmentService: 200 OK (course available)\n EnrollmentService-->>User: 200 OK (enrollment successful)\n EnrollmentService->>NotificationService: POST /notifications (enrollment confirmation)\n NotificationService-->>User: 200 OK (notification sent)\n User->>ProgressService: GET /progress/{user_id}\n ProgressService-->>User: 200 OK (progress details)\n\n```\n### Event Drivent - Kafka\nProses interaksi bersifat Asinkron dimana memerlukan broker messanger seperti rabitMQ atau kafka, sekaligus sebagai streaming producer dan konsumer pattern. Pertimbangkan skalabilitas dan latensi dari konsumsi waktu komputasi. Event driven mengurangi coupling yang terjadi pada request driven.\n```mermaid\ngraph TD\n A[User] -->|POST /enrollments| B[Enrollment Service]\n B -->|Publish enrollment_requested event| C((Kafka Topic: enrollment_events))\n C -->|Consume enrollment_requested event| D[Course Service]\n D -->|Check course availability| D\n D -->|Publish course_available event| E((Kafka Topic: course_events))\n E -->|Consume course_available event| B[Enrollment Service]\n B -->|Update enrollment status| B\n B -->|Publish enrollment_successful event| F((Kafka Topic: enrollment_success_events))\n F -->|Consume enrollment_successful event| G[Notification Service]\n F -->|Consume enrollment_successful event| H[Progress Service]\n G -->|Send confirmation to user| A\n H -->|Update progress| A\n\n```\n\n### Database Schema and Example Data\n\n```mermaid\nerDiagram\n COURSE {\n string id PK\n string title\n string description\n string instructor\n }\n\n CHAPTER {\n string id PK\n string course_id FK\n string title\n }\n\n LESSON {\n string id PK\n string chapter_id FK\n string title\n string type\n string content\n }\n\n RESOURCE {\n string id PK\n string lesson_id FK\n string type\n string title\n string url\n }\n\n USER {\n string id PK\n string name\n string email\n string password\n }\n\n ENROLLMENT {\n string id PK\n string user_id FK\n string course_id FK\n date enrollment_date\n }\n\n LEARNINGTRACK {\n string id PK\n string user_id FK\n string lesson_id FK\n string status\n date start_date\n date end_date\n }\n\n COURSE ||--o{ CHAPTER: contains\n CHAPTER ||--o{ LESSON: contains\n LESSON ||--o{ RESOURCE: contains\n USER ||--o{ ENROLLMENT: enrolled_in\n ENROLLMENT }o--|| COURSE: enrolls_in\n USER ||--o{ LEARNINGTRACK: tracks\n LEARNINGTRACK }o--|| LESSON: tracks\n\n```\n#### Course JSON Object\n\n```json\n{\n \"id\": \"course-12345\",\n \"title\": \"Introduction to Programming\",\n \"description\": \"A beginner's course on programming concepts and practices.\",\n \"instructor_id\": \"instructor-67890\",\n \"created_at\": \"2023-01-15T08:00:00Z\",\n \"updated_at\": \"2023-06-20T08:00:00Z\",\n \"popularity\": 98\n}\n\n{\n \"id\": \"chapter-54321\",\n \"course_id\": \"course-12345\",\n \"title\": \"Getting Started with Python\",\n \"description\": \"An introduction to Python programming language.\",\n \"created_at\": \"2023-01-16T08:00:00Z\",\n \"updated_at\": \"2023-06-21T08:00:00Z\"\n}\n\n{\n \"id\": \"lesson-67890\",\n \"chapter_id\": \"chapter-54321\",\n \"title\": \"Python Basics\",\n \"content\": \"This lesson covers the basic syntax and constructs of Python.\",\n \"created_at\": \"2023-01-17T08:00:00Z\",\n \"updated_at\": \"2023-06-22T08:00:00Z\"\n}\n\n```\n\n#### Student Enrollment JSON Object\n\n```json\n{\n \"id\": \"user_001\",\n \"name\": \"Alice Smith\",\n \"email\": \"alice@example.com\",\n \"password\": \"hashed_password\"\n}\n\n{\n \"id\": \"enroll_001\",\n \"user_id\": \"user_001\",\n \"course_id\": \"course_001\",\n \"enrollment_date\": \"2024-01-01T08:00:00Z\"\n}\n\n{\n \"id\": \"track_001\",\n \"user_id\": \"user_001\",\n \"lesson_id\": \"lesson_001\",\n \"status\": \"completed\",\n \"start_date\": \"2024-01-02T08:00:00Z\",\n \"end_date\": \"2024-01-03T08:00:00Z\"\n}\n\n```\n### 4.2 Project Management Services\nModul project management service back end seperti ditunjukkan pada Gambar :\n\n\n```mermaid\ngraph TD\n style A fill:#f9f,stroke:#333,stroke-width:2px\n style B fill:#bbf,stroke:#333,stroke-width:2px\n style C fill:#f99,stroke:#333,stroke-width:2px\n style D fill:#9f9,stroke:#333,stroke-width:2px\n style E fill:#ff9,stroke:#333,stroke-width:2px\n style F fill:#9ff,stroke:#333,stroke-width:2px\n style G fill:#cff,stroke:#333,stroke-width:2px\n\n A[Project Service] <--> B[Task Service]\n B <--> C[Comment Service]\n D[User Service] <--> A\n D <--> B\n A <--> E[Message Queue RabbitMQ, Kafka]\n B <--> E\n C <--> E\n F[Notification Service] <--> E\n D <--> F\n G[Progress Service] <--> A\n G <--> B\n\n subgraph Core Services\n A\n B\n C\n G\n end\n\n subgraph Messaging\n E\n end\n\n```\n\n\n**Base URL:** `\t/projects`\n\n#### Project Management Endpoints\n\n### Project Management Service API Specification\n\n| Method | Endpoint | Description | Request Body | Response |\n|--------|---------------------------|--------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------|\n| POST | /projects | Create a new project | `{ \"name\": \"Project Name\", \"description\": \"Project Description\", \"start_date\": \"2024-01-01\", \"end_date\": \"2024-12-31\" }` | `201 Created` - `{ \"id\": \"project_id\", \"name\": \"Project Name\", \"description\": \"Project Description\", \"start_date\": \"2024-01-01\", \"end_date\": \"2024-12-31\" }` |\n| GET | /projects | Get a list of all projects | N/A | `200 OK` - `[ { \"id\": \"project_id\", \"name\": \"Project Name\", \"description\": \"Project Description\", \"start_date\": \"2024-01-01\", \"end_date\": \"2024-12-31\" }, ... ]` |\n| GET | /projects/{project_id} | Get details of a specific project | N/A | `200 OK` - `{ \"id\": \"project_id\", \"name\": \"Project Name\", \"description\": \"Project Description\", \"start_date\": \"2024-01-01\", \"end_date\": \"2024-12-31\" }` |\n| PUT | /projects/{project_id} | Update a specific project | `{ \"name\": \"Updated Project Name\", \"description\": \"Updated Description\", \"start_date\": \"2024-01-01\", \"end_date\": \"2024-12-31\" }` | `200 OK` - `{ \"id\": \"project_id\", \"name\": \"Updated Project Name\", \"description\": \"Updated Description\", \"start_date\": \"2024-01-01\", \"end_date\": \"2024-12-31\" }` |\n| DELETE | /projects/{project_id} | Delete a specific project | N/A | `204 No Content` |\n| POST | /projects/{project_id}/tasks | Create a new task within a project | `{ \"name\": \"Task Name\", \"description\": \"Task Description\", \"assigned_to\": \"user_id\", \"status\": \"not_started/in_progress/completed\", \"due_date\": \"2024-02-01\" }` | `201 Created` - `{ \"id\": \"task_id\", \"name\": \"Task Name\", \"description\": \"Task Description\", \"assigned_to\": \"user_id\", \"status\": \"not_started/in_progress/completed\", \"due_date\": \"2024-02-01\" }` |\n| GET | /projects/{project_id}/tasks | Get a list of tasks within a project | N/A | `200 OK` - `[ { \"id\": \"task_id\", \"name\": \"Task Name\", \"description\": \"Task Description\", \"assigned_to\": \"user_id\", \"status\": \"not_started/in_progress/completed\", \"due_date\": \"2024-02-01\" }, ... ]` |\n| GET | /tasks/{task_id} | Get details of a specific task | N/A | `200 OK` - `{ \"id\": \"task_id\", \"name\": \"Task Name\", \"description\": \"Task Description\", \"assigned_to\": \"user_id\", \"status\": \"not_started/in_progress/completed\", \"due_date\": \"2024-02-01\" }` |\n| PUT | /tasks/{task_id} | Update a specific task | `{ \"name\": \"Updated Task Name\", \"description\": \"Updated Description\", \"assigned_to\": \"user_id\", \"status\": \"not_started/in_progress/completed\", \"due_date\": \"2024-02-01\" }` | `200 OK` - `{ \"id\": \"task_id\", \"name\": \"Updated Task Name\", \"description\": \"Updated Description\", \"assigned_to\": \"user_id\", \"status\": \"not_started/in_progress/completed\", \"due_date\": \"2024-02-01\" }` |\n| DELETE | /tasks/{task_id} | Delete a specific task | N/A | `204 No Content` |\n| GET | /projects/{project_id}/progress | Get the progress of a project based on tasks | N/A | `200 OK` - `{ \"project_id\": \"project_id\", \"progress\": \"75%\", \"tasks_completed\": \"3\", \"total_tasks\": \"4\" }` |\n\nPertimbangan independent desain microservice dengan referensi click up:\n\n```mermaid\ngraph TD\n A[API Gateway]\n B[User Service]\n C[Project Service]\n D[Task Service]\n E[Notification Service]\n F[Comment Service]\n G[File Storage Service]\n H[Message Broker]\n\n A --> B\n A --> C\n A --> D\n A --> E\n A --> F\n A --> G\n\n B -->|CRUD Users| B_DB[(PostgreSQL)]\n C -->|CRUD Projects| C_DB[(MongoDB)]\n D -->|CRUD Tasks| D_DB[(MongoDB)]\n F -->|CRUD Comments| F_DB[(MongoDB)]\n E -->|Send Notifications| E_DB[(Redis)]\n G -->|Manage Files| G_FS[(AWS S3/MinIO)]\n\n E --> H\n C --> H\n D --> H\n F --> H\n\n```\n### Skema Database & JSON Data\n\n```mermaid\nerDiagram\n USER {\n int id PK\n string name\n string email\n string password\n }\n \n PROJECT {\n int id PK\n string name\n string description\n int owner_id FK\n }\n \n TASK {\n int id PK\n string title\n string description\n int project_id FK\n int assignee_id FK\n date due_date\n }\n\n COMMENT {\n int id PK\n string content\n int task_id FK\n int author_id FK\n date created_at\n }\n\n NOTIFICATION {\n int id PK\n string message\n int user_id FK\n date sent_at\n }\n\n COLLABORATION {\n int id PK\n int project_id FK\n int user_id FK\n }\n\n USER ||--o{ PROJECT : owns\n PROJECT ||--o{ TASK : contains\n\n```\n### 4.3 Student Portfolio Services\n\n```mermaid\ngraph TD\n B[User Service]\n C[Student Portfolio Service]\n D[Course Management Service]\n E[Project Management Service]\n F[Notification Service]\n G[File Storage Service]\n H[Message Broker]\n\n B -->|CRUD Users| B_DB[(PostgreSQL)]\n C -->|Manage Portfolio| C_DB[(MongoDB)]\n D -->|Manage Courses| D_DB[(MongoDB)]\n E -->|Manage Projects| E_DB[(MongoDB)]\n F -->|Send Notifications| F_DB[(Redis)]\n G -->|Manage Files| G_FS[(AWS S3/MinIO)]\n\n F --> H\n C --> H\n D --> H\n E --> H\n\n subgraph Interaction\n C -- Publish Event --> H\n D -- Publish Event --> H\n E -- Publish Event --> H\n H -- Notify Users --> F\n end\n\n style B fill:#ffcccc,stroke:#333,stroke-width:2px\n style C fill:#ccffcc,stroke:#333,stroke-width:2px\n style D fill:#ccccff,stroke:#333,stroke-width:2px\n style E fill:#ffffcc,stroke:#333,stroke-width:2px\n style F fill:#ccffff,stroke:#333,stroke-width:2px\n style G fill:#ffccff,stroke:#333,stroke-width:2px\n style H fill:#dddddd,stroke:#333,stroke-width:2px\n\n classDef class1 fill:#ffcccc,stroke:#333,stroke-width:2px;\n classDef class2 fill:#ccffcc,stroke:#333,stroke-width:2px;\n classDef class3 fill:#ccccff,stroke:#333,stroke-width:2px;\n classDef class4 fill:#ffffcc,stroke:#333,stroke-width:2px;\n classDef class5 fill:#ccffff,stroke:#333,stroke-width:2px;\n classDef class6 fill:#ffccff,stroke:#333,stroke-width:2px;\n classDef class7 fill:#dddddd,stroke:#333,stroke-width:2px;\n\n```\n### Sequence Diagram\nKomunikasi antar object student dapat mengambil course dan membuat project yang secara langsung dapat dipantau progress pemnbelajaran maupun progress proyek berjalan sebagai update dari portfolionya.\n\n```mermaid\nsequenceDiagram\n participant Student\n participant UserService\n participant CourseService\n participant ProjectService\n participant NotificationService\n participant MessageBroker\n\n Student ->> UserService: Login / Register\n UserService -->> Student: Auth Token\n\n Student ->> Profile: View / Edit Profile\n Profile -->> Student: Profile Information\n\n Student ->> CourseService: View Enrolled Courses\n CourseService -->> Student: List of Courses\n\n Student ->> CourseService: Start / Continue Course\n CourseService -->> Student: Course Content\n\n Student ->> CourseService: Update Course Progress\n CourseService ->> CourseService: Update Progress\n CourseService ->> MessageBroker: Publish Progress Event\n MessageBroker ->> NotificationService: Notify Progress Update\n\n Student ->> ProjectService: View Projects\n ProjectService -->> Student: List of Projects\n\n Student ->> ProjectService: Create / Update Project\n ProjectService ->> ProjectService: Save Project Details\n ProjectService ->> MessageBroker: Publish Project Event\n MessageBroker ->> NotificationService: Notify Project Update\n\n Student ->> ActivityLog: View Activity History\n ActivityLog -->> Student: Activity Details\n\n Student ->> SocialInteraction: Comment / Discuss\n SocialInteraction -->> Student: Interaction Details\n\n Student ->> Settings: Manage Account Settings\n Settings -->> Student: Account Settings\n```\n\n```mermaid\ngraph TD\n A[Identifikasi Kebutuhan] --> B[Pengguna Akhir]\n A --> C[Jenis Konten]\n A --> D[Skalabilitas]\n A --> E[Fitur Utama]\n\n F[Pemilihan Platform CMS] --> G[Open Source vs. Proprietary]\n F --> H[Kemampuan Integrasi]\n F --> I[Dukungan Pengembang]\n\n J[Desain Arsitektur] --> K[Backend]\n J --> L[Frontend]\n J --> M[Keamanan]\n J --> N[API Integration]\n\n O[Pengembangan dan Implementasi] --> P[Tim Pengembang]\n O --> Q[Pembuatan Konten]\n O --> R[Manajemen Media]\n O --> S[Workflow Approval]\n O --> T[Pengujian]\n\n U[Peluncuran dan Pelatihan] --> V[Peluncuran]\n U --> W[Pelatihan]\n U --> X[Dokumentasi]\n\n Y[Pemeliharaan dan Pembaruan] --> Z[Monitoring]\n Y --> AA[Pembaruan]\n Y --> AB[Dukungan Pengguna]\n\n subgraph Content Management Service\n A\n F\n J\n O\n U\n Y\n end\n\n```\n","coverArticle":"https://api-portfolio.gft.academy/storage/images/fileAlbum_1677213161363.jpeg","isPublic":true,"tags":["GFT","micro credential","learning management system","portfolio"],"createdAt":"2024-07-14T12:29:08.377Z","comments":[],"updatedAt":"2024-08-08T08:28:09.438Z","__v":0}