||Due to the fact that the environment which business confront is very dynamic, so the business require the software to reduce the response time, provide the high quality, and supply the flexible modeling process and high maintainability. In order to meet the requirement, a new software solution is emerged. Component-based software engineering is a method to integrate existed component to produce faster speed, lower cost and higher quality software. And it is concerned with the rapid assembly of systems from components where components and frameworks have certified properties; and these certified properties provide the basis for predicting the properties of systems built from components. Therefore, component based software engineering replace the position belong to traditional software engineering progressively, it become the next generation software engineering paradigm.|
Because businesses want to transform their requirement to be final components, so the component-based software engineering must have component modeling methodology in the system analysis stage. For this reason, the advantage and disadvantage of the component modeling methodology makes a very deep influence on component-based software engineering. And after the survey we made, we discover the greater parts of the existed component modeling methodology have a lot of defects, for example: the modeling method stay at abstract level, lack of clear and definite modeling rules, short of consistence of process document and can’t meet the good component modeling characteristics. Fortunately, in our surveyed methodology, we discover the “UML Component” is a component modeling methodology which can meet the good component modeling characteristics and have the develop potential.
But the “UML Component” methodology still has some problem, for example: lack of explicit component identify rules, complete tools support and simply modeling process. Due to these reasons, our study provides three solutions to refine and extend the “UML Components” methodology. First of all, we utilize the use case identify method by [吳仁和2002]、the concept of “Fan-in and Fan-out” by [Marquis2002] and the use case association transform method to refine the problem of component modeling rules. Secondly, we employ data glossary, data relation matrix and operation reference matrix to improve the problem of component modeling tools. Finally, we redesign the process model which includes four stages as follows, requirement acquisition, component identification, component interaction and component specification to resolve the irrational parts of original modeling process.
With this refined methodology, the system analysts can follow the stand modeling rules and process. In the other hand, the system developer also can develop the system which meet the business requirement exactly, ensure the component quality and speed up the software develop rate.
[Bachman2000] Bachman, F., Bass, L., Buhman, C., Comella-Dorda, S., Long, F., Robert, J., Seacord, R., Wallnau, K.,” Volume II: Technical Concepts of Component-Based Software Engineering”, at URL: http://www.sei.cmu.edu/pub/documents/00.reports/pdf/00tr008.pdf, 2000
[Barn98] Barn, B, Brown, A., W., “Methods and Tools for Component Based Development”, Technology of Object-Oriented Languages and Systems, August 1998
[Bergner99] Bergner, K., Rausch, A., Sihling, M., Vilbig, A., “Componentware - Methodology and Process”, The 21st International Conference on Software Engineering, 1999
[Booch94] Booch, G., Object-Oriented Analysis and Design-With Applications, Addison-Wesley, USA, 1994
[Chessman2001] Chessman, J., Daniels, J., UML Components, Addison-Wesley, Boston, 2001
[D’Souza99] D'Souza, D., Wills, A. C., Catalysis: Objects, Frameworks, and Components in UML, Addison-Wesley, Boston, 1999
[Ganesan2001] Ganesan, R., Sengupta, S., “O2BC: a Technique for the Design of Component-Based Applications”, Proc. 39th International Conference and Exhibition on Technology of Object-Oriented Languages and Systems, Santa Barbara, USA, 2001
[Hallsteinsen99] Hallsteinsen, S., Skylstad, G., “The Magma approach to CBSE”, The 21st International Conference on Software Engineering, May 1999
[Heineman2001] Heineman, G., T., Councill, W., T., Component-Based Software Engineering-Putting the Pieces Together, Addison-Wesley, USA, 2001
[Sang99] Sang, D., L., Young, J., Y., Eun, S., C., Soo, D., K., Sung, Y., R., “COMO: A UML-Based Component Development Methodology”, Proc. 6th Asia Pacific Software Engineering Conference, Japan, December 1999
[Veryard98a] Veryard, R., “SCIPIO: Aims, Principles and Structure”, SCIPIO Consortium, April 1998
[Veryard98b] Veryard, R., “SCIPIO: Effective management of component-based system project”, SCIPIO Consortium, November 1998
[Marquis2002] Marquis, G., P., “Application of traditional system design techniques to web site design”, Information and Software Technology, Vol. 44, No. 9, pp.507–512, 2002
[Flowler99] Fowler, M., Scott, K., UML Distilled Second Edition, Addison-Wesley , Boston, 1999
[Kwon99] Kwon, O. C., Yoon, S. J., Shin, G. S., “Component-Based Development Environment: An Integrated Model of Object-Oriented Techniques and Other Technologies”, The 21st International Conference on Software Engineering, Los Angeles, USA, 1999
[Warmer99] Warmer, J., Kleppe, A., The Object Constraint Language-Precise Modeling with UML, Addison-Wesley, 1999