Object-oriented Information Systems Research Articles

ALGORITHM FOR DETECTION OF ABUSIVE CONTENT IN AUDIO CONTENT FOR IMPLEMENTATION IN OBJECT-ORIENTED INFORMATION SYSTEM

The paper proposes the basic principles of developing an object-oriented information system for detecting abusive content in Ukrainian-language audio content based on a new algorithm that uses statistical and neural network approaches to detect abusive content. Detecting offensive content in text and audio content is an urgent task, as it helps to create a safe and healthy environment for communication, especially in online platforms. Offensive content can harm the people who hear or read it and violate their rights. It can also have a negative impact on society, contributing to the spread of hatred and violence. To detect abusive speech in audio content, the proposed approach uses two key components: the use of dictionary methods and the analysis of the emotional tonality of utterances. A set of reviews was used as a dataset to determine the abusive component of the content, which was expanded by the authors by adding words of abuse. An object-oriented information system architecture written in the Python programming language in the PyCharm programming environment is proposed. The information system consists of a software module for training recurrent neural network models and further saving trained instances, and a software module for detecting abusive content in Ukrainian-language audio content using trained RNN models. Since the recurrent neural network is trained on a short text data set, the system is less efficient at identifying texts that have a larger number of words. In the example of the proposed approach, the accuracy of detecting offensive content is more than 90%. This means that the algorithm works correctly in the absence of offending highlights in the test data set. The results of the analysis of the effectiveness of the proposed approach show that in the vast majority of cases the conclusions regarding the acceptability of audio content based on the level of abuse are correct.

Metaclasses in UML and in Programming Languages

Design and programming are important stages of the development process of object-oriented information systems. At the design stage, a domain model is built, in which metaclasses can be used. But, as widely known, there is no direct support for metaclasses in UML. The article describes how in some cases it is possible to switch from models with metaclasses to models with regular classes. Several variants of such a transition are given. Two concepts of the metaclass are considered, which have now found application. Examples are given showing what capabilities the Python, Scala and Objective-C programming languages have for implementing such models. In addition, it analyzes how the concept of a metaclass is interpreted differently in programming languages.

Use of Unified Modeling Language in the Development of Object-Oriented Information Systems

Use of Unified Modeling Language in the Development of Object-Oriented Information Systems

National high-resolution land cover and land use information system

ABSTRACT In the last few years, the Spanish Land Cover and Land Use Information System (SIOSE) is undergoing a methodological and productive evolution focused on achieving a high level of geometric, thematic, and temporal detail. This methodological advance is based on the reuse and integration of official reference information on land cover and land use, such as cadastre (1:500–1:5000), agricultural identification systems (1:5000), forest maps (1:25,000), or LiDAR data (0.5 p/m2). This article presents the work carried out by the Instituto Geográfico Nacional (Spanish National Geographic Institute), in coordination with the rest of the project partners, in the generation of a high-resolution SIOSE by automatic data integration and visual review. To carry out the latter, an online framework has been designed to facilitate the access to data and to guide reviewers in editing. Resulting integrated data offers a detailed description for all thematic domains on land cover and land use never seen before in Spain at the National level and advances in the land management on many application fields. High-resolution SIOSE provides information at 1:5000 for the majority of classes and ensures a complete thematic content with more than 140 classes structured in an object-oriented information system.

Modeling Unified Language Templates for Designing Information Systems

Abstract—The most popular tools for developing object-oriented information systems are CASE-tools. More often, they do not support n-ary association relationships between classes. It is shown how, when describing a domain model, one can go from n-ary associations to binary ones, how to reduce the number of information system objects, and how to take into account the restrictions placed on objects. Situations that allow this kind of transformation are presented in the form of design patterns.

Managing Construction Projects: Developing Complexity into Complicatedness

Construction projects are understood as being complex and therefore in need of support through adequate tools to be successfully managed. Among others, the Building Information Model (BIM) is expected to provide a modern and powerful toolset allowing for reliable prediction of the respective development and behaviour. Based on Theory of Systems, the term of complexity in fact matches the principal capabilities of an object-oriented information system where e.g. the Building Information Modelling rests upon. However, any complex system tends to instable behaviour allowing principally for no reliable prediction, in particular in the single run required for unique projects with no possibility to rearrange processes without major losses. Correspondingly, experienced Construction Managers are judging the complexity of projects as a crucial obstacle to efficient execution but declare complexity as not measureable, thus as degree of unmanageability. Therefore, the inherent complexity of interdisciplinary projects needs to be reduced, i.e. transformed into complicatedness, not reducing the effort of elaboration but allowing for stable solutions. In order to achieve such a transfer, the inherent heterogeneity is utilized tracking down the strictness and linearity of the internal and external system borders, thus, investigating the separability of the adjacency matrices. These mainly topological considerations lead to criteria forming substructures finally allowing for predictable behaviour of the project structures with limited uncertainty. Therefrom, we expect some significantly improved understanding of the cybernetics of projects and consequently advanced possibilities in shaping and establishing activity-based risk management, which is crucial to nowadays construction and real estate projects.

