• Journal of Information Technology Services
• /
• v.10 no.2
• /
• pp.223-234
• /
• 2011

Loosely coupled properties of SOA(Service Oriented Architecture) services do not guarantee that service applications always work properly. Service errors may also influence other services of SOA. These characteristics adversely affect software reliability. Therefore, it is a challenge to effectively manage system change and errors for operating services normally. In this study, we propose a SOA based framework using AOP(Aspect Oriented Programming) for reliable service applications. AOP provides a way to manipulate cross-cutting concerns such as logging, security and reliability and these concerns can be added to applications through weaving process. We define a service specification and an aspect specification for this framework. This framework also includes service provider, requester, repository, platform, manager, and aspect weaver to handle changes and exceptions of applications. Independent Exception Handler is stored to exhibited external Aspect Service Repository. When exception happened, Exception Handler is linked dynamically according to aspect rule that is defined in aspect specification and offer function that handle exception alternate suitable service in systematic error situation. By separating cross-cutting concerns independently, we expect that developer can concentrate on core service implementation and reusability, understanding, maintainability increase. Finally, we have implemented a prototype system to demonstrate the feasibility of our framework in case study.

• Journal of KIISE:Software and Applications
• /
• v.34 no.9
• /
• pp.773-784
• /
• 2007

Aspect-Oriented Programming (AOP) has focused on improving the modularity of the crosscutting concerns. The existing AOP methodology has been mainly focused on the implementation method of programs and thus developer-oriented concern extraction and development were performed. Recently, many studies for applying AOP to the entire software development processes ranging from requirement analysis to design and implementation are being conducted. But specification methods having consistency from the initial phase of concern extraction to implementation phase are not sufficient. In this paper, we have presented the specification of crosscutting concerns so as to solve these problems. The specification of crosscutting concerns provides guidelines and specification from the requirement analysis phase to the process of converting extracted crosscutting concerns to codes. This method reduces the gap to the process of mapping extracted crosscutting concerns into a single class and thus enhances program development and understandability. In addition, it raises program reusability, maintenance and extensibility by enhancing traceability.

• The KIPS Transactions:PartD
• /
• v.15D no.5
• /
• pp.669-680
• /
• 2008

There are various studies about AOP(Aspect-Oriented Programming) which modularizes cross-cutting concerns like logging and security effectively. But, we need to utilize techniques which specify the information of aspects modularizing cross-cutting concerns and detailed join information between aspects and targets. We propose a specification technique for aspects which focuses on clarifying the join information between aspects and targets. The technique includes the activities of specifying aspects, defining priority, specifying join information, and specifying pointcuts. We describe the join matrix which represents relationships of aspects and targets and the pointcut specification which is made by analyzing the commonality of join points. The proposed specification technique supports detailed information of the aspects and the join information between aspects and targets so that we can use detailed information to implement aspects.

• Journal of KIISE:Information Networking
• /
• v.37 no.1
• /
• pp.8-15
• /
• 2010

In this study, we present an extended complex event model by considering both of the complex event and the aspect-oriented programming. We propose an advanced scheme for the event specification suited for the event correlation based network management systems by merging these two models. Specifically, we extend the model to support hierarchical event structures and let the model recognize point-cuts of aspect-oriented programming as events. We provide the event operators designed to specify the events on instances and handle temporal relations of the instances. Lastly, we compare the proposed model with other event models and present the benefits of it.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2005.11a
• /
• pp.405-408
• /
• 2005

현재 컴포넌트 기반 소프트웨어 엔지니어링의 접근은 소프트웨어 컴포넌트 인터페이스 디자인과 실행에 중심을 둔 경향이다. 컴포넌트 기반 소프트웨어 개발을 하기 위하여, 전체 시스템을 분석하는 것은 복잡하고, 이해하기 어렵다. 이를 위하여 aspect 기반 컴포넌트 개발방법을 도입한다. Aspect 기반 개발에서는 필요로 하는 컴포넌트를 표현하기 위하여 provide 와 require 를 사용한다. 또한 Aspect 기반 컴포넌트 엔지니어링을 위하여 컴포넌트 사이의 provide/require 서비스에 대한 분류와 추론을 위하여 다른 컴포넌트와 함께 이용할 수 있는 방법을 제안한다. 이 방법은 개발자들은 전체 시스템 개발을 위해 필요로 하는 적합한 컴포넌트의 provide/require 을 사용하여 접근하기 때문에 컴포넌트 검색, 합성, 재사용에 도움을 줄 수 있다. 컴포넌트 aspect 정보의 확장을 위하여 XML 문서 포맷을 사용함으로써 서로 다른 환경에서도 사용할 수 있도록 명세 하였다.

