Analysis of Back-End Requirements of a Web-Based Application to Identify Damage for Building Structures

The need for well-maintained facilities can certainly affect activities in the building. To meet these needs, a building maintenance work program is needed to achieve the planned life of the building. The problem with contractors is that they still use telephone communication to receive reports of any damage to the building. This paper discusses the needs analysis in the construction of a building damage reporting system from the backend side. The application is built on a web-based basis and provides information about the building in terms of the structural aspect as well as grouping the damage based on the damage criteria. The results of this study are obtained in the form of 10 tables that will compile a system database and transaction analysis that can be done in the system, namely generating building damage data reports where there are four categories of damage, namely light damage, moderate damage , severe damage, total damage and this application can later be used by building managers in reporting building damage through applications and contractors can monitor through applications.


Introduction
Building is a physical form resulting from construction work that is integrated with its domicile, partially or wholly located above and/or in the land and/or water, which functions as a place for humans to carry out their activities, either for housing or residence, religious activities, business, social, cultural, or special activities, so that the building needs to be maintained so that the building is able to stand well in the long term. As stated in the Regulation of the Minister of Public Works No : 16/PRT/M/2010 CONCERNING TECHNICAL GUIDELINES FOR PERIODIC BUILDING INSPECTIONS, every building in Indonesia must be regularly maintained/inspected [1]. The aspects that need to be considered in building maintenance are aspects of architecture, structure, mechanical, electrical, outdoor layout, and housekeeping. economical. Overall the building structure consists of two parts, namely the upper structure in the form of floors, beams, columns, walls and roofs, while the lower structure consists of foundations and sloof beams [2]. A building defect is a failure or mistake that reduces the value of the building and may cause a dangerous condition to the user's if neglected building. A defect may arise from some carious factors such as poor workmanship, design fault, wrong selection of material and so on. Building defects will result in various implications [3]. It may reflect the negligence occurred, and also illustrates the lack of concern on problems arising from the construction work on the building as well as building refurbishment. A defect may be considered to be failing or unsatisfactory in the functional performance, user or statutory requirements of a building and might manifest itself within the fabric, structure, services and facilities of the affected to the building [4].
Ransom states that despite calls for closer integration of design and construction, the role remains essentially separate [5] This paper shows that more than 90% of building defects can be explained partially or completely as a result of easily identifiable design and construction errors that could be foreseen and therefore prevented. According to Hardianto [6] maintenance activities are not given much attention due to several factors. These factors include: (1) Maintenance activities are seen as not urgent compared to development activities. (2) Improper maintenance organizational structure. (3) The activity manager assumes that the maintenance of the building is a technical matter alone, not related to the purpose of the building's function according to the wishes of the user. In previous studies that have been carried out, discussing the design of the building damage reporting system that may occur in the observed building and compiling technical reporting that will be carried out by building managers in contacting the party responsible for the damage [7]. However, in this paper, the researcher discusses the continuation of the previous problem, namely the need from the back-end side of the web-based system to be built.

Research Methodology
In writing this paper, the author designs the needs from the back-end side of a Webbased building damage reporting application. This type of research is experimental, by testing the use of applications in buildings for recording reports of building damage and classifying damage based on damage criteria. There are several methods to obtain the required data, including: a. Library Studies Looking for reference books that can help provide information and understanding of the basic concepts of building maintenance and maintenance. b. Observation (Observation) The data obtained is the result of direct observation of similar applications that provide input on building damage and direct data retrieval of each building.

Context Diagram
Context Diagram is a general description of showing the boundaries of the external system entity with the system and as a tool for global system design that shows the system and its parts in general.

Cases a)
In the meeting room of building A, there is subtle damage to the stucco smaller than 0.075 cm, stucco fragments fall, and covers a limited area. b) In the hall of building B, there are small cracks in the width of the gap between 0.075 to 0.60 cm on the wall, the plaster is loose and falling off, covering a large area, damaged parts of the chimney and lip tank, and is fit for function / habitation. c) In the toilet of building C there is a large crack damage of more than 0.60 cm on the wall, the cracks are widespread in many places, such as in (walls, load bearings, columns, chimneys tilted and collapsed), reduced part of the structure to bear the load, and the fit function / occupancy d) In building D there is heavy damage, the building collapses 50%, the load-bearing wall splits and collapses, the main element is thought to be damaged and unfit for function / habitation e) In building E there is total damage to the building falling >65%, most of the main components of the structure are damaged and the building is not fit for function / habitability.

Entity Relationship Diagram (ERD)
Entity Relationship Diagram (ERD) is a chart depicting a database design tool, which consists of real objects. Entity Relational Diagram (ERD) can help in studying the relationship between database files to be designed. From the Normalization process to 3 NF, ERD is obtained as shown figure 2.

Conclusion
In the construction of a building damage reporting system, a needs analysis from the back-end side is needed, one of which is the need for transaction processing between the user interface and data storage. there will be 5 types of damage to buildings from the structural side and the number of user levels who will use this system is 3 people.