• ETRI Journal
• /
• v.29 no.4
• /
• pp.477-488
• /
• 2007

In recent years, numerous studies have identified and explored issues related to web-service-oriented business process specifications, such as business process execution language (BPEL). In particular, business rules are an important cross-cutting concern that should be distinguished from business process instances. In this paper, we present a rule-based aspect oriented programming (AOP) framework where business rule aspects contained in business processes can be effectively separated and executed. This is achieved by using a mechanism of the business rule itself at the business rule engine instead of using existing programming language-based AOP technologies. Through some illustrative examples, this work also introduces a method by which business rule aspects, separated through an external rule engine, can be represented and evaluated. We also demonstrate how they can be dynamically woven and executed by providing an implementation example which uses two open-source-based products, the Mandarax rules engine and Bexee BPEL engine.

• The KIPS Transactions:PartD
• /
• v.17D no.6
• /
• pp.405-414
• /
• 2010

A rule is defined as a case to determine the target values according to combination of various Business factors. The information system is used to represent enterprise's business, which includes and implements the amount of these rules to Rule-Based System. A Rule-Based System can be constructed by using the rules engine method or Relational Database technology. Because the rules engine method has some disadvantages, the Rule-Based System is mostly developed with Relational Database technology. When business scales become larger and more complex, a large number of various rule cases must be operated in system, and processing these rule cases requires additional time, overhead and storage space, and the speed of execution slows down. To solve these problems, we propose a simplification algorithm that converts a large amount of rule cases to simplification rule cases with same effects. The proposed algorithm is applied to hypothetical business rule data and a large number of simplification experiments and tests are conducted. The final results proved that the number of rows can be reduced to some extent. The proposed algorithm can be used to simplify business rule data for improving performance of the Rule-Based System implemented with the Relational Database.

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.16 no.1
• /
• pp.735-743
• /
• 2015

The service oriented architecture assures flexibility of enterprise application development, so it supports agile reaction to business change. On the other hand, considerable effort is needed to develop a service by combining business and constraint consumes because the entire combination logic should be changed according to the change in business rule. To improve the current method, this paper applied an aspect oriented approach to service system development. In this paper, the rule concern is proposed in addition to the core concern and cross cutting concern of aspect oriented approach. The rule concern is extracted from business rules included in the business processes and services. The rule concern is classified into the process rule aspect and service rule aspect according to the level of the rule. In the proposed approach, system is modularized into the core concern, cross cutting concern and rule concern through separation of concern, and they are maintained independently. Therefore, the adaptability, reusability, and maintainability of a service system will be enhanced.

• Journal of information and communication convergence engineering
• /
• v.8 no.1
• /
• pp.89-94
• /
• 2010

The most important of rule-base system is the knowledge base that determines the power of rule-base system. The important form of this knowledge is how to descript kinds of rules. The Rule-Base System (RBS) has been using in many field that need reflect quickly change of business rules in management system. As far, when develop the Rule-Based System, we must make a rule engine with a general language. There are three disadvantage of in this developed method. First, while there are many data that must be processed in the system, the speed of processing data will become very slow so that we cannot accept it. Second, we cannot change the current system to make it adaptive to changes of business rules as quickly as possible. Third, large data make the rule engine become very complex. Therefore, in this paper, we propose the two important methods of raising efficiency of Rule-Base System. The first method refers to using the Relational database technology to process the rules of the Rule-Base System, the second method refers to a algorithm of according to Quine McCluskey formula compress the rows of rule table. Because the expressive languages of rule are still remaining many problems, we will introduce a new expressive language, which is Rule-Base Data Model short as RBDM in this paper.

• Proceedings of the Korea Inteligent Information System Society Conference
• /
• 2007.11a
• /
• pp.362-366
• /
• 2007

최근 기업 경영활동의 의사결정시 사용되는 비즈니스 룰(Business Rule)을 정형화하고 하나의 시스템으로 구축하여 효과적으로 기업의 경쟁력을 제고하기 위한 노력이 다양하게 시도되고 있다. 비즈니스 룰 시스템 구축 작업의 경우 기업 내부에 비정형적으로 존재하는 비즈니스 룰을 체계적으로 관리하기 위해 BRMS(Business Rule Management System)와 같은 전문 관리 도구를 도입하나, 대부분의 경우 비즈니스 룰 리포지토리(Repository)를 단순히 기능별 혹은 업무별로 구성함으로 인해 동일한 내용의 룰이 서로 다른 룰 리포지토리에 중복 존재하게 되는 등 구조상의 문제점을 발생시킨다. 이로 인해 각 어플리케이션 간의 룰 또는 룰 세트(Rule Set) 공유 관계가 수동 관리되거나 중복 룰의 수정으로 인한 룰 세트별 버전 관리 문제 등 비즈니스 룰 리포지토리 운영의 어려움에 봉착하게 된다. 본 연구에서는 금융보험사의 룰웨어하우스 구축 사례를 통해 다양한 어플리케이션에서 참조되는 전사 수준의 비즈니스 룰 관리 아키텍처 구성 방법 및 각 방법이 지닌 장단점에 대해 분석한다. 본 연구의 결과를 토대로 다양한 어플리케이션에서 참조되고 수시로 변경되는 전사 수준의 통합 비즈니스 룰 관리 시스템 구축 방안에 대한 연구가 활성화되기를 기대한다.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2010.04a
• /
• pp.852-855
• /
• 2010

