• Proceedings of the KAIS Fall Conference
• /
• 2008.05a
• /
• pp.275-277
• /
• 2008

본 논문에서는 UML을 이용하여 소프트웨어 아키텍처를 표현하는 방법을 소개하고, 복수의 뷰를 통한 아키텍처를 문서화하는 방법을 설명한다. 무엇보다 논문의 핵심은 UML의 다이어그램이 복잡하여 특별한 편집도구 없이는 표현이 불가능한 점을 반영하여, UML의 표현방법을 개선하고 이를 아키텍처뷰의 표현에 적용한 점이라고 할 수 있다.

• Journal of KIISE:Software and Applications
• /
• v.30 no.5_6
• /
• pp.515-528
• /
• 2003

Component Based Software Development has been recognized as a new software development paradigm, and received much attention among researchers. However, it requires software architecture based development to assure component reusability and efficient software development. This paper proposes the Component Based 4+1 View Model of software architecture to support component based software development. It is redefined on the basis of the existing 4+1 view model of software architecture developed by Kruchten. Also, we describe the elements of the view model in detail with UML. This architecture constructs the foundation of component based software such as increasing the understanding of software and providing the information about how the components interact with each other. It can be done by exposing the context for the use of software components to each views.

• Journal of the Korea Society for Simulation
• /
• v.19 no.4
• /
• pp.309-318
• /
• 2010

Simulation-based acquisition(SBA) is a new acquisition paradigm to deliver combat systems cheaper, faster, and better. ROK MND adopts the vision of SBA and is pushing ahead with dramatic reform. However, ROK MND does not develop the SBA architecture framework which facilitates the reuse of tools and techniques and data software code and algorithms among participants of collaborative environments. In this paper, we propose a conceptual Model of architecture framework for SBA. To do so, we analyse acquisition process of MND and propose the to-be operational view that describes fundamental concept for how Government, Industry, and Academia can collaborate and share information more effectively throughout the acquisition process. Furthermore, we identify the tools and techniques that supports the operational nodes, and propose technical view and all view, too. technical view compose of set of standards that can ensure interoperability among tools, techniques and data, and all view provide an overarching description of the architecture.

• 한국IT서비스학회:학술대회논문집
• /
• 2007.11a
• /
• pp.425-430
• /
• 2007

시스템을 결정하는 품질 요소에는 여러 가지가 있으나 그 중에서도 유지보수성(Maintainability)이 높은 시스템을 만드는 것은 쉬운 일이 아니다. 또한 유지보수성이 높은 시스템인지 여부를 시스템 개발이 완료 전에 측정하는 것도 어려운 문제이다. 모든 품질요소가 그렇겠지만 시스템을 구성하는 소프트웨어 아키텍처 수준에서 시스템의 품질을 명확히 측정해내지 못하고 시스템 개발 이후에 측정한다면 품질 향상을 위한 시스템 수정은 생각할 수도 없는 문제가 될 것이다. 이 논문은 유지보수성 중에서도 가장 중요한 기능확장성(Extensibility), 즉 기존 시스템에서 신규 서비스를 추가하려 할 때 기존의 서비스에 영향을 미치지 않으면서 비용 및 기간을 최소화하여 새로운 기능을 추가할 수 있는 품질 속성을 소프트웨어 아키텍처 수준에서 비교하는 방법을 정의하여 제시한다. 본 논문에서는 소프트웨어 아키텍처 중에서도 기능확장성에 가장 큰 영향을 미치는 모듈 뷰를 기준으로 기능확장성을 측정할 갓이나 모듈 내부의 변경을 통한 기능확장성은 고려하지 않고 새로운 모듈의 추가로 인한 기능확장성을 고려하였다. 본 논문은 기 수립된 소프트웨어 아키텍처의 모듈 뷰가 가지는 고유한 기능확장성을 측정하는 함수를 제시하고 여기에 새로운 모듈이 추가될 매 변화한 소프트웨어 아키텍처의 기능확장 effort 함수를 제시한다. 이 두 함수를 통해 두 개의 대안 소프트웨어 아키텍처 모듈 뷰에서 어떤 것이 더 기능확장성이 있는지 판단할 수 있게 한다. 우리는 이를 검증하기 위해서 기능확장성이 좋다고 제시되고 있는 디자인 패턴(계층패턴과 Broker 패턴)을 통해 본 논문의 이론을 정립하고 그 효용성을 입증하였다. 따라서 소프트웨어 아키텍처 수준에서 기능확장성이 얼마나 가능한지 서로 비교 가능한 수치를 제시하였고 이 수치를 통해 실제 개발이 완료되기 전 시점에 시스템의 기능확장성을 명백히 측정할 수 있게 하여 시스템 기능 확장에 들어가는 많은 비용을 줄일 수 있다는 것을 보여준다.

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

소프트웨어 아키텍처는 다양한 이해관계자들의 관점을 반영한 뷰들로 구성된다. 품질속성은 아키텍처의 구조를 결정하므로 아키텍처에 일관성 있게 반영될 수 있도록 설계되어야 한다. 품질속성 기반 아키텍처 설계 방법과 아키텍처 설계 산출물에서의 일관성을 위한 활동을 규정한 표준에도 불구하고 설계 과정에서 이를 실현하기 위한 구체적인 기법에 대한 제시가 없었다. 따라서 실제 설계 과정에서는 아키텍처 뷰들 간에 불일치 요소가 발생하며 특히 품질속성에 대한 일관성이 깨짐으로 재작업 발생과 시스템 품질 저하의 문제점이 나타나고 있다. 본 논문에서는 뷰 설계 산출물에 품질속성을 명시하고 뷰 품질속성 테이블을 활용함으로 아키텍처 설계에서 품질속성에 대한 일관성을 유지할 수 있는 기법을 제시한다. 제시된 기법은 품질속성에 대한 일관성을 유지함으로서 불일치성으로 인한 재작업 방지와 고품질의 소프트웨어 시스템 개발을 가능하게 한다.

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

• 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 the Korea Academia-Industrial cooperation Society
• /
• v.11 no.12
• /
• pp.5072-5082
• /
• 2010

The Paper describes the methodology for Software Architecture Design. The key idea is to find the interfaces between the actors, modules, and communicating entities, and use them to identify the software design elements. The identified interfaces and modules are further used to find new modules and interfaces until the every design elements are found and located in the software architecture. This method starts the architecture design with finding the interfaces and enables the natural design procedure by relating the cause and results of the design. It also makes use of not only 5 architectural views for analysis and design of the software, but also concept of architecture patterns in design procedure. Especially, this method is also useful for the novice of the software architecture design.

• Journal of the Korea Institute of Information and Communication Engineering
• /
• v.21 no.11
• /
• pp.2153-2166
• /
• 2017

Web apps have a problem that they cause same data to be repetitively retrieved, processed, and displayed when web browsers load different web pages. To resolve the problem, this paper presents and evaluates a new method for restructuring of Java web apps. This approach dynamically analyzes Java web apps from the MVC (Model-View-Controller) architecture point of view and identifies redundant data by using the composite view pattern. Then the input apps are restructured in order not to load the redundant data when users make requests for new pages. This restructuring generates new web apps that conform to the MVC architecture and improve the performance of input web apps. The experimental results showed that when compared to legacy web apps, the restructured apps' response time was reduced on desktop PCs and mobile devices by 38% and 55%, respectively. In addition, case studies using open-source web apps showed the applicability of the proposed approach.

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