• Journal of Korea Society of Industrial Information Systems
• /
• v.16 no.5
• /
• pp.83-92
• /
• 2011

IDEF is a widely used methodology for traditional structured software development. As object-oriented softwares are widely used, an object-oriented version of IDEF, IDEF4, is developed. UML is de facto standard for object-oriented software development methods. Whereas IDEF is widely used for CALS/EC, UML is used for general object-oriented software development. Most software developers are not familiar with IDEF4 but familiar with UML. Moreover, UML has many CASE tools. So we can develop software efficiently if we convert IDEF4 model to UML model. In this paper, we transform IDEF4 models to UML models. We explain the rules and methods to convert IDEF4 model to UML model and applied the transform methods and rules to a case study.

• International Journal of Computer Science & Network Security
• /
• v.21 no.6
• /
• pp.127-136
• /
• 2021

In the systems and software modeling field, a conceptual model involves modeling with concepts to support development and design. An example of a conceptual model is a description developed using the Unified Modeling Language (UML). UML uses a model multiplicity formulation approach, wherein a number of models are used to represent alternative views. By contrast, a model singularity approach uses only a single integrated model. Each of these styles of modeling has its strengths and weaknesses. This paper introduces a partial solution to the issue of multiplicity vs. singularity in modeling by adopting UML use cases and class models into the conceptual thinging machine (TM) model. To apply use cases, we adopt the observation that a use-case diagram is a description that shows the internal structure of the part of the system represented by the use case in addition to being useful to people outside of the system. Additionally, the UML class diagram is recast in TM representation. Accordingly, we develop a TMUML model that embraces the TM specification of the UML class diagram and the internal structure extracted from the UML use case. TMUML modeling introduces some of the advantages that have made UML a popular modeling language to TM modeling. At the same time, this approach supplies UML with partial model singularity. The paper details experimentation with TMUML using examples from the literature. Our results indicate that mixing UML with other models could be a viable approach.

• The KIPS Transactions:PartD
• /
• v.19D no.1
• /
• pp.81-94
• /
• 2012

FORM(Feature-Oriented Reuse Method) is one of representative product line engineering methods. The essence of FORM is the FORM architecture models, which can be reused in the development of multiple products of a software product line. The FORM architecture models, however, have the following problems when applied in practice. First, they are not standardized models like UML(Unified Modeling Language) and therefore they can be constructed only through a specific modeling tool. Second, they do not represent architectural variability explicitly. Instead their variability is only managed through a mapping from a feature model. To address these two problems, we developed at first a method for representing the FORM architecture models using UML, which enables the FORM architecture models to be constructed through various available UML modeling tools. Also, we developed an effective method for representing as well as managing the variability of the FORM architecture models through a mapping from a feature model.

• Journal of the Korea Society of Computer and Information
• /
• v.27 no.5
• /
• pp.109-116
• /
• 2022

Recently, a model-based development method centered on highly readable and standardized UML (Unified Modeling Language) models has been applied to solve unclear communications in large-scale software development. However, it is difficult to apply consistent UML models depending on software developers' proficiency, understanding of models and modeling tools. In this paper, we propose a method for developing a Model Verification System to apply an consistent UML model to software development. Then, the developed Model Verification System is partially applied to the Naval Combat System Software development to prove its function. The Model Verification System provides automatic verification of models created by developers according to domain characteristics. If the Model Verification System proposed in this paper is used, It has the advantage of being able to apply the consistent UML model more easily to Naval Combat System Software Development.

• The KIPS Transactions:PartD
• /
• v.15D no.1
• /
• pp.87-98
• /
• 2008

