• Proceedings of the Korean Society of Broadcast Engineers Conference
• /
• 2022.11a
• /
• pp.119-122
• /
• 2022

연합학습은, 데이터 샘플을 보유하는 다수의 분산 에지 디바이스 또는 서버들이 원본 데이터를 공유하지 않고 기계학습 문제를 해결하기 위해 협력하는 기술로서, 각 클라이언트는 소유한 원본 데이터를 로컬모델 학습에만 사용함으로써, 데이터 소유자의 프라이버시를 보호하고, 데이터 소유 및 활용의 파편화 문제를 해결할 수 있다. 연합학습을 위해서는 통계적 이질성 및 시스템적 이질성 문제 해결이 필수적이며, 인공지능 모델 정확도와 시스템 성능을 향상하기 위한 다양한 연구가 진행되고 있다. 최근, 중앙서버 의존형 연합학습의 문제점을 극복하고, 데이터 무결성 및 추적성과 데이터 소유자 및 연합학습 참여자에게 보상을 효과적으로 제공하기 위한, 블록체인 융합 연합학습기술이 주목받고 있다. 본 연구에서는 이더리움 기반 블록체인 인프라와 호환되는 연합학습 레퍼런스 아키텍처를 정의 및 구현하고, 해당 아키텍처의 실용성과 확장성을 검증하기 위하여 대표적인 연합학습 알고리즘과 데이터셋에 대한 실험을 수행하였다.

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

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

• The Journal of Society for e-Business Studies
• /
• v.13 no.4
• /
• pp.93-110
• /
• 2008

Reference modeling for Collaborative Networked Organizations(CNOs) has just started, and Enterprise Architecture Modeling Languages(EAMLs) for CNOs are very few. Lack of reference models makes it difficult for people to communicate with each other and lack of EAMLs also makes it difficult to implement information systems for CNOs. We propose an EAML for CNO called CAML. It supports (1) multi-level modeling based on Model- Driven Architecture of OMG's for expressive power and efficiency of implementations, and (2) multi-focus modeling based on Zachman Framework for completeness of modeling The effectiveness of the CAML is investigated through modeling of a supply chain and execution of change impact analysis.

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

• The KIPS Transactions:PartD
• /
• v.13D no.6 s.109
• /
• pp.807-814
• /
• 2006

Along with the enlargement of application scope, the growth of requirements complexity, and the fast development of product for embedded system, lots of industries developing embedded software try to evolve their traditional development environment into the new paradigm such as product line engineering approach. In order to sufficiently support the evolution, software architecture is essentially required to develop the embedded software. In this paper, we propose a tool, named TToSA which translates the conventional software models to software architecture models. Our TToSA is developed with the critical implication about that an industry can approach toward the new development paradigm without the big change of the existing software development method.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2011.11a
• /
• pp.1372-1375
• /
• 2011

프로덕트 라인 공학에서 프로덕트 라인 아키텍처는 가장 중요한 산출물 중에 하나이다. UML (Unified Modeling Language) 2.x 부터는 아키텍처를 모델링하기 위한 유용한 모델링 요소를 제공하고 있다. 이러한 UML을 이용하여 프로덕트 라인 아키텍처를 모델링하기 위해서는 가변성의 표현이 명시적으로 이루어져야 하지만, UML 자체에는 가변성을 표현하기 위한 방법 및 기법을 명시적으로 기술하고 있지 않다. 본 논문에서는 UML에서 제공하는 확장 메커니즘을 이용하여 가변성을 표현하는 방법을 제안한다. 즉, 모델링요소에 태그값(Tagged Value) 및 스테레오타입을 넣어주어 다양한 관점에서의 가변성을 표기하는 방법을 제안한다.

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

• Journal of Internet Computing and Services
• /
• v.6 no.4
• /
• pp.9-20
• /
• 2005

To design a software system in success, architectural approaches which are in basis of architectural design, must be primarily selected. What to chose among various architecture styles as specific as architectural approaches, varies along with the system status of what kind of functional or non-functional quality requirements should satisfy. In this study, we propose the evaluation model for making a selection of architectural approaches, and select an architectural approach for message system actively using in diversified internet utilization and enterprise application integration, In other words, if there may be possibly existed several architectural approaches, we present the most suitable method of architectural approach out of them through an evaluation of analyzing the system requirements satisfaction level. In addition, when it performs specific design and implementation utilizing design patterns based on thread, developers would be able to link up the architecture design directly.

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