Unified Modeling Language Notation Research Articles

Design and building system analysis on the smart fisheries village (SFV) website at the banyuwangi fisheries training and counseling center

This research aims to analyze and design a smart fisheries village-based website system to facilitate back-end, front-end, and UI/UX designers in the application of website creation according to the needs desired by the agency and with an organized database so that the creation of data reports will be faster. The early stages of the research began with the identification of the the specific needs of fishing villages and involved an in-depth analysis of the system needs that supported the vision of the Smart Fisheries Village. The design began with data collection consisting of observation methods and interviews, where researchers interviewed the authorities. In this method, the author gives 5 questions to the user, data analysis, and design of the Unified Modeling Language (UML). The design of this SFV web system uses a Unified Modeling Language (UML), which involves the use of diagrams and UML notation to describe various aspects of the system visually. The results of this study include UML diagrams, which encompass activity diagrams (for users and admins), flow diagrams (for users and admins), use case diagrams (for users and admins), and class diagrams that have undergone 4-5 iterations. The design of the Smart Fisheries Village website system is necessary to improve the welfare of the fishing village. Contributions of this research include the standardization of modeling, increased productivity, improved analysis and planning, and improved understanding. Previous research might have concentrated on a single type of system or domain. However, research should be expanded to various types of systems and industries.

Analysis and Design of Customer Service Information Systems at Bersaudara Car Repair Shop Of Pangkalpinang

Bersaudara Car Repair Shop of Pangkalpinang is a business that operates in the field of automotive services, specializing in car maintenance and repair. Currently, customer service data processing still uses a manual system with Microsoft Office tools. In its application, this application cannot support fast and easy work. This can have implications for service providers towards customers, because they often encounter obstacles in the process of handling repairs and making reports. The aim of this research is to provide a solution in forming a needs analysis and documented information system design which will be developed into an information system application at the brothers' car repair shop. Based on the SDLC (Software Development Life Cycle) concept, the initial thing needed to produce an information system is to create a needs analysis and documented system design. The system analysis and design carried out here goes through the stages of data collection, carrying out analysis using the PIECES (Performance, Information, Economic, Control, Efficiency, Service) framework and carrying out system design using an object-oriented approach using UML (Unified Modeling Language) notation. The results of the analysis and design were tested in the form of a design evaluation using the consistency analysis method which was proven to have a consistent percentage value of 100%. The results of this design are included in the correctness category which proves that the system requirements and system design are consistent and correct.

Application of Rapid Application Development Method in Designing Knowledge Management System to Improve Employee Knowledge and Performance at Ministry of Agriculture

This research aims to design and build a knowledge management system that can accommodate, manage, and disseminate knowledge to increase employee knowledge. In this research, data collection was obtained in three ways, including observation, interviews, a literature study, and a study of similar literature. The author uses the building block knowledge management method, unified modeling language (UML), to design a web-based system with a user interface that is quite easy to use. In this research, the author uses an object-oriented system development method, namely rapid application development (RAD), which uses unified modeling language tools to describe use case diagrams. Based on the research results, it was found that the KMS was built on a web basis using the RAD (rapid application development) approach and UML (unified modeling language) notation for system analysis design and PHP and MySQL for coding and databases. Before the existence of KMS, searching for documents could take 10 minutes, whereas after the KMS application, users only need five minutes to search for stored documents, resulting in a time efficiency of nine minutes. This system also helps employees communicate with each other anytime and anywhere by creating new discussion topics. Apart from fostering a culture of knowledge sharing, discussion forums in this system can be used as a place for employees to collaborate and find solutions.

“MALIK” (APLIKASI MARKETPLACE BUSANA MUSLIM)

