• Journal of KIISE
• /
• v.42 no.3
• /
• pp.341-360
• /
• 2015

While architectural patterns provide software development solutions by providing schemas for structural organizations of software systems based on empirical knowledge, Jackson's problem frames provide a method of analyzing software problems. Problem frames are useful to understanding the software development problem, by putting emphasis on the problem domain, rather than on the solution space. Research exists that relates problem frames and software architecture, but most of this research uses problem frames only to understand given problems. Moreover, none of the existing research derives architectural patterns by considering both problem frames and quality attributes. In this paper, we propose a software architecture design method for pattern-based architecture design, by matching problem frames and architectural patterns. To that end, our approach first develops the problem model based on the problem frames approach, and then uses it to match with candidate architectural patterns, from the perspectives of both functionality, and quality attributes. Functional matching uses the problem frame diagram to match the problem model of an architectural pattern. We conduct a case study to show that our approach can systematically decide the right architectural patterns, and provide a basis for fine-grained software architecture design.

• The KIPS Transactions:PartD
• /
• v.19D no.1
• /
• pp.63-80
• /
• 2012

Mobile devices with Android OS and iOS have been emerged as mobile computing devices where various software applications are deployed. Furthermore, they are anticipated to be used not only for traditional personal computing but also for enterprise computing. However, such mobile devices have their intrinsic characteristics such as limited resources and flexible network capabilities, which are not revealed in traditional computers. Hence, there is high demand for methods to develop mobile applications with reflecting their intrinsic characteristics. Since those characteristics belong to non-functional requirements, they should be reflected in architecture design while designing mobile applications. To design architecture, the architecture drivers that are architecture non-functional requirements are decided from mobile application characteristics. Conventional architecture design methods do not consider those characteristics so that the methods cannot be straightforwardly applied to mobile applications. In this paper, to efficiently develop mobile applications reflecting those characteristics, we propose a set of architecture patterns and define a guideline to apply those patterns. First, we define the characteristics of mobile applications distinguished and derive architectural drivers from them. Then, we propose architecture patterns in terms of static and dynamic views and define an architectural guideline to apply the patterns to designing architecture for mobile application. And, we perform case studies to verify the applicability of proposed patterns. Finally, we assess the proposed architecture patterns by proving how the patterns can fulfill identified architecture drivers and by comparing our approach with previous works.

• Journal of KIISE:Computing Practices and Letters
• /
• v.16 no.4
• /
• pp.392-404
• /
• 2010

Recently, as both business processes and IT systems become ever more complex. Especially, enterprise applications tend to become unmanageably complex and increasingly costly to maintain. Therefore complexity is the insidious enemy of software development. It is critical to have a methodology that recognizes and manages this enemy effectively. In this paper, we propose ISIS (Integrated System of Independent Subsystems) - the architectural style needed to develop the complex enterprise applications. The ISIS was developed to meet the challenge of reducing the complexity of a larger enterprise application today. It gives us architecture models for reducing development complexity and composite application. The enterprise application is partitioned into a collection of independent subsystems using ISIS decomposition schemes and equivalence relations. We use middleware named ISIS engine that provides a service for subsystems interoperability by enabling the integration of distributed, cross-platform subsystems. We have implemented an ITSM system that achieves our objectives, reducing development complexity, using the ISIS architecture. Finally, ISIS architecture provides greater flexibility and productivity when an organization needs either to change its business processes, or to update the underlying systems.

• Proceedings of the Korean Information Science Society Conference
• /
• 2005.11b
• /
• pp.1-3
• /
• 2005

최근 소프트웨어 재사용과 소프트웨어의 응용범위가 넓어짐에 따라 잘 정의된 아키텍처를 기반으로 개발된 컴포넌트 소프트웨어 개발(CBD . Component-Based Development)방식의 채택이 빠르게 확산되고 있다. 이러한 컴포넌트 소프트웨어 개발 방식이 빠르게 확산되면서 아키텍처를 정확하게 기술, 분석, 정제할 수 있는 능력 또한 점차 중요시 되고 있다. 아키텍처를 정확하게 기술, 분석 정제하기 위해서는 아키텍처 기술 언어(ADL)의 사용이 필요하다. 또한 ADL로 기술된 모델 정보들을 서로 다른 ADL지원도구들이 공유할 수 있도록 ADL 모델 관리기의 개발이 필요하다. 본 논문에서는 ADL 모델 관리기의 구성요소를 기술하여. ADL 모델 정보를 XML형태로 변환하는 변환기의 변환 과정을 설명하고, XML 형태로 변환된 ADL 모델 정보들을 저장하는 저장소 구조를 각각 기술하고, 검색기의 검색 과정 및 검색 결과를 보여준다.

