Proposed Requirement Definition Method for Developing Global Disaster Database Based on Various Means of Data Collection

Abstract

Even typical system development models considered to be optimal for individual conditions are not always flawless. It is preferable to have clearly defined requirements of the end users when constructing a system. However, to construct the present Global Database (GDB) system, it was necessary to identify these requirements while conducting a status survey and analysis of the country that provided the data and drawing up suitable response guidelines, and to carry out system development at the same time. In this environment of continually changing system requirements, we selected the spiral model, which is used for system development, and applied it to the present construction task. We recognized various issues during the construction of the GDB, including the granularity of the collected data, the validity of the computed results, and the need for data other than disaster data. It was thus necessary to adopt an approach, based on the spiral model, in which the requirements were identified from the prototype. To follow up this study, it will be necessary to consider matters such as securing more flexibility, storing various data types (realizing an “iron stomach”), examining the issue of data access rights, examining the contents of the GDB’s automatic computation function, and creating added value to personnel charged with disaster response in each country. It will also be necessary to verify the validity of the approach of digging up unknown requirements from collected data.