Informal Requirements

These are the requirements that are determined after the first meeting with the project owner:

• The aim is to show the information in a structured manner. We are supposed to quantize and digitize the real life events and actions that occurs after a disaster occurs.

  We are not asked to organize the help. Only meet the helpers and people in need together. In the earthquakes of Türkiye, there were many data on social media. But they may be out of date, or some data actually did not reach the people it should have reach. This causes to lack of coordination.

• Ways to show data in a structured manner is important.

  Since location is a considerable aspect in disasters, visualizing on the map is highly recommended

  Locations for the help should be shown to the users.

• There should be users who are classified into their profession: verified users.

  These can be: rescuer, driver, crane men, pharmacist, translator, headman, mayor… These users are verified and have some extra permissions.

• Other users should be able to see general data without login
• The ways without the Internet should be considered.

  A way can be provide the informations without the internet and it can update itself when it reaches the internet.

• People should be assumed to have good intentions.
• All kinds of events and actions should be considered.

  Apart from disaster area, Aid center may also use the app to announce their human/ good needs.

• Although events and actions can be predefined, they can also be generic

  A need for food or clothes can be an example of a predefined event. Application should have an UI to support these predictable events and actions. But it should be kept in mind that, there can be unpredictable cases as well. Application should support that.

• Suggestions are not necessary,

  Maybe small suggestions can be included, but it is not the priority. Optimization is not the aim of the project. People’s mind are more trusted.

• All kinds of resources should be considered.

  Resources can be human resources like rescuers and some of the verified users above. It can be food, clothes, accommodation, transportation, heat resources, equipments etc.

  A disaster can cause diseases, we should also understand these needs

  The needs of urban and rural areas are different, it should be considered.

• Resources should be classified semantically well.

  Wikidata offers a wide range of general data about everything under the sun. We can use that data collection while annotating. Further research will be needed.

• Application should be able bond a link between similar resources.

  It should provide boots for someone looking for shoes.

• Application should eliminate duplicate data for the consistency and prevent redundancy

• Application should also keep the data for the resources in a detailed manner. The need should be clear.

  The quantity of aid materials should be specified.   It should keep the shoe size information. A user in need of a shoe of size 40, cannot use one with 35. A food can have an expiration date. We may request a minimum of one week to the consumption date.

• Application should cover Türkiye for now

• Application should be flexible with verification.

  There can be cases that is not predictable and does not go as planned.

• Update of the data is important.

  Date should be shown to the user and there can be filter mechanisms to show latest data. Someone can forget to update a data. Verifiers can be used for check of that event, action or need.

• It should be taken into account that the number of people in the place where aid is sent is dynamic.

  The population in the villages may increase.

• Qr codes can be used for the help that goes to the areas that are affected by the disaster.

• Notifications should be considered

  A user can follow a topic, so they can get notifications from certain topics. A driver can follow the driving actions(need for a driver) and road events(road is closed). Pushed notifications.

• The platform should have a web application and a native Android application.
• The platform should provide all kinds of search functionality (e.g., search with filters, sort by date) for models.
• The platform should use W3C Geolocation API [1] standard for implementing location-related information.
• The models in the platform (i.e., resources, events, actions) should be filled with rich meta-information: location, source, date, and/or anything related, so that the entity will have a semantic meaning, which would ultimately serve as a way to process/visualize information.