Personal Wiki & Effort: Elif Nur Deniz - bounswe/bounswe2024group6 GitHub Wiki

I'm a 4rd grade student at Boğaziçi University. I am very passionate about my major and have great time management skills.

• Programming skills in Java, Python, C, C++ etc.
• Knowledge in data types and algorithms
• Web scraping and data handling

• Athletics ❤️. In the school team for 3 years.
• Yoga
• Traveling & hiking

• Email: [email protected] | [email protected]
• Linkedin: Elif Nur Deniz

1. Joined lab meeting.
2. Archived CmpE352 related documents and reorganized wiki sidebar.
3. Got to know the new team members. Created teams for frontend, backend and mobile.
4. Started learning about the project and had a question-answer session with the TA.
5. Joined the weekly meeting

1. Started editing requirements based on the answers we got in the previous lab. Added the quiz requirements part and made some additions to other functional requirements.
2. Joined lab session and asked the customer our elicitation questions with the team.
3. Filled the answers to the elicitation questions.
4. Joined a meeting with the frontend team. Started the initial design for pages in the project and started designing mockups.
5. Searched for component libraries with the frontend team.

1. Joined the lab session and reviewed use-case diagrams together with the team.
2. Joined the weekly meetings and created notes for it.
3. Reviewed sequence and class diagrams, mobile and web mockups with the team.
4. Discussed about additional features for the project.
5. Added profile page mockups and login-register page mockups. Reviewed the rest of the mockups and compared them all with mobile mockups.

1. Reviewed and edited user scenarios. Decided to replace the illustrations with mockups.
2. Checking the wiki for inconsistencies in mock-ups, diagrams and requirements.
3. Discussed frontend presentation with teammates.
4. Started coding the post component and the forum page. Did pair programming with Ali Tarık.
5. Started coding the comment component and post details page. Changes got discarded after we decided to implement comments as posts too.
6. Joined weekly and lab meeting.
7. Started profile page design for frontend.

1. Continued with profile page design and made it ready for the 1st milestone.
2. Adjusted navigation bar multiple times based on our design choices.
3. Created a Readme file and explained how to run web application both locally and on a cloud host.
4. Determined implemented requirements for this milestone to be used in release tag.
5. Presented the frontend features in milestone presentation.
6. Updated diagrams and requirements based on the review from last week.

1. Joined weekly and lab meeting.
2. Start designing quiz components and initial solving page at a frontend meeting
3. Edited profile page and added a drop-down page for extra options when clicked on profile image on navbar.

1. Reviewed current project status in lab meeting.
2. Joined weekly and lab meeting.
3. Started documenting and adding application tags to wiki.

1. Joined weekly and lab meeting.
2. Implemented mock quiz feed and quiz card.
3. Added a mock resume quiz from where we left of feature.
4. Created a user scenario for continuing unfinished quizzes.

1. Joined weekly and lab meeting.
2. Finalised quiz feed and quiz card design.
3. Created Customer Milestone 2 demo plan
4. Created quiz results page.
5. Added more functionalities to profile icon and made it navigate to profile page.
6. Finalised application tags.
7. Added tags to the related field in the code and changed designs.
8. Added a photograph feature to quizzes and applied the design changes everywhere necessary.
9. Created Profile page related JSON request and response formats.
10. Fixed the design error on profile icon.
11. Implemented sorting by date and like count feature for forum page.
12. Made filtering by tags functional.
13. Fixed a bug for non-working difficulty tag in posts.
14. Implemented other/own users' profile views and connected them to backend.
15. Replaced mock profile page path with the real usernames.
16. Reviewed profile and quiz related json responses and asked for the required changes to backend.
17. Added missing features to profile page after the changes in the backend.

1. Joined weekly and lab meeting.
2. Created a popover for users in post and quizzes which will give details about the creator.
3. Created a profile edit page.
4. Listed bookmarked posts in related profile tab.
5. Fixed a issue of missing usernames in profile created posts section.
6. Fixed follower count not updating after follow operation issue in every related place.
7. Made many design related changes to the whole frontend for a better presentation in milestone.
8. Fixed an issue related to post comments' missing contents.
9. Created profile page unit tests.
10. Listed implemented requirements for the 2nd milestone to be added to the report.
11. Fixed some dark mode display related issues.
12. Prepared for milestone customer demo and took part in presentation.

