Emergency Maintenance Module Design for Hull Using Visual Basic 6.0

Pemeliharaan darurat(emergency maintenance) pada lambung kapal memegang peranan yang penting untuk mengembalikan keselamatan dan performa dari suatu kapal. Pemeliharaan darurat pada lambung kapal meliputi keseluruhan aktivitas manusia untuk menghasilkan produksi yang meliputi banyak pihak yang saling terkait dan juga meliputi suatu kombinasi aktivitas yang kedua- duanya mempunyai karakter operasional dan juga managerial, antara lain aktivitas: meninjau ulang, mensurvei, memeriksa, mengukur, pendeteksian, pengujian, perbaikan, persediaan material, pengumpulan data, meneliti, dokumentasi, pelaporan, pengujian, perekaman, dan verifikasi atau auditing. Melihat banyaknya pihak yang terkait, banyaknya pekeijaan yang harus dilakukan dan juga standar mutu yang harus dicapai maka pemeliharaan darurat untuk lambung kapal akan menjadi kompleks dan memerlukan sebuah alat yang dapat membantu dalam pelakasanaa pemeliharaan darurat untuk lambung kapal. Berdasarkan situasi di atas kita menawarkan suatu alat alam wujud perangkat lunak, yang diharapkan dengan adanya perangkat lunak ini pengambilan keputusan dan koordinasi mengenai pemeliharaan darurat untuk lambung kapal bisa dilakukan dalam satu meja(single desktop solution). Perangkat lunak yang kita kembangkan akan kita beri nama Hull Emergency Maintenance Modul dimana Hull Emergency Maintenance Modul akan kita kembangkan menggunakan suatu bahasa program yang dibuat oleh Microsoft. Bahasa program ini dinamakan Visual Basic 6.0 sedangkan untuk mengembangkan Database Management System yang digunakan untuk mengolah basis data pemeliharaan darurat untuk lambung kapal kita menggunakan Microsoft SQL Server 2000 yang kompatibel dengan Visual Basic 6.0. ============================================================================================= Hull emergency maintenance plays an important part to restore the safety and performance of ship. Hull emergency maintenance cover the overall activity of human being to yield the production, covering a lot of party which related each other and covering an activity and represent combination of operational character as well as managerial character, for example the activity is: review, surveying, checking, measuring, detection, examination, repair, material supply, data collecting, checking, documentation, reporting, examination, recording, and verification or auditing Because the number of related party that involved, the number of a work to be done and quality standard that must be reached hence hull emergency maintenance will become complex and need a tool which can assist in execution of hull emergency maintenance. According the situation above we offer a tool in form of software, and is expected with the existence of this software the decision making and coordination between related party to execute hull emergency maintenance can be done in single desktop solution. Software that we develop we called Hull Emergency Maintenance Module. This software will we develop constructively using programming language that made by Microsoft. This Programming language is Visual Basic 6.0, and to develop the Database Management System that used for managing the database of hull emergency maintenance we use the Microsoft SQL Server 2000 that compatible with Visual Basic 6.0

Reverse engineering in construction

Recently a great deal of research into construction IT has been completed, and this is ongoing to improve efficiency and quality in the construction sector. The new innovation of 3D laser scanning is aimed at being used to improve the efficiency and quality of construction projects, such as maintenance of buildings or group of buildings that are going to be renovated for new services. The 3D laser scanner will be integrated with other VR tools such as GIS solutions and workbench for visualisation, analysis and interaction with a building VR model. An integration strategy is proposed for an Ordnance Survey map of the area and 3D model created by means of the laser scanner. The integrated model will then be transferred to the VR workbench in order to visualise, interact and analyse the interested buildings on purpose

Technical Debt Prioritization: State of the Art. A Systematic Literature Review

Background. Software companies need to manage and refactor Technical Debt issues. Therefore, it is necessary to understand if and when refactoring Technical Debt should be prioritized with respect to developing features or fixing bugs. Objective. The goal of this study is to investigate the existing body of knowledge in software engineering to understand what Technical Debt prioritization approaches have been proposed in research and industry. Method. We conducted a Systematic Literature Review among 384 unique papers published until 2018, following a consolidated methodology applied in Software Engineering. We included 38 primary studies. Results. Different approaches have been proposed for Technical Debt prioritization, all having different goals and optimizing on different criteria. The proposed measures capture only a small part of the plethora of factors used to prioritize Technical Debt qualitatively in practice. We report an impact map of such factors. However, there is a lack of empirical and validated set of tools. Conclusion. We observed that technical Debt prioritization research is preliminary and there is no consensus on what are the important factors and how to measure them. Consequently, we cannot consider current research conclusive and in this paper, we outline different directions for necessary future investigations

Using Automatic Static Analysis to Identify Technical Debt

The technical debt (TD) metaphor describes a tradeoff between short-term and long-term goals in software development. Developers, in such situations, accept compromises in one dimension (e.g. maintainability) to meet an urgent demand in another dimension (e.g. delivering a release on time). Since TD produces interests in terms of time spent to correct the code and accomplish quality goals, accumulation of TD in software systems is dangerous because it could lead to more difficult and expensive maintenance. The research presented in this paper is focused on the usage of automatic static analysis to identify Technical Debt at code level with respect to different quality dimensions. The methodological approach is that of Empirical Software Engineering and both past and current achieved results are presented, focusing on functionality, efficiency and maintainabilit

A Review of the Enviro-Net Project

Ecosystems monitoring is essential to properly understand their development and the effects of events, both climatological and anthropological in nature. The amount of data used in these assessments is increasing at very high rates. This is due to increasing availability of sensing systems and the development of new techniques to analyze sensor data. The Enviro-Net Project encompasses several of such sensor system deployments across five countries in the Americas. These deployments use a few different ground-based sensor systems, installed at different heights monitoring the conditions in tropical dry forests over long periods of time. This paper presents our experience in deploying and maintaining these systems, retrieving and pre-processing the data, and describes the Web portal developed to help with data management, visualization and analysis.Comment: v2: 29 pages, 5 figures, reflects changes addressing reviewers' comments v1: 38 pages, 8 figure