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

근래의 소프트웨어 관련업계에서는 소프트웨어 개발 및 관리에 있어 소프트웨어구조를 중심으로 생산성 및 품질의 극대화를 추구하고 있다. 또한 소프트웨어 컴포넌트 관련 기술 및 컴포넌트 기반 소프트웨어 개발 방법론에 대한 연구도 활발히 진행중이며, 많은 응용기술들이 나오고 있다. 소프트웨어 구조는 소프트웨어를 컴포넌트로 구성하고 그 사이의 상호작용을 커넥터를 이용해 기술함으로서 전체적인 구조를 분석하고 유지하는데 필수적인 요소로 고려된다. 본 연구에서는 우리가 개발한 HappyWork라는 모델링 도구를 사용하여 소프트웨어 구조를 설계하는 기법을 설명한다. HappyWork를 이용한 소프트웨어 구조 설계 과정에는 System Context Diagram, Component Diagram, Component Sequence Diagram과 같이 세 가지 다이어그램이 사용되며, 이 Diagram들을 User, System, Component, Connector와 같은 네 가지 element들로 구성된다.

• Journal of KIISE:Computing Practices and Letters
• /
• v.9 no.4
• /
• pp.381-392
• /
• 2003

Component-based Development(CBD) based on the software reuse has been more attractive from software companies that want to enhance software productivity. However, since component identification process is mainly dependent on domain expert´s intuition and experience, it was very difficult to develop tools for supporting the component identification process. In this paper, we propose a systematic procedure of identifying reusable component by using object dependencies and object usages and provide a design and implementation of its supporting tool. In object-oriented domain models. there exists several diagrams which are described in different viewpoints. From these diagrams, object dependency and object usages are extracted and merged into an object dependency network, which is a basis for performing a comfonent identification algorithm. Finally, through a case study of internet banking system, we evaluate the applicability of the proposed identification process and tool.

• Proceedings of the Korean Operations and Management Science Society Conference
• /
• 2000.10a
• /
• pp.223-226
• /
• 2000

현재의 소프트웨어들은 그 요구사항이 늘어나고 규모 역시 커져서 여러 사람이 팀을 이루어 개발하는 것이 일반적이다. 이런 개발과정에서 서로 다른 개발자가 구현한 코드를 통합하는 것은 무척 어려운 일이며 이렇게 구현한 소프트웨어에 대한 명세를 작성하거나 분석하는 것 또한 많은 노력을 필요로 한다. 특히 ERP 어플리케이션과 같이 많은 수의 개발자들이 분산 환경에서 협력 작업을 통하여 프로그램을 개발하는 경우에 있어서는 개발자 상호간의 의견교환과 정보 공유는 물론, 서로 다른 개발자가 자신이 필요로 하는 코드를 찾아내고 분석하여 통합하는 일은 필수적이면서도 많은 시간과 노력을 요구한다. 따라서 견고한 어플리케이션을 위해서는 개발 도구가 이러한 요구사항들을 충분히 반영하여야 한다. 본 논문에서는 컴포넌트 기술을 이용한 ERP 패키지 시스템인 SEA+의 개발 도구에 포함되어 있는, 분산 협력 개발시 요구되는 이와 같은 사항을 반영하여 설계 개발한 순차 다이어그램 편집기에 대하여 설명한다.

• Journal of the Korea Society for Simulation
• /
• v.15 no.2
• /
• pp.59-69
• /
• 2006

Component-based software development is introduced as a new development paradigm in software development method. This approach is different from existing software development approach because it is based on reusable and autonomous unit, component. Therefore, component-based development(CBD)is divided into two stages; component development process and component assembly process; application development process. Component development process is the core of CBD because component has a key for good software. Currently many methodologies or tools have been introduced by various academies or industries. However, those don't suggest systematic and flexible modeling techniques adaptable easily into component development project. Existing approaches have a unique orarbitrary modeling technique or provide heuristic guidelines for component modeling. As a result, many component developers are faced with a difficult problems; how to developcomponent models, when develop which diagrams, and so on. In order to address this problem, we suggest a meta-model driven approach for component development in this paper. We provide meta-models according to both layer and development phase. We expect that suggested meta-models allow component developers to develop appropriate models of the time.

• Proceedings of the Korean Information Science Society Conference
• /
• 2006.06c
• /
• pp.196-198
• /
• 2006

