• Title/Summary/Keyword: UML Class Diagram

Search Result 85, Processing Time 0.028 seconds

The Design of a Class Diagram Authorization Tool based on the MVC Design Pattern (MVC 디자인 패턴에 기반한 클래스 다이어그램 저작도구의 설계)

  • Kim, Jae-Hoon;Kim, Yun-Ho
    • Journal of the Korea Institute of Information and Communication Engineering
    • /
    • v.14 no.12
    • /
    • pp.2707-2715
    • /
    • 2010
  • This paper suggests a implements and a design of class diagram authorization tool based on the MVC pattern. It defines and descries the structure of ClassInformation, ScreenDisplay and ToolManager. ClassInformation is responsible for processing or handling information of a diagram. ScreenDisplay is responsible for GUI to configure the screen of the authorization tool. ToolManager is responsible for event handling to process I/O of the authorization tool. Based on MVC pattern, ClassInformation, ScreenDisplay and ToolManager of the authorization tool are assigned each role independently. It is flexible to new requirement, because of loose coupling.

Comparison of Test Case Effectiveness Based on Dynamic Diagrams Using Mutation Testing (뮤테이션 테스트를 이용한 동적 다이어그램에 근거한 테스트 케이스의 효율 비교)

  • Lee, Hyuck-Su;Choi, Eun-Man
    • The KIPS Transactions:PartD
    • /
    • v.16D no.4
    • /
    • pp.517-526
    • /
    • 2009
  • It is possible to indicate the complex design and execution of object-oriented program with dynamic UML diagram. This paper shows the way how to make several test cases from sequence, state, and activity diagram among dynamic UML diagram. Three dynamic UML diagrams about withdrawal work of ATM simulation program are drawn. Then different test cases are created from these diagrams using previously described ways. To evaluate effectiveness of test cases, mutation testing is executed. Mutants are made from MuClipse plug-in tool based on Eclipse which supports many traditional and class mutation operators. Finally we've got the result of mutation testing and compare effectiveness of test cases, etc. Through this document, we've known some hints that how to choose the way of making test cases.

XML-GL Query Modelling using UML Class Diagram (UML 클래스 다이어그램을 이용한 XML-GL 질의 모델링)

  • Choi, Bong-Jin;Yoo, Chun-Sik;Kim, Yong-Sung
    • The KIPS Transactions:PartB
    • /
    • v.14B no.1 s.111
    • /
    • pp.23-32
    • /
    • 2007
  • Nowadays, XML has been favored by many companies internally and externally as a means of sharing and distributing data, due to its open-architectural structure. XML-GL, a graphical query language for document has the advantage of containing both structuring and defining of itself. By incorporating UML an XML document can become object-oriented and can be represented by graphical means. This paper proposes a XML-GL query modeling solution by using UML class diagrams. In order for the modeled objects to be properly restricted, the Object Constraint Language has been defined. This process converts XML documents into Object-Oriented data and combined with UML class diagrams, searches for XML documents can be increased.

Design and Implementation of A Conceptual Class Diagram Elicitation System (개념클래스 다이어그램 도출 시스템의 설계 및 구현)

  • Park, Ga-Young;Lee, Yong-Hun;Lee, Sang-Bum
    • 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.

Dynamic Impact Analysis Method using Use-case and UML Models on Object-oriented Analysis (객체지향 분석의 유스케이스와 UML 모델을 이용한 동적 영향 분석 방법)

  • Lee, Chan;Youn, Cheong
    • Journal of KIISE
    • /
    • v.43 no.10
    • /
    • pp.1104-1114
    • /
    • 2016
  • Software is continuously changing during development and after development. When a change is required, it is difficult to precisely grasp the scope of impact intuitively. A systematic method is needed to accomplish the required change. The purpose of impact analysis on software change is to avoid missing any information by recognizing the ripple effect that the change might cause. This paper proposes a dynamic method that can easily identify the scope of change request by using the association between use-case scenarios and artifacts of UML modeling in object-oriented development environment. By using this approach, the scope of impact that the change might have on other components such as class diagram and sequence diagram in use-case scenarios can be identified by forward tracing. In addition, analysis of influence of possible further changes due to changes in other components can be identified iteratively through backward tracing. The results of this paper are not limited to impact analysis on artifacts and change type. They can also be used as basic guidelines during impact analysis for various change requests.

Design and Implementation of Marketing and Sales Information System for Automotive Part Company Using Object-Oriented Methodology (객체지향 방법론을 이용한 자동차부품기업의 영업관리시스템 설계 및 구현)

  • Kang Sung-bae;Moon Tae-Soo
    • The Journal of Information Systems
    • /
    • v.13 no.1
    • /
    • pp.77-95
    • /
    • 2004
  • According to the increase of organizational complexity and the change of rapid information technology environment, many firms have shifted their information technology(IT) strategy from developing information systems in-house to purchasing application software such as Enterprise Resource Planning(ERP) Systems. Marketing and Sales functions within a Korean automotive part company include developing new assembly products, determining pricing, taking customer's orders, and shipping assembly products to customers. Marketing and Sales Information System(MSIS) in ERP system plays an important role in next Production Planning process. MSIS also makes management reporting and decision making faster and more uniform throughout an organization. MSIS promotes thinking about corporate goals, as opposed to thinking only about the goals of a single department or functional area. This paper intends to design and implement a MSIS in ERP systems for Korean automotive part company using object-oriented methodology In order to accomplish the implementation of MSIS in ERP system, 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. In traditional marketing and sales function, a company with an unintegrated information system can have marketing and sales data that is data redundant or inaccurate. MSIS integrated in ERP system can solve the sales forecast problem, which minimizes the total costs of production, inventory, and transportation under constraints of production capacity. Also, the use of UML methodology makes S/W programmers shorten the phase of analysis and design in the implementation of MSIS system, and increase the reuse of software and the interoperability with corporate internal Information system.

  • PDF