Rancangan Sistem Informasi Pengendalian Kualitas Produk Barrel pada PT OneJect Indonesia dengan Metode Six Sigma

PT OneJect Indonesia faces the high level of defect on its barrel products. To overcome this problem, this study proposes an application quality control based on information system. We implement requirement analysis based on the needs of quality control methods, while to lower the defect rate we utilize Six Sigmamethod with DMAIC (define, measure, analyze, improve, control) phases. In define phase we determine the type of product to be investigated using Critical to Quality, as well as the problems and objectives. In measure phase we calculate DPMO value and sigma level; sigma value of 3.520 is obtained. Then we calculate P control chart to see the production process control. In analyze phase we create pareto diagram to see the types of dominant defects. Then we create cause-and-effect diagram to determine the cause of defects, and five whys diagram to determine the root causes of the defects. In improve phase, we do improvement analysis through FMEA table by calculating the RPN value to determine the failure modes to be controlled. In control phase, we implement the proposal and simulation of sigma value increase. The analysis and design uses object-oriented information system by Lars Mathiasen, and UML as the requirement modeling and the design system. The results obtained are the documents of top-level analysis and design of information system as a quality control material for the actual system development.

Sistem Informasi Pembelian, Persediaan, dan Penjualan untuk Apotek

This study aims to create a system that can simplify common operational activities of pharmacy such as purchasing, inventory, and sales. The system is expected to improve manual processes of purchasing, inventory, and sales into a computerized ones. In addition, this system also provides convenience, accuracy, and speed for owner or management to access reports of purchase, inventory, and sales in real-time. The research methods used are literature studies, field studies, and the methods of analysis and design of object-oriented information system design language UML (Unified Modeling Language). Tthe result of this research is an information system of purchasing, inventory, and sales of medicines that may help pharmacies to get information quickly and accurately, and to help pharmacy operations to run more effectively and efficiently.

A User-Centered, Object-Oriented Methodology for Developing Health Information Systems: A Clinical Information System (CIS) Example

The aim of this study is to present our perspectives on healthcare analysis and design and the lessons learned from our experience with the development of a distributed, object-oriented Clinical Information System (CIS). In order to overcome known issues regarding development, implementation and finally acceptance of a CIS by the physicians we decided to develop a novel object-oriented methodology by integrating usability principles and techniques in a simplified version of a well established software engineering process (SEP), the Unified Process (UP). A multilayer architecture has been defined and implemented with the use of a vendor application framework. Our first experiences from a pilot implementation of our CIS are positive. This approach allowed us to gain a socio-technical understanding of the domain and enabled us to identify all the important factors that define both the structure and the behavior of a Health Information System.

A Structure Recognition Technique in Contextual Generalisation of Buildings and Built-up Areas

A structure recognition technique is presented that can be employed for contextual building and built-up area generalisation in medium-scale topographic maps. Owing to various spatial configurations, a contextual mechanism is necessary to achieve acceptable results in cartographic generalisation. Spatial structures are usually implicit in data, and advanced analysis and processing methods are required to detect them. This technique is based on auxiliary geometric data structures and spatial analysis methods. A case study is performed with a topographic data set, using an interface developed in an object-oriented geographic information system (O-O GIS). The proposed approach was found to assist and improve automation.

객체지향 기반 효율적인 기능점수 측정 프로세스 설계 및 사례연구

