• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.10 no.8
• /
• pp.1970-1976
• /
• 2009

It is more emphasized on the software architecture recently, as the scale of a software becomes huge and the need of the software management becomes more dynamic. Software architecture is a representation of structures of software framework just like the blueprint of building architecture. In order to describe software components and their relationships accurately and entirely, software architecture is documented in some different views, by using of modeling tools. UML(Unified Modeling Language) is a software modeling tool recently used for documentation of software and as well as software architecture. Nevertheless, what we have to agree with is that UML is not easy to use and its standard changed continuously. And also the documentation with UML is found some burden because of its difficulties in learning and using. This inconvenience enforces us to purchase and use commercial tool for UML. The study introduces the architecture views refined from 4+1 Views for architecture design and shows how to represent architecture views for software architecture. Especially, we simplifies UML diagrams for the purpose of focusing on architecture views and facile manipulation. At the end, we add the evaluation on the refined architecture views as well as refined UML diagram.

• Journal of the Korean Operations Research and Management Science Society
• /
• v.28 no.2
• /
• pp.91-103
• /
• 2003

Use case modeling on UML (Unified Modeling Language) is getting widely used in OOAD and CBD and it is considered a useful technique in dealing with the complexity of the requirements analysis. However, some of the problems with use case modeling are that it is not structured, difficult to handle non-functional requirements, and to analyze impacts among use cases. To alleviate these problems, we propose a scenario-based goal-oriented approach for use case modeling. The proposed approach is to apply a goal-oriented analysis method to use case modeling. Since goal-oriented analysis method is not systematic and many heuristics are involved, we have adopted scenarios as the basis for goal extraction. The proposed method is applied to CBIS (City Bus Information Subsystem) in ITS (Intelligent Transportation System) domain. The proposed approach helps software engineers to analyze the impact among use cases and represent non-functional requirements.

• Proceedings of the KIEE Conference
• /
• 2008.04a
• /
• pp.47-48
• /
• 2008

UML(Unified Modeling Language) is the most frequently used modeling language in the process of analysis, design, implementation and etc. The main reason of using UML is not only to help users to work visually but also to draw better communication among developers. In addition, UML is one of the global standards and supports MDA. In this paper embedded software development method for USN using UML is discussed To show how the development method is used, IEEE 802.15.4 radio module are programmed using UML software tool.

• Proceedings of the Korean Information Science Society Conference
• /
• 2001.04a
• /
• pp.394-396
• /
• 2001

인터넷 상에서의 다양한 멀티미디어 응용 및 정보 서비스의 요구가 급증하게 되고, 이에 따른 효율적인 운영 및 서비스에 대한 표준 기술의 개발 또한 활발히 진행되게 되었다. 이에 1998년 W3C(World Wide Web Consortium)에서 웹 기반 동기화 된 멀티미디어 통합 언어인 SMIL이 제안되었다. 선언적 마크업 언어인 XML(eXtended Markup Language)에 기반을 둔 SMIL은 웹 상에서의 멀티미디어 프리젠테이션을 위한 다양한 기능들을 제공하지만, SMIL 또한 HTML(HyperText Language)과 같은 태그 기반 마크업 언어이므로 각 태그의 사용법을 숙지하여 텍스트 편집기를 이용한 비효율적인 저작에 치중되어 있었다. 이에 SMIL 응용업무에서의 효율적 활용을 위한 SMIL 전용 저작도구의 필요성이 대두되었고, 국내외에서의 활발한 연구 개발이 진행되고 있다. 본 논문에서는 UML(Unified Modeling Language) 표기법에 기반 한 객체지향 모델링 툴을 사용하여 체계적인 소프트웨어 설계에 따른 SMIL 저작도구를 구현하였다. 템플릿 기능의 지원으로 효율적이고 편리한 SMIL 컨텐츠 생성을 위하여 인턴넷 망(network)의 대역폭에 따른 저작이 가능하도록 구현되었으며, 미리 보기 기능을 활용한 멀티미디어 데이터의 직관적이 운영을 지원하도록 구현하였다.

• Journal of KIISE:Software and Applications
• /
• v.26 no.9
• /
• pp.1105-1113
• /
• 1999

객체 지향 소프트웨어의 확장과 더불어 소프트웨어의 재사용성의 중요도가 부각되면서 소프트웨어를 콤포넌트 단위로 구현하는 추세이다. 따라서 콤포넌트 기반의 소프트웨어 개발에서의 통합 테스트가 중요한 이슈로 떠오르고 있다. 그러나 콤포넌트들의 통합 테스트에 대한 연구는 미흡한 상태이다. 본 논문에서는 UML을 기반으로 체계적인 통합 테스트 모형을 제안하고. 나아가 본 논문에서는 "멀티미디어 정보처리 시스템"의 사례를 본 논문의 콤포넌트 통합 테스트 모형에 적용한 결과를 분석하여 기술한다. 콤포넌트 통합 테스트 모형은 UML(Unified Modeling Language)의 순서도(sequence diagram)와 협력도(collaboration diagram)를 이용하여 전체 시스템에서 UML의 사건흐름을 구성하는 콤포넌트들 사이의 인터페이스 영역에 존재하는 오류들을 추출한다. 그리고 UML을 기반으로 통합 테스트를 수행함으로써, 테스트 준비 작업을 줄이고, 기존의 UML 지원 도구들과 연계하여 테스트 자동화 도구의 구현을 앞당길 수 있다. 또한 시스템의 순차적 흐름 뿐 아니라, 동시에 수행되는 흐름에 대한 정보까지 모두 수용하여 테스트함으로써, 콤포넌트 기반의 분산 환경의 특성에 적합하다. Abstract As the object-oriented approach to software development becomes more mature, software development from pre-existing, independently developed components becomes an important aim of software engineering. Therefore, integration testing becomes an important aspect of component-based software development. However, there has been little work done in the area of the component-based integration testing. In this paper, we propose the "component integration test model" which is based on UML. Furthermore, we describe a case study on "Multimedia Information Processing System" conducted to analyse the result from which our model is applied. Our model extracts the faults, which exist in interfaces of components, using sequence diagram and collaboration diagram of UML(Unified Modeling Language). As our model is based on UML, the preparation effort for testing is reduced and its test-tools can be implemented more easily through linking existing UML tool. And our model accepts the information of concurrent flow represented by collaboration diagram as well as sequential flow, so it is more suitable to component-based distributed environment.based distributed environment.