This study aims to carry out business planning and system design for the creation of a business startup marketplace based on a Muslim fashion mobile application with the name MALIK. The research method used is by using observation, questionnaires, interviews, and literature study. For system design, the approach method used is object-oriented analysis design. The results of this research will be a business plan in the form of business plan documentation complete with analysis using the business model canvas, industry analysis using Porter's Five Forces Model, and SWOT analysis. The next stage is to design a system in the form of a diagram with a unified modeling language notation, and a user interface. The results of the research that can be taken are that the target sample of customers is interested in Muslim clothing, buying Muslim clothing using the marketplace media with feature development carried out by MALIK in the form of online Muslim clothing tailoring, and virtual fitting rooms.

Modelling Quality Assurance System Process Using UML Notation

Higher learning institutions (HLIs) employ academic quality assurance (AQA) approach to assess quality performance in the higher education system. It aims to assist in the process of obtaining accreditation and recognition for HLIs. Modelling the AQA process is significant for understanding the current process and subsequently developing an information system. Therefore, this paper describes steps in modelling the academic quality assurance (AQA) process through unified modelling language (UML) notation. Metamodelling approach is used to identify the domain concepts and relationships before transform into UML-based foundations. The findings propose AQA domain into three different UML diagram which are use case modelling, structural modelling and behavioural modelling. Use case diagrams show the interaction between users and the system. While class diagrams structure the AQA endeavour process into categorisation systematically. The communication diagrams show the behavioural structure of the system through messages that pass between the objects in the interaction. This work gives stakeholder’s insight into AQA endeavour through UML notation proposed; i.e.; understanding the AQA process, assist in decision making process and helps in designing new system related to the endeavour process.

UML Transformation to Java-based Software Product Lines

Software product line engineering (SPLE) is an emerging approach that enables variability management in software development. SPLE offers tremendous benefits, but lack of tool support becomes a barrier in the adoption of SPLE. Variability modules for Java (VMJ) is an implementation approach that is defined based on the variability modules (VM) concept to support SPLE. VMJ combines Java modules system and design patterns that are commonly used by software developers. VMJ is accompanied by a UML profile, called UML-VM profile, which extends UML notation to model variability in the UML diagram. UML-VM diagram is used to model the problem domain, and VMJ is used in the domain implementation. In this research, we design a model transformation from Unified Modeling Language (UML) diagram into VMJ. The transformation rules are defined based on the UML-VM profile and implemented in the Eclipse Acceleo model to text transformation. As a result, a UML diagram can be transformed automatically into Java-based software product lines. The transformation tool is evaluated using a case study by comparing the generated code and the actual implementation.

Sistem Informasi Absensi Kepegawaian Berbasis WEB Pada PT. Prada Bangun Persada

PT. Prada Bangun Persada is a branch company that has a headoffice in the Jakarta area which is engaged in the field of SportsEquipment which has staff that must be managed properly. In thismanagement, the company makes an annual performance report,one of which contains a report on staffing. PT. Prada BangunPersada has several sections in the organizational structure, one ofwhich is the general responsibility section and the finance section.The general responsibility department and the finance department inthis company do not yet have an efficient personnel informationsystem application and are still processing data manually, resultingin various obstacles. Constraints experienced by the general personin charge are still using paper forms in making employee data andsubmitting employee letters so that they are less efficient and alwaysprovide paper forms. Then the storage of these letters still uses theirrespective folders based on the type of letter so that it is difficult toaccess and search for employee data and it is not safe if the storageis still using a folder and sometimes its validation is not handledproperly. Then in the finance department in the employee payrollprocess, which still calculates and saves with Microsoft excel formatfiles which causes low security and confidentiality of employeepayroll data at risk of file damage if exposed to a virus andemployees can easily access the file. This Personnel InformationSystem uses a 2-step method. First, the data collection method wascarried out in three ways, namely the observation method, theinterview method and the literature study. Second, the systemdevelopment method that will be used is the waterfall systemdevelopment method, and uses UML (Unified Modeling Language)notation as tools.

A Retargetable Model-Driven Framework for the Development of Mobile User Interfaces

