Gözde Ünver Weekly Efforts - bounswe/2021SpringGroup5 Wiki

451

352

  1. Task: I made some modifications in the home app and my weatherCondition API documentation. Pull request is here Duration: 30 mins Type of work: Development, documentation

  2. Task: We had a meeting with our TA. We reviewed what we have done so far. We showed APIs that we implemented, API documentations, pull requests and issues. He gave us feedback how to document our actions. Duration: 1 hour Type of work: Meeting

  3. Task: We had a team meeting after we had a meeting with out TA. We gave deadlines to do the group documentation, code review, API documentation and AWS instance task. Duration: 1 hour Type of work: Meeting

  4. Task: Furkan and I worked on resolving the bugs in the home app and the total project. Detailed information is here Duration: 5 hours Type of work: Development

  5. Task: I finished my individual report. Issue is here Duration: 3,5 hours Type of work: Documentation

  6. Task: I reviewed Kemal's code and Mehmet Fatih's code Duration: 3 hours Type of work: Reviewing code

  7. Task: I wrote the table of deliverables and the definition of the code documentation deliverable in the group report of M2. Issue is here Duration: 30 mins Type of work: Documentation

  8. Task: I learned how to create a tag and created the version tag for our project. Issue is here Duration: 20 mins Type of work: Enhancement

  9. Task: I opened a google docs file and wrote the titles to fill for the deliverables submission for M2. I wrote the parts that required my documentation in the file. Issue is here Duration: 45 mins Type of work: Documentation

  1. Task: I studied how to write unit tests. I wrote unit tests for my weatherCondition api. I tested my code and it passes the tests. I pushed my code to my branch. Duration: 5 hours Type of work: Development

  2. Task: I wrote description of my weatherCondition API. While doing that I realized some mistakes in the html file. I changed it so that even though the current search is invalid, the results of the previous search is shown. Duration: 1 hour Type of work: Documentation, development

  3. Task: I tested my API using postman Duration: 15 mins Type of work: Testing

  4. Task: We had a team meeting to split the M2 report tasks. Duration: 1 hour, 40 mins Type of work: Meeting

  5. Task: I updated my api. I changed the limits of the weatherCondition model from 30 to 15 so that I can check when the data is valid to the model. I updated the test_invalid_long_input test so that it checks the status code being 400 for a real town name longer than 15. I modified the my API documentation and pushed everything to my branch Duration: 1 hour Type of work: Development, documentation

  6. Task: I wrote my personal effort to the excel sheet that we created for our team. Issue is here Duration: 10 mins Type of work: Documentation

  7. Task: I wrote my individual M2 report. Duration: 1 hour Type of work: Documentation

  8. Task: I modified my code and pushed it to my branch again according to the feedback I received from Berkay Bör. It can be seen here Duration: 30 mins Type of work: Development

  9. Task: I made modifications on the home app and weatherCondition app. It can be seen here Duration: 1 hour Type of work: Development

  10. Task: I reviewed Kemal's code and gave feedbacks. It is not ready to merge with master. It can be found here and here Duration 30 mins Type of work: Code review

  1. Task: I studied Django forms, models, serializers, how to hide api keys in the project, how to change the default database. Duration: 6 hours Type of work: Learning technologies

  2. Task: I finalized my weatherCondition api using model and serializer. I used mysql to see if the api is working well and since I didn't know how to use postgreql but I will modify it to postgresql. I pushed my weatherCondition api to my branch on github. Duration: 6 hours Type of work: Development

  3. Task: I studied Git ps slide and tried these commands on my private repository. Duration: 1 hour Type of work: Studying git commands

  4. Task: I studied, tried the commands, rewatched the ps videos and read the lecture slides about the docker. Duration: 1,5 hours Type of work: Studying docker

  5. Task: We had a team meeting to review what we have done so far. We splitted the next tasks (docker,aws instance, unit test -everyone-, reviewing the code of one of the team member) Duration: 1 hour Type of work: Meeting

  6. Task: I studied "Quality Assurance- Verification Validation" slide on moodle Duration: 1 hour Type of work: Study

  7. Task: I created a home app for our project that renders an html file that has buttons to go other apps. I connected my weatherCondition app and added a button for that in the html file. I updated uri's of my weatherCondition api so that one route refers to api service other refers to html rendered web site. Issue is here Duration: 2 hours Type of work: Development

  1. Task: I studied Web Application Development with API slide. I created a postman account. Duration: 1,5 hour Type of work: Studying lecture

  2. Task: We had a team meeting to discuss M2 and how to start. Duration: 1 hour Type of work: Meeting

  3. Task: I took the meeting notes about the meeting we had on 22.05.2021 and the issue is here. I created an issue that states a meeting with our TA is needed, our communicator will arrange it. Duration: 12 mins Type of work: Documentation

  4. Task: We had a meeting with out TA to clear things about the project. We will do the project according to the feedbacks we had. Duration: 1 hour Type of work: Meeting

  5. Task: I started studying Django, Django REST framework. Duration: 5 hours Type of work: Study and learn

  6. Task: I started writing my API about weather conditions. I haven't pushed yet since it is still missing some parts. Duration: 5 hours Type of work: Development

  1. Task: We had a team meeting to talk about project plan, RAM and when to finish the tasks. There was a misunderstanding about how to write down the project plan but we resolved it. Duration: 1 hour Type of work: Meeting

  2. Task: I wrote the tasks I have done so far on the project plan draft excel sheet that we have created. Issue is here Duration: 30 mins Type of work: Documentation

  3. Task: I filled my personal effort on RAM draft sheet. Issue is here Duration: 5 mins Type of work: Documentation

  4. Task: I filled my summary of personal work on our excel draft sheet. Issue is here Duration: 15 min Type of work: Documentation

  5. Task: I wrote the project description for our milestone 1 report. Issue is here Duration: 30 mins Type of work: Documentation

  6. Task: We had a meeting with our TA. In the meeting I showed the project description I wrote for the milestone. The other parts of the milestone which I contributed were also shown to TA. Duration: 1 hour Type of work: Meeting

  1. Task: We had a meeting with our TA to review our class diagram, use case diagram and sequence diagrams. I wrote down the things I should modify on the sequence diagrams I created. Duration: 2 hours Type of work: Meeting, writing down feedbacks

  2. Task: I modified sequence diagrams I created. I reopened my create sequence diagram issue. Details of my modifications can be seen there. Duration: 40 mins Type of work: Update on sequence diagrams, documentation, issue reopening

  3. Task: I reviewed our previous tasks. I created an issue stating the updates on the tasks we have done so far and need to be done before milestone 1 report. Duration: 40 mins Type of work: Reviewing, documentation

  4. Task: I reviewed previous years' milestone 1 reports. I searched for RAM diagram Duration: 40 mins Type of work: Research

  5. Task: Before our team meeting, I had taken some notes about our previous tasks that needed update before we finalize our tasks as a milestone report. Detail information is in this issue. Duration: 30 mins Type of work: Review, documentation

  6. Task: We had a team meeting to split milestone 1 report tasks. We wrote down some of the things for the tasks together on an excel sheet. I wrote the reason why we used Whatsapp and added some more explanation to Slack and draw.io. Issue is here. Duration: 1,5 hours Type of work: Meeting, documentation

  1. Task: I studied UML diagrams. I read lecture slides and read from this web site Duration: 2,5 hours Type of work: Studying current lecture topic

  2. Task: We had a team meeting to split the tasks. During the meeting we wrote down the the blueprint of the class diagram by each of us writing fields&methods of some of the classes. I wrote some on notification and analytics. Duration: 1,5 hours Type of work: Meeting, task sharing, documentation.

  3. Task: I reviewed previous years' sequence diagrams. Duration: 40 mins Type of work: Research

  4. Task: I wrote new project requirements (1.1.2.21, 1.2.4.3, 1.2.4.4, 1.2.5.1.5, 1.2.5.2.2, 1.2.5.2.3, 1.2.5.2.4) according to the feedbacks we received from professor. Issue is here Duration: 15 mins Type of work: Documentation

  5. Task: I reviewed class diagram and noted the things needed to be changed to Furkan. Dependency arrows were pointing the opposite and I asked him to modify createPost method of user class. Duration: 20 mins Type of work: Reviewing class diagram

  6. Task: I created sport event creation and apply to sport event sequence diagrams and issue is here Duration: 1,5 hours Type of work: Creating sequence diagram, documentation

  1. Task: We had a team meeting about how we should create scenarios and mock-ups. We came up with questions to ask our TA about the project. Duration: 2 hours Type of work: Team meeting

  2. Task: I wrote scenario 3 Duration: 1,5 hours Type of work: Scenario creation and documentation

  3. Task: I updated shall-should structure of 1.1.4 sign in requirements, I deleted filtering requirements and added the requirements (1.2.4.2.4 and 1.2.4.2.5) to the 1.2.4.2 game/events section. I created 1.2.4 sports equipment posts section, 1.2.5.3 sports equipments section, 1.2.9 badges section, added 1.2.3.1.6-1.2.3.1.7-1.2.3.1.8 to event requirements, 2.3.3 to availability requirements and 1.1.2.20 to user requirements. Duration: 40 mins Type of work: Requirement elicitation and updating.

  4. Task: Berkay and I had a meeting to write scenario 1 Duration: 1 hour Type of work: Scenario creation, documentation, meeting

  5. Task: We had a meeting with our TA and we went over our project requirements, scenarios and mockups. We took notes to make updates. Duration: 1 hour Type of work: Meeting with TA

  6. Task: I updated the requirements according to the feedbacks that our TA gave and the detailed description can be found in this issue. Duration: 25 mins Type of work: Updates on project requirements

  7. Task: I added the acceptance criteria to scenario 4 Duration: 15 mins Type of work: Documentation

  8. Task: I checked the mockups and examined them whether they are relevant to our requirements, scenarios and also relevant to other mockup pages. When there is an irrelevance in pages, I contacted with team members to add/subtract features from the pages. Duration: 4,5 hours Type of work: Mockup validation checks

  1. Task: Team meeting to decide the project. We discussed the projects and made a poll to decide our list of choices. Duration: 1 hour Type of work: Discussion and deciding the project

  2. Task: Inspecting more repositories and adding more advanced labels. Issue is here Duration: 1 hour Type of work: Research and design

  3. Task: Team meeting to split the tasks about writing down project requirements Duration: 1 hour Type of work: Discussion

  4. Task: Writing down report of the meeting we had on 02.04.2021 Duration: 1,5 hours Type of work: Documentation

  5. Task: Creating issues and assigning them to the people that are responsible for them Duration: 30 min Type of work: Job sharing and documentation

  6. Task: I wrote user requirements (section 1.1.2 in the requirements page), one user profile requirement (1.1.1.10) and definition of 9 keywords (applicants to an event, event creator, spectator, badge, notification, recommendation, blocking, report, follow) used in the user requirements to the glossary. I removed 1 availability requirement in section 2.2 because it was no longer relevant to our project according to the customer answers. Duration: 3,5 hours Type of work: Documentation

  7. Task: We had a team meeting to review the requirements and customer questions we have done. We made some changes to them Duration: 2 hours Type of work: Meeting, documentation

  8. Task: I created my personal wiki page. Duration: 10 min Type of work: Documentation

  9. Task: I created 25 issues Duration: 30 min Type of work: Task assigning

  10. Task: I added the links to the requirements and customer questions wiki pages to the sidebar and added the glossary to the top of the requirement page. I deleted the glossary wiki page. Duration: 10 min Type of work: Design

