ENTERPRISE ARCHITECTURE SEBAGAI STRATEGI DALAM OPTIMALISASI PROSES DAN TEKNOLOGI MENGGUNAKAN TOGAF ADM

PT XYZ merupakan perusahaan yang menawarkan audit pihak ketiga untuk menyediakan jasa sertifikasi sumberdaya alam dan lingkungan. Dalam menjalankan perusahaannya, PT XYZ memiliki layanan utama pada fungsi sertifikasi yaitu Audit Sertifikasi dan Penerbitan Dokumen Legalitas. Seiring dengan kemajuan teknologi informasi dan komunikasi, PT XYZ memiliki beberapa kendala dan membutuhkan strategi teknologi informasi yang tepat untuk menyelesaikan permasalahannya. Pertukaran data yang belum efektif merupakan salah satu kendala yang terjadi di fungsi sertifikasi yang menyebabkan munculnya keluhan pelanggan terhadap kecepatan layanan. Dalam penelitian ini akan membahas perancangan Enterprise Architecture sebagai strategi dalam optimalisasi proses dan teknologi menggunakan TOGAF ADM. Perancangan tersebut dimulai dari preliminary phase, architecture vision, business architecture, data architecture, application architecture, technology architecture, opportunities and solution, dan migration planning. Dengan blueprint dan IT Roadmap sebagai hasil akhir dari penelitian ini, diharapkan akan membantu PT XYZ dalam menyelesaikan permasalahannya segaligus menjadi strategi dalam optimalisasi proses dan teknologi yang tepat.

ENTERPRISE ARCHITECTURE SEBAGAI OPTIMALISASI PROSES DAN PENGEMBANGAN TEKNOLOGI INFORMASI MENGGUNAKAN TOGAF ADM (STUDI KASUS: PT XYZ)

Teknologi Informasi memiliki peran penting bagi perusahaan dalam mengolah dan menyediakan informasi yang dibutuhkan oleh para stakeholder. Namun, tidak semua perusahaan mampu mengimplementasikan dan mengembangkan teknologi informasi yang bersesuaian dengan kebutuhan perusahaan, termasuk PT XYZ. PT XYZ merupakan perusahaan jasa yang bergerak dibidang sertifikasi Verifikasi Legalitas Kayu (VLK). Dalam menjalankan perusahaannya, PT XYZ didukung oleh fungsi Manajemen Umum dan Keuangan. Namun seiring berjalannya waktu, fungsi Manajemen Umum dan Keuangan tidak dapat menyesuaikan dengan cepat perkembangan teknologi yang ada. Hal ini ditandai dengan terbatasnya sistem yang digunakan oleh perusahaan seperti Microsoft Excel. Penggunaan TI yang belum optimal berdampak pada internal dan eksternal perusahaan, yang menyebabkan terjadinya penurunan tingkat loyalitas pelanggan sebesar 46,43% selama setahun terakhir. Untuk itu diperlukan solusi Enterprise Architecture (EA) guna menyelaraskan kebutuhan bisnis dan teknologi, juga mengoptimalisasi pengembangan teknologi informasi. Enterprise architecture dirancang menggunakan metode TOGAF ADM. Perancangan EA dimulai dari Preliminary Phase sampai Information System Architecture (Application Architecture). Penelitian ini akan menghasilkan artefak berupa matrices, catalog, dan diagram. Adapun hasil akhir penelitian ini adalah rancangan Blueprint Enterprise Architecture sebagai gambaran umum usulan proyek untuk mendukung strategi bisnis dan pengembangan teknologi pada fungsi Manajemen Umum dan Keuangan di PT XYZ.

Principles of securing RESTful API web services developed with python frameworks

This article discusses the key points of developing a secure RESTful web service API for keeping a student achievement journal. The relevance of using web services has been analyzed. The classification of web applications is given. The features of the Single Page Application architecture were considered. Comparative characteristics of architectural styles of application programming interfaces are given. Requirements to be met by RESTful API services are considered. The basic principles of API security were analyzed. A list of the main vulnerabilities that may appear during the development of the REST API is given. An overview of popular authentication schemes (methods) is given. Comparative characteristics of web frameworks of the Python programming language are given. The main tools used in the development of web API applications are listed. The process of creating a secure prototype of a RESTful web service API in Python using the Flask microframework and a tool for describing the Swagger specifications is presented. The process of configuring the application was examined in detail. The main recommendations for securing a web application, database and web server settings are listed. The key points of ensuring the protection of the developed web application are considered. The results obtained were analyzed.