In company with the demand of powerful processing units for embedded systems, the method to develop embedded software is also required to support the demand in new approach. In order to improve the resource utilization and system performance, software modeling techniques have to consider the features of hardware architecture. This paper proposes a partitioning technique of UML-based software models, which focus the generation of the allocatable software components into multiprocessor architecture. Our partitioning technique, at first, transforms UML models to CBCFGs(Constraint-Based Control Flow Graphs), and then slices the CBCFGs with consideration of parallelism and data dependency. We believe that our proposition gives practical applicability in the areas of platform specific modeling and performance estimation in model-driven embedded software development.

• Proceedings of the Korea Society for Simulation Conference
• /
• 2002.05a
• /
• pp.73-80
• /
• 2002

UML(Unified Modeling Language)은 소프트웨어 설계뿐만 아니라 네트워크 상에서의 데이터 전송, 가상데이터를 이용한 물리현상, 회로 분석 및 설계 등 다양한 형태의 시뮬레이션에서도 사용되고 있는 모델링 언어이다. 이러한 UML로 개발된 소프트웨어 설계 모델이나 시뮬레이션 모델들을 효율적으로 저장하고 관리할 수 있는 통합 시스템의 필요성이 제기되고 있다. 이를 위하여 본 논문에서는 UML 모델들의 저장과 관리의 효율성을 높이기 위해서 저장하부 구조를 데이터베이스화할 수 있는 방법을 제안한다. 제안한 방법을 적용한 시스템은 UML 모델들을 다수의 사용자들이 서로 공유할 수 있으며 모델의 재사용성을 높이고 모델 정보의 효율적인 검색을 지원할 것이다.

• The Transactions of the Korea Information Processing Society
• /
• v.6 no.11
• /
• pp.2965-2980
• /
• 1999

There are several models and the corresponding diagrams to express software system in many kinds of viewpoints, but these are supposed to be integrated and implemented into only one system. Therefore, the software modelers should have the models ensuring the consistency between information in software development life cycle. To support the robust models for modelers using OO modeling methods, i.e. UML, and CASE tools, the meta models of the software architecture and the consistency rules between the models are suggested in this thesis. Finally, the rules are implemented in the OO CASE tool, DEBUTO(Design By UML Tool). It supports UML1.1 notations and has visual modeling editors that enable users make their own software model.

• The Journal of Society for e-Business Studies
• /
• v.5 no.1
• /
• pp.123-134
• /
• 2000

Over the past several decades, several architectural approaches have been applied to develop Information Systems, The software architectural model has been recognized as one of the most important methods for improving productivity. Most conceptual models are difficult to understand and interpret at various system models. As a consequence, conceptual models of many Information Systems fail to represent, exploit, and apply to various aspects, which is needed for reducing development step of the architecture. In this paper, we will explain the architectural model as the 4＋1 View of UML. This model integrates the Knowledge Management System into five views： the Logical View, the Process View, the Deployment View, Implementation View, and the Use-Case View. Moreover, this paper will not only provide information on the application of the software architectural model by stakeholders, but also ultimately improve productivity.

• Journal of KIISE:Computing Practices and Letters
• /
• v.14 no.5
• /
• pp.492-496
• /
• 2008

Much research has been conducted to describe metrics for UML models by extending OCL that was proposed to define structural constraints. However, metrics descriptions in OCL are complex, so they are very difficult to understand. This paper defines MDL4UML by abstracting the conventional OCL. By abstracting OCL constructs, the MDL4UML can produce simpler descriptions of metrics, which can help metrics designer to understand and describe metrics.

• Proceedings of The Korean Society of Agricultural and Forest Meteorology Conference
• /
• 2011.11a
• /
• pp.12-14
• /
• 2011

Crop growth simulation models have been developed as research and management tools. When these models are needed to incorporate new knowledge on phenology and physiology of crops, programming languages have been used for development and documentation of these models. However, researchers may have limited skill in programming languages. Furthermore, software developer may find it challenging to improve the crop models because documentation of the models are rarely available. The Unified Modeling Language (UML) can provide a simple approach for development and documentation of model. A template for implementation of the model can be obtained using the UML, which would facilitate code re-use and model improvement.