• 한국IT서비스학회:학술대회논문집
• /
• 2002.11a
• /
• pp.444-450
• /
• 2002

실세계의 사물을 다중측면에 의하여 분석한 후 개체노드, 측면개체노드, 균일성 개체 및 다중화 추상화라는 여러 개념을 이용하여 디자인할 수 모델인 I-Farmer 모델의 구현 방안을 제시하였다. 컴포넌트는 컴포지션에 의한 소프트웨어 블록 재사용성을 제공하며 컴포넌트는 이들의 수행하는 기능에 대한 명세를 나타내는 인터페이스 명세 모델이 반드시 필요하게 된다. 본 논문에서는 I-Farmer 모델링 방법론에 의하여 디자인되어진 시스템을 컴포넌트 기반개발의 인터페이스 명세 모델로의 변형(transformation) 메카니즘인 ITI 알고리즘 및 CORBA / JAVA RMI COM IDL과의 상호관련성을 제시한다.

• Proceedings of the IEEK Conference
• /
• 2000.07a
• /
• pp.545-548
• /
• 2000

A fundamental tenet of CBD is that a component has a specification which describes what that component does, and how it behaves when its services are used. In general, the implementation may be written in a different programming language and execute on different technology platform, from the language and platform used by the client program. In order to implement practically the system that is designed by the Farmer model, there is need to have the ISM (Interface Specification Model) which explains specification about the functions of entities of the Farmer model, such as, entity node, aspect node and ILB/OLB. This paper suggests the transformation methodology from the concepts of the Farmer model to the mapping notions of the ISM. Also in reality, TMN agents system which is designed by the Farmer model is transformed to the ISM system design.

• Journal of the Korea Society for Simulation
• /
• v.18 no.3
• /
• pp.113-122
• /
• 2009

Software is getting more complex due to a variety of requirements that include desired functions and properties. Therefore, verifying and testing the software are complicated problems. Moreover, if the software is already implemented, inserting and deleting tracing/logging code into the source code may cause several problems, such as the code tangling and the code scattering problems. This paper proposes the Aspect DEVS Verification Framework which supports the verification and testing process. The Aspect DEVS Verification Framework utilizes Aspect Oriented Programming features to handle the code tangling and the code scattering problems. By applying aspect oriented features, a user can find and fix the inconsistency between requirement and implementation of a software without suffering the problems. The first step of the verification process is the building aspect code to make a software act as a generator. The second step is developing a requirement specification using DEVS diagrams and implementing it using the DEVSIM++. The final step is comparing the event traces from the software with the possible execution sequences from DEVS model.

• Journal of Digital Convergence
• /
• v.9 no.3
• /
• pp.213-223
• /
• 2011

Today, information resource management is key task in the data-centre as like as NCIA(National computing integration Agency of Korea). In IRM, the server's performance is one of the core elements, it must be importantly managed during whole of system life cycle. As first step of such management is in purchase phase, it is very important that the optimum specification is determined. The server's specification contains such as performance of core, criteria for performance verification, minimum cores, etc. There is constant controversy concerning the minimum cores. In this article, we present criteria for determination of the minimum cores that considered three aspects: (1) Costly aspect as TCO(Total Cost of Ownership, (2) Environmental aspect as Green IT (3) Technical aspect as RAS(Reliability, Availability, Serviceability) functionality. Finally, we propose scheme to ideally determinate the minimum cores.

• The KIPS Transactions:PartD
• /
• v.11D no.4
• /
• pp.929-936
• /
• 2004

A major limitation of available component-based platforms Is that they do not provide suitable means for describing and reasoning on the concurrent behaviour of interacting component-based system. Indeed while these platforms provide convenient ways to describe the typed signatures of components, e.g. like CORBA's IDL, they offer a quite low-level support to describe the concurrent behaviour of component. The ability to describe and verify the concurrent behaviour of interacting components is key aspect In the development of large component-based software system. This study propose a component interface specification using process algebra and configuration's role which allows one to prove correctness of software architecture generated at design level as well as to define compatibility relations by our evolution rule and $\pi$-graph. Also, we shown on an appropriateness of a specification techniques and definitions proposed in this paper by case-study.