The Single Page Application architecture when developing secure Web services

The article is devoted to the development of a prototype of a secure single page-application (SPA) web service for automating user information accounting. The relevance of this study is very high due to the use of web services. The article provides a classification of web applications and shows the features of the architecture of a single page application used in the development of the service. Based on a comparative analysis of the architectural styles of the API, the most appropriate style was selected. Considered and taken into account the key points of the development of a secure application programming interface (API), the requirements that must be met by RESTful API services. The work used popular authentication schemes (methods). A comparative characteristic of web frameworks of the Python programming language is given, on the basis of which a tool for implementing a web service is selected. Shows the main advantages of using Python when developing paged web services and the security tools included in the standard package of the Flask web services development framework. Shows how to securely prototype a Python RESTful SPA Web Service API using Flask. An example of using the Swagger tool to describe the specifications of the developed API is given. The process of setting up the application is considered in detail. The main recommendations for securing a web application, setting up a database and a web server are listed. The key points of ensuring the protection of the developed web application are considered. Conclusions are made regarding the choice of the architectural style of the application API, the most suitable tools and technologies for the software implementation of the service.

Modelling owner’s physiognomies & incitements for the adoption of enterprise application architecture for supply chain management in small and medium enterprises: A case of Capricorn District Municipality

The adoption of enterprise application architecture (EAA) for supply chain management (SCM) in small and medium enterprises (SMEs) was influenced by the owner’s physiognomies and incitements (OPIs) on a routine basis. The study employs a quantitative approach based on a linear regression model, which uses diagnosis tests “Cronbach's Alpha, normal distribution, and Kolmogorov-Smirnov test” that makes descriptive statistics possible on Pearson correlations, analysis of variance (ANOVA), Pearson's Coefficients, and linear regression. The study examines whether OPIs affect the adoption of EAA for SCM in SMEs within Capricorn District Municipality. The paper exploits the original data set of 310 SMEs, targeting predominantly both SMEs’ owners and managers to run linear regression models with the dependent variable “actual adoption of EAA” and independent variable “OPIs”. A novel piece of authenticity for the models is the incorporation of OPIs within the SCM activities and whether there were any, collaborative influences affecting the adoption of EAA. The findings have a bearing on SMEs’ SCM growth strategies, directed towards the technology acceptance model.

Robust Integration of Biodiversity Data by Process- and State-based Representation of Object Histories and Modular Application Architecture

Biodiversity data is obtained by a variety of methodological approaches—including observation surveys, environmental sampling and biological object collection—employing diverse sample processing protocols and data transformations. While complete and accurate accounts of these data-generating processes are important to enable integration and informed reuse of data, the structure and content of published biodiversity data currently are often shaped by specific application goals. For example, data publishers that export specimen-based data from collection management systems for inclusion in aggregations like those in the Global Biodiversity Information Facility (GBIF) must frequently relax their internal models and produce unnatural joins to fit GBIF’s occurrences-based data structure. Third-party assertions over these aggregated data therefore assume the risk of irreproducibility or concept drift. Here we introduce process- and state-based representation of object histories as the main organizing principle for data about specimens and samples in Digital Information System for Natural History Data (DINA, Glöckler et al. 2020)-compliant collection management software (Fig. 1). Specimens, samples and objects in general are subjected to a variety of processes, including planned actions involving the object, e.g., collecting, preparing, subsampling, loaning. Object states are any particular mode of being of an object at a certain point in time. For example, any one intermediate step in preparing a collected specimen for long-term conservation in a collection would constitute an individual object state. An object’s history is the entire chain of these interrelated processes and states. We argue that using object histories as main conceptual modeling paradigm in DINA offers the generality required to accommodate a diverse, open set of use cases in biodiversity data representation, yet also offers the versatility to serve as basis for use-case specific data aggregation and presentation. Specifically, a representation based on object histories provides a coherent structure for documenting individual processes and states for any given object and for linking this documentation (e.g., textual descriptions or images pertaining to a given process or state), a natural representational structure of the real-world sequence of processes an object participates in and for the data generated in these processes (e.g., a DNA-extraction procedure and sequence information generated on its basis), a straightforward structure to link data about related objects (e.g., tissue samples, the biological specimen a bone is derived from) in a network of connected object histories. a coherent structure for documenting individual processes and states for any given object and for linking this documentation (e.g., textual descriptions or images pertaining to a given process or state), a natural representational structure of the real-world sequence of processes an object participates in and for the data generated in these processes (e.g., a DNA-extraction procedure and sequence information generated on its basis), a straightforward structure to link data about related objects (e.g., tissue samples, the biological specimen a bone is derived from) in a network of connected object histories. The approach is designed to be embedded in DINA’s modular application architecture, so that information on object histories can be accessed via corresponding APIs either through its own interfaces (Fig. 2) or by integration with external web services (Fig. 3). Viewing collection management tasks as part of object histories also informs delineation of modules to support these tasks with specialized functions and interfaces. It also admits the use of persistent, dereferencable identifiers for individual processes and states in object histories and for linking their representations to elements in ontologies and controlled vocabularies. In this contribution to the symposium, DINA's object histories as a main organizing principle for collection object data will be discussed and the utility of using it in the context of modular application architecture, data federation, and data integration in projects like BiCIKL will be illustrated.

