Service of SURF
© 2025 SURF
The Tuntang Watershed is an important watershed in Central Java. Management of watersheds in the Tuntang stream is a priority for various parties to carry out. One of the things that threatens the sustainability of the Tuntang watershed is erosion. The erosion rate can lead to sediment accumulation and siltation in the Tuntang River reservoir, which can cause catastrophic flooding. Flood disaster mitigation caused by erosion needs to be done, one of which is by calculating the erosion rate per year that occurs in the Tuntang watershed. This study calcultated the predicted erosion rate (per year in the Tuntang watershed) using the Revised Universal Soil Loss Equation (RUSLE) method, processed using the Google Earth Engine (GEE). Google offers a cloud-storage technology called GEE. Programming in JavaScript is required to operate GEE. GEE is a petabyte-scale data-based tool that can be used to analyze and archive geospatial data that is open source. The computing environment is designed for the processing of geospatial data, including the depiction of spatial analysis of satellite imagery. Data for RUSLE is obtained from the database in GEE, and the results can be imaged on a map. According to the study's findings, the degree of soil erosion throughout the Tuntang Watershed was essentially constant, with Moderate erosion predominating in the majority of locations. Senjoyo Sub Watershed, Rowopening Sub Watershed, and Tuntang Hilir Sub Watershed are the primary locations with severe erosion. Rowopening Sub Watershed is the region that is the worst.
LINK
MULTIFILE
Abstract-Architecture Compliance Checking (ACC) is an approach to verify the conformance of implemented program code to high-level models of architectural design. ACC is used to prevent architectural erosion during the development and evolution of a software system. Static ACC, based on static software analysis techniques, focuses on the modular architecture and especially on rules constraining the modular elements. A semantically rich modular architecture (SRMA) is expressive and may contain modules with different semantics, like layers and subsystems, constrained by rules of different types. To check the conformance to an SRMA, ACC-tools should support the module and rule types used by the architect. This paper presents requirements regarding SRMA support and an inventory of common module and rule types, on which basis eight commercial and non-commercial tools were tested. The test results show large differences between the tools, but all could improve their support of SRMA, what might contribute to the adoption of ACC in practice.