최근 정보시스템 개발 패러다임이 객체지향 및 컴포넌트 기반으로 변해가고 있으며 이러한 방법론이 소프트웨어 산업계를 주도하고 있다. 소프트웨어 비용측정 분야도 이러한 변화에 적응하기 위해서 OO 환경에 적합한 비용 측정 모델로의 전환이 요구되고 있으며 실제 UCP 기법 등 객체지향 개념의 기능점수 연구가 진행되고 있다. 특히 객체지향 기능점수 측정 기법은 사용사례 중심으로 개발 프로젝트 초기에 적용 가능하고, 개발 진행 단계별 소프트웨어 산출물에 따라 생명주기 전체에 걸쳐서 적용 가능하고, UML 표기법에 의한 사용자와 의사소통으로 이해가 항상 가능하기 때문에 LOC 및 기존 기능점수 측정 기법의 한계를 극복하는 장점이 있다. 따라서 본 논문은 최근 객체지향 정보시스템 개발 환경에서 널리 사용되고 있는 UML 표기법 및 국방 CBD 방법론 절차에 의한 정보시스템 개발 프로젝트 진행에 따라 초기단계 시점(ROFP)과 분석단계 시점(AOFP)에서 기능점수를 측정하며, 전통적인 FPA 모델과 객체지향 FPA 모델을 통해 UML 모델링과 산출물을 기반으로 한 유스케이스와 클래스의 상관도 분석에서 서비스 기능과 객체/클래스 기능을 식별하고 기능점수를 구하는 측정기법을 제안한다. 무엇보다 전통적인 기능점수 측정 기법인 IFPUG-CPM 및 소프트웨어 대가기준의 기능점수 측정기법을 개선하여 객체지향 정보시스템 개발에 적합한 기능점수 측정 프로세스를 제시하고 사례연구를 통한 적합성 평가 결과를 제시한다. Recently, development paradigm of information system is turning into object oriented and component based, and this methodology is leading the software industry. To acclimatize aptly to this trend, users demand the assessment of software expenses to change with the appropriate model of computing costs of the environment, and some people are actually studying the concept of Object Oriented Function Point and UCP method. Especially, Object Oriented Function Point Measurement Process has good points in overcoming the bound of LOC and the existing the Function Point Measurement Process because Object Oriented Function Point Measurement Process is applicable to the early stage of development project mainly with the used cases, and valid to the life long period as the each stage of software products develops, and always understandable to communicate with users by the UML mark rules. Accordingly, this research is to measure Functional Point at ROFP and AOFP in accordance with the development project of information system by the national defense CBD methodology procedures and UML Interrelation Analysis that are recently and widely used in the developmental environment of object oriented information system. Furthermore, this study suggests the measurement method to obtain Functional Point, and identifies service function and object/class function in the correlation analysis of use case and class based on the products and UML modeling via traditional FPA model and object oriented FPA model. Above all, this study is to demonstrate the improvement of traditional Function Point Measurement Process, IFPUG-CPM and software cost basis, and reveal Function Point Measurement Process, which is appropriate to the development of object oriented information system, and suggest the evaluation results of the compatibility through case studies.

BUSINESS KNOWLEDGE-BASED GENERATION OF THE SYSTEM CLASS MODEL

The article presents principles of the Enterprise model-based generation of the Class model of the system (on the Platform independent level). Enterprise model being an integral part of the Repository of a CASE system becomes a core structure (Knowledge base) for the accumulation of business domain knowledge. The purpose of this article is to show that the knowledge stored in the Knowledge base is enough to generate one of the main models of the object-oriented Information systems development approaches, namely, Class model on the Platform independent level. In order to show the basic principles of the Class model generation algorithm, Enterprise and Class metamodels as well as mappings between the corresponding elements of these metamodels are presented and briefly discussed. The algorithm of the Class model generation and a brief overview of its realization are also presented in this paper.

Stepwise rigorous development of distributed agile information systems: from UML-diagrams to component-based Petri Nets†

The Unified Modelling Language (UML) is nowadays the de-facto standard method for developing Object-Oriented (OO) information systems (IS). UML is endowed with semi-formal graphical diagrams, allowing a multi-view based modelling. Further decisive UML strengths include advanced supporting tools as well as the readiness to extensions through stereotypes and profiles. Nevertheless, for contemporary critical IS where high-degree of reliability, flexibility and distribution are requested, such early semi-formal and multi-viewed UML-based modelling requires to be leveraged towards more disciplined, verifiable and intrinsically distributed specification. That is, first, the rigorous coherence between structural and behavioural diagrams have to be addressed. Secondly, the formal validation/certification of the application crucial properties should be soundly handled. Thirdly, the targeted UML-driven unified framework has to cater for componentisation, true-concurrency and adaptability. With the aim to preserve all the above UML strengths, we propose to describe early IS requirements using tailored UML diagrams, with mainly class-diagrams, OCL constraints and state-charts. We then smoothly shift these intuitive UML-driven IS multi-views towards a more unified, rigorous and distributed conceptual modelling, where certification and validation are intrinsic. This phase is governed by a rigorous component-based operational and visual framework called CO-NETS. It is based on a formal integration of most OO concepts and mechanisms, enhanced with modularity principles, into a variant of high-level Petri Nets. For rapid-prototyping purposes, CO-NETS behaviour is governed by Meseguer's rewriting logic. This innovative UML-CO-NETS-driven proposal for IS model-driven development is a validated, through a non-trivial case-study, on production systems. †A preliminary shortened version of this work appeared in MSVVEIS'07, a workshop at ICEIS'07 (June 12–17, Madeira) under the title ‘UML-driven Information Systems and their Formal Integration Validation and Distribution (Aoumeur and Saake 2007b)’.

A Theoretical Formulation of Object-Oriented Rough Set Models