Since the emergence of mobile devices, the architecture of mobile applications has been transformed significantly. In mobile applications, the User Interface (UI) is one of the major elements, but its development is complex and time-consuming. Existing practices do not support various presentation issues of the UI at a higher abstraction level, in a retargetable fashion, with complete tool support. Therefore, it is critical to develop a simple and automated framework for the development of mobile UIs by exploiting model-driven engineering concepts. In this paper, a Unified Modeling language (UML) profile for Mobile User Interfaces (UMMUI) has been proposed, which employs some standard UML notations for representing the mobile UI requirements at a higher abstraction level. Subsequently, a complete open-source transformation engine has been developed to automatically transform the high-level source models (in UMMUI) into the target low-level React Native implementation. Finally, the applicability of the proposed framework is validated through two benchmark case studies, i.e., Patient Management System and Library Application. The results verify that the proposed framework allows the modeling of UIs with simplicity and generates the target code automatically with minimum transformation losses.

Modeling the operation of synchronized supply chains under a collaborative structure

PropósitoEste documento propone y modela estrategias de colaboración y habilitación de intercambio de información, diseñadas para lograr mejoras significativas en el rendimiento de la cadena de suministro (SC). Algunas de estas mejoras incluyen la reducción del efecto látigo y mayores beneficios para los clientes y socios de la cadena de suministro. Proponemos un modelo de reabastecimiento totalmente colaborativo. El estudio detalla el flujo de información requerido para implementar nuevas estrategias de colaboración en la cadena de suministro, aclarando una estrategia específica para el intercambio de información que involucra niveles de inventario (en mano, en proceso, etc.), pedidos y previsión de la demanda.Diseño/metodología/enfoqueSugerimos la adopción de la metodología de Modelado de Procesos de Negocio, dirigida a identificar qué información debe ser compartida por los socios de la cadena de suministro, a fin de crear estrategias totalmente colaborativas.Hallazgoslas características del Modelado de Procesos de Negocio permiten la integración, sin un excesivo esfuerzo, de las estrategias de colaboración modeladas en un sistema de información general, creando una estructura flexible que puede adaptarse rápida e incluso automáticamente a las nuevas condiciones.Limitaciones/implicaciones de la investigaciónen este documento, se ha analizado una cadena de suministro en serie, sin embargo las empresas también suelen administrar cadenas más complejas. Cadenas compuestas de más de un miembro en el mismo escalón, cadenas divergentes, cadenas convergentes, cadenas de red, son todas configuraciones diferentes que requieren su propio algoritmo. Igualmente, en este artículo usamos la política de pedido “order up to” aunque también existen otras políticas que se pueden considerar para ampliar el alcance del modelo.Implicaciones prácticasel modelado de procesos BPM, específicamente a través del Lenguaje Unificado de Modelado (UML) y estándares para la notación de Modelado de Procesos de Negocio (BPMN), representa una técnica adecuada para desarrollar e implementar nuevas prácticas de colaboración de cadena de suministro, que sirve como un enlace de comunicación entre los gerentes y los desarrolladores de software.Implicaciones socialeslos resultados esperados de este trabajo implican la propuesta de un modelo de referencia para la colaboración de las organizaciones de la cadena de suministro, contribuyendo a la mejora de la creación de valor para toda la cadena de suministro colaborativa.Originalidad/valorel objetivo de este documento es aclarar el algoritmo de intercambio de información requerido para implementar una estructura colaborativa para una cadena de suministro. Este algoritmo se expresa utilizando la técnica BPM, específicamente a través de los estándares UML y BPMN.

Aplicación del Proceso Unificado en la Implementación del Método de Diferencias Finitas en el Dominio del Tiempo en Lenguaje Python mediante Programación Orientada a Objetos