A Methode for Object-Relational Database Design with Extended UML Class Diagram (확장된 UML 클래스 다이어그램을 이용한 객체 관계형 데이터베이스 설계 기법)

  • Kim, In-Chul;Kim, Young-Ung
    • Proceedings of the Korea Information Processing Society Conference
    • /
    • 2005.11a
    • /
    • pp.91-94
    • /
    • 2005
  • 공학적 기반의 응용 프로그램에서는 복합관계(complex relationship) 및 복합객체(complex object)의 개념이 요구되는데, 이러한 개념들은 비즈니스 응용에 적합한 관계형 데이터베이스로 다루기에는 저장과 검색 시 많은 문제점을 야기한다. 이와 같은 문제점을 해결하기 위해서 객체 관계형 데이터베이스 시스템이 출현하게 되었다. 한편, 고전적인 데이터베이스 설계 기법은 개체 관계형 모델(Entity Relationship Model)과 같은 개념적 모델을 사용하며 데이터 중심의 구조적 관점(structural aspect)만을 고려하는 반면, UML(Unified Modeling Language)같은 객체지향형 설계 도구를 사용하여 데이터베이스를 설계할 경우 구조적 관점 및 행위적 관점(behavioral aspect)을 모두 포함한다. UML은 확장 가능한 언어로서, 특정 응용프로그램에 대한 새로운 스테레오타입(stereotype)의 사용이 가능하다. 데이터베이스 설계를 위한 확장된 UML의 스테레오타입이 제안되었지만, 대부분 관계형 데이터베이스에 초점이 맞추어져 있다. 본 논문에서는 객체 관계형 데이터베이스 설계를 위한 확장된 UML 스테레오타입을 기술하며, 복합관계 및 복합객체를 지원하기 위해 Aggregation, Composition, Association의 개념을 재정의한 설계기법을 제안하고, 제안한 설계기법을 지원하는 설계 도구(ORDesigner)의 구현에 대해서 기술한다.

  • PDF

An Algorithm for Mapping an SGML DTD to UML Class Diagram (SGML DTD로부터 UML 클래스 다이어그램으로의 사상 알고리즘)

  • Hwang, Yong-Ju;Kim, Yong-Seong
    • Journal of KIISE:Software and Applications
    • /
    • v.26 no.4
    • /
    • pp.508-520
    • /
    • 1999
  • 이 기종 시스템들간의 교환을 목적으로 사용되는 SGML(Standard Generalized Markup Language)문서는 논리적인 구조를 나타내는 구조를 나타내는 DTD(Document Type Definition )가 필요하다. 이러한 SGML DTD을 모델링하기 위해 기존에 여러 가지 방법이 제안되어 왔는데, 본 연구에서는 SGML DTD를 UML (Unified Modeling Language)클래스 다이어그램이 객체 모델로 사상시키는 알고리즘과 데이터 베이스 스키마 형태로 나타내기 위한 형식 모델을 제안한다. 본 연구에서 제안한 사상 규칙들과 알고리즘을 이용하면 SGML DTD을 보다 자연스럽게 객체지향 모델링하므로 데이터베이스 스키마로 변환이 용이하며, 형식모델을 데이터베이스 스키마 형태를 정의하므로 객체지향적인 문서 처리와 검색을 위한 효율적인 환경을 제공하게 된다.

Method and Implementation (or Consistency Verification of DEVS Model against User Requirement (DEVS 모델과 사용자 요구사항의 일관성 검증 방법론 및 환경 구현)

  • Kim Do-Hyung;Kim Tag-Gon
    • Proceedings of the Korea Society for Simulation Conference
    • /
    • 2005.05a
    • /
    • pp.100-105
    • /
    • 2005
  • Development of complex discrete event simulators requires cooperation between domain experts and modeling experts who involve the development. With the cooperation the domain experts derive user requirement and modeling experts transform the requirement to a simulation model. This paper proposes a method for consistency verification of simulation model in DEVS formalism against the user requirement in UML diagrams. It also presents an automated tool, called VeriDEVS, which implements the proposed method. Inputs of VeriDEVS are three UML diagrams, namely use case, class and sequence diagrams, and DEVS Graph, all in Visio; outputs of a verification result is represented in PowerPoint files.

  • PDF

Design of a Messaging System for B2B Workflow (B2B 워크플로우의 메시징 시스템 설계)

  • Suh, Chang-Kyo;Kim, Jeong-Sam;Lee, Hyung-Seok
    • Asia pacific journal of information systems
    • /
    • v.11 no.1
    • /
    • pp.117-137
    • /
    • 2001
  • B2B(business-to-business) commerce has become the prime driver of contemporary electronic commerce. Under B2B commerce, corporations often must operate across organizational boundaries to share their business processes. Workflow management was proposed by Aalst(4, 5) to support several business partners that are involved in shared workflow processes in B2B commerce. We designed a messaging system for B2B workflow, where heterogeneous workflow management systems on each organization for trade were integrated. Based on Aalst's example in(4, 5), we analyzed B2B workflow by using class diagram, use case diagram, activity diagram, and statechart diagram of UML, and designed the messaging system, We also demonstrated a prototype system which was implemented by using Java API and XML. To compare with a holistic system such as EDI systems, the messaging system allows the business partners in B2B commerce to communicate with each other by dedicated messages and integrate each B2B interoperable workflow without any restrictions.

  • PDF