Harun Reşid Ergen Individual Contribution Report

Member

Harun Reşid Ergen, Group 1 - Disaster Response Platform.

Responsibilities

• Creating an introduction page for myself.
• Researching a GitHub Repository or an API.
• Creating initial version of the home page. Keeping the home page up-to-date.
• Determining the Event Creation, Action Creation and Action Tracking requirements.
• Creating Mockup for the Coordinator role.
• Creating Use Case Diagram of the Facilitator role.
• Creating Use Case Diagram of the Admin role.
• General design and revision of the Use Case Diagrams.
• Creating Class Diagram.
• Detecting inconsistencies between Mockups, Requirements and Use Case Diagrams.

Main contributions

• I opened an introduction page on the wiki and introduced myself.
  Issues: #15
  Links: Harun Reşid Ergen

• I made a research on Python Telegram API and created a section for our Research page.
  Issues: #13
  Links: Python Telegram API

• I created the initial version of our wiki's homepage and have been adding new materials to it in a timely manner to keep it up-to-date.
  Issues: #10 #35 #115
  Links: Home

• While working on the first version of the requirements, I wrote Action Creation, Event Creation, and Action Tracking requirements.
  Issues: #65
  Links: System Requirements / Action Creation, Event Creation, Aciton Tracking

• I participated in the mockup for the Coordinator actor of our project. I created a Coordinator user profile, pre-requisites, and a scenario. Ilgaz and I worked together as partners on this task. Following that, I identified and resolved any incompatibilities between the Mockup and Requirements.
  Issues: #68
  Links: Coordinator

• In the Use Case Diagram section of our project, I was responsible for the main design of the diagram. We began by dividing the actors into tasks, and my specific task was to create the use case diagram for the Facilitator actor. However, as the use cases were interconnected, I grouped them into blocks and distributed them among all the actors. Additionally, I also designed the use case diagram for the Admin actor. As the final step, I took charge of revising the Use Case Diagram with the aim of keeping an attractive and appealing design. During this process, I made sure to detect and address any conflicts that arose with the Requirements and Mockups.
  Issues: #90 #112 #114
  Links: Use Case Diagrams

• We made a start to make the Class diagrams with Alperen. As Alperen focused on constructing the classes, I took charge of categorizing the relationships between them as either Aggregation, Composition, or Association. Then, I determined whether these relationships were One-to-One, Many-to-One, or Many-to-Many. Finally, I associated the classes with each other.
  Issues: #91 #95 #100 #110 #116
  Links: Class Diagrams

• I detected inconsistencies between mockups, requirements, and use case diagrams. I prepared a report to my team to resolve those inconsistencies. I rewrote 1.2.1 Multi-hazard support. I made some corrections, additions and deletions in the 1.1.2 subheadings
  Issues: #62 #88 #104
  Links: System Requirements / Multi-hazard support, User Requirements / 1.1.2

Management related significant issues

#104 #112 #116

Additional information

I designed 2nd version of the logo.