En este artículo se analiza la posibilidad de la utilización del Procedimiento Unificado para el diseño de un programa computacional en la implementación del método de Diferencias Finitas en el Dominio del Tiempo. De esta manera, se ha desarrollado un programa con características de Programación Orientada a Objetos mediante el seguimiento de las etapas del Proceso Unificado: incepción, elaboración, construcción y transición. Las actividades delegadas a los objetos fueron definidas mediante la aplicación del criterio Patrones Generales de Asignación de Responsabilidades, es decir, experto en información, creador, controlador, bajo acoplamiento y alta cohesión. Los resultados principales para cada paso se muestran en Lenguaje de Modelamiento Unificado. La estructura final del programa, que incluye módulos, paquetes y arquitectura ha sido implementada en lenguaje Python 3.5. Se presentan las clases más importantes que resultaron de la última iteración del Proceso Unificado de tal manera que el diseño pueda ser aplicado a cualquier lenguaje de programación.

A Notation of Unified Modeling Language in various Areas

Any complex system is best understood by making some kind of diagrams or pictures. These diagrams have a better impact on our understanding. So if one looks around then it is realized that the diagrams are not a new concept but it is used widely in different form in different industries. UML diagrams are defined to understand a system in better and simple way. A single diagram is not enough to cover all aspects of the system. So UML defines various kinds of diagrams to cover most of the aspects of a system. Own set of diagrams can also be created to meet the users requirements. Diagrams are generally made in an incremental and iterative way. In this paper why one requires the UML is shown in brief. Importance of UML diagrams is also highlighted in this paper. Different criterion's of importance are elaborated. Here in the paper two broad categories of diagrams and then are again divided into sub-categories is shown: a) Structural Diagrams, b) Behavioral Diagrams. The picture of building blocks of UML diagram is also highlighted. Types of modeling describes how the user can draw different diagrams and in what areas these can be used. A description of web based UML is also given in this paper.

DESIGN OF OBJECT-ORIENTED DEBUGGER MODEL BY USING UNIFIED MODELING LANGUAGE

Debugging on computer program is a complex cognitive activity. Although it is complex, it’s still one of the popular issues in computer programming task. It is a difficult task, which is to understand what the e rror is and how to solve such error? In computer programming the difficulty is to understand the Object-Orient ed programming concept together with the programming logic. If the programming logic is incorrect, the program codes will have such error named as logic e rror and can caused highly maintenance cost. Logic error is a bug in a program that causes it to opera te incorrectly, without terminating or crashing the program. It will produce unintended output or other behavior than what we are expecting. Method that use to dev elop a propose model Object Oriented Debugger is Unified Modeling Language (UML). It is the best choice model and suitable to design the Object Oriented De bugger which will be developed in an object oriente d programming environment. The model will provide an ability to capture the characteristics of a system by using notations in the process of designing and imp lementing the system. The model of Object Oriented Debugger has been successfully implemented. This model has been developed using Unified Approach methodology, which consists of two methods such as Object-Oriented Analysis (OOA) and Object-Oriented Design (OOD). The model developed is to capture the structure and behavior of the Object Oriented Debugger by using the UML diagram. The model also can ease the readability of the documentation for th e maintenance purposes. The design of the Object Oriented Debugger Model has been developed using the UML notation. It’s consisting of two parts that are object-oriented analysis and object-oriented desig n. All the developing and designing are based on the model in UML.

Transformation of UML Class Diagram to UML Sequence Diagram

For object-oriented software development, The Unified Modeling Language (UML) has become an industrial standard. There are different models which have been described under UML notation. Use case model can represent the functional view of the system, UML class model can represent static view of the system, activity or sequence diagram can represent the dynamic view of the system. If we focus on field of UML class diagram & UML activity diagrams then a lots of research still is required. In this paper we describe a transformation process which can be used to transform the UML class diagram to UML sequence diagram. Transformation process is quite helpful so that we can easy obtain the UML sequence diagram from UML class diagram. General Terms UML Class diagram, UML Sequence diagram

XML-GDM을 기반으로 한 UML 클래스 다이어그램으로 사상을 위한 XML문서와 질의의 객체 모델링

