G21-2023

h1=. <pre>

About Us </pre>

---

*[[Wiki]]*   |  *[[About Us]]*  |  *[[Regarding Our Project]]* | 

---

h2. *%{color:black}OUR MEMBERS%*

|\4={background-color: #aaf;}. *OUR MEMBERS*|

|!tomas.JPG!|!pix_yuta.jpg!|!pix_shuto.jpg!|!abhi.png!| 

|??Quote?? - *Tomas Brande Sastre* (Project Manager & Doxy-Issues)|??Quote?? - *Yuta Hirahata* (Project Leader & Programmer)|??Quote?? - *Shuto Tamaoka* (Programmer Supervisor)|??Quote?? - *Oggu Abhiram* (Wiki Supervisor)|

|is0699hi@ed.ritsumei.ac.jp |is0687pe@ed.ritsumei.ac.jp|is0678ke@ed.ritsumei.ac.jp|is0701ex@ed.ritsumei.ac.jp|

|!littlekid.jpeg!|!littlekid.jpeg!|!littlekid.jpeg!|!cellur.jpg!|

|??Quote?? - *Gabriel Evans* (Doxy-Doc Generator)|??Quote?? - *Khoo Zhneyu* (Programmer)|??Quote?? - *Lyu Yuanming* (Programmer)|??Quote??- *Wei Xiaoang* (Commenter & UML Buddy)|

|is0700ih@ed.ritsumei.ac.jp|is0700vx@ed.ritsumei.ac.jp|is0701fv@ed.ritsumei.ac.jp|is0702hv@ed.ritsumei.ac.jp|

|!littlekid.jpeg!|!ayato.png!|!littlekid.jpeg!|!littlekid.jpeg!|

|??Quote?? - 

*Zhang Xinai* (Commentor & UML Buddy)|??Quote?? - *Ayato Kotsugi* (Wiki Buddy)|??Quote?? - *Byeon Seongjoon* (Wiki Buddy)|??Quote??|

|is0702fk@ed.ritsumei.ac.jp|is0668hx@ed.ritsumei.ac.jp|is0645xr@ed.ritsumei.ac.jp |email4|

---

h2. *%{color:black}ROLES AND DUTIES%*

|_. Roles |_. Duties |_. Members|

| *%{color:blue}Project Manager%* | Managing all members' progress and shares information to outer person, if necessary. | Tomas Brande Sastre|

| *%{color:blue}Project Leader%* | Leading other members to success for a project. | Yuta Hirahata|

| *%{color:blue}Doxy-Issues%* |  Assign tasks to each member in Redmine| Tomas Brande Sastre| 

| *%{color:blue}Doxy-document generation%*  | generate documentation in Redmine| Gabriel Evans|

| *%{color:blue}Programmer%*  | Coding for the project. | Yuta Hirahata, Tamaoka Shuto, Khoo Zhenyu, Lyu Yuanming|

| *%{color:blue}Commenter%*  | Commenting on programs or others, if necessary. | Wei Xiaoang, Zhang Xinai |

| *%{color:blue}UML Buddy%* | Creating UML diagrams related to the project. | Wei Xiaoang, Zhang Xinai|

| *%{color:blue}Wiki Buddy%*  | Editing the page called "Wiki" of Redmine. | Oggu Abhiram, Ayato Kotsugi, Byeon Seongjoon|

h2. *%{color:black}TEAM ORGANIZATION%*

eam Organization for "Multi-projector Project" in Prof I. Goncharenko's Lab

Project Overview:

The "Multi-projector Project" involves cutting-edge software development supporting technology. The project is divided into three specialized teams, each playing a crucial role in achieving the overall objectives. The teams work collaboratively, guided by a Project Manager, to ensure seamless integration of their efforts.

Team Roles and Responsibilities:

Team 1: Automatic Source Code Generation from UML Design

Role: Transforming UML designs into executable code.

Key Responsibilities:

Utilize tools and scripts to automate code generation from UML diagrams.

Collaborate closely with the design team to address UML specifications.

Perform rigorous code reviews and testing to ensure quality and functionality.

Team 2: Code Commenting in Doxygen Style and Program Reference Document Generation

Role: Enhancing code readability through effective documentation.

Key Responsibilities:

Implement Doxygen-style comments for clarity and understanding.

Generate comprehensive program reference documents, including API references.

Collaborate with Team 1 to align documentation with generated code.

Team 3: Software Project Management by Redmine

Role: Overseeing project management using the Redmine platform.

Key Responsibilities:

Utilize Redmine for task tracking, issue management, and project planning.

Assign tasks based on priorities and individual skills.

Generate reports and metrics to assess project progress.

Leadership and Communication:

Project Manager: Guides the overall project, ensuring coordination among sub-teams, and task assignments during weekly meetings.

Leaders (sub-teams): Facilitate communication, task distribution, and serve as liaisons between teams and the Project Manager.

Tools and Technologies:

Specify the tools and technologies used by each team (e.g., programming languages, UML tools, Doxygen, Redmine) to give a more concrete understanding of the technical environment.

Collaboration and Coordination:

Emphasize the collaborative nature of the project by highlighting cross-team interactions, dependencies, and how the teams complement each other.

Meeting Structure:

Provide more details about the structure of weekly classroom meetings and Discord meetings, emphasizing their significance in fostering effective communication and resource sharing.

This alternative presentation style provides a more detailed and specific breakdown of each team's responsibilities and highlights the technological aspects of the project. It also underscores the collaborative nature of the teams and their interaction points.