Component software: beyond object-oriented programming
Component software: beyond object-oriented programming
Investigating and improving a COTS-based software development
Proceedings of the 22nd international conference on Software engineering
Business components: a case study of bankers trust Australia limited
Communications of the ACM
Business Modelling for Component Systems with UML
EDOC '02 Proceedings of the 6th International Enterprise Distributed Object Computing Conference
Business Component Framework and Modeling Method for Component-Based Application Architecture
EDOC '00 Proceedings of the 4th International conference on Enterprise Distributed Object Computing
Hi-index | 0.00 |
In this paper we present how to use rule for manipulating the variability of a business. We can classify the business component as business domain components and business process components. The most important thing to design the component, designer should identify the variability among the same business components. If we put the variability into the components, we should modify those components whenever we reuse that. It is not easy to modify the component since the user of that component might not be same with the writer. We extend component property to business rules. We define the component property to customize the component execution environment. Like this, we can define the difference business strategy in rules. With our rule engine, the component can use the rule during the component execution time so that the user of component can redefine or rewrite the rules according to their business context. Based on this approach, the reusability of component is improved. In this paper we describe new component architecture including rule component, our rule engine and case study.