최근 다양한 분야에서 폭넓게 활용되고 있는 XML 문서는 유연하고도 개방적인 특성으로 인해 정보교환이나 전송을 위한 수단으로 널리 이용되고 있다. 한편 XML 문서를 위한 시각적, 직관적 질의 언어인 XML-GL은 질의에 대한 의미와 결과 문서의 구조를 시각적으로 표현할 수 있기 때문에 XML 문서에 대한 구조 검색과 정보의 공유가 용이하다. 그리고 UML은 정해진 표기법과 다양한 다이어그램을 이용하여 객체지향 분석과 설계를 위한 도구로 사용되고 있다. 따라서 본 논문은 XML-GL의 데이터 모델인 XML-GDM을 기반으로 표현된 XML 문서를 UML 클래스 다이어그램으로 사상하기 위한 새로운 객체 모델링 방안을 제안한다. 이를 통해서 XML 문서를 직관적인 방법으로 객체지향데이터로 변환하고 저장/관리할 수 있다. 또한 객체지향 검색방법을 적용하면 보다 효율적으로 XML 문서를 검색할 수가 있다. Nowadays, XML has been favored by many companies internally and externally as a means of sharing and distributing data. there are many researches and systems for modeling and storing XML documents by an object-oriented method as for the method of saving and managing web-based multimedia document more easily. The representative tool for the object-oriented modeling of XML documents is UML (Unified Modeling Language). UML at the beginning was used as the integrated methodology for software development, but now it is used more frequently as the modeling language of various objects. Currently, UML supports various diagrams for object-oriented analysis and design like class diagram and is widely used as a tool of creating various database schema and object-oriented codes from them. This paper proposes an Efficinet Query Modelling of XML-GL using the UML class diagram and OCL for searching XML document which its application scope is widely extended due to the increased use of WWW and its flexible and open nature. In order to accomplish this, we propose the modeling rules and algorithm that map XML-GL. which has the modeling function for XML document and DTD and the graphical query function about that. In order to describe precisely about the constraint of model component, it is defined by OCL (Object Constraint Language). By using proposed technique creates a query for the XML document of holding various properties of object-oriented model by modeling the XML-GL query from XML document, XML DTD, and XML query while using the class diagram of UML. By converting, saving and managing XML document visually into the object-oriented graphic data model, user can prepare the base that can express the search and query on XML document intuitively and visually. As compared to existing XML-based query languages, it has various object-oriented characteristics and uses the UML notation that is widely used as object modeling tool. Hence, user can construct graphical and intuitive queries on XML-based web document without learning a new query language. By using the same modeling tool, UML class diagram on XML document content, query syntax and semantics, it allows consistently performing all the processes such as searching and saving XML document from/to object-oriented database.

E-Business in the Regulation of Medicines in Serbia

This article describes the application of electronic business (e-business) in the regulation of medicines in Serbia, as one of the e-government services of Serbia. In addition to the development of the information society of Serbia, the article puts forward a methodological framework for the development of e-services, through the use of rational unified process methodology. The unified modeling language notation was used for the description of the system model. The article presents modeling of the process of marketing of medicines. The analysis of the marketing of medicines in Serbia was carried out from 2004 through 2007 by the Medicines and Medical Devices Agency of Serbia (the Agency for Medicines). We present the results of performance analysis of the development of e-business in the regulations concerning medicines, conducted by the Agency for Medicines in April 2007 and March 2008. The findings identify e-business as of particular significance in medicine regulation in Serbia.

Ontology-driven analysis of UML-based collaborative processes using OWL-DL and CPN

