Skip to content

Musa Nuri İhtiyar Time Tracking

Musa Nuri İhtiyar edited this page Jan 4, 2022 · 28 revisions

Cmpe 451

Personal Effort Week 1


Closing unnecessary issues that were related with the previous semester

  • 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.

Practicing React

  • 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

Determining a meeting time for front-end team

  • 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

Personal Effort Week 2


Meeting

  • Task: Attending the meeting
    Duration: 1.5 hours
    Type of work: Communication

Uploading Meeting Notes To The Repository

  • 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

Personal Effort Week 3


Updating Sequence Diagram 1

  • 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

Personal Effort Week 4


Forming The Project Structure

  • 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.

Preparing Header For Front-End

  • 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.

Preparing Sidebar For Front-End

  • 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.

Preparing Footer For Front-End

  • 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.

Preparing Reset Password For Front-End

  • 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.

Personal Effort Week 5


Password Reset 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.

Dockerization Of Front-End Part

  • 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

Personal Effort Week 6


New Event Page

  • Task: The page for new event part has been partially prepared.
    Duration: 1 hour
    Type of work: Coding

Deployment Of Front-End Part

  • 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

Personal Effort Week 7


New Event Page

  • 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

Personal Effort Week 8


New Event Page Completion

  • 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.

Search Page

  • 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.

Personal Effort Week 9


Executive Summary For Milestone 2 Report

  • 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

Screenshots For Certain Front-end Pages

  • 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

Writing personal report for the milestone 2

  • 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

Personal Effort Week 10


Open New Equipment Page

  • 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

Search Equipment Page

  • 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

Personal Effort Week 11


Adding badge functionality to opening a new event.

  • 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.

Complete Open New Equipment Page

  • 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.

Complete Search Equipment Page

  • 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.

View Equipment Information Page

  • 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.

Cmpe 352

Personal Effort Week 1

This was the first week, so I have tried to get familiar with the fundamentals of the course.

Git and Github

  • Task: Trying to learn the basics of Git and Github
    Duration: 2 hours
    Type of work: Research

Meeting

  • Task: Attending the meeting
    Duration: Half an hour
    Type of work: Communication

Meeting Wiki Page

Github Repos

Assigning an Issue

At the moment, there isn’t any problem about following the plans.

Personal Effort Week 2

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.

Meeting

  • Task: Attending the meeting
    Duration: 2 hours
    Type of work: Communication

Meeting Wiki Page

Requirements Elicitation (My Part)

At the moment, there isn’t any problem about following the plans.

Personal Effort Week 3

Meeting

  • Task: Attending the meeting
    Duration: 40 mins
    Type of work: Communication

Meeting Wiki Page

Questions to Customer

  • 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

Overview for Requirements

Personal Effort Week 4

Meeting

  • Task: Attending the meeting
    Duration: 40 mins
    Type of work: Communication

Meeting Wiki Page

Scenario and mockup for person selection

Personal Effort Week 5

Meeting

Sequence diagram

Personal Effort Week 6

Meeting

Executive summary

  • 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.

Personal work done 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.

Personal Effort Week 7

Meetings

List and status of deliverables

  • 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.

Personal Effort Week 8

Meetings

HTML and CSS

Personal Effort Week 9

Meetings

Implementation assignment

  • Task: Getting familiar with back-end, RESTful API and working on implementation assignment.
    Duration: 4 hours
    Type of work: Research and implementation\

Personal Effort Week 10

Meetings

Implementation assignment part

  • 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

Personal Effort Week 11

Meetings

Implementation assignment part

  • 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

Milestone 2 Report

  • 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.

Template


Title

  • Task: _______
    Duration: _______
    Type of work: _______
    Details: _______

Title

  • Task: _______
    Duration: _______
    Type of work: _______
    Details: _______

Title

  • Task: _______
    Duration: _______
    Type of work: _______
    Details: _______

Title

  • Task: _______
    Duration: _______
    Type of work: _______
    Details: _______

General

🏠 Home

📖 Project Description

📞 Communication Plan

📝 Contributing

Team

Project

Cmpe 451


Cmpe 352

Meeting Notes

CmpE352 Meetings
Android Meetings
Front-End Meetings

Research

Templates

Clone this wiki locally