Süleyman Emir Taşan

About Me

Hi! I'm Süleyman Emir. I use both my names. I am senior CS student at Bogazici. I try to enjoy life by doing the things I'm interested in like traveling, reading, researching, developing myself and trying new activities.

Skills

• Programming Skills

  • Python / Java / C

• Softwares

  • MySQL / PostgreSQL / Spring

• Soft Skills

  • Communication, Crisis Management

Hobbies

I love traveling, especially to historical cities and buildings. I love reading and writing. I write poetry. I love Chelsea FC and watching its matches. I love video games.

Contact Information

• E-mail
• GitHub
• LinkedIn

Contributions during CMPE451

Weekly Contributions

Week 1

Task	Type	Time taken	Outcome	Related issue
Meet new friend, organize the personal wiki page.	Organization	40 min	----	----
Doing research on linked data resources, and seeking answers to the questions we asked during our weekly meeting about generating quiz question	Organization	40 min	We found some crucial information about WordNet and BabelNet	#263

Week 2

Task	Type	Time taken	Outcome	Related issue
Attending lab to discuss requirements and the use of linked data usage	Organization	120 min	----	----
Create the general meeting #1 notes	Organization	120 min	#262	----
Write System Requirements	Design	6 hours	Requirements	#268

Week 3

Task	Type	Time taken	Outcome	Related issue
Attending lab	Organization	120 min	----	----
Review System Requirements with Semih during the Lab	Design	1 hour	Requirements	---
Initialize the back-end	Implementation	??	?	#288
Create the general meeting #3 notes	Documentation	120 min	#289	----

Week 4

Task	Type	Time taken	Outcome	Related issue
Attending lab to discuss database and API design	Organization	120 min	----	----
Quiz Endpoints	Implementation	+6 hours	#328	#340
Create backend meeting notes	Documentation	30 min	Backend Notes	#341

Week 5

Task	Type	Time taken	Outcome	Related issue
Attending lab to discuss feedbacks from presentation and future plans	Organization	120 min	----	----
Favorite Quiz - Question Endpoints	Implementation	+6 hours		#391

Week 6

Task	Type	Time taken	Outcome	Related issue
Attending lab	Organization	120 min	----	----
Favorite Quiz - Question Endpoints (continued)	Implementation	+3 hours		#391
File upload	Implementation	+2 hours		#387

Week 7

Task	Type	Time taken	Outcome	Related issue
Attending lab	Organization	120 min	----	----
Difficulty algorithm for words and quizzes	Conseptual Design & Implementation	+11 hours		#372
Score system for application	Conseptual Design & Implementation	+8 hours		#372

Week 8

Task	Type	Time taken	Outcome	Related issue
Attending lab	Organization	120 min	----	----
Revise auto-complete	Implementation	1 hour		#424
Finalize favorite quiz-question endpoints	Conseptual Design & Implementation	+8 hours		#391
Implement some unit tests for backend	Implementation	75 mins	Related PR	#440

Week 9

Task	Type	Time taken	Outcome	Related issue
Attending lab	Organization	120 min	----	----
Adjusting difficulty algorithm	Implementation & Design	2 hours		#484
Wikidata usage for hint	Implementation	3 hours		#490
Unit tests	Implementation	1 hour		#595

Week 10

Task	Type	Time taken	Outcome	Related issue
Attending lab	Organization	120 min	----	----
Continue to wikidata API	Implementation & Design	4 hours		#484
Conversion favorite questions to a quiz	Implementation	3 hours		#527
Unit tests	Implementation	2 hours		#595

Week 11

Task	Type	Time taken	Outcome	Related issue
Attending lab	Organization	120 min	----	----
Fix in /hint, /from-favorites endpoints	Implementation	1 hour		#555, #575
Fix bug in "GET /favorite-questions(quizzes)" and FavoriteQuestionResponse	Implementation	1 hour		#551 and #544
Unit tests	Implementation	4 hours		#595

Contributions during CMPE352

Week 2

Task	Type	Time taken
Add personal wiki page	Documentation	10 min
Add a repository that I like	Documentation / Assignment	50 min
Create the labels for issues	Documentation	5 min

Week 3

Task	Type	Time taken
Review old issues and update them	Documentation	20 min
Update the repository that I like	Documentation / Assignment	20 min
Add description and labels to our repository	Documentation	25 min

Week 4

Task	Type	Time taken
Take meeting notes	Documentation	40 min
Convert taken notes to proper format	Documentation	10 min
Research and take notes about Web Application Development	Research/Documentation	60 min
Create Web Application Development page	Documentation	35 min

Week 5

Task	Type	Time taken
Attending Meeting	Meeting	40 min
Determine the requirements for the search.	Documentation	70 min
Find a domain idea	Research/Planning	3 days