1. Joined weekly and lab meeting.
2. Listed primary and domain specific features, determined acceptance criteria and gave examples for them in the lab.
3. Started connecting quiz related pages to backend.

1. Joined weekly and lab meeting.
2. Connected quiz forum with backend.
3. Connected Quiz Details Page with backend.
4. Connected Quiz Solve Page with backend.
5. Connected Quiz Results Page with backend.
6. Connected Quiz review page with backend.
7. Added all the functionalities to the connected pages.
8. Added created and solved quizzes to profile page.
9. Added followers and following list to profile as a popup.
10. Enabled guests to access specified pages in requirements
11. Added popover user-cards to quiz cards
12. Added sorting and filtering to quiz feed
13. Fixed quiz results page not responding and wrong message issue
14. Made quiz and post cards clickable
15. Added saved posts and quizzes to profile

352 Journal

Week 1: February 13 - February 19

1. Joined the weekly meeting.
2. Created my personal effort page.
3. Created a page to add the repositories that we like and added mines.
4. Studied git.

Week 2 : February 20 - February 26

1. Joined the weekly meeting.
2. Updated personal wiki & effort page.
3. Tracked team members' updates on favourite repositories.
4. Updated my own favourite repository.

Week 3 : February 27 - March 4

1. Joined the weekly meeting.

Week 4 : March 5 - March 11

1. Hosted the weekly meeting.
2. Did my own research.
3. Tracked team members' researches of the week and gave feedback when necessary.
4. Created issues that where determined in the meeting and created Meeting Notes 3 page.
5. Joined another meeting to discuss about our project.

Week 5 : March 12 - March 18

1. Joined the weekly meeting.
2. Searched for previous years' milestones to understand the assignment better.
3. Prepared glossary for the requirements page.
4. Prepared elicitation questions to make project details more clear and documented it with the answers.
5. Created a table for everyone to add their contributions to the first milestone and filled it for myself.
6. Created Responsibility Assignment Matrix and filled it for everyone.
7. Joined a review meeting for mock-ups.

Week 6 : March 19 - March 25

1. Joined lectures.

Week 7 : March 26 - April 1

1. Joined the weekly meeting.
2. Studied UML diagrams.
3. Reviewed last milestone with team members.

Week 8 : April 2 - April 8

1. Joined the weekly meeting.
2. Talked about project design and distributed UML diagram designs with the team.
3. Studied class diagrams in more detail.

Week 9 : April 9 - April 15

1. Joined lectures.

Week 10 : April 16 - April 22

1. Joined the weekly meeting.
2. Discussed about development planning with the team.
3. Hosted another meeting to distribute class diagram tasks.
4. Organised wiki page.
5. Created user and messaging class diagrams.

Week 11 : April 23 - April 29

1. Joined the weekly meeting.
2. Talked about Git Workflow, PR Structure, Docker structure with the team.
3. Set up local development environment.
4. Selected UI component libraries for web and mobile and implemented it with Tailwind CSS.
5. Talked about implementation plan with the team.
6. Added finalised version of class diagrams to Github.
7. Studied React.
8. Designed browse page and search bar.
9. Helped deploying the project.

Week 12 : April 30 - May 6

1. Joined the weekly meeting.
2. Presented demo session in class.
3. Added functionalities to register and login pages.
4. Added missing meeting notes to Github wiki from my past notes.
5. Updated Readme file and added current project status.
6. Wrote milestone report with team members.
7. Wrote down my contributions in work done page.

Week 13 : May 7 - May 13

1. Joined a milestone review meeting with frontend team.
2. Joined another meeting with frontend team and distributed tasks. Also, discussed the next steps.
3. Created mock data for wiki Building page using wikidata.

Week 14 : May 14 - May 20

1. Continued to create mock data for other wiki result pages. Investigated the results on wiki data.
2. Joined a meeting with the team. Presented my mock data. Talked about task prioritisation.
3. Filled wiki pages with mock data and created a temporary design.
4. Reorganised wiki pages with real data.
5. Tested the application for many searches. Reported bugs to backend side and reviewed the bugs myself too.
6. Created post component UI. Created mock data for it and made the initial and final design with my teammate's reviews. After that filled it with real data and fixed bugs.
7. Dynamically linked result pages to each other so that you can visit the architect page from its building page etc.
8. Created response messages for post creation.