• The KIPS Transactions:PartA
• /
• v.10A no.5
• /
• pp.503-512
• /
• 2003

Recently many applications are being developed as web technologies are evolved rapidly, but the development emthodology and quality improvement speed of the web apllications is not so. The creations of Most web applications have developed depending on the developer's knowledge and experience without a systematic development methodologies. But the web-based application systems require the various developing gechniques and the rich developing methodogies for a design process. This paper applies the UML(Unified Modeling Language) supporting an object-oriented development methodology to the design and implementation of a mobile customer management system. That is, it appliesthe UML to the system modeling based on a story board and a requirement specification at the web development of the similar web applications. Applying UML to this system achieved the analysis and the design of an web application effciently.

• Journal of KIISE:Software and Applications
• /
• v.34 no.8
• /
• pp.697-707
• /
• 2007

Since embedded software is very dependent for target hardware architecture, characteristics of the platform must be considered when designing the software. Furthermore, MPSoCs consists of heterogeneous hardware components that are specified in micro level. Thus mapping of embedded software for MPSoCs should be considered the characteristics. In this paper, we provide an approach to automatic mapping PIM (Platform Independent Model) of an embedded software to PSM(Platform Specific Model) for MPSoC(Multi Processor System On Chip) and verify its effectiveness with simulation. In the proposed approach, tasks are derived from an object oriented model based on the UML (Unified Modeling Language). And then the types of the derived tasks are identified. With the identified types and inter relationship between tasks, the tasks are assigned to appropriate heterogeneous hardware components. We expect that the approach improve accuracy of the assigning and concurrency of the deployed software.

• Proceedings of the Korean Information Science Society Conference
• /
• 2004.10b
• /
• pp.454-456
• /
• 2004

데이터베이스에 대한 제약사항들은 소프트웨어의 개발 및 사용에 있어 개발자와 사용자가 모두 참고해야 하는 중요한 사항임에도 불구하고 데이터베이스 모델링괴 소프트웨어 모델링의 불일치 및 표현 방법의 차이로 인해, 일관성 있는 제약사항 명세 및 설계에 많은 어려움을 겪어왔다. OCL(Object Constraint Language)은 객체의 제약사항을 표현하는 언어로서 UML(Unified Modeling Language)의 일부분이다. 본 논문은 객체의 제악사항을 표현하는데 사용하던 OCL을 데이터베이스의 제악사항을 설계에 일관성 있게 표현, 반영하기 위하여 사용하는 기법을 제시하고, 이에 대한 검증을 수행하는 방법에 대한 연구이다. 본 논문에서는 요구사항에서 추출한 데이터베이스의 제악사항을 정의한 규칙에 따라 추출해내고, 이를 OCL의 표현법을 이용하여 정형적으로 표현한다. 그리고 그 OCL의 형식적 표현을 ODL(Object Description Language)로 정의하는 기법을 정의함으로서 이에 대한 일관성 검증을 수행하는 기법을 제안한다.

• Proceedings of the Korean Operations and Management Science Society Conference
• /
• 2001.10a
• /
• pp.318-321
• /
• 2001

A collaboration supporting system, which enables multi-user collaboration and communication in Internet environment, is being a new indispensable tool to compete and collaborate with business peers. A collaboration supporting system in distributed environment requires scalable and open system architecture to rapidly deploy a new technology and trends. In this paper, we propose such a collaboration supporting system where communication API is using XMI(Extended Markup Language)-based SOAP(Simple Object Access Protocol)protocols, which is independent on programming language and platform. In our system, sever components are developed with EJB(Enterprise Java Beans). System analysis, design, and development are based on UML(Unified Modeling Language).

• Journal of Korean Society of Industrial and Systems Engineering
• /
• v.25 no.1
• /
• pp.20-28
• /
• 2002

A collaboration supporting system, which enables multi-user collaboration and communication in Internet environment, is being a new indispensable tool to compete and collaborate with business peers. A collaboration supporting system in distributed environment requires scalable and open system architecture to rapidly deploy a new technology and trends. In this paper, we propose such a collaboration supporting system where communication API is using XML(Extended Markup Language)-based SOAP(Simple Object Access Protocol)protocols, which Is independent on programming language and platform. In our system, server components are developed with EJB(Enterprise Java Beans). System analysis, design, and development are based on UML(Unified Modeling Language).