Can Atakan Uğur (Effort Tracking) - bounswe/bounswe2022group7 GitHub Wiki
Here you can find the weekly effort reports of Can Atakan Uğur.
Week 1
Task | Duration | Type of Work | Remarks |
---|---|---|---|
Making research on & updating issue labels | 30 minutes | Research & Documentation | Details |
Creating my personal Wiki page | 30 minutes | Documentation | Details |
Making research on the format of the meeting reports | 15 minutes | Research | Details |
Preparing a meeting report template | 30 minutes | Documentation | Details |
Making research on high-quality Github repositories | 45 minutes | Research | Details |
Reviewing the material about Git | 30 minutes | Research | |
Reviewing the README file | 5 minutes | Documentation | Details |
Team Meeting #1 | 40 minutes | Meeting | Meeting Information |
Taking notes during the meeting | - | Planning | I was the note taker in this meeting. It does not take extra time. |
Preparing the meeting notes for Meeting #1 | 30 minutes | Documentation | Details |
Total Time: 4h 15m
Summary: This week, I actively participated in the infrastructure setup process. I have also reviewed the parts of the job that were not done by me. Therefore, I can conclude I am well aware of the current progress of our repository and I am also contributing to it.
Week 2
Task | Duration | Type of Work | Remarks |
---|---|---|---|
Creating personal effort Wiki pages for everyone according to the template | 20 minutes | Documentation | Details |
Research and study on requirements | 1 hour | Research | Details |
Reporting the results of the research, and contributing to the collaborative Google document with my ideas about requirements using the results | 1.5 hours | Planning | The results are reported under the same issue, here, and this is the link to the Google document. |
Creating a draft page for our Requirements | 1 hour | Documentation | According to the ideas shared on the Google document, I created a template for our Requirement page. The relevant issue can be found here as well. |
Completing the sign up, sign in and search requirements in addition to describing user types | 1 hour | Documentation | Details |
Team Meeting #2 | 50 minutes | Meeting | Meeting Information |
Total Time: 5h 40m
Summary: I mostly made research on the features of well-described requirements and individually studied this topic by both reviewing the slides and looking for implemented examples this week. I contributed to the ideas for our requirements page significantly and created the template for it. Also, completed some parts in the requirements with my current knowledge. I can say that I played a crucial role this week, and both me and my team are keeping track of everything and completing the tasks even before we should.
Week 3
Task | Duration | Type of Work | Remarks |
---|---|---|---|
Enriching the home Wiki page | 40 minutes | Documentation | Details |
Documenting the scenario of copyright infringement reporting (mobile version) | 1 hour | Documentation | Details |
Reviewing the mock-ups for our scenario | 20 minutes | Documentation | The comment for the review can be found here. |
Making research on customer questions and coming up with ideas | 1 hour | Research | Details |
Meeting with my partner on preparing the scenario | 20 minutes | Meeting | |
Team Meeting #3 | 1 hour 30 minutes | Meeting | Meeting Information |
Total Time: 4h 50m
Summary: This week, I worked on my part of the main assignment. I collaboratively worked with Atilla to deliver the task and checked other parts. Made major changes in our Wiki, and studied customer questions. I am able to track our development, and I am content with my situation in the project.
Week 4
Task | Duration | Type of Work | Remarks |
---|---|---|---|
Continue reviewing and working on customer questions | 30 minutes | Research | Details |
Participate in the customer meeting during the PS hours | 2 hours | Meeting | We also reviewed our questions until it was our team's turn to start the interview. |
Taking notes during the customer meeting | - | Planning | I was the note taker in the customer meeting. It does not take extra time. |
Editing and uploading the Project Analysis and Possible Customer Questions document mainly prepared by Cahid Arda Öz | 30 minutes | Documentation | Document |
Preparing the Customer Meeting Report | 2 hours 30 minutes | Documentation | Created the report using the quick notes that I took during the customer meeting. Tried to be consistent with our requirements and the customer's demands. The issue including the report can be found here. The report itself can be found here. |
Total Time: 5h 30m
Summary: In general, Week 4 was mostly about the longly awaited customer meeting. I kept working on the questions and how to improve them at the beginning. I actively attended to the meeting, posed our team's questions from time to time, took notes of the key points. I also prepared the report of the meeting using my quick notes. I can briefly conclude that I had significant responsibilities on our development this week.
Week 5
Task | Duration | Type of Work | Remarks |
---|---|---|---|
Attended PS and reviewed the development of the project | 40 minutes | Meeting | |
Team Meeting #4 | 50 minutes | Meeting | Meeting Information |
Taking notes during the team meeting | - | Planning | I was the note taker in the customer meeting. It does not take extra time. |
Preparing meeting notes for Team Meeting #4 | 1 hour | Documentation | Meeting Notes and the issue for this task. |
Updating requirements related to the customer's answer about copyright infringement | 1 hour | Documentation | Details |
Reviewing the updates on the requirements related to customer's answer about auctions | 30 minutes | Documentation | Details |
Fixing the issue about the requirements related to payment flow in auctions | 30 minutes | Documentation | Details |
Team Meeting #5 | 50 minutes | Meeting | Meeting Information |
Creating basic use case diagram template | 30 minutes | Design | Details |
Adding "Bidding" use case to the use case diagram | 1 hour | Design | Details |
Team Meeting #6 | 3.5 hours | Meeting | Meeting Information |
Reviewing the final version of the use case diagram and making necessary updates | 1.5 hour | Design | Details |
Meeting with Demet Yayla to review current work, and make a plan and assign the work to the team members | 1 hour | Meeting & Planning | Details |
Creating a draft for the Class Diagram | 40 minutes | Design | Details |
Working on the "Artist" and "ArtItem" classes for the Class Diagram | 1 hour | Design | Details |
Team Meeting #7 | 2 hours | Meeting | Meeting Information |
Total Time: 16h 30m
Summary: It was an extremely busy week! The deadline was tight and we met many times in order to be able to deliver the work beforehand. The meetings were long, the workload during them were heavy. I have participated in all these tough meetings, played an active role during those, and even had an extra meeting to plan the workflow. I contributed to the development of the project significantly and exceeded myself.
Week 6
Task | Duration | Type of Work | Remarks |
---|---|---|---|
Team Meeting #8 | 1.5 hour | Meeting | Meeting Information |
Preparing a research document about Annotations | 2 hours | Research & Documentation | Issue and the Research Report |
Writing requirements related to Annotations with Demet Yayla | 1 hour | Meeting & Documentation | Details |
Adding use cases about Annotations to the Use Case Diagram | 1 hour | Design | Details |
Editing the Class Diagram on a meeting with Demet Yayla and Cahid Arda Öz | 1.5 hour | Meeting & Design | The main purpose of the meeting was to complete this task. However, we noticed there were some other problems in our Class Diagram and worked on those collaboratively on Lucidchart. We updated the placement of classes, relationship between them and functions and state variables. |
Total Time: 7h
Summary: This week, although I am still trying my best, there are still many things to be accomplished. Since we did not have much information about annotations, it took some time for me to get familiar with the notion and explain it to my team. Both my team and myself individually, are behind our plans. I should try harder and finalize my work on the Class Diagram and complete Sequence Diagram for annotating as soon as possible. Afterwards, I shall start working on the project planning before Milestone 1.
Week 7
Task | Duration | Type of Work | Remarks |
---|---|---|---|
Team Meeting #9 | 2 hours | Meeting | Meeting Information. Please note that we communicated via other communication channels to divide the extra work between us, too. So, the action items shown in these notes are not complete and we worked on many additional tasks. |
Reviewing the sequence diagram for "Bidding" | 30 minutes | Design | Details |
Working on the "Annotated" interface | 1 hour | Design | Details |
Creating the sequence diagram for "Annotations" | 1 hour | Design | Details |
Studying the details about the UML Class Diagram model | 40 minutes | Research | On a group meeting, we made some research as to how the relationships are formed in UML Class Diagrams. The resource we mostly followed can be found here. |
Reconstructing the entire UML Class Diagram with correct relationships, and fixing the problems in classes | 2 hours | Meeting & Design | We collaboratively worked on Lucidchart. |
Updating Scenario 3 | 40 minutes | Documentation | Details |
Updating the mock-ups for Scenario 3 | 1 hour | Design | Details |
Completing the Project Plan | 3.5 hours | Planning | Issues: #129, #133. Project Plan |
Filling my column in RAM and make minor edits on the format of the file | 30 minutes | Planning | Details |
Filling my individual contributions in the Milestone 1 Report | 1 hour | Documentation | Milestone 1 Report |
Contributing to the Milestone 1 Report's "Evaluation of Tools" part | 40 minutes | Documentation | Details |
Reviewing the Milestone Report, fixing grammar issues, creating the Table of Contents, and reformatting it | 1 hour | Documentation | |
Submission Meeting | 2.5 hours | Meeting & Documentation | Exported the final versions of the diagrams, and combined all deliverables in a single file. Updated the repository with the final versions of deliverables. Here are some revisions and commits made by me: Use Case Diagram, Class Diagram, RAM, Milestone Report Reviewed all jobs that are "Pending Review" during the meeting and concluded them to finalize all deliverables. The issues for these jobs were marked as "Completed" and closed accordingly to keep the repository updated. These reviews can be observed in these issue comments: #118, #121, #124, #127, #134. |
Making minor fixes on the Milestone 1 Report, after the discussions with the TA | 1 hour | Documentation | Details |
Total Time: 19h
Summary: It was an extraordinary week! I checked every aspect of our Milestone 1 deliverables and the report. Actively assumed significant responsibilities to complete our tasks before the due date. I led the Submission Meeting and participated in the process of creating the final deliverables. Submitted our work before the deadline.
Week 8
Task | Duration | Type of Work | Remarks |
---|---|---|---|
Team Meeting #10 | 1 hour | Meeting | Meeting Information |
Taking notes during the team meeting | - | Planning | I was the note taker in this meeting. It does not take extra time. |
Preparing meeting notes for Team Meeting #10 | 40 minutes | Documentation | Meeting Notes and the issue for this task. |
Make research on different frameworks | 40 minutes | Research | I made some individual research on Flask, Django and .NET. |
Total Time: 2h 20m
Summary: This week, it was like a break for me after such a busy week. Participated in the meeting and conversations about the planning for the Practice App.
Week 9
Task | Duration | Type of Work | Remarks |
---|---|---|---|
Making research about dockerization and documenting it | 2.5 hours | Research & Documentation | I studied docker and prepared Docker Research Report. The relevant issue can be found on #140. |
Checking the other research reports about Practice App prepared by the other members | 45 minutes | Research | |
Team Meeting #11 | 1 hour | Meeting | Meeting Information |
Database Foundation Team Meeting | 1.5 hour | Meeting | To create the basis for the database structure, participated in the meeting with other team members, namely Aziza Mankenova and Mehmet Emin İpekdal. The planning after the meeting can be found here. |
Working on the foundation of basis for the database structure of Practice App | 3 hours | Practice App - Database Foundation | - Created a plan for the database foundation team in #148. - Created the relevant branch in the repository. - Added basic __init.py__ & models.py files to the branch that I created. The progress of this job can be observed in #149. |
Total Time: 8h 45m
Summary: Since we had decided to divide into teams for building the basic structure before we start to implement our parts, and I was in the database foundation team, I actively worked on tracking the job and added the basic files to the branch that I created. Observed the progress in the repository closely.
Week 10
Task | Duration | Type of Work | Remarks |
---|---|---|---|
Implementing the ArtItem , ForumPost , PostComment , and EventDiscussionComment models for the database basis |
1.5 hour | Practice App - Implementation | Issue and Commit |
Reviewing the implementations of Event , Participant , User , Artist models for the database basis |
30 minutes | Practice App - Implementation | Issue and Commit |
Team Meeting #12 | 2.5 hours | Meeting |
Meeting Information In this meeting, we merged all the fundamental structures that we prepared (front-end basis, back-end basis, and database basis). I actively monitored the pull requests and the structure in the other branches, during the meeting. We made sure that everything was correct before merging. You can check my review on one of the pull requests. |
Total Time: 4h 30m
Summary: Started the implementation with the basics. Reviewed the works of the other team members both during the meeting and regularly through our repository. Also, participated in the planning of our future work in Meeting #12. I am able to catch up with our progressive work.
Week 11
Task | Duration | Type of Work | Remarks |
---|---|---|---|
Team Meeting #13 | 1 hour | Meeting | Meeting Information |
Implementing the Admin , and Copyright models for the database basis |
1 hour | Practice App - Implementation | Issue and Commit |
Attending PS partially | 1 hour | Meeting | |
Creating the Docker configuration with Erim Erkin Doğan | 1 hour | Practice App - Implementation | Details |
Research and individual study on back-end implementation in Flask | 45 minutes | Research | |
Research and individual study on JavaScript and HTML | 45 minutes | Research | |
Working on the Art Item related endpoints | 3 hours | Practice App - Implementation | Details |
Total Time: 8h 30m
Summary: This week, I advanced in the implementation. I worked on database, front-end and back-end simultaneously. Since the time is ticking, it can be said that I need to work more intensely in order to get the deliverables ready before the deadline.
Week 12
Task | Duration | Type of Work | Remarks |
---|---|---|---|
Team Meeting #14 | 1 hour 20 minutes | Meeting | Meeting Information |
Completing the back-end and front-end for Art Item related endpoints | 4 hours | Practice App - Implementation |
Main tracking issue Pull requests: #193, #206 Other: Commit, Issue Comment, Commit |
Finalizing requirements related to Art Items and creating a template page on Wiki | 1.5 hours | Design | Issue and Page |
Preparing the template for software design documents on Lucidchart | 1 hour | Design | Details |
Completing software design documents related to Art Items | 3 hours | Design | Details |
Testing Art Item related endpoints with Postman and documenting the results | 2 hours | Practice App - Testing | Issue and Revision |
Team Meeting #15 | 1 hour 20 minutes | Meeting | Meeting Information |
Unit testing for art item related endpoints | 3 hours | Practice App - Testing | Issue and Commit |
Preparing Swagger documentation configuration and template, and completing my API documentation | 2 hours | Practice App - Documentation | Issue, Commit, Commit |
Code reviews | 3 hours | Practice App - Implementation |
Pull requests: #201, #202, #205, #209, #215 Other reviews: Bootstrap Integration, Endpoint Naming, Unit Testing |
Completing the Project Plan deliverable | 3.5 hours | Planning | Issue, Practice App - Project Plan and Main Project Plan |
Evaluation of tools for Swagger, Docker, and ProjectLibre on Milestone 2 Group Report | 45 minutes | Documentation | Details |
Filling individual contributions table on Milestone 2 Group Report | 2 hours | Documentation | Details |
Finalizing the software diagrams, exporting files and preparing the final report for submission | 2 hours | Documentation | Details |
Completing the Individual Milestone Report | 6 hours | Documentation |
Total Time: 36h 25m
Summary: For Milestone 2 deliverable, I pushed my limits both in implementation and documentation. I completed my part in full including testing and documentation. Reviewed the repository, the code, and the application. Documented my work clearly, with details in every step. Played a crucial role while preparing the group deliverables. Apart from those, prepared a detailed and explanatory individual report with utmost meticulosity.
Week 1
Task | Duration | Type of Work | Remarks |
---|---|---|---|
Team Meeting #1 | 1 hour 30 minutes | Meeting | Meeting Information |
Prepare meeting notes for Team Meeting #1 | 40 minutes | Documentation | Meeting Notes and the issue for this task. |
Update the Class Diagram with Demet Yayla | 1 hour 30 minutes | Meeting & Design | Revision and the issue for tracking |
Update the Project Plan | 2 hours 30 minutes | Planning | Revision and the issue for tracking |
Review if our new team members are added to our Wiki page and make revisions if necessary | 40 minutes | Documentation | Issue and commit for updating README |
Review the Customer Questions | 20 minutes | Design | Issue comment |
Review the updates in the Sequence Diagram for Discussion Posts | 20 minutes | Design | Issue comment |
Total Time: 7h 30m
Summary: It was a quick start for the new semester. I participated in the revision of new documents and onboarding process for our new friends. I made updates according to our new Requirements and closely followed the process. Therefore, I was able to remember the details of our project and I am now ready for the development.
Week 2
Task | Duration | Type of Work | Remarks |
---|---|---|---|
Team Meeting #2 | 1 hour 30 minutes | Meeting | Meeting Information |
Mobile Team Meeting #1 | 1 hour | Meeting | Meeting Information |
Prepare Mobile Team Meeting Notes # 1 | 40 minutes | Documentation | Meeting Notes and the issue |
Implement Home Page for Mobile | 7 hours | Implementation |
Tracking issue: #265 Pull request: PR #266 Some significant commits: 867e235, c43d610, ef16183d |
Total Time: 10h 10m
Summary: This week was an introduction to Flutter for me and I am very happy to be able to deliver such a nice looking homepage. I think we had some coordination issues between different teams (and even among our own sub-team) but we should be able to work better as we proceed with the development.
Week 3
Task | Duration | Type of Work | Remarks |
---|---|---|---|
Mobile Team Meeting #2 | 40 minutes | Meeting | Meeting Information |
Prepare Mobile Team Meeting Notes # 2 | 1 hour | Documentation | Meeting Notes and the issue |
Review the Profile Page for Mobile | 1 hour 30 minutes | Implementation | - Pull Request Review (requested changes) - Merge Commit - Issue conversations are also available. |
Review the User Provider implementation for Mobile | 40 minutes | Implementation | - Pull Request Review (approval) - Issue comment |
Total Time: 3h 50m
Summary: Since the Mobile Team was ahead of the Project Plan and I have completed my part earlier than expected, this week, I mostly focused on the reviews of my friends' code. Next week, we are planning to catch-up with the back-end team as well, so that everything should be integrated to each other.
Week 4
Task | Duration | Type of Work | Remarks |
---|---|---|---|
Team Meeting #3 | 1 hour 40 minutes | Meeting | Meeting Information |
Team Meeting #4 | 1 hour 40 minutes | Meeting | Meeting Information |
Mobile Team Meeting #3 | 45 minutes | Meeting | Meeting Information |
Extra Mobile Team meetings for organization | 2 hours | Meeting | We held some occasional meetings among our sub-team. I participated in those and even had a session in which I helped Ali Can Milani for his environment setup. |
Revise and update the Sequence Diagram for Annotations | 40 minutes | Design | #240, Revision |
Fix Comment and Discussion Post structure designs | 1 hour | Design | #296 |
Customize the Home Page for Guest Users | 40 minutes | Implementation | #313 |
Implement Event Page with endpoint integrations | 10 hours | Implementation | This part of the implementation took an extremely long time as we were not able to have a consistent format with the back-end team. The design of the models took so much time. Also, I needed to learn many things about Flutter as well. #316, #330, PR #348 |
Add tests for the Event Page | 1 hour 30 minutes | Testing | #361, PR #364 |
Implement Art Item Page UI and models | 5 hours | Implementation | #316, #331, PR #365 |
Merge the development on android into the develop branch | 30 minutes | Implementation | PR #328 |
Update the App Name and design for Mobile | 40 minutes | Implementation | #350, PR #352 |
Prepare for the Customer Presentation and present it | 1 hour | Presentation | #353 |
Prepare the Use Case and Class Diagram deliverables and upload them | 30 minutes | Milestone Report | #329 |
Write Individual Contributions in Milestone Report | 1 hour 30 minutes | Milestone Report | Commit |
Review the merging of the development on front-end into the develop branch | 20 minutes | Implementation | PR #324 |
Review Art Item endpoint integrations | 20 minutes | Implementation | #339, Issue comment |
Review the back-end connections for the Register form | 20 minutes | Implementation | #318, PR #320 |
Review the tests for Register Page | 20 minutes | Testing | #359, PR #360 |
Review Home Page endpoint integrations | 40 minutes | Implementation | #351, PR #362, Requested changes, Issue comment |
Review .env file configuration | 20 minutes | Implementation | #357, PR #363 |
Review the tag created for our release | 20 minutes | Implementation | #368, Issue comment |
Total Time: 31h 45m
Summary: An extraordinary week! I worked extremely hard in order for our team to be able to deliver the product before the Milestone and I believe my performance was exceptional. That being said, I think another reason for many team members being have to work that hard was that we were not on the same page with the back-end team until the very last days. We needed more precise endpoints with detailed documentation, and tests and hopefully with no bugs. We could not plan our implementation phase as detailed as we were supposed to, especially for the back-end team, and this was the result.
Week 5
Task | Duration | Type of Work | Remarks |
---|---|---|---|
Team Meeting #5 | 1 hour 40 minutes | Meeting | Meeting Information |
Mobile Team Meeting #4 | 45 minutes | Meeting |
Meeting Information |
Prepare Mobile Team Meeting Notes #4 | 40 minutes | Documentation | Meeting Notes and the issue |
Review Android CI workflow | 20 minutes | Implementation | PR #412 |
Review the Removal of Optional Fields in Signup Page | 20 minutes | Implementation | #410 |
Fix a bug in the Event Page widget test | 40 minutes | Implementation | #405 |
Start to work on Home Page updates related to Posts | 1 hour | Implementation |
Total Time: 5h 25m
Summary: A relatively relaxed week after Milestone 1. Although we had a great customer presentation, we also had some significant feedback and started to implement them. I could not allocate as much time as I planned for this week but reviewed my team's work and started to work on my part.
Week 6
Task | Duration | Type of Work | Remarks |
---|---|---|---|
Team Meeting #6 | 1 hour 40 minutes | Meeting | Meeting Information |
Mobile Team Meeting #5 | 20 minutes | Meeting |
Meeting Information |
Complete post widgets in Homepage | 6 hours | Implementation | #442, PR #444 |
Start to work on fixes for Homepage endpoint and images | 3 hours | Implementation | #445, PR #471 |
Review the Geotagging feature | 30 minutes | Implementation | #439, PR #443 |
Total Time: 11h 30m
Summary: This week, I focused on my parts for finalizing our Homepage. I completed the implementation of the Post model, which is the parent of Event and ArtItem models in this newly formed inheritance relationship. I still need to complete some additional fixes such as correcting the way we handle images and updating the endpoint integrations for our team.
Week 7
Task | Duration | Type of Work | Remarks |
---|---|---|---|
Team Meeting #7 | 1 hour | Meeting | Meeting Information |
Complete the fixes for Homepage endpoint and images | 3.5 hours | Implementation |
#445, PR #471 My pull request was not merged into the develop since the issue with the homepage was fixed in a different branch, in a different way. I contributed to the final functions that are used in the fixed Homepage. Additionally, participated in the discussions about the Homepage's situation and provided my team with code segments, referring to my commits in this branch. |
Contribute to fixing the image processing issue | 40 minutes | Implementation | Commit, PR #494 |
Review the Art Item model fix | 40 minutes | Implementation | #484, PR #485, Approval with feedback |
Review the updates in develop branch into master for deployment | 20 minutes | Implementation | PR #478 |
Start implementing user profile settings | 2 hour | Implementation | #481, PR #505 |
Total Time: 8h 10m
Summary: This week, I managed to complete the tasks about Homepage. Although my pull request was not merged since we were not coordinated well and multiple people in the Mobile Team worked on a similar task, our team utilized my code. Additionally, I provided code segments and functions for the developments in other branches. After the fixes for the Homepage were done, I started to work on the new feature that I was assigned to integrate which is User Settings Page.
Week 8
Task | Duration | Type of Work | Remarks |
---|---|---|---|
Team Meeting #8 | 1 hour | Meeting | Meeting notes are not available for this meeting as only the current situation in our development was reviewed. |
Complete User Profile Settings implementation | 8 hours | Implementation | #481, PR #505 |
Add widget tests for Settings Page | 2 hours | Testing | #528, PR #529 |
Implement the UI for Image Annotations | 6 hours | Implementation | #507, PR #524 |
Review the Comment feature | 2 hours | Implementation | #486, PR #519, Requested changes, Final approval |
Review the Follow feature | 30 minutes | Implementation | #435, PR #499, Approval with feedback |
Review the updated Project Plan | 1 hour | Planning | Tracking issue |
Prepare the scenario for the presentation and present the mobile part | 1.5 hours | Planning & Presentation | Issue comment |
Total Time: 21h
Summary: Another busy week before the customer presentation! I was able to deliver most of my work and I tracked the development in the Mobile Team very closely by providing feedback, requesting changes and approving with additional remarks etc. Even though I could not complete implementing the UI for Annotations, I was able to show the most crucial parts in the customer presentation. We also had a successful customer presentation for Milestone 2 as well.