Berk Atıl Time Tracking - bounswe/2021SpringGroup6 GitHub Wiki
CmpE 451
- I discussed our requirements and and sequence diagrams with my team members and also our customer.
- I changed one of the sequence diagrams (commit)
- I studied Django, I learn the basics. I understood how to to structure the project.
- I initialized our back-end API (Related commits are below, related PR is here)
- Initialization commit: Here I initialized our API with Django
- Requierments and conda yml commit: Here I added a requirements file with specific library versions and also exported my conda environment so that we have a consistency. As a result, the problems related to library versions will be minimized.
- Secret key deletion: I deleted the django secret key which was pushed by mistake.
- Validators and basic models: I added some validators and some db models.( The related PR is here)
- Block table model : I added the db model and validator for blocking relationship. (The related PR is here)
- User model change: Since we decided to use authorization system in Django, I changed the definition of User model. (The related PR is here)
- I studied how to configure postgresql in Django (Related commits are below)
- I started writing Register endpoint (Related commits are below and the related PR is here)
- Beginning of Register Endpoint: I started writing an endpoint for register functionality.
- I continued working on Register endpoint (Related commits are below)
- Tests and bug fix: I added unittests and also as we talked with Elif, I changed the code to sent the validated data
- Sport name model change: I changed the primary key of the Sport model to its name because it will be easier to add user skill levels during registration.
- Bug fix about user validator and deletion of unnecessary checks in register endpoint.
- Bug fix about the user validator and adding more meaningful response mssage
- Message filed into the response: As we talked with Elif, I added message field into our response to add response messages. In the future we will also use message codes.
- Register test bug fix and adding path field
- Register bug fix
- Return user object after it is added to the db. We do that to make our job easier during tests
- Register test bug fix
- I stared working on get user endpoint (Related commits are below, the related PR is here):
- I have added a helper function to create a user for tests(Commit is here, related PR is here)
- I have added docker files(Related commits are below, related PR is here)
- I have added functionality that before application starts, supported sports are added into our database, related commit is here
- I have added the code to get secret keys, passwords etc. from .env file (related commit is here)
- I continued working on Get user end point(Related commits are below)
- As we talked in the group meeting, get user endpoint should check if the user wants to see own data or not. Based on this, information that should be returned should change. For now, we haven't implemented visibility so I have just added the if condition and todo
- I made the get user endpoint compatible with scheme and activity scream
- I fixed the bug stemming from removing authentication
- I implemented get sports endpoint(Related commit is here, related PR is here)
- I started implementing update user endpoint(Related commits are below, related PR is here).
- I changed the response messages of the register based on the integrity error, also made the transaction atomic(related commit is here, related PR is here)
- I made the gender field character(related commit is here, related PR is here)
- I fixed the bug related to first name, I fixed the bug related to external sports api(Related commits are sports api, name bug, related PR is here)
- I have started implementing Set visibility endpoint(Related commits are below, related PR is here)
- I have started implementing Block endpoint(Related commits are below, related PR is here)
- I have started implementing Delete user endpoint(Related commits are below, related PR is here)
- I have made get sports endpoint compatible with Scheme(Related commit is here, related PR is here)
- I have started implementing Unblock endpoint(Related commits are below, related PR is here
- I have started updating get user endpoint so that visibility checks are done(Related commits are below, related PR is here)
- I have started implementing get blocked users endpoint(Related commits are below, related PR is here)
- I have started implementing get event endpoint(Related commits are below, related PR is here)
- I have started implementing Activity Stream DB model and addition of data into it in related endpoints.(Related commits are below, related PR is here)
- I have started implementing Get Activity Stream Endpoint.(Related commits are below, related PR is here)
- I have started implementing filter/search events.(Related commits are below, related PR is here)
- I have started implementing delete event endpoint(Related commits are below, related PR is here)
- I have started implementing update event endpoint(Related commits are below, related PR is here)
- I fixed the bug in update event endpoint(Related commit is here, related PR is here)
- I changed the get user endpoint so that users cannot see the user pages who blocked them (Related commit is here, related PR is here)
- I have started implementing filter/search users.(Related commits are below, related PR is here)
- I have started implementing sort functionality to event search endpoint (Related commits are below, related PR is here)
- I have started implementing notification functionality (Related commits are below, related PR is here)
- I have started implementing recommendation functionality(Related commits are below, related PR is here)
- I have started implementing filtering activity stream(Related commits are below, related PR is here)
- I have added more visibility options(Related commits are below, related PR is here)
CmpE 352
Date: 27.03.2021
Task: Communication Plan
Details: I created a Wiki Page for our Communication Plan.
Duration: 20 minutes
Type of Work: Documentation
Date: 27.03.2021
Task: Discovering different Github Repositories
Details: I searched for different kinds of Github Repositories to get some intuitions to make repositories easily understandable and also comprehensive.
Duration: 1 hour
Type of Work: Research and Learning
Date: 28.03.2021
Task: Creating a Personal Wiki Page
Details: Firstly I created an issue for this and then I created my personal Wiki Page.
Duration: 25 minutes
Type of Work: Documentation
Date: 28.03.2021
Task: Learning Git
Details: I watched the Git For Ages 4 And Up video and then looked at the tutorial on git-scm.com
Duration: 2 hours
Type of Work: Research and Learning
Date: 03.04.2021
Task: Documenting Non-Functional Requirements
Details: I started to write non-functional requirements by writing the ones that we talked about during the meeting and also did some research about what else can be added.
Duration: 30 minutes
Type of Work: Documentation
Date: 05.04.2021
Task: Analyzing Related Projects
Details: I looked at the related projects and listed some common and missing features
Duration: 30 minutes
Type of Work: Research and Documentation
Date: 06.04.2021
Task: Glossary Contribution
Details: I extracted the terms that should be explained in our Glossary from the Non-Functionalities part of the Requirements
Duration: 30 minutes
Type of Work: Documentation
Date: 07.04.2021
Task: Filling out answers to some of the questions that were asked to the customer
Details: I wrote the answers to some of the questions that we asked during the meeting and also I added small details to the non-functional part of the requirements.
Duration: 20 minutes
Type of Work: Documentation
Date: 14.04.2021
Task: Filling out answers to some of the questions that were asked to the customer
Details: I wrote the answers to some of the questions that we asked via an email.
Duration: 20 minutes
Type of Work: Documentation
Date: 14.04.2021
Task: Creating User Scenario Template
Details: I created a Scenario template so that all of our scenarios are consistent.
Duration: 15 minutes
Type of Work: Documentation
Date: 14.04.2021
Task: Beginning the User Block Scenario
Details: I started to write the user block scenario and finished all parts except Acceptance Criteria
Duration: 1 hour
Type of Work: Documentation
Date: 15.04.2021
Task: User Block Scenario
Details: I finished the acceptance criteria part of the user block scenario and adjusted our requirements. It can be found here
Duration: 20 minutes
Type of Work: Documentation
Date: 15.04.2021
Task: User Block Scenario 2
Details: I created another user block scenario from a perspective of the blocked user. It can be found here
Duration: 20 minutes
Type of Work: Documentation
Date: 15.04.2021
Task: Mockup for a user block scenario
Details: I started creating some mockups for user block scenario. It can be seen here
Duration: 45 minutes
Type of Work: Documentation
Date: 17.04.2021
Task: User Block Scenario
Details: I made small modifications on user block scenarios and created a new small one.
Duration: 15 minutes
Type of Work: Documentation
Date: 17.04.2021
Task: Customer Meeting
Details: We met with our customer and went over our requirements, scenarios, and mockups. Also, we got some feedback to improve our work.
Duration: 120 minutes
Type of Work: Learning and Getting Feedback
Date: 18.04.2021
Task: User Block Scenario
Details: I completed the web mockup part of user block scenario 1,2 and 3. The second one and The third one.
Duration: 30 minutes
Type of Work: Documentation
Date: 20.04.2021
Task: Group Meeting
Details: We discussed about our class diagram. Meeting note can be found here
Duration: 120 minutes
Type of Work: Documentation
Date: 22.04.2021
Task: Group Meeting
Details: We finished the class diagram and discussed about the use case diagram. Meeting note can be found here
Duration: 120 minutes
Type of Work: Documentation
Date: 24.04.2021
Task: Group Meeting
Details: We finished the use case diagram and assigned the tasks related to sequence diagrams. Meeting note can be found here
Duration: 120 minutes
Type of Work: Documentation
Date: 25.04.2021
Task: Creating User Block Sequence Diagram
Details: I created a sequence diagram for blocking a user based on our class diagram and use case diagram. The issue can be found here
Duration: 30 minutes
Type of Work: Documentation
Date: 26.04.2021
Task: Customer Meeting
Details: We met with our customer and went over our UML class diagram, use case diagrams, and also some sequence diagrams. We got some feedbacks to improve our work and will implement these this week.
Duration: 60 minutes
Type of Work: Learning and Getting Feedback
Date: 27.04.2021
Task: Group Meeting
Details: We made some modifications on use case and class diagram based on the feedback from our customer. Meeting note can be found here
Duration: 120 minutes
Type of Work: Documentation
Date: 28.04.2021
Task: Class diagram
Details: I added some functions into our class diagram.
Duration: 30 minutes
Type of Work: Documentation
Date: 29.04.2021
Task: Class diagram
Details: I added the relationships between classes
Duration: 60 minutes
Type of Work: Documentation
Date: 06.05.2021
Task: Tools Evaluation
Details: I created a document to express the tools that we use and their evaluation
Duration: 30 minutes
Type of Work: Documentation
Date: 23.05.2021
Task: Flask Learning
Details: I started learning Flask framework from here and wrote some code in order to practice and understand it better.
Duration: 1.5 hours
Type of Work: Learning
Date: 24.05.2021
Task: Flask Learning
Details: I continued learning Flask framework from here.
Duration: 1.5 hours
Type of Work: Learning
Date: 26.05.2021
Task: REST API
Details: I searched for REST API and understood what it actually means.
Duration: 1 hour
Type of Work: Learning
Date: 29.05.2021
Task: Research on Bitcoin Price API
Details: I searched for an API that provides a way to get the current Bitcoin Price and I found this. I read their API documentation and wrote code to get the Bitcoin Price to use in our API.
Duration: 1.5 hours
Type of Work: Research
Date: 01.06.2021
Task: Creating Post Endpoint for Badge
Details: I start coding about the post endpoint for Badge. I created the model, view, and endpoint itself.
Duration: 2 hours
Type of Work: Development
Date: 05.06.2021
Task: Post Endpoint for Badge
Details: I finished this endpoint with its front-end part. Only unit test is remaining.
Duration: 2 hours
Type of Work: Development
Date: 06.06.2021
Task: Docker Study
Details: I watched the PS videos related to Docker and made some trials
Duration: 2.5 hours
Type of Work: Learning
Date: 07.06.2021
Task: Post Endpoint unit-test
Details: I wrote unit-tests for posting a badge. Also, I added some comments to the code.
Duration: 2.5 hours
Type of Work: Development
Date: 08.06.2021
Task: Get Endpoint for point of a badge
Details: I wrote an endpoint to get point of a badge given its name. Additionally, I fixed some bugs on my previous endpoints(Response code was wrong). Additionally, I added swagger docs for both endpoints. Also, I added a front-end page for get endpoint.
Duration: 3 hours
Type of Work: Development
Date: 08.06.2021
Task: Merging Codes and Dockerization
Details: We merged some codes to master branch. Then, we tested current final version of our program.Afterwards, we dockerize our program.
Duration: 2 hours
Type of Work: Development
Date: 08.06.2021
Task: Code Documentation
Details: I wrote the documentations for the codes that I wrote(post badge and get badge point by name)
Duration: 2 hours
Type of Work: Documentation
Date: 08.06.2021
Task: AWS Research
Details: I researched about how to deploy an application into AWS servers and tried to deploy it. Resources :https://www.youtube.com/watch?v=zs3tyVgiBQQ, https://docs.aws.amazon.com/AmazonECS/latest/developerguide/docker-basics.html
Duration: 2 hours
Type of Work: Learning
Date: 09.06.2021
Task: Milestone Report Contribution
Details: I continued writing the documentations and their explanations. Also, I added the Screenshots of my screens. Additionally, I wrote evaluation of tools part of the milestone. Also, I added my contributions part for the milestone report
Duration: 4 hours
Type of Work: Documentation
Date: 09.06.2021
Task: Individual Milestone Report
Details: I wrote the API part of my individual report.
Duration: 2 hours
Type of Work: Documentation
Date: 09.06.2021
Task: Merging codes and fixing small bugs. Deployment to AWS
Details: We merge all of the PRs, afterwards we fixed the small bugs and deployed our application to AWS.
Duration: 2 hours
Type of Work: Development
Date: 10.06.2021
Task: Individual Milestone Report
Details: I finished my individual report.
Duration: 2 hours
Type of Work: Documentation
Date: 10.06.2021
Task: Group Milestone Report
Details: I finished my part of the group report
Duration: 1 hour
Type of Work: Documentation
Date: 10.06.2021
Task: Deployment and Bug Fixing
Details: I helped my teammates to fix some bugs and also deployed our code when the code changes several times
Duration: 1 hour
Type of Work: Development