Tree type of Rule Case will be processed by the method that provide practical Rule Case to Rule Engine that is made with procedural language beforehand, then the Rule Engine according to the condition of the special Rule Case to return result in current Rule-Based System. There are two disadvantages in the method; the first is according to specific business rule after construct the Rule Engine when the business rule changing the Rule Engine also must be changed. The second is when Rule have many conditions the Rule Engine will become very complex and the speed of processing Rule Case will become very slow. In this paper, we will propose a simplified algorithm that according to the theory of ID Tree to produce Rules which be used in Rule-Based System. The algorithm can not only produce Rules but also make sure of satisfying change of business rule by execute the algorithm. Because it is not necessary to make a Rule Engine, we will anticipate effect of increasing speed and reducing cost from Rule-Based System of applying the algorithm.

• Journal of Information Technology Applications and Management
• /
• v.9 no.3
• /
• pp.13-30
• /
• 2002

ebXML (Electronic Business using extensible Markup language), sponsored by UN/CEFACT and OASIS, is a modular suite of specifications that enables enterprises of any size and in any geographical location to conduct business over the Internet. Using ebXML, companies now have a standard method to exchange business messages, conduct trading relationships, communicate data In common terms and define and resistor business processes. It is the mission of ebXML that provides an open XML-based infrastructure enabling the global use of electronic business information in an interoperable, secure and consistent manner by all parties for creating a single e1ectronic electronic market. This paper briefly overviews the concept of core component, context, assembly rule and context rule. Then, It designs by standard specifications of ebXML core component commonly used in an industry and among industries, and assembles business messages by using XML schema. Therefore, it suggests the mechanism which effectively exchanges business messages among the trading partners. This paper designs core component by using only three business messages of retail industry : orders, dispatch report, sales report.

• Journal of Korean Institute of Industrial Engineers
• /
• v.39 no.1
• /
• pp.10-19
• /
• 2013

Dispatching rule plays an important role in a hybrid flow shop. Finding the appropriate dispatching rule becomes more challenging when there are multiple criteria, uncertain demands, and dynamic manufacturing environment. Using a single dispatching rule for the whole shop or a set of rules based on a single criterion is not sufficient. Therefore, a multi-criteria decision making technique using 'the order preference by similarity to ideal solution' (TOPSIS) and 'analytic hierarchy process' (AHP) is presented. The proposed technique is aimed to find the most suitable set of dispatching rules under different manufacturing scenarios. A simulation based case study on a PCB manufacturing process is presented to illustrate the procedure and effectiveness of the proposed methodology.

• Proceedings of the Korea Database Society Conference
• /
• 2010.06a
• /
• pp.99-107
• /
• 2010

BSC(Balanced Scorecard)는 재무적 성과지표의 한계를 지양하고 고객관점, 내부 프로세스 관점, 학습과 성장 관점, 재무 관점의 다양한 관점에서 성과측정시스템으로 상용 될 수 있을 뿐만 아니라 전략의 해석, 전략적 캐스케이딩(cascading), 전략적 자원분배, 전략적 학습도구를 위한 전략관리시스템으로 또한 의사소통도구로서 사용된다. 분 논문에서는 대학내의 학과들이 각각 개별적인 특성이 존재하고 학과의 제한된 자원과 역량하에서의 효율적인 운영과 이에 대한 조직적인 접근방법이 필요하기 때문에 학과조직에 BSC를 적용하는 방안을 모색하였다. 이러한 학과 BSC는 대학 전체 또는 그 상위조직의 BSC를 위한 토대로 이용될 수 있을 뿐만 아니라 교육에 관련한 다양한 인증 및 평가와 연계할 수 있을 것이다. 또한 본 논문에서는 최소한의 프로그래밍과 이해하기 용이한 수행규칙, 그리고 유연한 개정을 위하여 비즈니스 규칙(Business Rule)으로 이루어지는 BRMS(Business Rule Management System)로 학과 BSC를 설계할 수 있는 방안을 모색하였다.

• The Journal of Asian Finance, Economics and Business
• /
• v.6 no.4
• /
• pp.297-307
• /
• 2019

Despite the fact that the implementation of 5% rule is widely recognized to enhance the transparency of capital market and fairness of corporate governance market, a few evidences present information effect of 5% rule. Using 7,088 non-financial firm-year observations listed on the Korea Stock Exchange from 2006 to 2012, we analyze the relation between trading volume and 5% rule disclosure. The results show that the daily and abnormal trading volume is increased when 5% rule disclosure is released. Moreover, the trading volume is significantly increased during cooling period. Specifically, trading volume is significantly greater when one day before cooling period or the expiration day of cooling period. We also find the information effect of firms with stable ownership structure before 5% rule disclosure is relatively smaller than the firms with unstable ownership structure with unstable ownership structure. These results imply that capital market participants use the information from 5% rule disclosure and reflect in their real economic decision.