paint-brush
Building a Web-Based Roads Update Information System: Design, Development, and Evaluationby@restfulapi
147 reads

Building a Web-Based Roads Update Information System: Design, Development, and Evaluation

tldt arrow

Too Long; Didn't Read

The study discusses the design, development, and evaluation of a web-based roads update information system. It includes system architecture details, screenshots, and evaluation results based on ISO/IEC 25010 criteria, showing high acceptance and effectiveness across various functionality and usability parameters.
featured image - Building a Web-Based Roads Update Information System: Design, Development, and Evaluation
The RestfulAPI Publication HackerNoon profile picture

Authors:

(1) Benzar Glen S. Grepon, Northern Bukidnon State College, Philippines [email protected] (corresponding author);

(2) JC P. Margallo, Northern Bukidnon State College, Philippines;

(3) Jonathan B. Maserin, Northern Bukidnon State College, Philippines;

(4) Rio Al-Di A. Dompol, Northern Bukidnon State College, Philippines.

Abstract and Intro

Literature Review

Methodology

Results

Discussions

Conclusions

Recommendations

Research Implications

Practical Implications

Declarations

References and Author's Biography

DISCUSSIONS

This study intent to design, develop and evaluate a web-based roads update information system as an instrument that can be used by anybody who wishes to know the current situation of a particular road in a specific place. Figure 2 shows the over-all System Architecture of the study, where we can see the conceptual model, which defines its structure, behavior, and more views of the developed system; in the case of this study, there are three (2) external entities that can access the API set by the proponents for front end use. For this system to function, a working internet connection is necessary in syncing the Front-end, API, and access to the data and information in the database.


System screenshots and system views are presented in Figures 3, 4, 5, and 6. Figure 3 requires the Login of an administrator to have access to the system to control malicious use and to verify that all contributors are legit users to avoid inaccurate updates. The Homepage in Figure 4 shows the home page of the web application by accessing through Smart Phone's browser, Laptop, and Computer. It is the landing page of a web application that the users can access. It contains the search location bar to search the old posts. Traffic alerts include the reports submitted to the users. The recent road updates include the type of incident, location, and time. Location maps are specialized maps dedicated to finding a specific place, while Figure 5 shows the report information page, allowing users to post information about a particular incident. The admin will review the report information to determine if the report is valid and concise. If the reviewed post were approved, it would be shown as a recent road update. Figure 6 shows the Admin Dashboard, where all approvals and management of the road updates are done. The Administrator has the discretion whether to approve or disapprove a particular report of road cases by a citizen because the admin needs to verify whether the claims are valid to avoid possible confusion if all case reports are just done without a reasonable basis.


In terms of the evaluation results, table 1 shows a very interesting result. The respondents of this study are drivers, commuters, and travelers. During the evaluation of the regular users, it gives the feedback score about the system of the final output. ISO/IEC 25010 is used for the application evaluation assigned to the participants. The developed web application was evaluated and highly accepted average which is 4.21. Functionality suitability with a mean of 4.00, which is "Very Good", the degree to which a product or system provides functions accomplished defined and suggested needs when used under specified conditions; performance efficiency has a mean of 4.0, which is "Very Good", the performance relative to the amount of resources used under stated conditions; compatibility has a mean of 4.0, which is "Very good" the system can interchange details with other goods, systems/structure or elements, and/or carryout its necessary functions while sharing the same hardware or software environment, usability has a mean of 4.6 which is "Excellent", the system can be used by specified users to achieve established goals with efficacy, efficiency and satisfaction in a specified context of use, reliability has a mean of 4.5 which is "Excellent", It performs designated functions under specified state for a specified period of time, security has a mean of 4.5 which is "Excellent", the system safeguard information and data so that entities such as persons or other commodity or systems/modules have the standard of data access suitable to their types and levels of authorization. , maintainability has a mean of 4.5, the potency and efficiency with which a product/commodity or systems/modules can be change to improve, correct, or adapt it to changes in the environment, and requirements and portability have a mean of 4.5 which is "Excellent"- the system can be transferred from one hardware, software or other operational or usage environment to another. The overall average weighted mean of the application is 4.21, which was rated as "Excellent". This means that application is acceptable during the evaluation.


This paper is available on arxiv under CC 4.0 license.