소프트웨어 프러덕트 라인 개발 방법론이란 개발 초기에 시스템의 공통적인 부분과 가변적인 부분을 명확히하여 소프트웨어 자산을 구축한 후 다양한 요구 사항에 따라 가변적인 부분을 커스터마이징하여 목표 시스템을 생성하는 소프트웨어 개발 패러다임이다. 일반적인 소프트웨어 프러덕트 라인에 대한 연구는 활발히 진행되고 있지만, 병렬성을 지원하는 소프트웨어 프러덕트 라인에 대한 연구는 상대적으로 미약하다. 본 논문에서는 병렬 소프트웨어 프러덕트 라인 구축에 있어서 특성 모델을 통해 기능적 가변성을 지원하고 상태 다이어그램을 통해 동시성을 지원하는 컴포넌트의 코드를 자동 생성하는 도구를 제안한다. 본 연구 결과는 병렬성이 중요한 실시간 임베디드 소프트웨어 프러덕트 라인 구축에 활용될 수 있다.

• Journal of Korea Society of Industrial Information Systems
• /
• v.5 no.3
• /
• pp.87-93
• /
• 2000

Recently Software Industry has tended to enhance the productivity and quality with using the software architecture in software development and administration. The research of software component technique and software development methodology are just doing and making many applications. The software architecture is considered as the essential element for analyzing and maintaining the entire structure with organizing the software into components and describing the relations with connectors. The software modeling methodology that we propose is generating Happy Work Language describing the software structure with the modeling tool as Happy Work. We can use System Context Diagram, Component Diagram, Component Sequence Diagram, and they are composed of four Elements as Users, Systems, Components, Connectors.

• The Journal of Korea Institute of Information, Electronics, and Communication Technology
• /
• v.8 no.6
• /
• pp.556-561
• /
• 2015

The actual aircraft flight training can be done, throw this platform. this paper focuses on identifying the functions with respect to software components in the development of a aerodynamics system, which is based on the functions necessary to develop the real environment aircraft system. It also design activity diagram, concept as well as class diagram. This paper presents the main features and direction of aircraft to be equipped in the future gaming platforms. By designing a pilot platform updates that allow for new aircraft models students can understand exactly what they want and aircraft. this study presents a use case based on the aerodynamic simulation CSU concept to execution.

• Journal of the Korea Society of Computer and Information
• /
• v.13 no.5
• /
• pp.171-177
• /
• 2008

CBD(Component-based Development), which refers to the method of treating software as parts of a larger whole and developing new information systems through the assembly and synthesis of existing software, has been popular among many methods for developing software. However, CBD has limitations in the mobile environment which requires frequent requirements change and flexible process. To overcome those limitations, we propose an improved mobile development process based on the UML(Unified Modeling Language) components. Our Proposal is the simple development process implemented as three phase of component diagrams for the mobile system having quickly evolving technology and small-size project. Through the implementation of a mobile banking service with the proposed development process, we show that our proposal works efficiently for the requirements change and flexible development.

• Journal of Korea Society of Industrial Information Systems
• /
• v.6 no.4
• /
• pp.39-47
• /
• 2001

Software architecture serves as a framework for understanding system component and their interrelationships. Software architectures can be reusable assets to achieve low costs, high productivity, and consistent quality. We have developed a software architecture design environment, called Happy Work. In this paper, we would like to present the structure and functions of Happy Work. Happy Work has two main functions. First, it provides a graphic editor for modeling of software architecture diagram. Second, it provides an ADL, called HWL(HappyWork language). HWL is a language that describes software architecture.

• The Journal of Society for e-Business Studies
• /
• v.14 no.1
• /
• pp.13-34
• /
• 2009

As ubiquitous computing technology is proliferating, a wider range of u-services applying ubiquitous computing technology has been implemented and some of the u-services have been actively considered for commercialization. Accordingly, establishing corresponding business models based on u-services also have been increased. However, structured methodologies to build u-service business models are still in its very early age. Moreover, since most of the legacy business model formulation and analysis methodologies have stressed on conventional or digital services, not u-services. Hence, the purpose of this paper is to propose a structured methodology of formulating and analyzing business models for u-services. An illustrative example is described to show the feasibility of the proposed methodology. To do so, Business Model Diagram (BMD), which adopts model components for u-services, is newly developed.