• 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 Korea Society of Industrial Information Systems
• /
• v.15 no.5
• /
• pp.149-158
• /
• 2010

A messenger program in this paper was designed and implemented using Use Case Diagram, Class Diagram, Activity Diagram, and Sequence Diagram. We selected total 7 major functionalities such as PC server, login, friends management, chatting, file transfer, account management, etc. The followings are various implementation results from this paper. First, developers could easily understand the desired product and programming flow from using UML Diagrams. Second, PDA users could communicate with developers for a long time without time constraints. Third, there was high usability of UML Diagram in the phase of objected-oriented analysis. Forth, it was easy to update and maintain a program.

• Journal of KIISE:Software and Applications
• /
• v.27 no.4
• /
• pp.357-369
• /
• 2000

SMIL(Synchronized Multimedia integration Language) allows integrating a set of independent multimedia objects into a synchronized multimedia presentation. In this paper, I propose modeling rules, formal models, modeling function and an algorithm for SMIL documents using use case diagram and sequence diagram of UML(Unified Modeling Language), It will be used the use case diagram and collaboration diagram for object-oriented visualizing tool to describe the temporal behavior of the presentation. The main contribution of this paper is that developers of SMIL documents easily generate them using this rules and algorithm. And, the formal models and modeling functions provide an environment for processing object-oriented documents.

• Journal of the Korea Institute of Information and Communication Engineering
• /
• v.16 no.6
• /
• pp.1291-1299
• /
• 2012

UML is a semantically rich language, but it is difficult to ensure consistency of the diagrams you have written. Therefore, in this paper, we propose cross checking rules to improve consistency between UML diagrams, especially between UML static diagram and dynamic diagram. We use metamodels in order to more clearly reflect interactions of UML elements in the checking rules and use OCL(Object Constraint Language) to accurately represent the checking rules. By comparing with the well-formedness rules of UML specification, we focus on consistency of UML diagrams. And we derive metamodels of static diagram and dynamic diagram, analysis the relationships of UML diagrams and finally, we test the usability of derived rules through a case study.

• IE interfaces
• /
• v.16 no.2
• /
• pp.268-279
• /
• 2003

This paper presents critical steps in building client/server application with UML and Visual Basic, which are derived from the implementation case of a typical order processing system. To begin with, we briefly review the software architecture, the diagrams and the object-oriened building process in the UML. In the inception phase, it is critical to define the project charter, to draw use case diagrams, and to construct a preliminary architecture of the application. In the elaboration phase, it is critical to identify classes to be displayed in the class diagram, to develop user interface prototypes for each use case, to construct sequence diagram for each use case, and finally to design an implementation architecture. Steps to construct implementation architecture are given. In the construction phase, it is critical to design both the database and components. Steps to design these components are described in detail. Additionally the way to create the Internet interface is suggested.

• The KIPS Transactions:PartD
• /
• v.9D no.4
• /
• pp.639-650
• /
• 2002

We have to carry out systematic, definite requirements analysis for the successful development of software. The UML gives the ways to grasp user or customer requirements and decide the boundary of business systems from the use case modeling. This paper presents how to extract use case diagram from the requirements specification systematically by applying the standardized rules as a part of the study for use case modeling. We modify requirements specification by applying $R_{RS}$ (Rules for Requirements Specification) and extract actor, use case, relationship by applying $R_{A}$(Rules for Actors), $R_{U}$(Rules for Use Cases) and $R_{R}$(Rules for Relationships) to the modified requirements specification separately and then become to make out use case diagram in the end. By applying the rules presented in this paper to the requirements specification for personnel management, we can reduce the existing difficulties of extracting use case diagram based on the narrative descriptions without any standardized rules.rules.

• The Journal of Society for e-Business Studies
• /
• v.7 no.3
• /
• pp.139-158
• /
• 2002

Most of companies related to the area of B2B electronic commerce are making their efforts to innovate their existing business process into new designed process. XML-based electronic data interchange has potential to impact on reshaping the traditional EDI systems. This study intends to suggest a prototype of XML-based electronic data interchange using unified modeling language, with a case study applied in Korean automobile industry. In order to accomplish the research objectives, we employed UML as its standard modeling language, In this study, four diagramming techniques such as use case diagram, sequence diagram, class diagram, component diagram among eight modeling techniques are used for analyzing hierarchical business process. As a result of applying UML methodology, we design and develop XML/EDI applications efficiently. Our field test applied to Korean automobile industry shows that data modeling to design XML application using UML is better than existing methodologies in representing object schema of XML data and in extension and interoperability of systems.

• Proceedings of the Korean Institute of Information and Commucation Sciences Conference
• /
• 2001.10a
• /
• pp.717-719
• /
• 2001

인터넷의 급격한 확산에 따라 컴퓨터 응용산업은 이를 응용하려는 노력과 연구가 활발히 진행되었다. 또한, 다변화되는 수요환경에 따라 점차 응용소프트웨어의 효율성에 문제점이 제기 되었고, 이를 보완할 수 있는 보다 포괄적이고 효과적인 소프트웨어 분석 및 개발기법들이 제시되었다. 이에, 본 논문에서는 이들 요소들을 적용하여 자동화시스템에서 운용한 수 있는 인격제어관리시스템을 구현 및 개발하였다. 즉, 본 시스템의 개발을 위한 분석 부분에서는 UML을 이용한 Use Case Diagram, Sequence Diagram, Collaboration Diagram등을 활용하였으며, 개발 부분에서는 웹 기반의 문서 데이터 표준을 위하여 XML을 이용하였고 Java언어로 이를 보완하였다.

• Journal of the Korea Society of Computer and Information
• /
• v.7 no.4
• /
• pp.157-162
• /
• 2002

In this paper, we implement the XML and data modeling by the UML tool, in which the class diagram is constructed from the sequence diagram after making the use case diagram. For the XML modeling. the guiding line will be presented to transform the UML class into the XML document, and then an example to draw the XML DTD from the UML class will be also shown. Furthermore, through the proposed data modeling, the integrated design methods for the transformation of the UML class into relational database schema. object-relational database schema and object-oriented database schema also will be proposed. Finally, we will be presented schema for each database system.

• Journal of KIISE:Computing Practices and Letters
• /
• v.8 no.6
• /
• pp.657-668
• /
• 2002

Software life cycle consists of requirement analysis, design, implementation, and maintenance phases, and the product of each phase has various format. The UML normalizes such products, and the class diagram, use case diagram, activity diagram and collaboration diagram are usually used for the requirement analysis phase. Because most of UML development tools store such diagrams in a file, there nay be some difficulties of information retrieval and co-work among users. To cope with the difficulties, this paper proposes a database supported methodology to store and manage the diagrams produced by the requirement analysis. In this methodology, the constituents of class, use case, activity and collaboration diagram are first analyzed and then transformed in the form of relational fables. The constituents of such diagrams are stored as tables in a database, and can be easily retrieved from the database by using some queries. This database supported methodology provides the concurrent sharing and high reuse of diagrams.