• 한국IT서비스학회:학술대회논문집
• /
• 2006.11a
• /
• pp.177-184
• /
• 2006

시스템의 동적 요소를 기술하고 분석하기 위해 C&C view 아키텍처를 주로 사용하지만 시스템의 실행 순서나 상태에 대한 정보가 부족하기 때문에 단지 C&C view 아키텍처로만 시스템의 동적 요소를 분석하기가 어렵다. FSP model은 시스템의 동작을 표현하기 위한 모델링 언어로써 시스템의 동작을 모델링 할 뿐만 아니라 LTSA라는 FSP 검증 툴을 이용하여 시스템의 특성을 자동으로 파악하기에도 용이한 특성을 가지고 있어 시스템 동적 요소 분석에 도움을 준다. 하지만 관련 정보를 얻기 어려워 FSP model을 구현하는데 어려움이 있다. 이 논문은 C&C view 아키텍처와 요구 사항(Use Case Scenario 혹은 Sequence diagram)을 근간으로 시스템의 동적 요소를 FSP로 모델링 하는 방법을 정의한다. 또한 LTSA 툴을 이용하여 자동적으로 시스템의 특성을 검증할 수 있고, 이를 통해 시스템 구현 전에 시스템의 에러를 찾아내고 해결하는 도움을 줄 수 있다. C&C view 아키텍처는 시스템의 컴포넌트와 커넥터에 대한 정보를 제공하여 주고 요구 사항은 소프트웨어 시스템의 행동에 대한 정보를 제공하여 줄 수 있다. 만약 우리가 컴포넌트와 커넥터에 대한 정보가 있고 시스템 동적 요소에 대해 알고 있다면 우리는 이것을 기반으로 메시지 흐름도를 구현할 수 있다. 메시지 흐름도는 Harel, Kugler 와 Pnueli에 의해 개발된 Synthesized 알고리즘을 이용하여 Statechart로 만들어지고 이것은 바로 FSP model로 변환될 수 있다. 우리가 소프트웨어 시스템에 대한 FSP model을 가지고 있다면 이것을 기반으로 시스템 행동 특성을 체크할 수 있으며 이는 향후 발생할 수 있는 결함을 미리 찾아내는데 유용한 도움이 될 수 있다. 우리는 간단한 예제를 통해 본 논문의 이론을 수립하였으며 이를 기반으로 실제 어플리케이션에 적용하여 그 효용성을 검증하였다.

• Journal of KIISE:Software and Applications
• /
• v.34 no.4
• /
• pp.328-341
• /
• 2007

When the decision to initiate a software product line has been taken, the first step is the domain analysis describing the variability in the requirements, the second important step is the definition of a domain architecture that captures the overall structure of a series of closely related products. A domain architecture can be a core asset in product line by describing the commonalities and variabilities of the products contained in the software product line. The variabilities, which are identified at each phase of the core assets development, are diverse in the level of abstraction. Therefore, it is important to clearly define, systematically identify, and explicitly represent variability at the architectural level. However, it is difficult to identify and represent the variability which should be considered at the architecture level, because these may be appeared in architecture elements and in architecture configuration. In this paper, we suggest a method of developing domain architecture as a core asset in product line where commonality and variability are explicitly considered. First of all, we will describe a domain architecture metamodel that can explicitly define commonality and variability concepts by extending the Object Management Group's ($OMG^{TM}$ Reusable Asset Specification eRAS) model. Using the domain architecture metamodel, architecture elements are defined and the variations that can be identified at the architecture level are classified into two types in according th abstract level. Additionally, we describe a domain architecture where commonality and variability are explicitly considered on basis of this metamodel.

• Information Systems Review
• /
• v.4 no.2
• /
• pp.111-131
• /
• 2002

Strategic information systems assist organization with the significant opportunity to gain competitive advantage in executing its business plans and realizing its business goals. The universities establish long-range plan of information systems in an effort to provide just-in-time, useful, efficient and effective information services to their members such as professors, students, and staffs when carrying out various organizational activities. The university information systems started from the primitive computer-based application, extended to the administrative and educational e-transformation, even to the virtual university concept. Through an empirical analysis and complementary case examples, the current study carefully chose three Korean universities according to their chronological importance, that have undergone the information systems planning process years from 1995 to 2001. These universities then, were compared in terms of the information technology architecture: the information architecture, infra architecture, and information management architecture. These three areas of system were cross-examined under the consideration of the evolution of information technology architecture, and its impact on the development of university e-transformation. As part of a fulfillment plan to satisfy the needs of customers of current trend, it is evident that the university e-transformation provides a stepladder to highly competitive, first class university in the market, through achieving the educational advancement, research enhancement, and administrative efficiency. The result of the study analysis indicates that, of the three architectures examined, the weakness showed in the information management architecture. Therefore it is crucial for the university staffs, managers and professors to understand the significance of the successful implementation of the information system and its maintenance. Our study certainly will act as a catalyst for the promotion of the future university e-transformation projects.

