About Us 

Wiki | About Us | Regarding Our Project | Coding | UML Diagrams | Results |

OUR MEMBERS¶

OUR MEMBERS
Tomas Brande Sastre (Project Manager & Doxy-Issues)	Yuta Hirahata (Project Leader & Programmer)	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
Gabriel Evans (Doxy-Doc Generator)	Khoo Zhenyu (Programmer)	Lyu Yuanming (Programmer)	Zhang Xinai (Commenter & UML Buddy)
is0700ih@ed.ritsumei.ac.jp	is0700vx@ed.ritsumei.ac.jp	is0701fv@ed.ritsumei.ac.jp	is0702fk@ed.ritsumei.ac.jp
Wei Xiaoang (Commentor & UML Buddy)	Ayato Kotsugi (Wiki Buddy)	Byeon Seongjoon (Wiki Buddy)	Professor Igor Goncheranko
is0702hv@ed.ritsumei.ac.jp	is0668hx@ed.ritsumei.ac.jp	is0645xr@ed.ritsumei.ac.jp

TEAM ORGANIZATION¶

Overview

Our team 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 and Leader, 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.

• Project Manager: Guides the overall project, ensuring coordination among sub-teams, and task assignments during weekly meetings.
• Project Leader: Leads the discussions and ensures the progress of the project heads in the right direction.
• Code, Wiki Leaders (for sub-teams): Facilitate communication, task distribution, and serve as liaisons between teams and the Project Manager.

Meeting Structure
Weekly classroom meetings are conducted on Thursday in an in-person style on campus. Out of classroom, Discord meetings are conducted online to foster 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.