Designing a reference architecture for health information systems

Background Healthcare relies on health information systems (HISs) to support the care and receive reimbursement for the care provided. Healthcare providers experience many problems with their HISs due to improper architecture design. To support the design of a proper HIS architecture, a reference architecture (RA) can be used that meets the various stakeholder concerns of HISs. Therefore, the objective of this study is to develop and analyze an RA following well-established architecture design methods. Methods Domain analysis was performed to scope and model the domain of HISs. For the architecture design, we applied the views and beyond approach and designed the RA’s views based on the stakeholders and features from the domain analysis. We evaluated the RA with a case study. Results We derived the following four architecture views for HISs: The context diagram, decomposition view, layered view, and deployment view. Each view shows the architecture of the HIS from a different angle, suitable for various stakeholders. Based on a Japanese hospital information system study, we applied the RA and derived the application architecture. Conclusion We demonstrated that the methods of the software architecture design community could be used in the healthcare domain effectively and showed the applicability of the RA.

Perancangan Federal Enterprise Architecture Framework Pengelolaan Surat Pada Dinas Perhubungan Kabupaten Sukabumi

Dinas Perhubungan Kabupaten Sukabumi mempunyai beberapa bidang salah satunya bidang Kasubag Umum dan Kepegawaian yang mempunyai fungsi pengumpulan dan pengolahan data. Fungsi tersebut tentunya banyak dikerjakan oleh bagian pengarsipan surat karena bagian tersebut merupakan bagian yang paling penting atau bisa disebut sebagai jantung dari Dinas Perhubungan Kabupaten Sukabumi. Dimana bagian tersebut mengatur pengelolaan dalam surat masuk, surat keluar, dan laporan surat. Kegiatan pengelolaan surat masih menggunakan buku agenda, kartu disposisi dan Microsoft Office sehingga kegiatan pengelolaan surat terlihat masih belum optimal. Dari kegiatan pengelolaan surat di Dinas Perhubungan Kabupaten Sukabumi ditemukan beberapa permasalahan yaitu terjadi kehilangan data surat masuk tahun 2019 mencapai 50% sedangkan kesalahan dalam pendataan surat terjadi pada data surat keluar mencapai 10-40% sehingga dapat berpengaruh terhadap pembuatan laporan jumlah surat. Dinas Perhubungan Kabupaten Sukabumi harus mewujudkan Enterprise Architecture untuk dapat mengatur dan mengawasi dalam pengelolaan surat. Dengan adanya hal tersebut, maka peneliti akan membuat “Perancangan Federal Enterprise Architecture Framework Pada Pengelolaan Surat Di Dinas Perhubungan Kabupaten Sukabumi”. Hal ini akan menjadi solusi dari permasalahan tersebut. Penelitian ini akan menghasilkan kerangka kerja (blueprint) yang berupa business architecture, data architecture, application architecture, dan technology architecture.