Hasan Baki Küçükçakıroğlu Individual Contribution Report

Hasan Baki Küçükçakıroğlu - SWE2023/Group 8

I am Hasan Baki. I am contributing Group 8 during this semester, on the project "Web Info Aggregator".

Responsibilities

Let's start the narrative from the beginning of the story. In the first weeks, in addition to my individual tasks, I tried to establish a team mindset among the group members. I created avatars for teammates and added them to the Readme page. To facilitate communication and collaboration, I set up channels like Slack, Drive, and Notion. Additionally, I integrated various extensions to make life easier for my colleagues. Ensuring a true democracy was also part of my efforts, so I initiated numerous polls to enable group decision-making as a whole.

As I worked to improve our Wiki page by adding my repository research and creating an elegant sidebar navigation, things began to get serious. Requirements analysis and mockups emerged on the horizon. We divided the group into two, and I was placed in the requirements analysis group. After determining our requirements and documenting them, Egemen and I led the requirement sub-group and completed the tasks successfully. However, we encountered another problem. The mockups task was larger than initially anticipated, so I needed to assist the mockup team leaded by Meriç.

Since I work professionally as a frontend developer, I added and organized various pages, as well as included numerous details. As mentioned earlier, our group created Use Case diagrams and Sequence diagrams in two separate group meetings, with subsequent revisions. I participated in creating both of these diagrams in those meetings but cannot specify which part belongs to me.

As we approached the end of the story, it was already April, and we had numerous academic responsibilities. My main role in Milestone 1 became apparent here: I took responsibility for planning and distributing tasks, initiating documents, creating issues, encouraging team members to create issues, helping them resolve their issues, and of course, addressing my own issues. In the end, we produced a visually appealing, well-structured set of deliverables and a report. It was undoubtedly exhausting, but it was worth the effort.

Main Contributions

Story of my responsibilities have been told above, let's show some solid works here to connect dots.

Repository/Wiki

My work in that section is mainly straightforward and individual.

• Creating Research Page #10
• Side Bar Revision #17
• About Me Page #26
• List Team Members with their Avatars in Readme Page #28
• Notes Of The Fourth Meeting #35

Milestone 1 Report

Besides the following issues, I managed the whole process of Milestone Report and help my friends do their tasks.

• Milestone Report - Introduction #65 #65
• Milestone Report - Executive Summary #72
• Milestone Report - List and Status of Deliverables #73
• Milestone Report - Evaluation of Deliverables - Project Repository #74 #74
• Milestone Report - Milestone Report #84
• Add Mockups to Milestone 1 Report Page #78
• Creating Individual Contribution Report - Baki #58
• Add Project Requirements to Milestone 1 Report Page #86

Software Requirements Specifications

We created software requirements specifications as a sub-group of 4. Me and Egemen managed the group and Wiki arrangements.

• Creating Template for Requirements #38
• Creating Glossary List #41
• Requirements Analysis Revision #47
• Formalize User Requirements. #40

Mock-ups

I was a substituted player in that part, but I design our logo and colors, created 4 mock-ups, created navigation-bar, added relevant content, and numerous styling.

• Mock-up revision #51

Use Case Diagrams

We created that part simultaneously with the team, so I involved almost each of the use case diagrams.

• Use Case Diagram #52

Sequence Diagram

We created that part simultaneously with the team, so I involved almost each of the use case diagrams.

• Sequence Diagram #56

Management Related Significant Issues

In most cases, we did not generate issues for administrative matters, instead discussing them across various communication channels based on their urgency. The majority of decisions were made during weekly meetings and through Slack conversations. Matters requiring immediate attention were addressed in WhatsApp discussions. I feel that I made an effort to provide my input whenever possible and occasionally reminded team members of certain tasks.