• Journal of Software Engineering Society
• /
• v.24 no.1
• /
• pp.1-7
• /
• 2011

MVC(Model-View-Controller) architecture is well-known for high maintainability and it makes efficient development possible. Recently, it has been applied in many fields such as web, desktop and mobile applications. Therefore, effective testing for this architecture is strongly needed. Although much research has been done, there was not much efforts for exploiting MVC architecture in GUI testing. Therefore, in this paper, we propose a scheme for efficient and accurate GUI testing for MVC based applications. In this study we separate original state diagrams into view state diagram and model-controller state diagram. Then, we present a case study showing the effectiveness of our proposed scheme.

• Journal of KIISE:Software and Applications
• /
• v.41 no.7
• /
• pp.457-468
• /
• 2014

Recently, several approaches are proposed to support developing Self-Adaptive System. However, they do not provide the way to accept interaction between requirements and architecture. It makes difficult to judge the impact of changing requirements, handle quickly, and understand adaptation process for stakeholder. To overcome above problems, this paper suggests the interweaving method for providing traceability based on the relationship between requirements and architecture. This traceability allows tracing the impact of changing requirements, and it provides the rationale of architectural decision for advanced degree of understanding. Example shows the usefulness through developing process and changing process on Smart Grid domain.

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

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

제품 계열 공학(Product Line Engineering, PLE)는 패밀리 멤버들의 공통성과 가변성을 분석하여 만든 핵심 자산을 특화시켜 어플리케이션을 개발함으로써 재사용성과 이용가능성을 증대시키는 접근 방법이다. 핵심 자산은 제품 계열에 속하는 패밀리 멤버들이 어플리케이션을 만드는데 기초가 되는 모든 자산을 포함하며, 아키텍처, 컴포넌트 둥이 포함될 수 있다. 범용 아키텍처는 패밀리 멤버들이 공통적으로 사용할 수 있는 아키텍처로, 제품 계열에 속하는 제품들의 구조를 정의하고 컴포넌트의 인터페이스 명세를 제공하여 컴포넌트만큼 중요한 재사용 단위이다. 본 논문에서는 대표적인 PLE 방법론에서 정의한 제품 계열 아키텍처와 일반 소프트웨어 아키텍처를 비교하여 범용 아키텍처에 포함되는 요소들을 선정하고, 메타 모델을 이용하여 범용 아키텍처 구성요소와 구성요소간 관계를 명확히 정의함으로써, 개념적인 아키텍처를 보다 실용적으로 설계하는데 도움이 되게 하고자 한다.

• Journal of Navigation and Port Research
• /
• v.37 no.1
• /
• pp.9-14
• /
• 2013

The e-navigation has been being developed in IMO is a sort of strategy to provide user-oriented services for safe navigation and environmental protection based on the architecture and its related services complying with the user needs. At NAV $57^{th}$ meeting in 2011, the overarching e-navigation architecture was approved which represent overall relationship only between onboard and ashore elements, so more detail technical architecture for each element should be developed for implementation in view of services and systems. Considering the continuous and iterative verification of e-navigation development process required by IMO, the relationship and traceability should be took in consideration between the outcome of e-navigation process and the element of the architecture. In this paper, we have surveyed literarily the user needs, result of gap analysis and practical solutions to address them and defined the architecture elements and their relationship considering the three kinds of views of DoDAF(Architecture Framework) of US department of Defence, in result, proposed the e-navigation shipboard technical architecture.

• Informatization Policy
• /
• v.18 no.1
• /
• pp.73-99
• /
• 2011

The Korean military has developed and operated computer, network, communication technologies as well as war game models to strengthen the national defense M&S continuously. In particular, lots of projects for developing models for drill/training, analyses, and acquired fields are being conducted in the military. However, it needs to look into the actual conditions and seek for strategies to develop the national defense M&S. First of all, in the field of war games, various national defense architectures have been built, including war and information environment architectures starting from the resource architecture in 2006. However, the function of drill and training is limited, so additional war game architectures are required to be built. To build joint war game architectures available as an effective verification tool to implement plans of the national defense and war architectures, this study examines the actual conditions of the current war game systems and suggested building joint war game architectures.