G21-2024

> h2. [[Wiki]] | [[Team Members]] | [[Our Project]] | [[User Manual]] | [[Functional & Non-Functional Requirements]] | [[Math Document]] | [[UML Diagrams]] | [[Test Report]] | [[Results]]

h1. Meeting Documentation

*Meeting Structure:* 

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.

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.

====================================================================================================================

h2. *Week 12*

h3. 1. Decided the roles

h3. 2. Multi-Projector (Issue)

# *Redmine*

# *UML*

1. Math

2. Configuration

3. Template (Draft) design

4. Make Diagram

        ・review reference

5. Skeleton code

# *Wiki*

1. The wiki

2. Meeting Docs (Every week)

3. The member profile

4. Functional and Nonfunctional require

5. Math Docs

6. UML diagram (Explanation)

7. The result

8. User manual

9. Test report

# *Doxygen*

1. The websites

2. Comments

3. Build configuration files

4. +Automation

# *Code*

1. How to show the image

2. Load the image (jpg, png)

3. Image proper files

4. Alpha manipulation

5. Load config files (.env)

6. Code

# *Testing*

1. Test plan

2. Test report

h3. 3. Until Next Week

* UML: 1-3

* Wiki: 1-5

* Doxy: 3

* Code: 1-5

* Test: 1

h2. Documentation

!week12.png!

!week12-2.png!

====================================================================================================================

h2. *Week 13*

h3. UML Review and Approval

* Reviewed the draft UML diagrams in detail.

* Discussed variables, operations, and relationships among the classes with all team leaders and the advisor.

* Incorporated feedback and secured final approval for the UML diagrams.

h3. Skeleton Code Development

* The UML team developed the skeleton code based on the approved UML diagrams.

* Prepared the base structure of the project, enabling the coding phase to begin.

h3. Coding Phase Initiated

* The team officially began the coding phase.

* Tasks were assigned to individual members or sub-teams based on the skeleton code structure.

h3. Image Selection

* Decided on the type of images to be used in the project (e.g., format, style, or content requirements). 

h2. Documentation

!week13-1.png!

!week13-2.png!

====================================================================================================================

h2. *Week 14*

h3. Gamma Functionality Implementation

* Integration: Seamlessly integrate the Gamma module/component into the existing system architecture.

* Testing & Validation: Conduct comprehensive unit tests to ensure the Gamma functionality operates as intended.

* Documentation: Provide clear documentation for the Gamma feature, including usage instructions and practical examples.

* Configuration Updates: Revise related configurations or dependencies to support the Gamma module.

h3. Testing

* Schedule and conduct functionality testing to verify how the Gamma feature performs.

* Ensure thorough testing procedures are followed to identify and resolve potential issues.

h3. Timeline

* The deadline for completing the Gama functionality is set for next week.

h3. Wiki Updates

* Publish the test results and report on the project Wiki for reference and transparency.

h3. Class Diagram Update

* Add a new class or component to represent the Gamma function.

* Modify existing class relationships, attributes, and methods to integrate the Gamma functionality.

* Refine the class diagram based on recent feedback and ensure seamless interaction between the new Gamma module and existing components.

h2. Documentation

!week14-1.png!

!week14-2.png!

!week14-3.png!

====================================================================================================================

h2. Week15

h3. 1. Final Testing

h3. 2. Last-Minute Fixes

h3. 3. Professor Review Preparation

h3. 4. Documentation

* Final check of project documentation

* Ensure README is up to date