• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.12 no.1
• /
• pp.420-426
• /
• 2011

In this paper, we introduce a system which helps to draw a conceptual class diagram from the problem description by combining various class diagram deriving methods. Generally, problem description is a kind of statements including user requirements in the early development phase. The system developer can derive a conceptual class diagram from this document, which playes an important role during the object-oriented software development. Until now, it is not easy for the novice to elicit classes because it requires good experience and intuition. In addition, there are also some difficulties of finding valid conceptual classes by hand when the size of system becomes larger. Therefore, we develop a system to solve these problems so that the developer is able to construct the conceptual class diagram easily.

• Journal of Information Technology Applications and Management
• /
• v.18 no.4
• /
• pp.95-118
• /
• 2011

In developing information systems, conceptual modeling is among the most fundamental means. The importance attributed to conceptual modeling has not only given rise to a lot of modeling methods, but also to the "yet another modeling approach (YAMA)" syndrome and the "not another modeling approach (NAMA)" hysteria. Criticism of conceptual modeling methods usually targets their lacking of theoretical foundations. In response to such criticism, various approaches towards theoretical foundations of conceptual modeling have been proposed so far. One of the recent responses to the quest for theoretical foundations of conceptual modeling is the reference to the philosophical ontology. The currently most prominent of diverse approaches towards ontological foundations of conceptual modeling appears to be the Bunge-Wand-Weber (BWW) ontology. Recent approaches attempt to regard BWW ontology as another conceptual data model as well as a criterion for evaluating various conceptual models. However, unfortunately, relatively few researches have been made on interoperability between the Entity-Relationship (ER) model, which is the most dominant conceptual data model, and ontology based model. In this paper, we investigate the interoperability between ontology and the ER model. In detail we (i) reclassify components of ER model with respect to ontology concepts, (ii) identify some components that cannot be directly represented in ontology notation, and (iii) present alternative representations to the components to acquire ontologically clear ER diagrams. Additionally, we (iv) present a set of mapping rules for converting the ontologically clear ER diagram into the corresponding ontology. In a case study, we show the process of converting an ER diagram for a concise Project Management System (PMS) into the ontologically clear ER diagram and the corresponding ontology. We also describe an experiment that we undertook to test whether users understand the Ontologically-Clear ER diagram better.

• 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 the Korea Institute of Information and Communication Engineering
• /
• v.9 no.2
• /
• pp.445-453
• /
• 2005

The design process of a relational database system consists of requirement analysis, conceptual design using ER diagram, logical design, and physical design. In logical design process, the conceptual schema is transformed to relational schema, and relational schema is normalized. This traditional design process is hard to applied in real database design process, since there is an ambiguity in conceptual design process. In this paper, we suggest a new design process, which provides more structural design steps by removing the conceptual design process. In new approach, we produce the data flow diagram by the structural methodology. From the attributes in the data store of data flow diagram, we construct relational table schema, and we normalize relational schema. Finally we produced table relationship diagram in order to figure out relationships between tables.

• Journal of the Korean Applied Science and Technology
• /
• v.31 no.4
• /
• pp.623-627
• /
• 2014

Emulsions are a class of disperse systems consisting of two immiscible liquids. Emulsions are affected by the size of oil drop, the type of continuous and disperse phase, the ratio of continuous and disperse phase, the type of emulsifies and emulsification devices. This study is to observe the viscosity of emulsions with oil polarities and interpret the results by organic conceptual diagram. The emulsions were made with hydrocarbon, ester and silicone oils and then the viscosity of emulsions was measured. As the oil polarity was increased, the viscosity of emulsion was decreased by reducing the amount of emulsifies and emulsion stabilizers arranged at interface. Organic conceptual diagram was used to compare the polarities among oils numerically. The interpretation of organic conceptual diagram and the results of experimental measurement were corresponded except emulsion made with silicone oil.

• The Journal of Society for e-Business Studies
• /
• v.9 no.3
• /
• pp.145-154
• /
• 2004

Class extraction of object or component based software development methodology is the major factor for software quality. Each method has the class definition and extraction method however there are some troubles when the beginners try. Especially, the conceptual gap results to make the class extraction hard. This research suggests three diagrams to support it. They are Information diagram, Behavio diagram and Management diagram. They specify which services a stakeholder wants, which information to support the service, which actions to solve the service and who has the responsibility for those. Any analysis process which takes class extraction can utilize these diagrams.

• Proceedings of the Korean Institute of Information and Commucation Sciences Conference
• /
• 2003.10a
• /
• pp.615-618
• /
• 2003

The design process of a relational database system consists of requirement analysis, conceptual design using ER diagram, logical design, and physical design. In logical design process, the conceptual schema is transformed to relational schema, and relational schema is normalized. This traditional design process is hard to applied in real database design process, since there is an ambiguity in conceptual design process. In this paper, we suggest a new design process, which provides more structural design steps by removing the conceptual design process. In new approach, we produce the data flow diagram by the structural methodology. From the attributes in the data store of data flow diagram, we construct relational table schema, and we normalize relational schema. Finally we produced table relationship diagram in order to figure out relationships between tables.

• The Journal of the Institute of Internet, Broadcasting and Communication
• /
• v.17 no.6
• /
• pp.211-216
• /
• 2017

XML is becoming a de facto standard for the representation and exchange of data, and XML itself is well structured to store and manage data, but it is difficult to understand the document structure at a glance due to its diverse and complex expressions. Thus, it is not appropriate to use it as a tool of conceptual model. In this paper, we propose a method to transform XML schema document structure into conceptual model. To do this, we describe CMXML as a conceptual modeling tool and present transformation rules and data structures for transforming an XML schema structure into CMXML diagram. In the transformation procedure, the XML schema document is input and the CMXML diagram is generated by applying the transformation rules.

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

• Journal of the Korean Operations Research and Management Science Society
• /
• v.10 no.1
• /
• pp.41-53
• /
• 1985

The influence diagram is a new conceptual tool that can be used for structuring a strategic decision problem in decision analysis. It has a graphical representation of probabilistic dependence among variables in the decision problem. In this formal procedures for constructuring the influence diagram and for translating it into the corresponding decision tree are studied. An example that shows the power of the infuence diagram is shown.