Rule based Component Development Technique and Case study


KIPS Transactions on Software and Data Engineering, Vol. 12, No. 2, pp. 275-282, Feb. 2005
10.3745/KIPSTD.2005.12.2.275, Full Text:

Abstract

In order to increase extendibility and reusability of components during component design, the variability discovered in a business application development needs to be defined to separate rules. That is because component adaptation techniques through redefinition of implementation classes and interface wrapping have limits to support the component reusability. Therefore, It's essential to design the component which takes into account the future reusability in the component development. In this paper, we extended the existing component architecture to incorporate rule components by separating variable properties from the components and defined the necessary syntax for the rule definition. In the case study, we built the business components for an insurance sales application and verified the component reusability through the rule redefinition.


Statistics
Show / Hide Statistics

Statistics (Cumulative Counts from September 1st, 2017)
Multiple requests among the same browser session are counted as one view.
If you mouse over a chart, the values of data points will be shown.


Cite this article
[IEEE Style]
J. A. Kim, S. M. Hwang and Y. T. Jin, "Rule based Component Development Technique and Case study," KIPS Journal D (2001 ~ 2012) , vol. 12, no. 2, pp. 275-282, 2005. DOI: 10.3745/KIPSTD.2005.12.2.275.

[ACM Style]
Jeong Ah Kim, Sun Myung Hwang, and Young Taek Jin. 2005. Rule based Component Development Technique and Case study. KIPS Journal D (2001 ~ 2012) , 12, 2, (2005), 275-282. DOI: 10.3745/KIPSTD.2005.12.2.275.