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

하나의 시스템의 아키텍처를 설계하기 위해서는 여러 아키텍처 스타일들이 복합적으로 결합하여 시스템의 전체적인 아키텍처를 구성하게 된다. 그러나 아키텍처 설계자 또는 개발자들이 아키텍처 설계 과정 중에 현재 설계된 아키텍처가 시스템의 요구사항을 적절히 반영하고 있는지 평가해 볼 수 있는 방법이 없다. 본 논문에서는 아키텍처 평가자와 다양한 이해관계자가 모여 아키텍처를 전반적으로 평가해 보기 전에 아키텍처 설계자가 설계과정 중에 자신이 담당한 부분의 현재의 아키텍처가 시스템의 요구사항을 적절히 반영하고 있는지 여부를 판단하여 설계 과정 중에 개선점을 도굴하고, 개선점을 재 설계에 반영하는 아키텍처 설계 방법론을 제안하고자 한다

• Journal of KIISE:Software and Applications
• /
• v.32 no.1
• /
• pp.10-21
• /
• 2005

Software architecture is increasingly being viewed as a key design in developing complex software systems, which largely affects the achievement of quality attributes. During the architecture-based software development, therefore, architectural transformation is needed to achieve quality attributes. Due to the variety of design alternatives and the poor predictability of the effects of the transformation, however, it is not easy to apply architectural transformation. Therefore, the method is needed to support architectural transformation through systematically analyzing the effects of applying various design alternatives to the architecture. This paper proposes an approach to support software architecture transformation. Based on architectural design decisions and the constraints on them included in the architecture, our approach defines a decision constraint graph representing the dependencies among architectural design decisions. Through using the decision constraint graph, architectural transformation can be systematically performed by understanding the effects of applying a transformation. While this work supports more understanding of applying architectural transformation, it also helps reconstruct a software architecture to improve the quality of the software.

• The Journal of Society for e-Business Studies
• /
• v.11 no.2
• /
• pp.71-91
• /
• 2006

Nowadays most enterprise want to organize all Information Technology elements for their vision and mission accomplishments by integration view Enterprise architecture is used by the solution. But IT is so more complex that it can't cover application development. This research defines software architecture framework by enterprise view and designs enterprise architecture framework for embracing application development. Software architecture framework consists of meta architecture, conceptual architecture, logical architecture, physical architecture. For enterprise architecture framework including enterprise software architecture framework, this research analyzes its perspectives and Views. After all, This research able to apply to systematic application development based on enterprise architecture and completely IT elements organization by enterprise view.

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

To design a software system many architecture styles have to be combined to construct the overall architecture of the system What to choose among various architecture styles or architectural approaches depends on the fact of what kind of functional or non-functional quality requirements the system should satisfy In this study, we define the method to choose suitable architectural approaches by the satisfaction level of system requirements that is evaluated through estimation about technical parts of architectural approaches, and verify the evaluation method by the case study that apply the evaluation method to choose architectural approaches for message system.

• Proceedings of the Korean Information Science Society Conference
• /
• 2006.10c
• /
• pp.396-401
• /
• 2006

아키텍처에 대한 기술은 아키텍처 평가와 검증을 위해서 반드시 필요하다. 아키텍처 기술(Architecture Description)을 위해서 아키텍처 기술언어, 아키텍처 모델에 대한 다양한 연구들이 있었다. IEEE-1471의 아키텍처 기술을 위한 개념적 모델이 아키텍처 기술에 대한 일반적인 모델로 제시되었고 이후에 아키텍처 기술에 대한 새로운 요소들이 제시되었다. 그러므로 IEEE-1471의 개념적 모델은 새로운 요소들의 개념 사이에 혼란이 존재한다. 본 논문에서는 IEEE-1471의 개념적 모델을 바탕으로 이후에 제시된 세 가지 요소를 추가함으로써 IEEE-1471의 개념적 모델을 확장하고자 한다.

• Proceedings of the Korean Information Science Society Conference
• /
• 2004.04b
• /
• pp.448-450
• /
• 2004

소프트웨어 아키텍처는 소프트웨어 시스템 구축시 설계단계의 첫번째 부분으로 소프트웨어 개발시 중요시 되고 있다. 아키텍처 설계시는 비즈니스 목표나 품질 요구사항, 도메인의 특징과 개발 환경 등 여러 가지 사항을 고려해야하고 설계된 아키텍처를 검증할 수 있어야 한다. 그러나 성숙한 아키텍처가 아닌 경우 개발하고자 하는 시스템의 아키텍처 설계나 검증이 어렵다. 따라서 본 논문에서는 비즈니스 정보시스템에서 많이 사용되고 있는 아키텍처를 도출, 분류해보고, 품질 속성 만족 여부를 분석함으로써 비즈니스 정보 시스템 구축시 아키텍처들에게 아키텍처 참조 모델을 제공하고자 한다.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2007.05a
• /
• pp.271-274
• /
• 2007

소프트웨어 아키텍처 평가는 시스템을 위한 아키텍처의 적합성을 판단한다. 아키텍처 평가를 통해 아키텍처 결정 또는 확장 설계를 진행하며 목표 시스템에 대한 품질예측이 가능하다. 그러나 지금까지의 아키텍처 평가 방법은 참가자들의 투표에 의한 합의나 경험적인 직관에 의존하므로 많은 일정의 소요와 의사결정에 있어 객관적이고 효과적인 절차로 진행되고 있지 않다. 본 논문에서는 소프트웨어 아키텍처 평가에 있어 품질속성의 추적성을 이용한 방법을 제시한다. 요구사항 명세서로부터 아키텍처 설계결정인 품질속성의 추적성을 활용한 효율적인 아키텍처 평가 절차를 제시하고 아키텍처 결정사항에 대한 명시적인 근거를 제공할 수 있게 한다. 제시된 방법은 아키텍처 평가를 체계적이고 객관적으로 수행 가능하게 하여 아키텍처의 신뢰성을 높이고 최종적인 시스템 품질 향상에 기여할 수 있다.

• 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 Software Engineering Society
• /
• v.23 no.4
• /
• pp.125-139
• /
• 2010

This paper first examines the notion of software and the importance of software development and then presents twelve fundamental principles for software architecture design as the key enabling technology for effective software development. This paper divides design steps into four groups, i.e. analyzing the problem, deciding architecture modeling methods, architecture design process and architecture evaluation. Then it identifies the principles within and across the various steps of software architecture design and explains their roles.

• The KIPS Transactions:PartD
• /
• v.12D no.6 s.102
• /
• pp.857-862
• /
• 2005

MND(Ministry of National Defense) has developed MND AF(Ministry of National Defense Architecture Framework) and CADM(Core Architecture Data Model to guarantee interoperability among defense information systems. But, it is very difficult to manage architecture product documented through MND AF and CADM. So, there Is necessity for development of modeling tool and repository system which can develop architecture products and manage architecture product informations in common repository In this paper, we developed architecture product management system which supports development and management of meta model and architecture product of MND AF and CADM. Through architecture product management system architect of each agency can construct architecture product in a more effective and efficient way with modeling method and a user can search and refer useful architecture product informations using query function. Also, architecture product management system provides the basis for system integration and interoperability with integration, analysis and comparison of architecture product.