Description Technique for Component Composition Focusing on Black-Box View
As component-based software is developed by integrating components that are implemented independently, expressing the usage protocols of each component is essential. However, there is no known proper way to describe them comprehensibly from the point of component user or developer. Black-box (exter-nal) point of view of component composition sees component-based development from the user’s or the system assembler’s point of view. But a description technique necessary to specify the dynamic constraint explicitly is necessary to define the external view more precisely. The key contribution of this paper is to present a technique for describing the structure of components in black-box view using UML 2.0. First, we present the relevant UML notations for describing the black-box point of view and then provide diagrams showing their usage. We further illustrate how this leads to a component based software specification of the structure of composition focusing on the black-box view.
KeywordsStructure Diagram Component Composition Description Technique External View Require Interface
Unable to display preview. Download preview PDF.
- 1.Selic, B.: What’s New in UML 2.0? IBM Rational Software (2005) Google Scholar
- 2.Jifeng, H., Liu, Z., Xiaoshan, L.: Contract-Oriented Component Software Development. Technical Report 276, UNU-IIST, POBox 3058, Macau (April 2003)Google Scholar
- 3.UML Modeling Language: Superstructure, Ver 2.0 (August 2005) Google Scholar
- 5.Beubnard, A., Jezequel, J., Plouzeau, N., Watkins, D.: Making Components Contracts Aware. Computer (July 1999)Google Scholar
- 6.Jubin, H., Friedrichs, J.: The Jalapeno Team: Enterprise JavaBeans by Example, pp. 141–191. Prentice Hall PTR, Englewood Cliffs (1999)Google Scholar
- 7.Ivers, J., Clements, P., Garlan, D., Nord, R., Schmerl, B., Silva, J.: Documenting Component and Connector Views with UML 2.0. Technical Report CMU/SEI-2004-TR-008 ESC-TR-2004-008 (2004)Google Scholar
- 8.Mayer, B.: Applying Design by Contract. IEEE Computer 25(10), 40–51 (1992)Google Scholar