-
Notifications
You must be signed in to change notification settings - Fork 2
Şefika Akman Time Tracking
Şefika Akman edited this page Jan 7, 2022
·
25 revisions
- I watched videos and read documents.
- Pull request: #169
- I have added logo, home page button, personal page button, notifications button, search button and sign up button.
- I watched videos and read documents.
- I did my own repository research and write them to my repository reseaarch page.
- I watched videos and read documents.
- We have orginized RAM and project plan.
- I started impementation of exploring events.
- I tried to add sign up control to navogation.
- I have implemented view event page. It has features of an event. When users want to see detaild of an event, it shows type of sport, location, event date, minimum and maximum ages, minimum and maximum skill levels, event owner, vreation date and player capacity informatio of that event. It also has an image of the sport which is taken from Decathlon sports api. It has further features that we have added later.
- Because we forgot before, I have added sport type filter to the search event page. It has sport types as text and users can select which event they want to search. While implementing, I have used Decathlon sports api for sport names.
- When users refreshed the page, data was getting lost. I fixed this probem by using local storage. Access and refresh tokens are working right now.
- I have implemented a page that has content, type of sport, type of equipment, creation date, location information of an equipment. When users search equipments or go to equipments from events, this page shows itself. It has more features that we have added after.
- When users log in or log out, navigation buttons and features should be changed. Before I have implemented this function, users must restart the page to renew navigation. Now, it updates automatically.
- For logged in users, there are home, search, new event, new equipment, profile and log out buttons and for logged out users, there are home, search, sign up and log in buttons in the navigation.
- For most events, there was no picture on the event page. It was because we were using more limited type of api for sports. I have changed the implementation to make it more comprehensive.
- I have added recommended events for each equipment. There are three events for every equipment which are selected according to sport type of equipment. Users can click on the events to see page of that event.
- I have added recommended equipments for each event. There are three equipments for every event which are selected according to sport type of event. Users can click on the equipments to see page of that equipment.
- Users can see their applied and owned events in their own profile page. It helps them to manage their events easily. They can click events from their profile page to see pages of that events. I have implemented applied and owned events as two tags to make them use properly and easily.
- We started to organize our Wikipage and then we shared tasks.
- I did my own repository research and write them to my repository reseaarch page.
- I watched a video teaching git.
- I wrote about myself.
- We added personal photographs.
- We fixed some labels according related groups, added and deleted some also.
- We discussed about the future assignments.
- We discussed about our project.
- We took a look at other projects' user requirements.
- We determined and wrote user requirements.
- We took a look what we have done.
- We have decided scenarios and issues.
- We took a look scenarios of other projects to get an idea.
- We wrote persona, story, pre-conditions, goals, acceptance criteria and scenario with mockups parts of scenario.
- We created mockups both for web and android.
- We reviewed what we should do.
- To create class diagram, we decided 11 entities and assigned one of them each people, also assigned all people for one entity.
- We asked TA our questions.
- After meeting with TA, we continued with a teammeeting and shared tasks to do.
- I created some part of the class diagram as a draft.
*Reviewing and decided to assign sequence diagrams among the members.
- Creating parameters and functions for "event Search" part.
- We reviewed and fixed class diagram and sequence diagrams.
- We set up the next team meeting.
- We added need things and deleted not required sentences.
- We checked what we have done and orginize use cases.
- We had a meeting with TA, reviewed what we have done for now, sequence diagrams, class diagram and use case diagram. Asked questions to TA and got feedback.
- We shared work about milestone.
- My part is "evaluation of tools and processes that you have used to manage your team project" and also fixing little things in wiki.
- We edited miro board to make easier preparing milestone report.
- We explained which tools we use for works of 352.
- We prepared milestone report 1. I contributed tools and processes part and also edited several parts of resport.
- This week is empty because it is spring break.
- We talked about API implementation. We found which APIs we should implement and share them.
- I have implemented get_players function which returns players of an event.
- I have implemented get_weather function which uses an API to get parameters. It returns the weather conditions for an event looking by its location.
- We reviewed what we have done so far. And we found new APIs because first time we didn't understand that each of us should implement both a get and a post method.
- I have implemented post_user function which posts a user and returns it. It takes user_id as parameter.
- I have implemented get_notification function which gets notifications of a user looking by its user_id and returns notifications.
- We (with Doğukan Akar) explained frontend tables in wiki page.
Task: Explaining get_players, post_user, get_weather and get_notification APIs in API Documentation Page
- I have explained these APIs in wiki page. (Definition, Example Response Value, Parameters and Response Messages).
- I have added API documentation to Milestone report and filled my parts.
-
Home
-
Communication plan
-
Some interesting GitHub repositories
- Git Basics
- Time Tracking
- RAM
- Lessons Learned
- System Manual
- Doğukan Akar
- Şefika Akman
- Ömer Arslan
- İbrahim Kağan Bayat
- Berkay Döner
- Ahmet Necip Görgülü
- Ege Can Kaya
- Bengisu Özaydın
- Mehmet Saraçoğlu
- Kerem Zaman
- Project Requirements
- Existing Examples
- Questions for Customers
- Customer Meeting Notes
- Scenarios and Mockups
- Class Diagram
- Sequence Diagrams
- Use Case Diagram
- Practice App API Documentation
- Rebound API Documentation
- Meeting Notes #1 (28.03.2021)
- Meeting Notes #2 (30.03.2021)
- Meeting Notes #3 (03.04.2021)
- Meeting Notes #4 (07.04.2021)
- Meeting Notes #5 (14.04.2021)
- Meeting Notes #6 (21.04.2021)
- Meeting Notes #7 (24.04.2021)
- Meeting Notes #8 (28.04.2021)
- Meeting Notes #9 (29.04.2021)
- Meeting Notes #10 (05.05.2021)
- Meeting Notes #11 (22.05.2021)
- Meeting Notes #12 (26.05.2021)
- Meeting Notes #13 (29.05.2021)
- Meeting Notes #14 (02.06.2021)
- Meeting Notes #15 (09.06.2021)