Kübra Aksu Individual Contribution Report - bounswe/bounswe2023group1 GitHub Wiki

Kübra Aksu - BOUNSWE2023/1

I am Kübra Aksu. I am contributing Group 1 during this semester, on the project "Disaster Response Platform".

Responsibilities

• Carrying out investigations into diverse subjects linked to the project.
• Producing and revising wiki pages as necessary.
• Passionately involved in various project aspects, from issue management to content creation, discussions, research, and diagramming. Prioritized clear communication and attentive issue tracking.
• Fostered a positive and collaborative environment by participating in meetings, providing insights, and supporting teammates.
• Contributed to mockups, use cases, and diagrams, creating a clear project vision.
• Pursued valuable external connections through a demo with an industry expert.

Main Contributions

• Issue Management:

1. Enhanced issue management by creating and editing labels, which streamlined our workflow and made it easier for team members to track progress.

Issues: #4

• Wiki Content & Documentation:

1. Improved the clarity and organization of the sidebar to facilitate navigation for users.

Issues: #132

2. Revisioned readme to ensure users receive accurate and helpful information.

Issues: #8 #44

3. Revisioned home page to offer a more user-friendly experience.

Issues: #10 #45

4. Crafted a personalized introduction page for myself, showcasing my skills.

Issues: #27

5. Ensured all team members were represented with appropriate photos on the home page to promote a professional and cohesive group image.

Issues: #39

6. Revised the introduction page template to enhance its effectiveness and adaptability for future use.

Issues: #42

7. For better documentation I have a plan for issue template, is decided to be postponed to the second milestone.

Issues: #80

8. Created first edition of our logo.

Issues: #132

• Discussions & Meetings:

1. Actively participated in and contributed to discussions on requirement elicitation topics, fostering collaboration and shared understanding. Made additional meetings with stakeholders (contact) and customer (instructor) to clarify requirements and mock-ups. Also requested a demo and made appointment with the executive director of one of the advanced projects in our domain.

Issues: #9 #51

2. Created and engaged in conversations around discussions, facilitating the exchange of ideas and feedback. Engaged in various topic discussions, contributing valuable insights and ideas.

Issues: #33 #34

3. Played a key role in deciding communication plan suggestions and assisted in documenting the final communication plan to ensure smooth team coordination.

Issues: #37 #38

• Requirements & Research:

1. Developed relevant questions for the requirements page to ensure comprehensive and accurate information gathering. To be comprehensive, 70 questions were created by me involving different scenarios and conditions.

Issues: #57

2. Conducted research on Terraform.

Issues: #58

3. Made domain analysis and by investigating similar projects, tried to eliminate their requirements work and use cases. Then collaborated with teammates to share and revise my knowledge. By ensuring a well-rounded perspective to enhance the overall quality of the project, strengthening the foundation for successful implementation.

Issues: #78 #79 #81

• Mockups, Use Cases & Diagrams:

1. Expertly crafted and finalized the victim mockup, including both web and mobile versions, reflecting a thoughtful and thorough understanding of user needs.

Issues: #71 #137

2. Deeply revised the victim's use case to ensure its accuracy and effectiveness. Because of changing requirements of victim user role this task is done repeatedly to satisfy requirements completely.

Issues: #103

3. Addressed and eliminated inconsistencies in mockups and design artefacts. Noted and arranged them, made meeting for this and collected my group friends' ideas.

Issues: #104

4. Enhanced the use case diagram for the coordinator role to accurately depict their responsibilities and interactions with other actors in the system.

Issues: #107 #111

5. Revised and refined the class diagram to ensure it accurately reflected the structure of the platform and included method parameters and return types.

Issues: #110

6. Created 'Information' class for use cases and class diagrams since it is necessary for the implementation and it was missing.

Issues: #102

7. Developed detailed sequence diagram scenarios to guide the team through complex interactions and processes. Also 6 scenarios which drawn by me is added to wiki.

Issues: #117 #144 #145 #146 #147 #148

• Demo & External Communication:

1. Proactively arranged and participated in a demo with Crisis Control's executive director, Vittoria Nicastro, fostering valuable connections and opening opportunities for collaboration and better foresight to our project.

Issues: #106

• Milestones & Reports:

1. Monitored and updated milestone due dates, keeping the team on track and focused on key deliverables.

Issues: #109

2. Drafted the first version of the Milestone Report 1, incorporating input from the entire team, and added it to the wiki and sidebar.

Issues: #121

• Meeting Notes:

1. Documented and uploaded meeting notes 5, 11, 12, providing a valuable resource for team members to reference.

Issues: #51 #75 #107 #133 #134

• Issue Tracking & Communication:

1. Demonstrated exceptional care in issue tracking and revisioning, ensuring a well-organized and efficient workflow.

Issues: #62

2. My work for documentation and tracking can be seen from the issues. To being on time, I created weekly milestones and opened necessary issues by assigning responsible members. Every week after our weekly tasks are declared by instructor I made researches to clarify tasks, investigated good project and repository examples and suggested tools for improvement. Also regularly I shared my class notes with my friends.

Issues: #62 #63 #65 #66 #67 #68 #69 #70 #72 #73 #79 #82

3. Prioritized clear and effective communication among team members, fostering a collaborative and productive environment.

Issues: #35

4. Communication establishment and consistency of that for a long period is necessary for project improvement and collaboration. So I tried to create this by using Github features such as discussion and poll. This enabled to discuss all the topics and anytime and also at the same time keeping the track of tasks. Those were beneficiary to represent every sound from the team. Also I asked my team members to comment on my work and I revisioned all the tasks and issues so far.

Issues: #20 #21 #23 #28 #33 #64 #84 #105

Management Related Significant Issues

As an enthusiastic and attentive team member, I've fostered a professional and collaborative atmosphere by encouraging open communication, strategic task delegation, and diligent milestone monitoring. By administering project resources effectively,I've empowered our team members to contribute their unique skills and perspectives. I've inspired our team to continually strive for excellence and innovation, nurturing a close-knit environment where every voice is valued and heard.