Design and Build of Road Damage Information System in Madiun Regency Using Web Development Life Cycle Methods

Government infrastructure development is growing rapidly, starting from the central and provincial levels. One of the infrastructures currently being pushed by the government is road infrastructure. Both toll roads, regional roads, and district/city roads. Road infrastructure that has been built requires maintenance and repair. Road damage maintenance and repair in urban districts, especially Madiun Regency, Existing Road damage data is still recorded manually using paper, where the government needs help knowing data on road damage that has been recorded, which road conditions have not been repaired, and which have been fixed immediately. Because manual data is prone to wear and loss, tucked in with other manual files. So, the road improvement priority in Madiun Regency still needs to be put on target. For this reason, an information system is required to record the damage to road infrastructure in Madiun Regency. This information system was built using the web development life cycle (WDLC) method. We chose this method because it can be used in all web application development processes and can be modified or added to prototyping and looping to maximize results. The information system for road damage in Madiun Regency was developed using the PHP & MySQL programming languages. The result of this study is a road damage information system that contains updated data on road damage conditions in the Madiun district. Apart from being paperless, digitized data has the advantage of minimal damage and expected data loss and can help decision-makers prioritize repairs by looking at the data in the road damage information system.


INTRODUCTION
Government development in road infrastructure is growing fast, starting from the central level with the Trans Java toll road development project to the construction of provincial and city-district roads. As a result, it can accelerate the economy at the regional and central levels. However, the rapid development of road infrastructure will only reduce its benefits if there is road maintenance and repair, whether periodic maintenance or repairs at certain times. Slightly different from toll road infrastructure, where the government and its partners have arranged the Because the process is still manual in the form of written reports to the government using paper, the data is prone to damage and data loss. Moreover, the regency government finds it difficult to see data on existing road damage, so the priority for repairing road damage becomes ineffective and inefficient. In addition, the level of satisfaction of road users will be low. The results of research conducted by Pradityo et al. showed that the comfort of road users and services from the local government determines road users' satisfaction level [1]. With the development of current technology, existing road damage data in Madiun Regency, which is still recorded manually, can be converted into digitized data and accessed by policymakers to prioritize road repairs in Madiun Regency. Therefore, research on the design and construction of a road damage information system in the Madiun district was made to provide convenience in accessing road damage data and make it easier for policymakers to decide priorities for road repair in the Madiun district.
The information system for road damage in Madiun Regency was built using the web development life cycle (WDLC) method. This method develops a complete life cycle model for a web-based system. This method is a basic SDLC development model that provides the basic structure for web-based system development. It includes various complete guidelines from planning to the final system product that can meet user needs. All types of web application development processes, like the waterfall model, prototyping, spiral, etc., can adopt this method. [2] In the WDLC method, there are five primary stages.
It was achieving the first phase of web feasibility, or the eligibility of a system requires careful planning. It is crucial in building a whole web-based information system. The next stage in the web development life cycle will go wrong if the planning goes wrong. In the planning stage, there are several planning steps. The first is to determine the purpose of the system used, and the next is to find out the user profile and the website development technology to be used along with the infrastructure to be used, such as web browser version, internet connection, highresolution monitor, etc. After determining the goals, user profiles, and technology to be implemented, the next stage is to pay attention to the owners and users involved in developing this web-based information system. Their participation plays an essential role in each phase of the WDLC. The last step that needs to be done is to pay attention to the type of content that will be displayed [2].
Website analysis is a series of analysts' activities in collecting user information needs and analyzing them systematically. The following are the steps in the WDLC analysis stage. The first is to identify functions based on user requirements. The next step is to focus on running functions and processes that form the basis for supporting the development of information systems [2]. At this stage, the details of the web-based information system are prepared. Includes diagrammatic representations, logical and physical artifacts to be developed, data models, process models, etc., and the documented system design [2]. the testing phase is the most critical in a web-based information system. In this phase, we compare the functionality that has been built with the expected functionality. If appropriate, we assume that the product follows the user's wishes. This stage is the stage where the system begins to be implemented. At this stage, a system first interacts with the user, and the user starts to take advantage of the system [2]. This method is used because it has benefits, including flexibility in its application.
Several studies related to the web development life cycle (WDLC) method and Information system were carried out by Febriani Nur A.K. et all., in his research using the WDLC method to design electronic official document management applications based on organizational needs so that they succeed in fulfilling security solutions including guaranteeing the confidentiality, authentication, and integrity. [3] D.trianti et al. have succeeded in building a web-based application for student savings data processing using the web development life cycle method. This application is used to help display transaction information in detail to students and parents of students. The application that was built also succeeded in minimizing recording errors and loss of student savings books. [4] R.kaban et al. in his research by applying the WDLC method for the design of a responsive web-based library information system that can be appropriately displayed by all browsers and hardware, such as PCs or mobile devices, so that it can make it easier for members and officers to carry out search, borrowing, and returning activities book [5].
Dermawan et al., In their research, succeeded in developing the IKRA-ITH National Semester web using the WDLC method. The IKRA-ITH National Semester Web development has fulfilled the user acceptance test and can be used to promote Universitas Persada Indonesia Y.A. In their research, I [6] Hisham M.R et al. have succeeded in developing a web marketplace for household needs using the WDLC method. Users can order the requirements in this web marketplace using the cash-on-delivery payment method and online bank payment points. Virtual or cashless payments are needed in the current era of the Covid 19 pandemic. [7] Meanwhile, Karim Luthfi et al., in their research using the web development life cycle (WDSL) method, succeeded in developing a guest scheduling information system at the ASN employee training center, the Ministry of Village Development, Disadvantaged Regions and Transmigration. This application can make it easier for the admin or user to fill in data and schedule [8]. Susanto, in his research entitled Implementation of an e-document information system at the Semarang City Public Works Service, has proven that a combination of technology and the activities of people using technology can support operations In this research, an android mobile-based information system for road damage complaints was built using Android Studio. This application was created to make it easier for the public to report road damage complaints. Moreover, related parties can respond adequately [11]. N. Rofi'ah et al., in their research in Probolinggo, succeeded in creating a geographic information system about road damage, making it easier for PUPR to prioritize or handle road repairs [12].

