-
Notifications
You must be signed in to change notification settings - Fork 1
Musa Nuri İhtiyar Time Tracking
Musa Nuri İhtiyar edited this page Jan 4, 2022
·
28 revisions
-
Task: Some of the issues were totally about the assignments given in Cmpe 352; therefore, it was beneficial to close them in order to keep the repo up to date.
Duration: 20 mins
Type of work: Documentation / Maintenance
Details: Only 1 issue has been founded and closed.
-
Task: Even though I learned React in the summer, it's better to make more practice about it; consequently, try to develop some example applications using it.
Duration: 3 hours
Type of work: Code practice
-
Task: We've selected an appropriate meeting time for front-end team with other members of the team and we've added it to communication part in the wiki page
Duration: 10 mins
Type of work: Communication
-
Task: Attending the meeting
Duration: 1.5 hours
Type of work: Communication
-
Task: Keeping the archive of the meeting notes is an important point. This week it's my turn
Duration: 15 mins
Type of work: Documentation
Details: More information can be found in the corresponding wiki page
-
Task: There're some problems in Sequence Diagram 1, so I have made necessary changes and uploaded it again.
Duration: 45 mins
Type of work: Documentation
Details: More information can be found in the corresponding issue page
-
Task: Initializing the project for front-end part.
Duration: 45 mins
Type of work: Coding
Details: More information can be found in the corresponding issue page and pull request.
-
Task: Header part will be permanent for all pages and I have written the code for that part.
Duration: 1 hour
Type of work: Coding
Details: More information can be found in the corresponding issue page and pull request.
-
Task: Sidebar part will be permanent for all pages and I have written the code for that part.
Duration: 1 hour
Type of work: Coding
Details: More information can be found in the corresponding issue page and pull request.
-
Task: Footer part will be permanent for all pages and I have written the code for that part.
Duration: 1 hour
Type of work: Coding
Details: More information can be found in the corresponding issue page and pull request.
-
Task: One of the functionalities that will be available in the application is password reset operation for users I have started to implement it, yet it hasn't finished yet.
Duration: 1 hour
Type of work: Coding
Details: More information can be found in the corresponding issue page.
-
Task: The page for password reset part has been prepared.
Duration: 1.5 hours
Type of work: Coding
Details: More information can be found in the corresponding issue page and pull request.
-
Task: Dockerization was an important step for the deployment of the front-end part, so I have tried to understand how we can do that, yet I couldn't find a solution which really work for us; therefore, I need to spend more time for that I guess.
Duration: 30 mins
Type of work: Research
-
Task: The page for new event part has been partially prepared.
Duration: 1 hour
Type of work: Coding
-
Task: Deployment is an important part of the project, so I have studied how we can do that by both asking the issue to the people in the class and looking from the internet; nevertheless, I couldn't achieve that despite the fact that I have spent serious amount of time on that part.
Duration: 10 hours
Type of work: Logistics of the project
-
Task: I have spent time on how to allow user to select a place from the map since the rest was already prepared.
Duration: 3 hours
Type of work: Coding
-
Task: Opening new event page has been completed in terms of both functionality and styling. Functionality part includes using map too.
Duration: 4 hours
Type of work: Coding
Details: More information can be found in the corresponding issue page, pull request1 and pull request2.
-
Task: Being able to search existing events was very crucial for our application. I have implemented the corresponding front-end page in terms of both functionality and styling. Again functionality includes adding map.
Duration: 6 hours
Type of work: Coding
Details: More information can be found in the corresponding issue page, pull request1 and pull request2.
-
Task: One of the parts of the milestone 2 report was executive summary in which we summarize the current situation of the project in general. I have written that part for the team.
Duration: 1 hours
Type of work: Documentation
-
Task: Screenshots for the existing front-end pages was required in the second milestone report; therefore, I have added the screenshots for the pages I have written.
Duration: 10 mins
Type of work: Documentation
-
Task: I have written personal milestone report for milestone 2 according to the description given in the moodle.
Duration: 1.5 hours
Type of work: Documentation
-
Task: Equipments are one of the additional features that our application ought to provide, so I have prepared the main skeleton of the page which will be used for defining a new equipment in the system, yet it isn't connected to the back-end since that part isn't ready yet.
Duration: 1 hours
Type of work: Coding
-
Task: When we have equipments in the application, being able to search the existing ones is a must; because of this, I have prepared the main skeleton of that page in the front-end part. This part is not connected to the back-end, either due to the same reason with the previous one.
Duration: 1 hours
Type of work: Coding
-
Task: Opening a new event page was already ready, yet it didn't have the option to add a badge to the event so that each user who attends the event will get that badge. I have changed new event page accordingly.
Duration: 1 hours
Type of work: Coding
Details: More information can be found in the corresponding issue page, pull request1 and pull request2.
-
Task: The page which will allow user to open new equipment was ready in terms of skeleton from the previous week; however, it wasn't connected to the back-end since that part wasn't ready. I have made the corresponding changes so that the page is now functioning.
Duration: 1 hours
Type of work: Coding
Details: More information can be found in the corresponding issue page, pull request1, pull request2 and pull request3.
-
Task: The page which will allow user to search for an equipment was ready in general from the previous week; nonetheless, it wasn't connected to the back-end since that part wasn't ready. I have made the corresponding changes so that the page is now functioning.
Duration: 1 hours
Type of work: Coding
Details: More information can be found in the corresponding issue page, pull request1 and pull request2.
-
Task: Even though searching for an equipment is a crucial feature for the application, it doesn't have much meaning unless the user can view more detailed information about the a certain equipment among the results came from the search, so prepare the front-end page in which all information related with a certain equipment will be shown.
Duration: 1 hours
Type of work: Coding
Details: More information can be found in the corresponding issue page, pull request1, pull request2 and pull request3.
This was the first week, so I have tried to get familiar with the fundamentals of the course.
-
Task: Trying to learn the basics of Git and Github
Duration: 2 hours
Type of work: Research
-
Task: Attending the meeting
Duration: Half an hour
Type of work: Communication
-
Task: Preparing wiki page for the meeting
Duration: Half an hour
Type of work: Documentation
Details: The wiki page can be accessed using the following link https://github.com/bounswe/2021SpringGroup6/wiki/Group-Meeting-1
-
Task: Conducting research about some example Github repositories
Duration: Half an hour
Type of work: Research
Details: The interesting ones are like the following
https://github.com/bounswe/bounswe2016group6
https://github.com/tensorflow/tensorflow
https://github.com/torvalds/linux
-
Task: Assign an issue to myself
Duration: 10 minutes
Type of work: Logistics
Details: Link is like the following https://github.com/bounswe/2021SpringGroup6/issues/1
At the moment, there isn’t any problem about following the plans.
This was the second week, so we learned what our project will be and have tried to carry out requirements analysis for the given project.
-
Task: Attending the meeting
Duration: 2 hours
Type of work: Communication
-
Task: Preparing wiki page for the meeting
Duration: Half an hour
Type of work: Documentation
Details: The wiki page can be accessed using the following link https://github.com/bounswe/2021SpringGroup6/wiki/Group-Meeting-2
-
Task: Completing registration and login sections of user requirements part in detail
Duration: An hour
Type of work: Documentation
Details: For more information, https://github.com/bounswe/2021SpringGroup6/wiki/Project-Requirements
At the moment, there isn’t any problem about following the plans.
-
Task: Attending the meeting
Duration: 40 mins
Type of work: Communication
-
Task: Preparing wiki page for the meeting
Duration: Half an hour
Type of work: Documentation
Details: The wiki page can be accessed using the following link https://github.com/bounswe/2021SpringGroup6/wiki/Group-Meeting-3
-
Task: Asking questions to customer (TA) about the part for which I'm responsible in requirements, documenting the answers and making related changes in the requirements document
Duration: 30 mins
Type of work: Communication and documentation
-
Task: Inspecting requirements part in general and sharing ideas about potential missing parts if they exist
Duration: 20 mins
Type of work: Documentation
Details: For instance, https://github.com/bounswe/2021SpringGroup6/discussions/23
-
Task: Attending the meeting
Duration: 40 mins
Type of work: Communication
-
Task: Preparing wiki page for the meeting
Duration: Half an hour
Type of work: Documentation
Details: The wiki page can be accessed using the following link https://github.com/bounswe/2021SpringGroup6/wiki/Group-Meeting-4
-
Task: Preparing scenario and mockup for person selection to an event
Duration: 2 hours
Type of work: Requirements
Details: https://github.com/bounswe/2021SpringGroup6/wiki/Person-Selection-for-an-Event-Scenario and https://github.com/bounswe/2021SpringGroup6/wiki/Person-Selection-Website-Mockup can be examined
-
Task: Attending the meeting
Duration: 6 hours in total due to 3 meetings
Type of work: Communication and requirements
Details: For more detail,
https://github.com/bounswe/2021SpringGroup6/wiki/Group-Meeting-5.1
https://github.com/bounswe/2021SpringGroup6/wiki/Group-Meeting-5.2
https://github.com/bounswe/2021SpringGroup6/wiki/Group-Meeting-5.3
-
Task: Preparing sequence diagram for editing event information
Duration: 1 hour
Type of work: Requirements
Details: It can be found in https://github.com/bounswe/2021SpringGroup6/wiki/Sequence-diagram-for-editing-event-information
-
Task: Attending the meeting
Duration: 2 hours
Type of work: Communication and requirements
Details: For more detail,
https://github.com/bounswe/2021SpringGroup6/wiki/Group-Meeting-6
-
Task: Prepare executive summary for the milestone 1 document
Duration: 1 hour
Type of work: Requirements
Details: It hasn't been put into the github repo, but it'll be in the milestone 1 document.
-
Task: Prepare summary of the work done by me until milestone 1
Duration: 1 hour
Type of work: Requirements
Details: It hasn't been put into the github repo, yet it'll be in the milestone 1 document.
-
Task: Attending the meetings
Duration: 3 hours in total
Type of work: Communication and requirements
Details: For more detail,
https://github.com/bounswe/2021SpringGroup6/wiki/Group-Meeting-7.1 and https://github.com/bounswe/2021SpringGroup6/wiki/Group-Meeting-7.2
-
Task: Prepare list and status of deliverables for the milestone 1 document
Duration: 1 hour
Type of work: Documentation
Details: It hasn't been put into the github repo, but it's in the milestone 1 document.
-
Task: Attending the meetings
Duration: 1 hour in total
Type of work: Communication and requirements
Details: For more detail,
https://github.com/bounswe/2021SpringGroup6/wiki/Group-Meeting-8
-
Task: Studying HTML and CSS from the internet
Duration: 3 hours
Type of work: Research
Details: https://www.codecademy.com/learn/learn-html and https://www.codecademy.com/learn/learn-css websites have been used
-
Task: Attending the meetings
Duration: 2.5 hours in total
Type of work: Communication and requirements
Details: For more detail,
https://github.com/bounswe/2021SpringGroup6/wiki/Group-Meeting-9.1 and https://github.com/bounswe/2021SpringGroup6/wiki/Group-Meeting-9.2
-
Task: Getting familiar with back-end, RESTful API and working on implementation assignment.
Duration: 4 hours
Type of work: Research and implementation\
-
Task: Attending the meeting which was about the implementation assignment
Duration: 1 hour in total
Type of work: Communication and requirements
Details: For more detail,
https://github.com/bounswe/2021SpringGroup6/wiki/Group-Meeting-10
-
Task: Writing the API for getting the discussions for an event, commenting it and preparing documentation. Also preparing both the back-end and front-end part related with that
Duration: 10 hours
Type of work: Implementation
-
Task: Attending the meeting in which parts of the implementation assignment which ought to be done collectively such as pull requests have been carried out.
Duration: 2.5 hour in total
Type of work: Implementation as a group
Details: For more detail,
https://github.com/bounswe/2021SpringGroup6/wiki/Group-Meeting-11
-
Task: Making necessary changes in my code for being able to merge with the master branch of the GitHub.
Duration: 4 hours
Type of work: Implementation
-
Task: Adding what personally done and my code with the related documentation. Also writing half of the challenges met part. Lastly, preparing my personal report
Duration: 4 hours in total
Type of work: Documentation
Details: For more detail,
both group report and personal report for Milestone 2 can be checked.
-
Task: _______
Duration: _______
Type of work: _______
Details: _______
-
Task: _______
Duration: _______
Type of work: _______
Details: _______
-
Task: _______
Duration: _______
Type of work: _______
Details: _______
-
Task: _______
Duration: _______
Type of work: _______
Details: _______
🏠 Home
- Berk Atıl
- Elif Sema Balcıoğlu
- İbrahim Melih Aktaş
- Ömer Faruk Süve
- Deniz Arda Budak
- Ekrem Yusuf Ekmekci
- Musa Nuri İhtiyar
- Salih Can Özçelik
- Requirements
- Related Software Systems
- Requirements Questions
- Scenarios
- Sequence Diagrams
- Use Case Diagrams
- Class Diagrams
- Practice-app API Documentation
CmpE352 Meetings
- Group Meeting 1 - 26.03.2021
- Group Meeting 2 - 02.04.2021
- Group Meeting 3 - 06.04.2021
- Group Meeting 4 - 13.04.2021
- Group Meeting 5.1 - 20.04.2021
- Group Meeting 5.2 - 22.04.2021
- Group Meeting 5.3 - 24.04.2021
- Group Meeting 6 - 27.04.2021
- Group Meeting 7.1 - 04.05.2021
- Group Meeting 7.2 - 08.05.2021
- Group Meeting 8 - 21.05.2021
- Back-End Meeting 1 - 22.05.2021
- Front-End Meeting 1 - 22.05.2021
- Group Meeting 9.1 - 25.05.2021
- Group Meeting 9.2 - 30.05.2021
- Group Meeting 10 - 05.06.2021
- Group Meeting 11 - 08.06.2021
- Group Meeting 12 - 12.10.2021
- Group Meeting 13 - 19.10.2021
- Group Meeting 14 - 26.10.2021
- Group Meeting 15 - 02.11.2021
- Group Meeting 16 - 09.11.2021