• Proceedings of the Korean Institute of Information and Commucation Sciences Conference
• /
• 2011.10a
• /
• pp.371-374
• /
• 2011

UML is a very good description of object-oriented concepts and supports the use case diagram for analyzing the system functionality, the class diagram for representing the domain object in the analysis step, the sequence diagram for connecting the action in the class. The visual-based, object-oriented LabVIEW OOP is an intuitive design tool that can be executed at the same time as a development tool. However, even the system developer using LabVIEW OOP is needed known about the object-oriented concept in the design stage. In this paper, we suggest the method to applying the UML modeling diagram to LabVIEW OOP design.

• Journal of the Korea Society of Computer and Information
• /
• v.7 no.1
• /
• pp.54-61
• /
• 2002

In this paper, we implement the XML modeling and data modeling by the class diagram that is made by the use case after drawing out the sequence diagram. For the XML modeling, the guiding line to map the UML classes on the XML document will be presented. Then, an example to generate the ie DTD from the UML classes will be shown under the presented guiding line. In the data modeling, the transformation method from the In classes into the object-oriented database also will be proposed. Finally, we will give an example developed by the Proposed transformation method.

• Journal of Internet Computing and Services
• /
• v.10 no.1
• /
• pp.175-182
• /
• 2009

Less efforts has been made in developing specifications and verification techniques for quality requirements. This paper suggests specification and traceability methods supporting quality issues such as usability, performance, and understandability when developing information systems with UML notation. With traceability checking methods that augment quality extension to the use cases and sequence diagrams, developers can confirm the level of implementation for both functional and nonfunctional requirements beforehand.

• Journal of KIISE:Computing Practices and Letters
• /
• v.11 no.1
• /
• pp.1-14
• /
• 2005

It is difficult to identify reusable and independent components in component-based development(CBD) process. Therefore existing methodologies have dealt the problem of component identification based on only developer's intuition and heuristics. As a result, it is difficult to identify the business components by common developers. Therefore, in this paper, we propose a new baseline and technique to identify the business components based on domain model such as use case diagrams, class diagrams, and sequence diagrams. proposed method identifies components through two phases; system component identification and business component identification. Especially, we consider structural characteristics as well as dependency characteristics according to methods call types and directions in identifying components. We also present a case study and comparative analysis and assessment to prove the practical use of our technique.

• The Journal of Society for e-Business Studies
• /
• v.8 no.4
• /
• pp.239-252
• /
• 2003

High quality software is the one that has an excellent performance with a low price, consumer's request satisfaction and less bug. In addition, it should have structure easily maintainable. CBD(Component Based Development)technology is getting more popular as a method for software development which can satisfy all above conditions. Although there are a lot of test methods about component for composition, function, compatibility and reliability, it's not enough to ensure that the component has reliability, maintainability, and reusability, so an integated method are necessary. In this paper, we are going to propose the solution model for integrating components, which are based on UML (Unified Modeling Language) technologies. This model can extract existing faults in the component interfaces by referencing sequence diagram and collaboration diagram.

• Annual Conference of KIPS
• /
• 2014.11a
• /
• pp.646-649
• /
• 2014

최근 레가시 소프트웨어 기능의 증가와 범위가 넓어져, 결함으로 발생하는 사고의 피해 규모가 증가하고 있다. 그로 인해 소프트웨어의 고품질화가 절대적으로 필요하다. 기존 NIPA의 소프트웨어 가시화는 코드로부터 아키텍처 추출을 중점을 고려한다. 이로부터 역공학 기법을 통한 객체지향 코드의 정적 분석과 가시화로 모델(클래스 모델, 순차적 모델, 패키지 모델, 그리고 유스 케이스 모델)과 요구사항을 추출하고자 한다. 이에 앞서 기존에 구축한 Tool-chain에서 가시화를 통한 클래스 모델 추출을 먼저 시도한다. 본 논문에서는 객체지향 패러다임에 맞게 수정된 결합도 측정 방법을 제안하고 추출된 UML 클래스 다이어그램에 적용한다. 그 방법은 측정된 결합도를 클래스 간 의존 관계와 비교하고 UML 클래스 다이어그램에 표현하는 것이다. 이를 통해 기존 레가시 소프트웨어의 재개발 과정에서 설계 문서의 추출과 고품질화가 가능하다.

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.16 no.5
• /
• pp.3071-3080
• /
• 2015

The increased demand on the transport of both passengers and goods through rail systems implies higher traffic intensity and congestion on the railways, resulting in greater likelihood of accidents and also degraded passenger services. To cope with the issues, development of an integrated communication network for rails has attracted great deal of attention lately. GSM-R is such an example developed in Europe, which seems to have restrictions in providing various communication services due to network speed limit. For the reason, an LTE-based approach is under study in Korea. After the network development, operation management of the network is necessary. Design of operation management systems has been studied little and thus is the objective of this paper. To do so, a conceptual design has been carried out based on model-based approach. Specifically, a context model has first been created using the use case diagram. Then, SysML models of operational scenarios were developed for the management system. The SysML models have alternatively been expressed as EFFBD models to simulate and verify them. Consequently, the result of the conceptual system design for the operation management of the integrated wireless network is expected to be used as a basis for the detailed design later.