|
ABSTRACT
Component-based development (CBD) has gained in popularity in recent years due to its promise of building applications from reusable and plug-and-playable software components. An ultimate goal of CBD is making plug-and-playable software development not only feasible, but also easy. In order to achieve this goal, techniques for clearly specifying functionality of components and for determining the degree to which two components can interoperate are needed. In this paper, we briefly review the ICM (Interoperable Component Model), and enhance the model by adding a formalism and providing a testing framework based on the formal specification. Each component is accompanied with an interface that describes the component's type and behavior. The component interactions are specified in message protocols. With the specification model, we will define the behavior type conformance rules on components.
REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
 |
1
|
Andrew Black , Norman Hutchinson , Eric Jul , Henry Levy, Object structure in the Emerald system, Conference proceedings on Object-oriented programming systems, languages and applications, p.78-86, September 29-October 02, 1986, Portland, Oregon, United States
|
| |
2
|
|
| |
3
|
Il-Hyung Cho and John D. McGregor. Component specification and testing interoperation of components. In Proc. of the IASTED Int'l Conf., Software Engineering and Applications, pages 27--31, 1999.
|
| |
4
|
|
| |
5
|
Tsun S. Chow. Testing software design modeled by finite-state machines. IEEE Transactions on Software Engineering, 4(3):178--187, May 1978.
|
| |
6
|
|
| |
7
|
|
| |
8
|
|
 |
9
|
|
| |
10
|
Metamata, www.metamata.com/JavaCC/docs/index.html. JavaCC documentation, 1999.
|
| |
11
|
|
| |
12
|
|
 |
13
|
|
|