Skip to content

Bengisu Özaydın Time Tracking

Bengisu Özaydın edited this page Jun 5, 2021 · 14 revisions

Week 1

  • ( 2.0 hr | team )
    • Participating in team Discord meeting.
      • Getting familiar with our team's Github repository
      • Discussing how standards such as issue labels should be.
      • Verifying that I can modify README.md file from my terminal.
  • ( 0.1 hr | documentation )
    • Setting up personal wiki page.
  • ( 1.0 hr | documentation )
    • Gathering favorite GitHub repositories and writing descriptions.
  • ( 0.3 hr | documentation )
    • Setting up personal time tracking page and filling it.

Pages created:

  1. Personal wiki page
  2. Personal interesting repositories page
  3. Personal time tracking page

Issues created:

  1. Issue

Week 2

  • ( 0.5 hr | study )
    • Revising Software Lifecycles & Introduction to Requirements Elicitation File.
  • ( 2.0 hr | team )
    • Participating in team Discord meeting.
      • Discussing project details.
      • Assigning roles to team members.
      • Preparing questions for the customer.
      • Brainstorming about related software and user / system requirements.
  • ( 0.5 hr | organization )
    • Creating issues, assigning/editing already created issues to team members as discussed in the meeting, editing labels of past issues for a uniform style.
  • ( 0.5 hr | documentation )
  • ( 0.1 hr | documentation )
    • Adding time tracking details.

Issues created:

  1. Issue

Week 3

  • ( 1.0 hr | team )
    • Participating in team Discord meeting.
      • Deciding on mockup scenarios.
      • Assigning roles to team members.

Week 4

  • (2.0 hr | team)
    • Participating in team Discord meeting.
      • Deciding on classes, sequence and use-case diagrams.
      • Assigning roles to team members.
  • (0.5 hr | documentation)
    • Working on class diagram (user search).
  • (1.0 hr | communication)
    • Meeting with TA about diagrams.

Week 5

  • (2.0 hr | team)
    • Participating in team Discord meeting.
      • Deciding on classes, sequence and use-case diagrams.
      • Assigning roles to team members.
  • (0.5 hr | documentation)
    • Working on class diagram (user search).
  • (1.0 hr | communication)
    • Meeting with TA about diagrams.

Week 6

  • (1.5 hr | team)
    • Participating in team Discord meeting.
      • Reviewing and updating class and sequence diagrams.
  • (1.5 hr | team)
    • Participating in team Discord meeting.
      • Updating use-case diagrams.
  • (1.5 hr | communication)
    • Meeting with TA about our progress.
  • (0.5 hr | documentation)
    • Contributed to changes in the class and use case diagrams (commented these changes under corresponding issues).

Week 7

  • (1.5 hr | team)
    • Participating in team Discord meeting.
      • Discussing the first milestone report.
      • Assigning roles to team members.
  • (1.5 hr | documentation, review)
    • Changing the class and use case diagrams using search action. Updating "searching equipment", "searching user" and event searching sequence diagrams regarding these changes.
  • (0.3 hr | documentation, review)
    • Re-labeling arrows in use case diagrams regarding search action. Issue
  • (0.5 hr | documentation, review)
  • (1.5 hr | documentation)
    • Merging screenshots of class and use case diagrams in Miro board and adding these to milestone report.
  • (0.5 hr | documentation)
    • Filling up responsibility assignment matrix for the milestone report.
  • (2.5 hr | documentation)
    • Meeting with team on Discord and completing the milestone report.

Issues created:

  1. Issue

Week 8

Spring Break


Week 9

  • (1.5 hr | team, research)
    • Participating in team Discord meeting.
      • Discussing the API implementation assignment and researching APIs.
      • Assigning roles to team members.
  • (0.5 hr | implementation)
    • Creating post_event API.
  • (3.0 hr | research)
    • Polishing React skills to be useful in the front-end of the app.

Issues created:

  1. Issue

Clone this wiki locally