-
Notifications
You must be signed in to change notification settings - Fork 0
Individual Contribution Report (Enes Furkan Arslan)
Enes Furkan Arslan edited this page Apr 10, 2023
·
2 revisions
- Name: Enes Furkan Arslan
- Student Number: 2021400327
- Group: 4 / B2
- Like each team member, I was responsible for attending lectures, PS meetings and weekly team meetings.
- I have attended to kick-off meeting with our project owner and ask necessary questions and take notes about our project and specified requirements.
- I was responsible for creating a self introduction page for myself.
- I was responsible for researching on a GitHub repository and report about it on wiki page.
- I was responsible for reviewing the meeting notes after team meetings like other team mates.
- I was responsible for suggesting functional requirements for the project which are suitable with the format that introduced in the lectures.
- I was responsible for researching on Non-Functional requirements of a software project and then creating non-functional requirements of our project accordingly with lectures and my researches.
- I have attended to first PS and got feedbacks about Functional Requirements, Non-Functional requirements and Mock-Up of the team and shared the feedbacks with the team members.
- I was responsible for researching about needed authentication information for users' sign up process. I have checked similar platforms and created the necessary requirements on wiki page.
- I have contributed to team discussions about 'cost for opening a poll', 'jury selection', 'vote changing' and 'point inflation prevention'.
- I have suggested a detailed point system for the project and it has been accepted by team members with minor modifications.
- I was responsible for tracking the use case diagram issue while creating the use cases for profile section of the platform and contributing to use cases for Poll system. I have also took notes for missing requirements while preparing the use cases and modified requirements page accordingly.
- I was responsible for taking meeting notes for a week and uploading it to wiki page.
- I was responsible for creating the sequence diagrams for profile use cases with Yusuf Suat Polat.
- I have suggested to team that we should use word 'member' instead of 'user' for better convenience since 'user' is too general and my suggestion has accepted by the team.
- I was responsible for make a research about project plan, RAM and communication plan for the first milestone. I have presented my research to group at team meeting.
- I was responsible for creating the RAM(Responsibility Assignment Matrix) and adding it to wiki.
- I was responsible for creating the communication plan of the team and uploading it to wiki.
Contribution | Description |
---|---|
Self Introduction Page | Check here |
Favorite Repository | Check here |
Suggesting functional requirements | Check issue #16 |
Creating Non-Functional Requirements | Check issue #20 |
Creating authentication info requirements | Check issue #26 |
Contribution to Discussions | Check issues #27,#28,#33,#35 |
Suggesting detailed point system | Check issue #38 |
Tracking Use Case Diagrams and creating Profile Use Cases | Check issue #41 |
Taking meeting notes | Check here |
Creating Sequence Diagrams for Profile Use Cases | Check issue #51 |
Research for milestone 1-Deliverable 4 | Check issue #56 |
Creating RAM of the team | Check RAM |
Creating Communication plan of the team | Check Communication Plan |
Some of my most important contributions are:
- Creating Non-Functional Requirements. #20.
- Getting and sharing feedbacks about all requirements elicitation process in PS.
- Suggestion for the point system which is vital for the platform. #38
- Creating profile system use case diagrams and sequence diagrams. #41 #51
- Creating RAM. RAM
- Creating Communication plan. Communication Plan
- Moderation of the last team meeting before the Milestone 1.
- Meeting 1 - 03/03/2023
- Meeting 2 - 09/03/2023
- Meeting 3 - 10/03/2023
- Meeting 4 - 16/03/2023
- Meeting 5 - 18/03/2023
- Meeting 6 - 23/03/2023
- Meeting 7 - 25/03/2023
- Meeting 8 - 30/03/2023
- Meeting 9 - 01/04/2023
- Meeting 10 - 06/04/2023
- Meeting 11 - 08/04/2023
- Meeting 12 - 27/04/2023
- Meeting 13 - 29/04/2023
- Meeting 14 - 04/05/2023
- Meeting 15 - 10/05/2023