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 |
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:
- https://happygitwithr.com/big-picture.html
- https://www.atlassian.com/git/tutorials/why-git
- https://guide.quickscrum.com/git-guide/