• Journal of the Korea Society of Computer and Information
• /
• v.14 no.3
• /
• pp.149-159
• /
• 2009

Nowadays, as the importance of service-oriented architecture software is recognized, the market of service-oriented software is getting bigger. In response to this, the requirements of high reliability and quality about service-oriented architecture software is getting increased. In this research, we clearly suggested the evaluation method by giving a specific evaluation example to evaluate the reliability qualify of service-oriented architecture software. It is expected to raise the objectivity and the utilization by inducing the reliability qualify improvement from this research.

• Proceedings of the Korea Database Society Conference
• /
• 2008.05a
• /
• pp.369-377
• /
• 2008

This paper is to provide the method of dynamic service composition in ubiquitous environment. This method is extended of Service Component Architecture, which is a standard about service composition. This standard only supports service composition in system design time. It has problem we cannot it ubiquitous environment, requests dynamic service composition. To solve this problem, we suggest dynamic service composition method based on SCA.

• Journal of the Korea Institute of Military Science and Technology
• /
• v.13 no.6
• /
• pp.1113-1120
• /
• 2010

In this paper, we have proposed Architecture Development methodology which can connect both operational view and system view. The Functional Architecture can connect both user and developer, and it is located between Activity analysis and System analysis. We suggest the new architecture methodology using the Functional Architecture and it provides effect to analyze the connection between user(military) and developer(enterprise) in Defence R&D and the new Architecture with the feedback analyze activity on a point of system view and the new architecture make the functional architecture.

• The KIPS Transactions:PartD
• /
• v.12D no.4 s.100
• /
• pp.589-600
• /
• 2005

Application developers need effective reuseable methodology to meet rapidly changes and variety of users requirements. Product Line and CBD(Component Based Development) offer the great benefits on quality and productivity for developing the software that is mainly associate with reusable architectures and components in a specific domain and rapidly changing environments. Product line can dynamically focus on the commonality and variety feature model among the products. The product line uses the feature modeling for discovering, analyzing, and mediating interactions between products. Reusable architectures include many variety plans and mechanisms. In case of those architecture are use in product version for a long time, It is very important in architecture product line context for product line design phase. Application developer need to identify the proper location of architecture changing for variety expression. It is lack of specific variety managements to design the product line architecture until nowdays. In this paper, we define various variety types to identify the proper location of architecture changing for variety expression and to design the reusable architecture. We also propose architecture variety on feature model and describe variety expression on component relations. We implemented the web learning system based on the methodology. We finally describe how these methodology may assist in increasing the efficiency, reusability, productivity and quality to develop an application. In the future, we are going to apply the methodology into various domain and suggest international and domestic's standardization.

• The KIPS Transactions:PartD
• /
• v.16D no.4
• /
• pp.631-642
• /
• 2009

Although the Korean government is making great effort to prevent the redundancy in IT investment and efficiently allocate the IT budget, actual achievements are quite limited because of the variety of IT resources and different architecture description among organizations and projects. Thus, a standardized description model of the system architecture is strongly needed to identify the common resources and improve the efficiency of IT investment. Therefore, in this paper, we have developed the function-network matrix model which can be used as the basic template for a standard for architecture description of e-Government systems. The function-network matrix model integrates the function tiers and the network areas into a single unified framework, which enables the functionality of each component and the flow of information clearly visible. Moreover, we described the architectures of Korean e-government’s citizen service systems using our model, resulting in clear demonstration of the similarities and differences between different systems, and easy identification of the common resources. Using the architecture description model developed in this research, the consolidation of national IT resources can be promoted, and non-expert IT users can easily recognize the architecture of their systems. In addition, more efficient and systematic IT resource management can be achieved using our model.

• Journal of the military operations research society of Korea
• /
• v.34 no.2
• /
• pp.175-191
• /
• 2008

The Korean military is aware that EA(Enterprise Architecture) is an important tool for transforming national defense and building Korean NCW, being developing the Ministry of National Defense Enterprise Architecture(MND-EA). However, unlike the importance of MND-EA, they are building MND-EA without the explicit EA governance system Many researchers have emphasized that it is difficult to develop the useful EA without EA governance. In this study, we present the EA governance framework for implementing the effective MND-EA. Through the investigation of the state of EA development and EA governance of home and abroad public institutions, we recognize the importance of EA governance, identifying the EA governance components. We set up the basic governance model consisted of principle, organization and process, designing the MND-EA governance framework by mapping the model to governance scope and target. The proposed governance framework provides direction for explicit and formal MND-EA governance system.

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