• 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 Korean Institute of Information and Commucation Sciences Conference
• /
• 2015.05a
• /
• pp.413-414
• /
• 2015

통합과 융합은 산업에 있어서 전 세계적 추세이며, 최근 국내산업도 업종 겸업화, 상품과 서비스의 복합화, 대형화 등의 변화를 거치고 있다. 이러한 통합과 융합은 IT의 구조적 복잡성을 증가시키면서도 변화에 민첩하게 대응할 것을 요구한다. 따라서 통합 시대의 정보시스템은 작고 간단한 컴포넌트들이 서비스 지향적으로 통합되어 있는 구조와 지속적으로 발전할 수 있는 구조가 요구되며, 유연성, 통합성, 재사용성 등이 핵심성공요인이 된다. 이에 본 논문에서는 이러한 구조적 변화를 반영하는 IT 통합방안의 하나로 서비스 지향적 아키텍처 기반의 통합 비즈니스 아키텍처 모델의 적용을 제안하고자 한다. 차별화된 특성을 가지는 이러한 비즈니스 아키텍처는 신규 비즈니스 및 상품의 민첩한 대응, 업무의 일관성 및 유연성 향상 등의 효과를 가져 올 수 있다.

• Information Systems Review
• /
• v.12 no.2
• /
• pp.1-23
• /
• 2010

Most enterprise information systems today are silo systems in that they are not properly aligned nor integrated with one another. Such silo systems result because enterprises lack an architectural perspective in the planning and development of the systems. This paper proposes an Enterprise Architecture Orientation Model as a framework for the analysis, planning and design of the architectural quality of enterprise information systems. The model decomposes enterprise architecture into two dimensions-alignment and integration, and specifies for each dimension the general development and evolution stages enterprises may traverse. The alignment dimension represents the vertical strategic alignment of the systems with the vision, mission, strategy and goals of the enterprise, and is analyzed in terms of the performance, capability, and strategy of the enterprise. The integration dimension, on the other hand, represents the horizontal and functional integration among the systems that span organizational functions and boundaries, and is analyzed in terms of such technological components as IT infrastructure, data, application, and business processes. The model combines the alignment and integration dimensions to form a two-dimensional conceptual space for mapping the architectural quality of the enterprise. It is proposed that an enterprise use the model to identify and understand its position now and in the future in the architectural quality of the enterprise information systems. It is also proposed that the model provides a tool for the planning and design of the transition from one stage to the next in the alignment and integration of the systems to reach an architectural maturity. At the end, the paper discusses how the model can be applied differently according to the strategic orientation of the enterprise. An example of the usage of the model is presented.

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

In this paper, a systematic approach of developing detail 00 designs from Component-and-Connector Architectures (CCAs) is proposed. In this approach, an intermediate model between the architecture model and the detail design model specified with class diagrams or sequence diagrams is introduced to narrow the wide gap between the two abstraction levels. Once a CCA is designed, candidate classes and their relationships are identified per each architectural element. In order to show the efficacy of this approach, we apply it to an industry software development project and verify that quality attributes supported by the CCA are equally maintained by the detail design.

• Journal of Information Technology and Architecture
• /
• v.9 no.4
• /
• pp.443-453
• /
• 2012

In order to minimize the damage from system failures, systems over various fields are requested to contain the safety-critical features. In this paper, we deliver the considerable issues, especially, in the cyber physical systems that is recently used as a safety-critical system, as well as we propose the model driven architecture based on time as its the important factor. Based on meta-modeling approach, we introduce the time-based architecture which is associated with deadline, transition state, and threshold, and also we work out a design for this by using model driven architecture. We propose a realizable safety-critical architecture by means of showing failure handling components with safety transaction model from the meta-model. In the detailed models and the example, we design a basic safety processing state, a multiple safety processing state, and a compound safety processing state for completing the safety-critical system architecture.

• The KIPS Transactions:PartD
• /
• v.15D no.6
• /
• pp.803-814
• /
• 2008

Product line architectures include variable parts to be selected according to product specific requirements. In order to derive architectures that are valid for a particular product from product line architectures, variabilities of product line architectures must be systematically managed. In this paper, we adopt an approach to variability management of product line architectures through an explicit mapping between a feature model and product line architecture models. If this mapping is incorrect or there exists inconsistency among product line architectural elements, variabilities of product line architectures cannot be managed correctly. Therefore, this paper formally defines product line architectural models in terms of conceptual, process, deployment, and module views, and mapping relationships between the feature model and the architectural models. Consistency rules for correct variability management of product line architectures are defined in terms of consistency in each of product line architecture model, consistency between different architectural view models, and consistency between a feature model and product line architectural models. These consistency rules provide a theoretical foundation for deriving valid product architecture from product line architectures.