We introduce object-oriented paradigm into rough set theory. First, we provide concepts of class, object, and name, respectively. Class structures represent abstract data forms, and abstract structural hierarchy based on is-a relationship and has-a relationship. Object structures illustrate many kinds of objects and actual dependence among objects by is-a relationship and has-a relationship. Name structures provide concrete design of objects, and connect class structures and object structures consistently. Next, combining class, name and object structures, we propose object-oriented information systems, which include “traditional” information systems as special cases. Moreover, we introduce indiscernibility relations on the set of objects, lower and upper approximations, and object-oriented rough sets in the object-oriented information systems.

Ontological Modeling Rules for UML: An Empirical Assessment

The Unified Modeling Language (UML) is widely accepted as the de-facto standard for object-oriented information systems (IS) design and software modeling. Recent research has proposed to extend the use of UML to conceptual modeling of application domains. Conceptual models serve both as the basis for communication and domain understanding among analysts, and as the starting point for IS software design. Prior research has proposed a set of modeling rules to provide the analyst or modeler with guidelines for using UML for conceptual modeling.This paper provides an empirical assessment of the benefits derived from using these modeling rules. Using an experimental study involving 53 subjects, it examines the effects of different levels of modeling rule application on application domain understanding. The results show statistically significant differences in the level of domain understanding that was derived from the various models.

Object-oriented modeling of construction processes by unified modeling language

Information processing to date between various participants and phases of construction is still often carried out verbally and through written communication on paper. The information exchange and processing through paper-based communication consumes substantial time. Due to increasing complexity of construction projects and the project management team setup, information processing and communication using information technology had become critical and essential for efficient project management and control. The inherent complexity of information flows in construction project has always posed the challenge for implementing standard information systems to cater to all the needs. It appears practically not feasible to develop and implement such systems for construction industry. In the present study, critical information flow common to all construction projects are evaluated and selected through a case study. An object-oriented information system model is developed for these selected processes using unified modeling language. The benefit of computerized information system is discussed and the model development by unified modeling language is compared with traditional structured modeling.

Object-oriented modeling of construction processes by unified modeling language

Information processing to date between various participants and phases of construction is still often carried out verbally and through written communication on paper. The information exchange and processing through paper-based communication consumes substantial time. Due to increasing complexity of construction projects and the project management team setup, information processing and communication using information technology had become critical and essential for efficient project management and control. The inherent complexity of information flows in construction project has always posed the challenge for implementing standard information systems to cater to all the needs. It appears practically not feasible to develop and implement such systems for construction industry. In the present study, critical information flow common to all construction projects are evaluated and selected through a case study. An object-oriented information system model is developed for these selected processes using unified modeling language. The benefit of computerized information system is discussed and the model development by unified modeling language is compared with traditional structured modeling.

Guest editorial: On Modeling Object-Oriented Information Systems

Object-Oriented Information System (OOIS) is an information system that employs object-oriented technologies in system design and implementation. Recent research advances and industrial innovations in distributed system modeling and Internet applications have enabled OOIS design and implementation to be carried out on the basis of new technologies and platforms. This special section on Modeling Object-Oriented Information Systems presents readers with a set of best papers selected from the 7th International Conference on OOIS. Reviews of theories and applications of OOIS’s are also provided for predicating trends in OOIS modeling.

Combining EXPRESS and UML to implement a STEP-based system

The STEP-based system is developed the same as the object-oriented information system with the exception of language usage. The data modelling language adopted in the STEP-based system is EXPRESS, while object-oriented methodologies employ UML. The translation or mapping between EXPRESS and object-oriented methodologies plays a key role when implementing a STEP-based system. This investigation focuses on the mapping between these two languages while implementing a STEP-based system. Current research has not completely examined the capability of EXPRESS in dynamic modelling and the collaboration of UML and EXPRESS in software engineering. Static and dynamic modelling mapping are considered herein to corroborate how to naturally amalgamate these two languages. Diagrams in UML are employed to discuss the elements to be mapped to EXPRESS language throughout the development of the system. On the other hand, EXPRESS representation of these elements is discussed and mapped to UML notations. An illustrative example, product structure management in PDMS, demonstrates the effectiveness of the proposed mapping methods. The development of a STEP-based system can be shortened and made more systematic via the designed methods.

Architecture and design of adaptive object-models

Many object-oriented information systems share an architectural style that emphasizes flexibility and run-time adaptability. Business rules are stored externally to the program such as in a database or XML files instead of in code. The object model that the user cares about is part of the database, and the object model of the code is just an interpreter of the users' object model. We call these systems "Adaptive Object-Models", because the users' object model is interpreted at runtime and can be changed with immediate (but controlled) effects on the system interpreting it. The real power in Adaptive Object-Models is that they have a definition of a domain model and rules for its integrity and can be configured by domain experts external to the execution of the program. This paper describes the Adaptive Object-Model architecture along with its strengths and weaknesses. It illustrates the Adaptive Object-Model architectural style by describing a framework for Medical Observations (following Fowler's Analysis Patterns) that we built.