Browse > Article

A Two-Phase Component Identification Method using Static and Dynamic Relationship between Classes  

Choi Mi-Sook (우석대학교 컴퓨터공학과)
Cho Eun-Sook (동덕여자대학교 컴퓨터정보과학부)
Park Jai-Nyun (숙명여자대학교 정보과학부)
Ha Jong-Sung (우석대학교 컴퓨터공학과)
Abstract
It is difficult to identify reusable and independent components in component-based development(CBD) process. Therefore existing methodologies have dealt the problem of component identification based on only developer's intuition and heuristics. As a result, it is difficult to identify the business components by common developers. Therefore, in this paper, we propose a new baseline and technique to identify the business components based on domain model such as use case diagrams, class diagrams, and sequence diagrams. proposed method identifies components through two phases; system component identification and business component identification. Especially, we consider structural characteristics as well as dependency characteristics according to methods call types and directions in identifying components. We also present a case study and comparative analysis and assessment to prove the practical use of our technique.
Keywords
System Component; Business Component; Component Identification; Component Development Method;
Citations & Related Records
연도 인용수 순위
  • Reference
1 Ivar Jacobson, Grady Booch and James Rumbaugh, The Unified Software Development Process, Addison Wesley, 1999
2 S.R. Chidamber and C.F. Kemerer, A Metric Suite for Object-Oriented Design, IEEE Transactions on Software Engineering, vol. 17, No. 6, pp. 636-638, 1994   DOI   ScienceOn
3 Clemens Szyperski, Dominik Gruntz and Stephan Murer, Component Software: Beyond ObjectOriented Programming, 2nd Edition, AddisonWesley, 2002
4 George T. Heineman and William T. Council, Component Based Software Engineering : Putting the Pieces Together, Addison-Wesley, 2001
5 David C. Kung, Jerry Gao and Pei Hsia, Class Firewall, Test Order, and Regression Testing of Object-Oriented Programs, Journal of Object-Oriented Programming, pp. 51-65, 1995
6 Henderson-Sellers, Brian, Object-Oriented Metrics, Prentice-Hall, 1996
7 Jong Kook Lee, Seung Jae Jung and Soo Dong Kim, Component Identification Method with Coupling and Cohesion, Proceedings of Asia Pacific Software Engineering Conference, pp. 79-88, 2001   DOI
8 Eun Sook Cho, Soo Dong Kim and Sung Yul Rhew, A Domain Analysis and Modeling Methodology for Component Development, International Journal of Software Engineering and Knowledge Engineering, Vol.14, No.2, April, 2004
9 David C. Kung, Jerry. Gao, Pei Hsia, F. Wem, Y. Toyoshima and C. Chen, Change Impact Identification in Object Oriented Software Maintenance, Proceedings International Technical Conference on Ciecuit/Systems, Computers and Communications, 1999
10 Hyung Ho Kim and Doo Whan Bae, Component Identification via Concept Analysis, Journal of Object Oriented Programming, 2001
11 ETRI, 컴포넌트 개발방법론 마르미 III, Technical Report, 2002
12 John Cheesman and John Daniels, UML Components: A Simple Process for Specifying Component-Based Software, Addison-Wesley, 2001
13 Desmond Francis Dsouza and Alan Cameran wills, Objects, Component, and Frameworks with UML: the Catalysis approach, Addison Wesley, 1999
14 Compuware, About Unitace, http://www.compuware.com/products/uniface/about.htm, 2001
15 Computer Associates, COOL:Joe 2.0, http:/www.- cai.com/products/cool/joe/ cooljoe_pd.pdf, 2001