References

Repositories that I inspected

  1. Catch2
  1. Task: I created a team whatsapp group Duration: 1 min Type of work: Communication

  2. Task: First team meeting Duration: 1 hour Type of work: Discussion and job sharing

  3. Task: Learning git Duration: 2 hours Type of work: Self improvement

  4. Task: Learning overall github functionalities Duration: 1 hour Type of work: Self improvement

  5. Task: Creating issues and assigning them to the team members(including myself) that are responsible for that task Duration: 15 min Type of work: Task assigning

  6. Task: Creating custom labels (their names are: good for you, low, medium, urgent, weekly task) with appropriate colors and descriptions to use them in issue descriptions Duration: 10 min Type of work: Customizing

  7. Task: Repository research and writing down observations Duration: 1,5 hour Type of work: Research

  8. Task: Last team meeting Duration: 1 hour Type of work: Discussion and review of completed tasks

  9. Task: I made some enhancements on the Git wiki page. I added pictures, new commands and links to the references where I studied. Duration: 30 min Type of work: Documentation

  10. Task: I wrote a funny quote to our footer segment Duration: 1 min Type of work: Design

Links to the issues I created

  1. Issue 13
  2. Issue 11
  3. Issue 9
  4. Issue 4
  5. Issue 3
  6. Issue 2
  7. Issue 1

Link to the labels

Labels

Link to the git wiki page

Git

References

Git learning:

  1. freecodecamp
  2. datacamp
  3. atlassian
  4. beanstalk Guides

Github learning:

  1. video 1
  2. video 2
  3. Github Docs- Discussions
  4. Github Docs- Creating tables
  5. how to break lines

Repository research: