Individual Contribution Report (Yunus Emre Altuğ) - bounswe/bounswe2023group7 GitHub Wiki

Responsibilities
In the first week, we were required to create our wiki pages. This and below task required us to learn Markdown also. I revise the page every week to keep track of my effort.
Secondly, we were required to review a Github repository to understand repository logic.
We prepared the ReadMe to have an explanatory content.
I elicitated user requirements, some of them is discussed in group meetings, some of them is what I added. I thought what this platform requires and recorded.
We elicitated non-functional requirements, some of them is discussed in group meetings, some of them is what we added. I thought what this platform requires and recorded.
After observing some redundant sentences, lack of some user requirements and good page organization, we needed to make major revision and made it
Also, system requirements needed to be more detailed. We added more system requirements and change requirement types of some articles.
Additionally, discussed about what non-functional requirements should be added.
I prepared a glossary for requirements for explain words in our platform jargon.
I was assigned to create some of the diagrams which we must do. These were, use case diagram of events, class diagrams of event actions and class diagrams of administration class.
I was assigned to create some of the diagrams which we must do. These were, use case diagram of events, class diagrams of event actions and class diagrams of administration class.
I was assigned to create some of the diagrams which we must do. These were, sequence diagram of events, class diagrams of comment classses.
We were assigned to prepare a project plan which contains past and future action of software project.
I was assigned in 7th meeting to take note.
I should prepare an individual report to explain what we have done.

My Contributions	Subject	Link to Work	Related Issues	Duration	Description
Prepared a repository research.	Research	See	#9,#3	90 Minutes	Repo structure, ReadMe and code of DS4Windows was analyzed.
Created my wiki page.	Documentation	See	#1	30 Minutes	It is revised every week.
Designed the README.md.	Documentation	See	#14	75 Minutes	Description, table of contents, contributors were added and some revisions were done after that.
Created the requirements page.	Requirements	See	#32	15 Minutes	The content we created are collected and indexed by me.
Formalized the user requirements.	Requirements	See	#37	6 Hours	All user requirements were elicitated by me in this page.
Formalized the non-functional requirements.	Requirements	See	#36	1 Hour	Performance and compatibility parts prapared by me.
Revised User, System and Non-Functional Requirements	Requirements	See	#45 #46 #48 #53	6 Hours	After opinions of group in the meeting, discussed with Elif Kızılkaya and Sena Alçı, made major alterations on requirements and created a new requirements page with a better design in two days. Adjusted face to face meeting on Thursday with Sena and Elif and on Friday with Elif. I am making still small revisions on the page.
Wrote Glossary for Requirements	Requirements	See	#54	75 Minutes	I defined terms what we decided to explain in revision meetings.
Drew the use case diagram of event actions.	Design	See	#63	75 Minutes	Checked the requirements, listed actions and connected them with the user based on diagram rules.
Drew the class diagram of Event class and EventComment.	Design	See	#64	75 Minutes	Checked the requirements, thought how class can be implemented and connected these two classes with the other classes based on uml rules.
Drew the class diagram of administration class.	Design	See	#64	25 Minutes	Created admin subclass of user and functions were delivered.
Drew the sequence diagram of 4 event actions.	Design	See	#87	60 Minutes	Created sequence for joining, creating, leaving event sequence diagrams and adding comment to event
Created Comment class and its subclasses.	Design	See	#88	30 Minutes	Drew the class diagram of Comment class and its subclasses ReviewComment, ForumComment other than EventComment which was drawn previous week.
Taken and published notes for Meeting #7.	Organizational	See	#105	45 Minutes	I published our notes to Github.
Created project plan.	Project Plan	See	#102	240 Minutes	With Tayyip and Elif, we got together and created a project plan before milestone deadline. We reviewed all issues and meeting notes to list all tasks which are given all group members.
Created individual report.	Documentation	See	#123	120 Minutes	I created a self report which explains all what I must have done and did in the period from beginning of the term.

Issues	Description	Link to Work	Issues
Requirements	Before eliciting, I had thought much about what this platform requires, and then we were assigned to elicit user requirements and non-functional requirements. Additionally, we should have created descriptive content to help mockup designers in the team in two days. I wrote almost all user requirements and half of the non-functional requirements. After the lecture, I understood I needed to rewrite the game page requirements. Also, group finding was much simpler in the requirements that I had written. I wanted to review them with some group members to eliminate mistakes and prepare content that does not need major revision in the short term. In revision meetings, I explained what I had denoted in the articles. Thus, I realized which quotes are unclear for someone to understand, and we changed some sentences. We made some organizational alterations on the page, reindexed articles, added requirements for group finding and review. Shortly, we formalized the requirements. Then I added a glossary. Until today, I have made some minor revisions and major revisions with asking my teammates' opinion. Also, I communicated with instructors when there is indecision in some requirements.	1. Requirements Draft 2. Requirements 3. Requirement Revisions	#32 #36 #37 #45 #46 #48 #53 #54

1. Requirement Draft: The first requirements page which I uploaded.
2. Requirements: The second requirements page which I, Elif and Sena revised in two meetings and Elif uploaded. Because of the fact that reorganising is difficult to add on same page, we created a new page and not to lose old versions of requirements we have kept it also.
3. Requirement Revisions: I have made 25 revisions on the page. This amount does not mean anything by itself, because approximately half of the revisions are minor and basic. Therefore, if there is not any problem on the page you can visit history of requirements what we have done from above link:

• Some of the revisions were made due to adjusting again desirability of requirements. For instance, some requirements will be more difficult to handle and are not mentioned in description. After consulting them, I made changes. These can be done in two ways: Converting "shall" to "should" in the article, or removing the article.
• Some of the revisions were made for adding basic necessary user actions which we forgot to mention. For instance, we thought admin can ban user, but unbanning was forgotten while recording.
• Some of the revisions were made for eliminating bad expressions.
• Some of the revisions were made for preventing contradiction between articles.
• Some of the revisions were made for correcting typos and grammar failures.
• Some of the revisions were made due to Markdown mistakes which I did and realized after revising requirements.
• Some of the revisions were made for adding glossary.
• Some of the revisions were made for reindexing and recategorizating the articles.

I attended all weekly team meetings, customer meeting, all problem sessions and lectures. Therefore, I discussed project not only my teammates, thus we realized our mistakes we missed.