• Proceedings of the Korean Institute of Information and Commucation Sciences Conference
• /
• 2010.10a
• /
• pp.634-637
• /
• 2010

This paper suggests the design of MVC model for an authorization tool of UML class diagram. In the design of MVC model, it is designed to define view, controller and model and perform the individual role of each component. The View represents GUI and the Controller is responsible for data input and output and the Model is to handle the business logic. The MVC model design for an authorization tool of class diagram gives the role independently and tries to be flexible with system by dividing into the suitable features of each component.

• Journal of Internet Computing and Services
• /
• v.3 no.1
• /
• pp.71-80
• /
• 2002

UML is an object-oriented development methodology to graphically modeling, a software system, We are developed UML, graphics editor and its generating various design objects during software development cycle. Its design object compose of semantics information and View information manage using of RDBMS. Extant tools supporting UDML. however, it does not have an explicit format to describe and interchange its design abject intentionally, In this thesis, to overcome the drawback, the UML design object interchange and presents our efforts to make UML design objects highly interoperable. We developed an interchange format called UDXF(UML Design object exchange Format) based on XML UDXF is a simple and well-structured format to encode UML design objects. It leverages the tool interoperability, team development and reuse of design objects by interchanging the model information with the XML standard. Also, we propose design object repository manager for design object of UDXF format.

• 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.

• Journal of KIISE:Software and Applications
• /
• v.32 no.3
• /
• pp.153-162
• /
• 2005

Component Based Development (CBD) is appealing as a technology to improve the productivity of software development through component reuse. Model Driven Architecture (MDA) is a new development paradigm which automatically generates application by transforming design models incrementally. Since both reusability of CBD and model transformation of MDA increase software productivity. integration of two technologies is desirable. To enable this technology integration, we need to devise a UML profile for specifying component design as a PIM. In this paper, we first define a meta-model for components, and propose a UML profile which is used to specify elements of component design as PIM. Since the proposed profile is based on Meta Object Facility (MOF) from which is MDA is derived, it is consistent and compatible with existing MDA methods and tools.

• The KIPS Transactions:PartD
• /
• v.8D no.6
• /
• pp.843-852
• /
• 2001

Statistics concerning software errors indicate that more errors are introduced in analysis and design phase than implementation phase. Therefore, it is needed to check whether the design modeling is appropriate for own function and structure. This paper discussed the effective test method for the object-oriented design model, i.e., UML. A new method was proposed for generating test data. This method consists of category partition theory by the representation each element in UML model with OCL (Object Constraint Language). Test data generated in this way can be used for testing the source code functionality as well as for checking the design model.

• Journal of the Korea Institute of Information and Communication Engineering
• /
• v.26 no.10
• /
• pp.1509-1516
• /
• 2022

This paper presents a method to generate a model of the code implementation for UML state diagrams. First, it promotes the states of a state machine into objects, and then it structures the behavior model on the mechanism of a state diagram based on State design pattern. Then, it establishes the rules of generating the code implementation, and using the rules, the Java code mode is generated for the implementations of State Diagrams in Java syntax grammar. In addition, Structuring the information of the code model is necessary for generating Java code automatically. The meta information is composed of Meta-Class Model and Meta-Behavior Model, on which we could construct the automatic code generating engine for UML State Diagrams. The implementation model generation method presented in this paper could be used as a stand-alone engine, or included and integrated as a module in the UML tools.

• Journal of the Korea Institute of Information and Communication Engineering
• /
• v.9 no.3
• /
• pp.561-569
• /
• 2005

Recently, the object-oriented design is the major paradigm for software development. Most systems are following this paradigm, but the past studies for a video conversation domain were not based on full-scale object-oriented design. Thus, this paper presents an systematical architecture design using UML for a video conversation system that is well-known and has high rate of usefulness. It analysis a video conversation system that has much demand of service as systematical functional/non-functional requirements, and the object-oriented design applying '4+1 View Model' guarantees the reusability of a component and makes it possible to extend a system by adding components as needed. Consequently, it is expected that the components of video conversation system designed by this paper will be useful the other video conversation systems and will be expanded to web environment.

• Journal of Internet Computing and Services
• /
• v.3 no.3
• /
• pp.39-53
• /
• 2002

Since domain model affects largely on the development of object model and design decisions, this model is widely used in the object-oriented and component-based system development. Current $\infty$ methods and UML notation, however, do not support both engineering with reuse and engineering for reuse, This problem causes delay in project development time and inadequate domain model. The integration of extended UML notation and reuse process method can provide a solution to the reusability problem. In this paper, we designed UML based domain model template for the reuse of domain model and proposed domain model development method for the reuse of analysis information, In addition, it was possible to represent reusable domain model template in UML and to develope domain model in the internet sales domain.

• International Journal of Computer Science & Network Security
• /
• v.21 no.1
• /
• pp.84-96
• /
• 2021

Certainly, the success of the Unified Modeling Language (UML) as the de facto standard for modeling software systems does not imply closing the door on scientific exploration or experimentation with modeling in the field. Continuing studies in this area can produce theoretical results that strengthen UML as the leading modeling language. Recently, a new modeling technique has been proposed called thinging machine (TM) modeling. This paper utilizes TM to further understand UML, with two objectives: (a) Fine issues in UML are studied, including theoretical notions such as events, objects, actions, activities, etc. Specifically, TM can be used to solve problems related to internal cross-diagram integration. (b) TM applies a different method of conceptualization, including building a model on one-category ontology in contrast to the object-oriented paradigm. The long-term objective of this study is to explore the possibility of TM complementing certain aspects in the UML methodology to develop and design software systems. Accordingly, we alternate between UML and TM modeling. A sample UML model is redesigned in TM, and then UML diagrams are extracted from TM. The results clarify many notions in both models. Particularly, the TM behavioral specification seems to be applicable in UML.

• International Journal of Computer Science & Network Security
• /
• v.21 no.5
• /
• pp.139-150
• /
• 2021

Object orientation has become the predominant paradigm for conceptual modeling (e.g., UML), where the notions of class and object form the primitive building blocks of thought. Classes act as templates for objects that have attributes and methods (actions). The modeled systems are not even necessarily software systems: They can be human and artificial systems of many different kinds (e.g., teaching and learning systems). The UML class diagram is described as a central component of model-driven software development. It is the most common diagram in object-oriented models and used to model the static design view of a system. Objects both carry data and execute actions. According to some authorities in modeling, a certain degree of difficulty exists in understanding the semantics of these notions in UML class diagrams. Some researchers claim class diagrams have limited use for conceptual analysis and that they are best used for logical design. Performing conceptual analysis should not concern the ways facts are grouped into structures. Whether a fact will end up in the design as an attribute is not a conceptual issue. UML leads to drilling down into physical design details (e.g., private/public attributes, encapsulated operations, and navigating direction of an association). This paper is a venture to further the understanding of object-orientated concepts as exemplified in UML with the aim of developing a broad comprehension of conceptual modeling fundamentals. Thinging machine (TM) modeling is a new modeling language employed in such an undertaking. TM modeling interlaces structure (components) and actionality where actions infiltrate the attributes as much as the classes. Although space limitations affect some aspects of the class diagram, the concluding assessment of this study reveals the class description is a kind of shorthand for a richer sematic TM construct.