Week 6

Task	Type	Time taken	Related issue
Create RAM	Documentation	100 min	#92
Revision search requirements	Documentation	30 min	#93
Construct communication plan table	Documentation	10 min	#95
Add all previous issues to new Project	Planning	20 min	#101

Week 7

Task	Type	Time taken	Related Issue
Design Use-Case diagrams	Design	2 hours	#104
Study Class diagrams and Sequence diagrams	Research	2 hours

Week 8

Spring break

Week 9

Task	Type	Time taken	Related Issue
Give feedback to Class diagram	Design	1 hour	#106
Revise use-case diagram with Ebrar	Design	1 hour	#104
First back-end meeting	Meeting	10 mins

Week 10

Task	Type	Time taken	Related Issue
Design 2 sequence diagram	Design	1 hour	#114 & #115
Review all remaining sequence diagrams	Design	3 hour	#111
Learn basics of back-end	Research	3 hours

Week 11

Task	Type	Time taken	Related Issue
Revise RAM	Documentation	1 hour	#138
Review all remaining sequence diagrams	Design	90 mins	#111
Learn basics of back-end	Research	2 hours

Week 12

Task	Type	Time taken	Related Issue
Revise RAM	1 hour	Documentation	#138
Review API Design	Design	30 mins	#122
Review Database Design	Design	20 mins	#132
Testing endpoints	Testing	1 hour
Implement Wikidata API	Implementation	1 hour	#155
Create back-end meeting notes	Documentation	30 mins	#162
Help mobile team to dockerize project	Support	2 hour

Week 13-14

Task	Type	Time taken	Related Issue
Attend meeting on 7th May	40 min	Meeting	---
Revise API Design with Semih	Design	2 hours	#168
Revise Database Design	Design	20 mins	I forgot to open an issue for this.
Find a solution for docker error	Research	4 days	---
Implement file upload functionality	Back-end Implementation	4 hours	#212
Implement follow/unfollow	Back-end Implementation	3 hours	#222
Revision for RAM	Wiki	30 mins	No need to open an issue.
Write project report for milestone 3	Documentation	120 mins	No need to open an issue.

Works need to explain

• Web Application Development: During a meeting with our friends, it was discussed that our project also included a web application, and it came to the fore that we needed to learn how to do this, and I wanted to take on this task voluntarily. After taking this task, I researched many sources on the internet and took various notes. These notes explained the basics of WAD and what was required for it. Later, I made these notes more descriptive and created the Web Application Development page so that I could share them with my friends.

• Creating Responsibility Assignment Matrix: During a recent meeting, the topic of creating RAM, a crucial deliverable for our Project 1 milestone, was brought to the table. Without hesitation, I volunteered to take on the task. However, initially, I found myself grappling with how exactly to structure it. Aware of the importance of clarity and organization, I delved into researching previous student works and consulted various resources on RAM production processes available online. After reviewing about ten examples, I began to form a clearer idea of what the table should entail. I crafted a design that I felt comfortable with and proceeded to create the RAM. Yet, upon reflection, I recognized the potential for improvement in both visual appeal and comprehensibility. Determined to enhance the presentation, I decided to integrate colored squares to aid in visualization and understanding. Here you can see final version of Responsibility Assignment Matrix.

• UML Diagrams: As one of the three responsible for use-case diagrams, we made the first version with my friends. Later, we received feedback from Ebrar and I revised it. Then, I made the final changes together with Ebrar according to the feedback received from TA. After this stage, I gave feedback to the first version as the reviewer of the Class diagrams. Later, the edit was made according to the feedback received from TA, and I evaluated it and gave it its final version. Then, together with my teammates, we created sequence diagrams according to use-cases and divided them among us. Everyone could receive a maximum of 2, and I took on 2 sequence diagrams. After finishing these 2, I checked all the remaining sequence diagrams, gave feedback and changed them.

• Back-end Implementation: Since I did not have much experience, I first learned the back-end basics from various sources around the internet. Later, as a reviewer of API Design, I finalized the API designs. Later, we finalized the database tables with Semih (I was the reviewer). Meanwhile, Utku had completed many small implementations, so I ran endpoint tests and gave feedback to Utku for the necessary adjustments. Later, I helped the mobile team about dockerizing the project. Finally, I implemented the Wikidata API together with Semih.

• Back-end File Upload Functionality: Since our users should be able to upload images, sounds, files, etc. our application has to support that functionality. Therefore, I took on this task and started researching how I could do impelentation. First, I learned which dependencies and services Spring has. I decided which cloud platform I would upload the files to (Google Cloud) and dealt with the authentication parts of it. Finally, I ran the endpoint tests and decided it was ready.