Meeting Documentation » History » Version 16
Manami SHINYA, 01/16/2025 01:23 PM
| 1 | 14 | Nathanael Muin JUSTIN | > h2. [[Wiki]] | [[Team Members]] | [[Our Project]] | [[User Manual]] | [[Functional & Non-Functional Requirements]] | [[Math Document]] | [[UML Diagrams]] | [[Test Report]] | [[Results]] |
|---|---|---|---|
| 2 | 2 | Nathanael Muin JUSTIN | |
| 3 | |||
| 4 | 1 | Nathanael Muin JUSTIN | h1. Meeting Documentation |
| 5 | 2 | Nathanael Muin JUSTIN | |
| 6 | 10 | Htar Aung THET | *Meeting Structure:* |
| 7 | |||
| 8 | In-Person Meetings: Weekly classroom meetings are held every Thursday on campus. These meetings focus on team progress updates, issue resolutions, and planning for the upcoming tasks. This face-to-face communication promotes effective collaboration and problem-solving. |
||
| 9 | Online Meetings: Out-of-class communication is conducted via LINE, where team members can share resources, collaborate on documents, and stay updated with the latest developments. |
||
| 10 | |||
| 11 | 8 | Nathanael Muin JUSTIN | ==================================================================================================================== |
| 12 | 1 | Nathanael Muin JUSTIN | |
| 13 | 8 | Nathanael Muin JUSTIN | |
| 14 | 2 | Nathanael Muin JUSTIN | h2. *Week 12* |
| 15 | |||
| 16 | h3. 1. Decided the roles |
||
| 17 | |||
| 18 | |||
| 19 | h3. 2. Multi-Projector (Issue) |
||
| 20 | |||
| 21 | # *Redmine* |
||
| 22 | # *UML* |
||
| 23 | 1. Math |
||
| 24 | 2. Configuration |
||
| 25 | 3. Template (Draft) design |
||
| 26 | 4. Make Diagram |
||
| 27 | ・review reference |
||
| 28 | 5. Skeleton code |
||
| 29 | # *Wiki* |
||
| 30 | 1. The wiki |
||
| 31 | 2. Meeting Docs (Every week) |
||
| 32 | 3. The member profile |
||
| 33 | 4. Functional and Nonfunctional require |
||
| 34 | 5. Math Docs |
||
| 35 | 6. UML diagram (Explanation) |
||
| 36 | 7. The result |
||
| 37 | 8. User manual |
||
| 38 | 9. Test report |
||
| 39 | # *Doxygen* |
||
| 40 | 1. The websites |
||
| 41 | 2. Comments |
||
| 42 | 3. Build configuration files |
||
| 43 | 4. +Automation |
||
| 44 | # *Code* |
||
| 45 | 1. How to show the image |
||
| 46 | 2. Load the image (jpg, png) |
||
| 47 | 3. Image proper files |
||
| 48 | 4. Alpha manipulation |
||
| 49 | 5. Load config files (.env) |
||
| 50 | 6. Code |
||
| 51 | # *Testing* |
||
| 52 | 1. Test plan |
||
| 53 | 2. Test report |
||
| 54 | |||
| 55 | h3. 3. Until Next Week |
||
| 56 | |||
| 57 | * UML: 1-3 |
||
| 58 | * Wiki: 1-5 |
||
| 59 | * Doxy: 3 |
||
| 60 | * Code: 1-5 |
||
| 61 | * Test: 1 |
||
| 62 | |||
| 63 | h2. Documentation |
||
| 64 | |||
| 65 | 1 | Nathanael Muin JUSTIN | !week12.png! |
| 66 | !week12-2.png! |
||
| 67 | 3 | Nathanael Muin JUSTIN | |
| 68 | 8 | Nathanael Muin JUSTIN | ==================================================================================================================== |
| 69 | 3 | Nathanael Muin JUSTIN | |
| 70 | 8 | Nathanael Muin JUSTIN | |
| 71 | 5 | Nathanael Muin JUSTIN | h2. *Week 13* |
| 72 | |||
| 73 | h3. UML Review and Approval |
||
| 74 | |||
| 75 | * Reviewed the draft UML diagrams in detail. |
||
| 76 | * Discussed variables, operations, and relationships among the classes with all team leaders and the advisor. |
||
| 77 | * Incorporated feedback and secured final approval for the UML diagrams. |
||
| 78 | |||
| 79 | |||
| 80 | h3. Skeleton Code Development |
||
| 81 | |||
| 82 | * The UML team developed the skeleton code based on the approved UML diagrams. |
||
| 83 | * Prepared the base structure of the project, enabling the coding phase to begin. |
||
| 84 | |||
| 85 | h3. Coding Phase Initiated |
||
| 86 | |||
| 87 | * The team officially began the coding phase. |
||
| 88 | * Tasks were assigned to individual members or sub-teams based on the skeleton code structure. |
||
| 89 | |||
| 90 | h3. Image Selection |
||
| 91 | |||
| 92 | * Decided on the type of images to be used in the project (e.g., format, style, or content requirements). |
||
| 93 | 6 | Nathanael Muin JUSTIN | |
| 94 | h2. Documentation |
||
| 95 | |||
| 96 | 1 | Nathanael Muin JUSTIN | !week13-1.png! |
| 97 | !week13-2.png! |
||
| 98 | 8 | Nathanael Muin JUSTIN | |
| 99 | ==================================================================================================================== |
||
| 100 | 15 | Manami SHINYA | |
| 101 | h2. *Week 14* |
||
| 102 | |||
| 103 | h3. Gamma Functionality Implementation |
||
| 104 | |||
| 105 | * Integration: Seamlessly integrate the Gamma module/component into the existing system architecture. |
||
| 106 | * Testing & Validation: Conduct comprehensive unit tests to ensure the Gamma functionality operates as intended. |
||
| 107 | * Documentation: Provide clear documentation for the Gamma feature, including usage instructions and practical examples. |
||
| 108 | * Configuration Updates: Revise related configurations or dependencies to support the Gamma module. |
||
| 109 | |||
| 110 | h3. Testing |
||
| 111 | |||
| 112 | * Schedule and conduct functionality testing to verify how the Gamma feature performs. |
||
| 113 | * Ensure thorough testing procedures are followed to identify and resolve potential issues. |
||
| 114 | |||
| 115 | h3. Timeline |
||
| 116 | |||
| 117 | * The deadline for completing the Gama functionality is set for next week. |
||
| 118 | |||
| 119 | h3. Wiki Updates |
||
| 120 | |||
| 121 | * Publish the test results and report on the project Wiki for reference and transparency. |
||
| 122 | |||
| 123 | h3. Class Diagram Update |
||
| 124 | |||
| 125 | * Add a new class or component to represent the Gamma function. |
||
| 126 | * Modify existing class relationships, attributes, and methods to integrate the Gamma functionality. |
||
| 127 | * Refine the class diagram based on recent feedback and ensure seamless interaction between the new Gamma module and existing components. |
||
| 128 | |||
| 129 | h2. Documentation |
||
| 130 | |||
| 131 | 16 | Manami SHINYA | !week14-1.png! |
| 132 | !week14-2.png! |
||
| 133 | !week14-3.png! |
||
| 134 | |||
| 135 | 15 | Manami SHINYA | ==================================================================================================================== |