• Journal of the Korea Society for Simulation
• /
• v.16 no.1
• /
• pp.49-57
• /
• 2007

Service-Oriented Architecture(SOA) is improving rapidly in IT Environment. Enterprise companies interest in implementation infrastructure based on SOA to adapt quick changes of large and complex distributed environment. SOA is a component model that inter-relates the different functional units of an application, called services, through interfaces and contacts between theses services. In this paper, we studied the concept of the relationship between SOA and standard web service core and therefore, we model the web service based on SOA. We implemented the application and business service architecture using web service that include the XML and SOAP. We confirmed that how the each SOA characters like interoperability, reusability, scalability and flexible business process adapted to web service and present a web service modeling that is maintained the neutrality using loose service coupling through the method of service model process and web service architecture designing methodology based on SOA.

• Proceedings of the Korean Institute of Information and Commucation Sciences Conference
• /
• 2009.05a
• /
• pp.415-418
• /
• 2009

최근 서비스 지향 아키텍처 (Service Oriented Architecture SOA) 기반의 애플리케이션 개발에 맞게 비즈니스 프로세스의 유연성을 확보하고 재사용을 증진시키기 위하여 비즈니스 프로세스 패밀리 모델(Business Process Family Model: BPFM)이 제시되었다. BPFM은 소프트웨어 프로덕트 라인 방법의 가변성 분석 기법을 사용하여 비즈니스 프로세스 군 (family)에서 나타날 수 있는 가변성을 분석하여 이를 명시적으로 표현하고 있는 모델이다. BPFM으로부터 여러 개의 BPM (Business Process Model)을 개발하기 위해서는 가변성 결정 및 가지치기 (Decision and Pruning) 과정을 거쳐야 한다. 이 때 가변성 사이에는 서로 협력적 또는 배타적인 관계를 가질 수 있고 이는 가변성 결정과 가지치기에 영향을 미치게 되는데, 현재 제시된 BPFM에는 이러한 바인딩 정보에 대해서 아직 고려하지 않고 있다. 본 논문에서는 비즈니스 프로세스 군에서 식별될 수 있는 가변성들 사이의 의존관계의 유형을 분석하고 이 정보를 모델의 형태로 나타낼 수 있는 방법을 제시한다. 먼저 BPFM에 포함된 가변성 정보를 독립된 의존관계 분석모델로 추출해 내고 각 가변성 결정유형에 따라 표현방법을 제시한다. 추출된 모델에서 의존관계를 표현하고 가변성 결정이 영향을 미치는 범위의 가변성들을 클러스터할 수 있는 방법을 제공한다. 본 방법을 이용함으로써 가변성 결정회수를 현저히 줄일 수 있음을 사례연구를 통해 보여준다. 또한 잘못된 가변성 결정으로 인한 BPM의 기능 불일치를 해소할 수 있음을 보여준다.

• Journal of Korea Multimedia Society
• /
• v.14 no.4
• /
• pp.554-566
• /
• 2011

Service-oriented architecture(SOA) is a paradigm where reusable units are independently executable and only accessible through outer interfaces. Standardized methodology based on SOA has not been decided yet although a lot of efforts have been made for systems using SOA. Therefore Development of system using SOA is facing many difficulties currently. In this paper, service oriented methodology of function based model for supporting legacy system is proposed. Standardized methods for function based reusability through analysing SOA methodology are proposed and guide lines for improvement of service reusability are presented.

• Journal of KIISE:Software and Applications
• /
• v.32 no.8
• /
• pp.730-741
• /
• 2005

Layered Architecture is a kind of nodule decomposition techniques, which decomposes a program by generality This paper proposes a ]aver based method for recovering layered architecture from object-oriented program and checking conformance against architectural document. To specify the rules for layered style in object-oriented program, we define a partially ordered set on modules by module use relationship and module layer relationship by module override relationship. The meaning of module layer relationship is explained with an example from design patterns. Steps to recover layered architecture from program are described and a metamodel for the recovery is proposed. Architecture recovery is performed on source codes from open-source software project, and the implication of parts that do not conform to its architectural document is discussed. As a result of checking, it is pointed out that, although the parts are considered allowable exceptions of layered architecture, their modifications should be controlled carefully.