Ecenur Sezer
Skills
Interests
- Mobile/Desktop/Web App Development
- Volleyball
- English
- German
Week 1
| Task | Duration | Type | Link (optional) |
|---|---|---|---|
| Attended to the first meeting with the team | 1h 15m | Meeting | Corresponding Issue |
| Created the personal wiki page, found helpful badges for the team | 2 hours | Documentation | Personal Wiki Page |
| Researched about Git and GitHub in general | 1h 15m | Research | Git and GitHub Research |
Week 2
| Task | Duration | Type | Link (optional) |
|---|---|---|---|
| Attended to the second meeting with the team | 2hrs | Meeting | Meeting Notes |
| Determining System Requirements - Notification | 2 hour 30 min | Documentation | Corresponding Issue |
| Researched about w3 web annotation model | 1h 15m | Research | Corresponding Issue |
| Reviewing Glossary | 20 min | Review | Corresponding Issue |
| Research about Semantic Search | 1 hour | Research | Corresponding Issue |
| Research on Software from Rival Companies | 1 hour | Research | Corresponding Issue |
Week 3
| Task | Duration | Type | Link (optional) |
|---|---|---|---|
| Attended to the third meeting with the team | 2hrs | Meeting | Meeting Notes |
| Determining Community Event Requirements | 2 hour 30 min | Documentation | Corresponding Issue |
| Creating Persona and Scenario for Community Event | 1h 40m | Scenario | Corresponding Issue |
| Reviewing issues | 20 min | Review | Corresponding Issue |
Week 4
| Task | Duration | Type | Link (optional) |
|---|---|---|---|
| Attended to the fourth meeting with the team | 2hrs | Meeting | Meeting Notes |
| Revising Community Event Requirements | 2 hour 30 min | Documentation | No basic changes were advised by our TBA on the requirements I worked on, so no issue was created |
| Reviewing issues | 20 min | Review | Corresponding Issue |
Week 5
| Task | Duration | Type | Link (optional) |
|---|---|---|---|
| Attended to the weekly meeting - Week #5 | 2h 15m | Meeting | Meeting Notes will be prepared |
| Involved in the Non lecture related part of the use-case diagram (includes creating, editing, viewing notes). Before starting, checked all requirements and mockups related to this part. | 2h | System Design - Use Case Diagrams | Corresponding Issue |
| Created the Search, Browse and View Homepage parts of the use-case diagram. Before starting, checked all requirements and mockups related to this part. | 3h | System Design - Use Case Diagrams | Corresponding Issue |
| Reviewed the course creation use case diagram | 30m | Scenario & Mockups | Corresponding Issue |
| Created the Viewing Course part of the use-case diagram | 1h | System Design - Use Case Diagrams | Corresponding Issue |
| Attended to the use-case diagram review and class diagram planning meeting | 3h | Meeting - Class and Use-Case Diagrams | Meeting Notes |
| Created the Class Diagram general issue | 30m | System Design - Class Diagrams | Corresponding Issue |
| Created the Message and Profile parts of the class diagram | 2h | System Design - Class Diagrams | Corresponding Issue |
| Reviewed the Search part of the class diagram and written all my feedbacks as comments. | 1h | System Design - Class Diagrams | Corresponding Issue |
| Detailed the Profile and Message classes after our meeting for class diagrams. | 30m | System Design - Class Diagrams | Corresponding Issue |
| Attended to the class diagram review and sequence diagram planning meeting. | 2h 30m | Meeting - Class and Sequence Diagrams | Meeting Notes |
| Watched beneficial diagram tutorials from Lucidchart's official account. | 45m | System Design - Diagrams | Youtube Channel |
Week 6
| Task | Duration | Type | Link (optional) |
|---|---|---|---|
| Attended to the weekly meeting - Week #6 | 2h | Weekly Meeting | Meeting Notes |
| Created the Edit Profile part of the sequence diagram | 2h | System Design - Sequence Diagrams | Corresponding Issue |
| Revised the Edit Profile part of the sequence diagram according to the feedbacks received in the PS from our TA, Egemen | 1h 15m | System Design - Sequence Diagrams | Corresponding Issue |
| Revised the indicated parts of the class diagram after we received feedbacks from our TA, Egemen in the PS. I have added a update comment related to my changes. | 40m | System Design - Class Diagrams | Corresponding Issue |
| Closed the main issue of class diagram. | 45m | System Design - Class Diagram | Corresponding Issue |
| Created the Communication Plan Evaluation of Deliverables and Deliverables part of the Milestone Report-1 | 2h | Milestone Report - 1 | Corresponding Issue |
| Created the Scenarios&Mockups Evaluation of Deliverables and Deliverables part of the Milestone Report-1 | 2h | Milestone Report - 1 | Corresponding Issue |
| Wrote the personal Summary of Work Done part of the Milestone Report - 1 | 2h 15m | Milestone Report - 1 | Corresponding Issue |
| Filled the RAM part of the Milestone Report - 1 by checking all previous issues and effort tables | 1h 10m | Milestone Report - 1 | RAM |
| Attended to the sequence-diagram review & milestone-1 planning meeting | 2h 30m | Meeting - Sequence Diagram & Milestone-1 | Meeting Notes will be provided. |
| Reviewed the RAM of the milestone - 1 report | 30m | Milestone Report - 1 | RAM |
Week 7&8
| Task | Duration | Type | Link (optional) |
|---|---|---|---|
| Attended to the weekly meeting - Week #7 | 2h | Weekly Meeting | Meeting Notes |
| Attended to the weekly meeting - Week #8 | 2h | Weekly Meeting | Meeting Notes |
| Documented Meeting Notes - Meeting 7 | 2h | Weekly Meeting | Corresponding Issue |
| Made research about API’s and endpoints | 4h 15m | Practice App | No issue |
Week 9
| Task | Duration | Type | Link (optional) |
|---|---|---|---|
| Attended to the weekly meeting - Week #9 | 2h | Weekly Meeting | Meeting Notes |
| Reviewed POST Category Endpoint | 2h | Practice App | Corresponding Issue |
| Implemented POST Rating Endpoint | 9h 15m | Practice App | Corresponding Issue |
| Implemented GET Rating Endpoint | 9h 35m | Practice App | Corresponding Issue |
| Implemented unit tests for POST/rating | 8h 45m | Practice App | Corresponding Issue |
| Implemented unit tests for GET/rating | 8h | Practice App | Corresponding Issue |
| Created manual tests for rating endpoints and documented using Postman | 2h | Practice App | - |
| Fixed bugs & changed the implementation of GET/rating and POST/rating endpoints | 4h | Practice App | Corresponding Issue |
| Fixed bugs & changed the implementation of unit tests of GET/rating and POST/rating endpoints | 5h | Practice App | Corresponding Issue |
| Implemented the UI for Rating page of Practice App | 8h | Practice App | Corresponding Issue |
| Fixed bugs on error messages of Rating page | 4h | Practice App | Corresponding Issue |
| Overall, more than 60 hours this week. I remember days I have studied all day and continued until morning. |
Week 10
| Task | Duration | Type | Link (optional) |
|---|---|---|---|
| Attended to the weekly meeting - Week #10 | 2h | Weekly Meeting | Meeting Notes |
| Created individual report | 2h | Milestone-2 | No issue |
| Reviewed Basic Functionality of the Project Part of Milestone-2 | 1h 15m | Milestone-2 | Corresponding Issue |
| Reviewed bugfix for POST/api/category | 40m | Practice App | Corresponding PR |
| Filled Introduction/Project Description & Project Status Parts | 45m | Milestone-2 | Corresponding Issue |
| Created and Documented Class Diagram for Practice-App | 2h | Milestone-2 | Corresponding Issue |
| Filled individual work | 2h | Milestone Report - 2 | Corresponding Issue |
General Git&GitHub Research
Git is a free and open-source version control system that enable developers to work collaboratively on big software projects.
GitHub is the hosting of git on the internet to enable communication, data sharing between developers easier.
\
Sources:
Rating API
API I introduced to our practice app is GET/rating and POST/rating. GET/rating API takes query parameters and used to filter lessons based on an interval of rating. POST/rating API is used to rate a lesson. Much detailed information with example calls is in my indiviual report. \