METHODS
The method used in this study adopts the WDLC (web Development Life Cycle) method. This method provides a basic structure that includes various guidelines for meeting the requirements of a web. All types of web application development processes can adopt WDLC. In addition, it can also be modified by including prototyping and iterative structure to improve quality. The following figure shows several stages in the Web Development Life Cycle method. b) Understand the user. Which serves to identify system users. And map the obstacles faced by users of this system c) Understand the technology to be used and its constraints d) Identification of system owners and system users. e) Deciding the use of information generated by the system will be helpful to what extent.
The next stage is the analysis stage. At this stage, the analyst uses information that has been obtained to be processed systematically into the primary function of the information system, such as the need for data input, output, and user performance. This study's programming language and database design use the PHP and MySQL programming languages. The next stage is the design and development stage. At this stage, the road damage information system has designed a blueprint using the Unified Modeling Language (UML), as shown in Figure 2.

Figure 2. Use Case Diagram
From the picture above, it can be concluded that the admin can manage broken road data, print damaged road data, and collect admin data. Moreover, it is required to log in first before working data; after successfully logging into the system, the admin can carry out three activities, namely, activities to manage damaged road data. This management includes inputting, editing, and deleting damaged data. In this case, damaged road data that has received treatment or repair can be deleted from the system. The next activity is that the admin can print road damage data based on the superior's request. The last activity is the admin data management activity, where the admin is authorized to manage system user data. The ERD or Entity-relationship Diagram System design can be described as shown in Figure 3.

Figure 3. ERD (Entity Relationship Diagram)
Based on the ERD design on Figure 3, the Madiun Regency Road Damage Information System Consists of 2 entities, each with different functions and attributes. The first entity has a role in verifying or validating admin data to gain access to the system. The entity has the attributes Id, Fullname, username, password, and email. While the second entity has a function to store road damage data where the second entity has the attributes Id, No_section, Section, Pangkal_ruas, Ujung_ruas, Width_ruas, Km_beginning, Km_end, Type_road, Class_road, User_input, and log_delete. Table design can be seen in Table 1 and  Table 2. The function of the admin table is to store admin data used to verify user data to gain access to the system. Admin table structure contains field id as a unique data parameter that cannot be the same and is auto incremental. The field "full name" is for storing complete name data, and the field "username" is used for storing username data as a user parameter for the login process. The password field is used for storing passwords user encrypted with MD5 mode and e-mail to keep the user's e-mail.
The Road Section table is used to store damaged road data, and this table is related  to the admin table with the id parameter in the admin table and user_input in the  road sections table.   Table 2. Type_jalan Varchar (50) 10 Kelas_jalan Varchar (50) 11 User_input Varchar (50) 12 Log_delete Enum The road segment table consists of the following fields, id, no_section, segment, base_section, end_section, length_section, width_section, km_beginning, km_end, type_path, class_path, user_input, log_delete.
The next stage is the testing stage. In this stage, the method used for the testing stage is Blackbox Testing. Blackbox testing is software testing in terms of functional specifications without testing the design and program code to determine whether the software's functions, input, and output comply with the required specifications [13]. Blackbox Testing is easy because it only requires the lower and upper limits of the expected data. Estimating the amount of test data can be calculated through the number of data entry fields to be tested, the entry rules it must meet, and the upper and lower limit cases it must try.
The last stage in the Web Development life cycle method is the implementation stage which includes system installation on the hosting/server and domain registration.

RESULTS AND DISCUSSION
The system interface design on the Madiun Regency Road Damage Information System is as follows. First, it is the interface design for logging into the system is shown in Figure 4. In figure 4. It can be seen that for the login process, the user is required to enter the user's username and password data and click the login button to enter the system. The design of the Road Damage SIM dashboard is as follows. When the user selects the delete table data menu, data deletion confirmation will appear. The interface design of Wipe Data Road Damage is as follows.  On the data printing menu, all data that has been stored will be displayed, and then the user can print the page. The login page displays the login form for the admin as verification of admin access rights into the system. The login display can be seen in Figure 11.  The Road Damage Data page displays a road damage data table, and users can add data, edit data, and delete data. The Road Damage Data Edit page displays data in the input then the user can make changes to the data, which will then be stored in the database .  If the decision maker needs road damage data as a reference for implementing road repair and maintenance, it can be done in two ways. The decision maker logs into the system and gets the data, or the admin can print the required road damage data and give it to the decision maker. For the system testing phase using BlackBox testing with the following results Users can print road damage data stored in the database via the print button on the right.
✓ 100 Based on the table above, the test results with the eight main parameters state that the function of the eight parameters can run and is appropriately validated.

CONCLUSION
From the explanation above, we can conclude that the road damage information system in the Madiun district has been successfully built using the web development life cycle (WDLC) method. The test results also show that all functions in the system can run properly. Data already stored in the system can be printed or viewed and used to assist decision-makers in prioritizing the construction and repair of damaged roads. In the future, the road damage information system in Madiun Regency can add new features according to the needs of the Madiun Regency government without changing the initial design.