A key ingredient in system and organization modeling is modeling business processes that involve the collaborative participation of different teams within and outside the organization. Recently, the use of the Unified Modeling Language (UML) for collaborative business modeling has been increasing, thanks to its human-friendly visual representation of a rich set of structural and behavioral views, albeit its unclear semantics. In the meantime, the use of the Web Ontology Language (OWL) has also been emerging, thanks to its clearly-defined semantics, hence being amenable to automatic analysis and reasoning, although it is less human friendly than, and also perhaps not as rich as, the UML notation — especially concerning processes, or activities. In this paper, we view the UML and the OWL as being complementary to each other, and exploit their relative strengths. We provide a mapping between the two, through a set of mapping rules, which allow for the capture of UML activity diagrams in an OWL-ontology. This mapping, which results in a formalization of collaborative processes, also sets a basis for subsequent construction of executable models using the Colored Petri Nets (CPN) formalism. For this purpose, we also provide appropriate mappings from OWL-based ontological elements into CPN elements. A case study of a mortgage granting system is described, along with the potential benefits and limitations of our proposal.

Pemanfaatan Sistem Informasi untuk Pengelolaan Medik dan Jasa Kesehatan di Klinik

Article presented an information system development which can facilitate the doctors and nurses at clinic in managingoutpatient and reporting data quickly, accurately, and effectively. Before using a computerized system, all data recording wasstill done conventionally using paper media. The research method used was an analysis and designing method, interviews,library research, and field study as to do an observation. The analysis and designing method, which was proposed, used anobject-oriented concept and presented through notation of Unified Modeling Language (UML). The research results showedthat a clinic needs a new system which can facilitate the doctors and nurses in processing operational data, such as medicalrecord data and other data relating to the outpatient. It can be concluded that with the presence of the information system, itis expected that it can facilitate the information needs by using a computerized system.Keywords: system utillty, information system, medical management, clinic

Multiple-view modelling and meta-modelling of software product lines

A multiple-view modelling and meta-modelling approach for software product lines (SPLs) using the unified modelling language notation is described. A multiple-view model for an SPL defines the different perspectives of the product line, namely the use case model, static model, collaboration model, statechart model and feature model, including the commonality and variability. The meta-model for SPLs depicts the life-cycle phases, views within each phase and meta-classes within each view. The relationships between the different meta-model views are described. Consistency checking rules are specified based on the relationships among meta-classes in the meta-model. These rules, which are specified formally using the object constraint language, are used to resolve inconsistencies between multiple views in the same phase or different phases, and to define allowable mappings between multiple views in different phases. Finally, tool support for the approach is described.

The feasibility of using UML to compare the impact of different brands of computer system on the clinical consultation

UK general practice is universally computerised, with computers used in the consulting room at the point of care. Practices use a range of different brands of computer system, which have developed organically to meet the needs of general practitioners and health service managers. Unified Modelling Language (UML) is a standard modelling and specification notation widely used in software engineering. To examine the feasibility of UML notation to compare the impact of different brands of general practice computer system on the clinical consultation. Multi-channel video recordings of simulated consultation sessions were recorded on three different clinical computer systems in common use (EMIS, iSOFT Synergy and IPS Vision). User action recorder software recorded time logs of keyboard and mouse use, and pattern recognition software captured non-verbal communication. The outputs of these were used to create UML class and sequence diagrams for each consultation. We compared 'definition of the presenting problem' and 'prescribing', as these tasks were present in all the consultations analysed. Class diagrams identified the entities involved in the clinical consultation. Sequence diagrams identified common elements of the consultation (such as prescribing) and enabled comparisons to be made between the different brands of computer system. The clinician and computer system interaction varied greatly between the different brands. UML sequence diagrams are useful in identifying common tasks in the clinical consultation, and for contrasting the impact of the different brands of computer system on the clinical consultation. Further research is needed to see if patterns demonstrated in this pilot study are consistently displayed.

A Paradigm for Object-Oriented Conceptual Modeling of Optical Networks

We present a conceptual framework for modeling optical networks and the solutions to its associated problems. The framework is targeted towards a large-scale initiative by us for designing a Unified Modeling Language (UML) Profile that can help with conceptual modeling of typical optical network design problems. While there are pieces of literature available that describe profiles for other application areas, there are no profiles for use in networking problems, in general. Our work is an important step forward to address this deficiency. Our proposed profile takes the existing UML notations and extends them to support the modeling of optical networks.