-
Notifications
You must be signed in to change notification settings - Fork 1
Timesheet Elif
BElifb edited this page Jan 3, 2023
·
32 revisions
Week 1
Hours spent | Task Type | Task Description |
---|---|---|
2 hours | planning | Attended weekly meeting/lab. |
15 minutes | documentation | Caught up with the repo updated necessary things. |
Week 2
Hours spent | Task Type | Task Description |
---|---|---|
1 hour 45 minutes | planning | Attended weekly meeting/lab. |
2 hours | planning | Attended weekly meeting. |
2 hours | revision/documentation | Revised the requirements, critically revised Bidding system, Notifications, Level and Verification systems. Here are related issues GEN-10, GEN-11, GEN-14, GEN-15 |
30 minutes | coding/upkeep | Updated issue template to include new member GEN-12. |
15 minutes | documentation/wiki | Updated questions and answers page GEN-13. |
Week 3
Hours spent | Task Type | Task Description |
---|---|---|
1 hour 45 minutes | planning | Attended weekly meeting/lab. |
30 minutes | documentation | Updated Bidding System requirements in accordance with last group meeting's decisions.GEN-14 |
30 minutes | code review | Reviewed the initial for pull request. Pull request |
5 hours | Research/Implementation | Researched authentication and authorization to set up the initial structure of the project the correct way. Implemented initial models. BE-4, Pull request |
30 minutes | planning | Attended backend catch-up meeting. |
2 hours | coding/documentation | Wrote the issue for initial models. Implemented serializers, decorator and created/configured admin site. commit |
40 minutes | coding | Implemented initial homepage with templates. commit |
30 minutes | coding | Merging the branch, some updates. comment |
45 minutes | research/review | Extra research about alternative methods of authentication, checking new commits to the repo. |
45 minutes | research | Researching CI/CD. BE-11 |
Week 4
Hours spent | Task Type | Task Description |
---|---|---|
2 hours | planning | Attended weekly meeting/lab. |
45 minutes | documentation | Created wiki page for best django practices, and research links. GEN-26 |
3 hours | implementation | Implemented alternative register (and part of logout) API's that use django authentication rather than Knox. |
5 hours | devops | Setting up Docker. |
2.5 hours | learning/implementation/devops | Learned how to use GitHub Actions. Implemented a workflow including testing and dockerization. Need to make some updates for testing. BE-11 Pull Request |
1.5+ hours | reviewing | Keeping up with repo, reviewing/updating mockups. GEN-19 |
- | planning | Naming the app GEN-28 |
1.25 hours | documentation | Updating timesheets. |
2 hours | planning | Preparing for Milestone presentation. |
1.1 hours | documentation | Preparing Personal Contribution report for milestone deliverables. |
Week 5
Hours spent | Task Type | Task Description |
---|---|---|
1 hour | documentation | Organized and added BE Meeting#2 notes to wiki. Issue link |
35 minutes | documentation | Adding work summary and work performed to Group Review Report, updating timesheet. |
Week 6
Hours spent | Task Type | Task Description |
---|---|---|
1 hour 15 minutes | review | Reviewed the Swagger PR. feature/BE-14 |
5 hours | research/coding | Researched for and coded the Reset Password APIs. Researched for sending automated emails through the app. Tested through the terminal. PR:Feature/be 19 , Issue:#254 |
20 minutes | review | Reviewed the hotfix PR. hotfix/BE-14 |
5 hours | research/coding | Researched alternative ways for Reset Password APIs (django-otp), implemented password update API. PR:Feature/be 19 |
4 hours | research/coding | Updated comment model using django-mptt. Implemented Comment APIs. PR:Feature/be 20, Issue:#261 |
1 hour | coding/documentation | Added swagger documentaton for comment APIs. |
Week 7
Hours spent | Task Type | Task Description |
---|---|---|
2.5 hours | coding | Updated comment get APIs to not require login. related comment |
Week 8
Hours spent | Task Type | Task Description |
---|---|---|
1h+ hour | coding | Configured production email settings, solved merge conflicts and and merged. related comment |
6.5 hours | devops/coding | Created Github Workflow for building and pushing docker images to Github Packages. PR:Feature/BE11, issue |
2 hours | research | Researched annotation. |
Week 9
Hours spent | Task Type | Task Description |
---|---|---|
1 hour | review | Reviewed,fixed account deletion API PR. PR:feature/BE-27 Account deletion API |
1 hour | research | Researched annotation. |
0.5 hour | research/upkeep | Investigated frontend code to add quasi-static content for milestone demo. |
Week 10
Hours spent | Task Type | Task Description |
---|---|---|
2 hours | documentation | Wrote executive summary for milestone2 report. #295 |
2 hours | documentation | Wrote the timesheet. |
Week 11+
Hours spent | Task Type | Task Description |
---|---|---|
6 hours | coding | Added user history as a separate app, created model, and signals, connected. feature/BE-32 : User History issue |
5 hours | review | Reviewed PR BE-30. |
2 hours | coding | Updated art item category, predefined choices. feature/BE-35: Art Item Category issue |
1 hour 30 minutes + | research | Researched for recommendation system. |
4 hour 30 minutes | coding | Created level system. feature/BE-36: User Level issue |
2 hours | coding | Created models for bidding system. feature/BE-38: Bidding System issue |
4 hours | coding | APIs for the bidding system. feature/BE-38: Bidding System issue |
4 hours | coding | Created APIs for updating art item sale status, list of newly bidded art items in profile page. feature/BE-38: Bidding System issue |
12 hours | coding | Created recommendation system. feature/BE-40: Recommendation System issue |
30 minutes | review | Reviewed unittest PR. feature/BE-39: Backend Unittests [1] |
30 minutes | coding | Bugfix PR. hotfix/BE-38: new_bids reset |
8 hours | testing/coding/learning | Created tests for Recommendation and Bidding systems. feature/BE-43: Backend Unittests [2] issue |
8 hours | documentation | Reviewing updating requirements for release and milestone. Updating use case diagram, part of executive summary, personal reports. MIL-22: Software Requirements Specification, MIL-29: Status of the requirements, MIL-32: Use Case Diagram Update, MIL-39: Executive/ what could have been done differently |
? | planning | Took part in all of the backend and general meetings. |
? | learning/planning | Attended all of the classes and PSs. |
Week 1
Week | Hours spent | Task Type | Task Description |
---|---|---|---|
1 | 3 to 3,5 hours | git/github | Learned about general workings of git and github through these videos vid 1, vid 2, vid 3, vid 4 and these pages page 1 , page 2. |
1 | 30 minutes | git/github | Played around with very basic git concepts (creating branches etc.) via following this. |
1 | 1.15 hours | markdown/wiki | Learned about markdown and wiki pages through here, here, here, here,this page and that page and created and organized my personal wiki page. |
1 | 1.5 hours | research | Researched and wrote about favorite repositories. |
1 | 30 minutes | documentation | Added some useful resources and explanations about git&github. |
1 | 1-2 hours | research | Browsed previous years' CMPE352/CMPE451 repositories. |
1 | 1.2 hours | project planning | Attended 2 meetings first meeting and second meeting. |
1 | 1 hour | learning | Attended PS. |
1 | 1.5 hours | documentation | Wrote this very list and the Time-Tracking report. Took a bit long to put together all the links 😅 . |
Week 2
Week | Hours spent | Task Type | Task Description |
---|---|---|---|
2 | 1.5 to 2 hours | research & documentation | Researched various websites as examples and wrote about 3 of my favorites to the Research about Art Page |
2 | 1 hour | studying | I studied the project description in detail and made a list of questions to be discussed in the meeting and the PS. |
2 | 1 hour | documentation | Took notes during meeting#4 and organized them by creating a wiki page. Here's the related issue that I've created. |
2 | 1 hours | research & documentation | Researched Non-Functional requirements and added my part to the requirements wiki page. Here's the related issue that I have created. |
2 | 45 minutes | documentation | Made additions to the glossary and created the related issue |
2 | 1.5 hours | learning | Attended PS. |
2 | 3 hours | project planning | Attended 2 meetings. Meeting#3 and Meeting#4 |
2 | 35 minutes | documentation | Wrote this list. |
Week 3
Hours spent | Task Type | Task Description |
---|---|---|
30 minutes | research | Went through some scenario/mockup examples from previous years. |
2 hours 15 minutes | documentation/design | Designed the pages for Add Art Item and Successful Addition for scenario 2. |
20 minutes | documentation | Created the issue for the second scenario. |
1.5 hours | documentation/design | Added the persona, preconditions and the acceptance criteria for scenario 2. |
1.5 hours | learning | Attended PS. |
1.5 hours | project planning | Attended Meeting#5 |
16 minutes | documentation | Wrote this list. |
Week 4
Hours spent | Task Type | Task Description |
---|---|---|
1 hour 45 minutes | project planning | Attended Customer Meeting 1 /PS |
4 minutes | documentation | Wrote this list. |
Week 5
Hours spent | Task Type | Task Description |
---|---|---|
1.5 hours | research/studying | Studied the slides, some online resources and past years' repos about UML diagrams. |
2 hours 30 minutes | Project Planning | Attended Meeting#7 and actively participated in the discussion. We decided on main types of classes, how to distinguish different types of users, the main actions for the use case, key scenarios for the sequence diagram and more. |
2 hours 45 minutes | revision/software design | Revised what had already been done to the Use Case diagram (in accordance with Meeting#7). Made some changes and additions and suggested some more. Comments can be seen below the issue |
1 hour 30 minutes | revision/software design | Examined the current state of the class diagram, created <>NotificationType and specified the fields and functions of Notification & <>NotificationType. Created the issue for the class diagram. |
2 hours 30 minutes | Project Planning | Attended Meeting #8. Actively participated in discussions. I think we changed the structure of the exhibition in use-case in this meeting and some revisions and more. |
2 hours | Project Planning | Attended Meeting#9. Again actively participated. Highlights are; we made changes to search engine and changed class structure of the bidding system on this one. |
1 hour 30 minutes | software design | The classes of bidding system needed some attention after Meeting#9's changes. So I added some fields and functions. Here's the related comment. |
1 hour | project planning | Made the first draft for sequence diagram for bidding on an item case. But this won't be the final version after reviewing it in Meeting#10(PS). But folks that's it for week5, stay tuned to see what happens next week. |
50 minutes | documentation | Wrote this list. |
Week 6
Hours spent | Task Type | Task Description |
---|---|---|
1 hour | repo enhancement | Created issue templates. |
1 hour 45 minutes | project planning | Attended Week6 Meeting #10 (06.04.2022) (PS). |
1 hour | documentation | Put together meeting notes for Week6 Meeting #10 (06.04.2022) (PS), added it to wiki. Here's the related issue that I have created. |
30 minutes | documentation | As discussed in Meeting#10 created the issue for Work done part of Milestone1 report. |
2 hours 40 minutes | software design/revision | Redesigned the sequence diagram for bidding on an art item, after revisions of last weeks PS and added it to lucidchart. |
1.5 hours | design/documentation | Rewrote bidding system requirements in accordance with the updates, added 1.2.4.1 through 1.2.4.18. Here's the related issue that I have created. |
25 minutes | design/documentation | Updated Scenario2 preconditions and acceptance criteria. Here' the related issue |
1 hour | research | Made research for Milestone1 report. Went through the description and previous years' repos. |
1 hour | project planning | Attended Meeting#11. We made some changes to the sequence diagrams, non-functional requirements and made decisions about the Milestone1 report. |
44 minutes | documentation | Wrote this list. |
Week 7
Hours spent | Task Type | Task Description |
---|---|---|
20+ hours | Unfortunately this week I was unable to track exactly how much time I spent on each task. I worked on a lot of things that were intertwined, also we were constantly communicating and switching between tasks for a good while. My estimate is that I spent a bit over 20 hours in total (excluding what's specified in terms of time below) working on CMPE352 related tasks this week. Here's the rundown. | |
review/documentation/design | I reviewed the entire Requirements, modified/added several things. Here are the related issues: #56, #75, #68, #35. Please refer to comments for more detail. | |
documentation/design/project planning | Created Project Plan with Sinem, Furkan and Karahan. Here's the related issue that I created #80. | |
review/design | Reviewed the designs and made/suggested some modifications. Especially to sequence and class diagrams. Here are the related issues: #50, #49 and #47. Please refer to comments for more detail. | |
documentation/design/project planning | Worked on the milestone report in general, and created the template for and wrote my personal work summary. Here are the related issues: #73, #65. | |
2+ hours | learning | Attended PS, discussed work summary details and which tool to use for project plan. |
1 hour | project planning | Attended Meeting#12 |
1 hour | research/learning | Started researching about API's. |
58 minutes | documentation | Wrote this list. |
Week 8
Hours spent | Task Type | Task Description |
---|---|---|
1 hour | research/learning | Watched Rest API Crash Course |
30 minutes | research/learning | Watched Python + Deploy to AWS |
2 hours | research/learning/implementation | Researched about and created my first push & pull request. Here's the related issue #83. |
3 hours | repo enhancement | Created 3 yml issue templates, committed to the repo created pull request #84, #60. Tested the templates #85. |
1.5 hours | learning | Studied git, mostly from PS slides. |
2+ hours | learning | Attended PS, learned about git. |
27 minutes | documentation | Wrote this list. |
Week 9
Hours spent | Task Type | Task Description |
---|---|---|
2+ hours | research/learning | Researched about different API's we could use for the practice app and the usage of API's in general. |
2+ hours | research/documentation | Researched about tools for the practice app such as Docker and AWS. Created the Research on Docker page #88(related issue) and contributed to Research on AWC #87(related issue). |
1+ hours | project planning | Attended Meeting#14,discussed practice app API's. |
12 minutes | documentation | Wrote this list. |
Week 10
Hours spent | Task Type | Task Description |
---|---|---|
Countless hours (seriousy way too many) | research/learning | Researched and learned about Django and web development in general. (+ REST API's) |
2 hours | project planning | Attended Meeting#15, actively participated, created ER diagram for practice app, allocated implementation tasks. |
3 hours 45 minutes | implementation | Created the initial database for practice app, via use of django models. (This task was allocated to Karahan and I, there were many later changes and improvements.) Pull request #96 |
22 minutes | documentation | Wrote this list. |
Week 11
Hours spent | Task Type | Task Description |
---|---|---|
2 hours | learning | Attended PS. |
4+ hours | reviewing/coding | Went over Karahan's changes for the models, changed a few things myself. Pull request |
1 hour | research/learning | Researched implementation of unit tests (for django). |
6.5 hours | coding | Created the search by tag API, along with the interface for it. Pull request #107 #111 |
2 hours | coding | Created the frontend html templates for homepage and base html. Pull request #109 #110 |
1 hour | coding | Worked on an API for creating new tags. This was just for practice, I didn't upload it to the repo. |
4.5 hours | coding | Implemented testing for search by tag. #107 |
2 hours | project planning | Attended Meeting#16, actively participated. |
30 minutes | documentation | Wrote this list. |
Week 12
Hours spent | Task Type | Task Description |
---|---|---|
2+ hours | learning | Attended PS. I think this one sort of turned into a group meeting in the end and exceeded the timeslot. |
1.5 hours | research/learning | Researched and learned about Docker. |
45 minutes | reviewing code | Reviewed and merged the pull request for feature/users_frontend branch. Pull request |
3+ hours | implementation/coding | Created questions API along with frontend and testing. Pull request #139 |
2+ hours | reviewing/project planning | We met over discord, went over the status of the project, corrected some things, answered some teammates questions. This wasn't an official meeting. |
1.25 hours | reviewing | Helped a teammate with their questions. |
2 hours | documentation | Wrote API documentation for my APIs. Made some contributions to the Milestone 2 report. #116 |
30 minutes | documentation | Made additions to the requirements. #121 |
~8 hours | documentation | Created 3 sequence diagrams, contributed to the usecase diagram, made my personal effort table for milestone 2 group report. Created individual report for milestone 2. #125, #126 |
35 minutes | documentation | Wrote this list. |
Milestone1 Work Summary
Task Type | Task Description |
---|---|
Research/Learning | Researched and learned how to use git & github. |
Research/Learning | Researched and learned how to use markdown, organize wiki pages. |
Documentation | Created and organized my personal wiki page. |
Research/Documentation | Researched and wrote about favorite repositories. |
Documentation | Added some useful resources and explanations about git&github to Research on Git page. |
Research | Made lots of research at different points, examined previous years' CMPE352/CMPE451 repositories. About mock-ups, UML's, Milestone etc. |
Project Planning | Attended all of the weekly meetings. Actively participated in the discussions. Meeting#1, Meeting #2, Meeting #3, Meeting #4, Meeting #5, Meeting #6, Meeting #7, Meeting #8, Meeting #9, Meeting #10, Meeting #11. |
Learning | Attended all of the problem sessions. |
Documentation | Kept time throughout the semester and filled the weekly timetable |
Research/Documentation | Researched various websites and wrote about 3 of my favorites to the Research about Art Page |
Documentation | Took notes during Meeting#4 and Meeting#10, created/organized their wiki pages. Here are the related issue4 and issue10 that I created. |
Research/Design | Created part of non-functional requirements. Here's the related issue that I created. |
Design/Documentation | After customer meetings' changes rewrote System-Bidding System Requirements. Here's the related issue that I created. |
Design/Documentation | Made several contributions to the glossary. Here's the issue that I created. |
Design/Documentation | Designed the pages for Add Art Item and Successful Addition, created/added the persona, preconditions and the acceptance criteria for scenario 2. Here's the related issue that I created. |
Research/Learning | Studied the slides and some other online resources about UML. |
Software Design | Designed the main components of the UMLs in week5's meetings, along with other team members. |
Software Design | Made contributions to the Use-case diagram. Especially to exhibition and bidding system. Here's the related issue |
Software Design | Made contributions to the Class diagram. Especially to Notification, NotificationTypes, ArtItem, ItemBids and Bid classes. Here's the related issue that I created. |
Software Design | Designed the bid for an item sequence diagram. Here's the related issue. |
Software Design | Went over the diagrams multiple times, along with other team members. |
Enhancement | Created issue templates. Here's the related issue that I created. |
Documentation/Milestone | Created the issue for Work done part of Milestone1 report. Designed a basic template and wrote my part. |
Design/Documentation | Updated Scenario2 preconditions and acceptance criteria. Here' the related issue |
Project Planning/Milestone1 | Planned Milestone1 report in meetings along with other team members. |
Project Planning/Milestone1 | Wrote my part of the project plan. Here's the related issue that I created. |
Design/Documentation | Reviewed the entire requirements made several changes. Here's the related issue |
Project Planning/Milestone1 | Reviewed Milestone1 report. |
Note I attended all of the lectures as well, didn't add them to the tables as it was given.
Note2: I was also checking the repo, and reviewing the changes made, communicating with teammates frequently during the last few weeks of the practice app, but ofcourse didn't track time for all of that.
Home 🏠
- Conventions
- Elevator Pitch
- Project Description
- Project Plan
- Scenarios and Mockups
- Requirements
- Diagrams
- Milestone Report I
- Serdar Akol
- Sena Mumcu
- Karahan Sarıtaş
- Mustafa Cihan
- Serhat Hebun Şimşek
- Elif Bayraktar
- Doğukan Türksoy
- Furkan Keskin
- Sinem Koçoğlu
- Metehan Dündar
- Mustafa Emre Erengül
- Favourite Github Repositories
- Research on Git
- Research on Art Community Platforms 🎨
- Research on Django
- Research on Docker 🐳
- Research on AWS EC2 ☁️
- Research on Postman
- Research on Frontend Tools
- Django Practices 💯
- Serdar Akol
- Sena Mumcu
- Karahan Sarıtaş
- Mustafa Cihan
- Serhat Hebun Şimşek
- Elif Bayraktar
- Doğukan Türksoy
- Furkan Keskin
- Sinem Koçoğlu
- Metehan Dündar
- Mustafa Emre Erengül
- Week1 - Meeting #1 (04.10.2022)
- Week2 - Meeting #2 (11.10.2022)
- Week2 - Meeting #3 (16.10.2022)
- Week4 - Meeting #4 (25.10.2022)
- Week5 - Meeting #5 (02.11.2022)
- Week9 - Meeting #6 (29.11.2022)
- Week10 - Meeting #7 (07.12.2022)
- Week 3- FE Meeting #1 (18.10.2022)
- Week 5- FE Meeting #2 (02.11.2022)
- Week 7- FE Meeting #3 (15.11.2022)
- Week 3- BE Meeting #1 (18.10.2022)
- Week 5- BE Meeting #2 (02.11.2022)
- Week 7- BE Meeting #3 (15.11.2022)
- Week 9- BE Meeting #4 (29.11.2022)
- Week 11- BE Meeting #5 (13.12.2022)
- Week 3- MOB Meeting #1 (18.10.2022)
- Week 5- MOB Meeting #2 (02.11.2022)
- Week 7- MOB Meeting #3 (16.11.2022)
- Week 8- MOB Meeting #4 (26.11.2022)
- Week1 - Meeting #1 (01.03.2022)
- Week1 - Meeting #2 (05.03.2022)
- Week2 - Meeting #3 (09.03.2022)
- Week2 - Meeting #4 (13.03.2022)
- Week3 - Meeting #5 (20.03.2022)
- Week4 - Meeting #6 (23.03.2022) Customer Meeting - I
- Week5 - Meeting #7 (01.04.2022)
- Week5 - Meeting #8 (04.04.2022)
- Week5 - Meeting #9 (05.04.2022)
- Week6 - Meeting #10 (06.04.2022) (PS)
- Week6 - Meeting #11 (12.04.2022)
- Week7 - Meeting #12 (14.04.2022)
- Week9 - Meeting #13 (26.04.2022)
- Week10 - Meeting #14 (01.05.2022)
- Week11 - Meeting #15 (10.05.2022)
- Week11 - Meeting #16 (15.05.2022)