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

• 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 Academia-Industrial cooperation Society
• /
• v.10 no.12
• /
• pp.3668-3674
• /
• 2009

Use case diagram is used for defining inter-action between users and systems in object-oriented modeling. It is very important to defining users' requirements for efficient software development. In this paper, we propose a object-oriented modeling process using hierarchical use case analysis for designing class model. First, We define many use case diagrams by several hierarchical modeling level. And next, we can also design class model using the use case diagrams. Our proposed modeling process provides interaction between use case model and class model. That can make us to check the modeling process during the software development. Using the proposed object-oriented modeling we can develop software based on users' requirements. It is very useful for class modeling.

• Journal of the Korea Society of Computer and Information
• /
• v.10 no.3 s.35
• /
• pp.161-171
• /
• 2005

SMIL(Synchronized Multimedia Integration Language) allows 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)to Develop for SMIL Documents Editor. 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 editor 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 Korean Society for Quality Management
• /
• v.43 no.4
• /
• pp.489-498
• /
• 2015

Purpose: This paper proposes S-NS diagram. S-NS diagram helps us find core factors which improve customer satisfaction. Methods: S-NS diagram draws a scatter diagram based on marks obtained from surveys consisting of several questions on satisfaction and non-satisfaction at the same time. S-NS diagram is divided into the 4 regions. We focused on region B which is High satisfaction and high non-satisfaction shown in S-NS diagram. Region B is the areas for needs to improve. Results: S-NS diagram can find few important factors which affect customer satisfaction. We improve Lecture Satisfaction using S-NS Diagram. Conclusion: S-NS diagram has been proven to be an effective method for improving customer satisfaction with a lecture satisfaction improvement example. We know S-NS diagram can use many fields including manufacture and service areas.

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

• Korean Institute of Interior Design Journal
• /
• v.15 no.3 s.56
• /
• pp.201-210
• /
• 2006

Among the architects who use diagrams as a digital design process, especially through Peter Eisenman and Ben van Berkel's works, we have specifically got the meaning of their diagrams. Their diagrams act as 'the block of becoming' and we can regard the diagrams not only as a tool of devenir including architect's root thoughts beyond a tool of schematic presentation, but also as architect's intention including devenir thought. And in the case of diagrams which the architects use, we can recognize that architects' intentions are to think that Deleuze's 'machine abstraite' evolve the diagram into various and transformed form. That is to say, Peter Eisenman interprets the machine abstraite as a root thought of devenir by using diagram as medium to reveal the virtual. And Ben van Berkel transforms the diagram by including all external conditions into selected diagram which shows the abstract relations to the elements. We can get the meaning of the machine abstraite from these cases well. This study will play an important role in giving good usage of the diagram in making a form of contemporary digital architecture and showing the direction of form creation field.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2012.11a
• /
• pp.1452-1455
• /
• 2012

본 논문은 출시된 지능형 교통 기반으로 설계된 RoboCAR 운행제어 개발과 시험을 하고자 한다. 이를 위해 시스템 설계를 통해,Test Case 추출과 실제로 적용하여 구현된 소프트웨어를 시험에 목적을 둔다. 이 절차는 Use-Case Diagram 설계, Decision Factor 추출, 이 기반으로 Cause-Effect Diagram을 생성한다. Cause-Effect Diagram을 통해 Decision Table을 생성한다. 최종적으로 Decision Table을 기반으로 Test Case를 추출한다. 추출된 Test Case를 적용하여 시스템을 테스트 하였고, 설계와 구현이 동일하게 되었음을 검증하였다.