Skip to content

Individual Report Merve Gürbüz

mervegrbz edited this page Apr 10, 2023 · 1 revision

Member:

  • Name: Merve Gürbüz
  • Group: A2

Responsibilities:

  • Attend meetings, create agenda.
  • Create personal wiki pages.
  • Write requirements, revising them.
  • Write templates, set rules.
  • Communicating to the assistants.
  • Contribute Functional and Non-Functional Requirements.
  • Ckeck and design the wiki pages regularly.
  • Assign issues to the team members, reassign if it is not done.
  • Create issues according to the actions taken in meetings.
  • Write meeting notes.
  • Decide meeting date, hour, place.
  • Created example mockups.
  • Revise mockups.
  • Collect mockups together, resolve conflicts.
  • Create use case diagram, collect them, redesign parts.
  • Add user, information,Role-based user class diagrams.
  • Add sequence diagram for Login, forgot password.
  • Add sequence diagram of Map.
  • Contributed to Milestone 1 preparation.

Main contributions:

Task Issues Links
Attended to Meeting 1 - Meeting #1
Created introductory personal wiki page #5 Merve Gürbüz
Created research wiki page about OhMyZsh #2 Merve Gürbüz - Research
Discussed questions with team members before the meeting with project owner - Meeting with project owner
Attended to meeting with project owner (Meeting 2) - Meeting with project owner
Added several questions to be asked in Requirement Elicitation #15 Questions for Requirements
Interview with Enes Doke as a disaster volunteer in Turkey Interview with Enes
Attended to Meeting 3 - Meeting #3
Attended to Meeting 4 - Meeting #4
Created Structure of Functional Requirements #58 Glossary
Write User Actions in Functional Requirements #37 Introduction
Write Admin part in Functional Requirements #33 Profile
Attended to Meeting 5 - Meeting #5
Review Events subsection in Activities section in Functional Requirements #53 Activities
Review Actions subsection in Activities section in Functional Requirements #54 Activities
Review Needs subsection in Activities section in Functional Requirements #52 Activities
Review Annotation in Functional Requirements #52 Annotation
Directed the Meeting 6 - Meeting #6
Created Security section in Non-Functional Requirements #71 Security
Directed to Meeting 7 - Meeting #7
Revise requirements and update many fields because of new desicions #80 -
Note taker of Meeting 8 - Meeting #8

Management related significant issues:

Additional information (optional):

  • I have taken a big responsibility on the project more than I expected. I tried to seperate the tasks equaly to the team members, and I tried to encourage all members to attend the work we are responsibily. However, just the half of team do their responsibilities. It was really devestating for us, since we had to deal with everything at the same time.
  • As a team member, I believe that me and some of my team members are keen on learning from the courses, but not all of us. I do not want any freeriders to pretend they have done something.

Group 2 Disaster Response Platform

CMPE451

📌 Communication Plan
📌 Docker and local deployment tutorial
📌 RAM
📌 Test Traceability Matrix

📜 Rules
📝 Lab Reports
📅 Meetings
📅 Backend Team Meetings
📅 Mobile Team Meetings
👥 Team Members

CMPE352

📌 Milestone Report 1

📌 Milestone Report 2

📅 Meetings
👥 Team Members
📁 Project
🔍 Research
📜 Rules
📝 Templates
💬 Interviews
Clone this wiki locally