ACM Home Page
Please provide us with feedback. Feedback
Using resemblance to support component reuse and evolution
Full text PdfPdf (205 KB)
Source International Conference on Software Engineering archive
Proceedings of the 2006 conference on Specification and verification of component-based systems table of contents
Portland, Oregon
SESSION: Session 4 table of contents
Pages: 49 - 56  
Year of Publication: 2006
ISBN:1-59593-586-X
Authors
Andrew McVeigh  Imperial College, London, United Kingdom
Jeff Kramer  Imperial College, London, United Kingdom
Jeff Magee  Imperial College, London, United Kingdom
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 16,   Downloads (12 Months): 47,   Citation Count: 3
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1181195.1181206
What is a DOI?

ABSTRACT

The aim of a component-based approach to software is to allow the construction of a system by reusing and connecting together a number of existing components. To successfully reuse a component, alterations generally need to be made to it, particularly if the abstraction level is high. However, existing usage of a component means that it cannot be altered without affecting the systems that reuse it already. This leads to a dilemma which frustrates the goals of the compositional approach to reuse.To help resolve this dilemma, we introduce the resemblance construct, allowing a new component to be defined in terms of changes to a base component. This allows us to effectively alter a base component for reuse, without affecting the existing definition or any users of the component. We use an example to show how this and other constructs ameliorate the reuse problems of complex, possibly composite, 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
 
2
 
3
 
4
M. Goulo and F. Abreu. Bridging the gap between acme and uml 2.0 for cbd. In Specification and Verification of Component-Based Systems (SAVCBS 2003), pages -, 2003.
 
5
 
6
7
 
8
9
 
10
11
 
12
OMG. Uml 2.0 specification. Website, http://www.omg.org/technology/documents/formal/uml.htm, 2005.
13
 
14
B. Selic, G. Gullekson, and P. Ward. Inheritance. In Real-Time Object-Oriented Modeling, volume First, pages 255--285. Wiley, 1994.
 
15
16
17
18
 
19
R. van Ommering. Mechanisms for handling diversity in a product population. In ISAW-4: The Fourth International Software Architecture Workshop, 2000.
20


Collaborative Colleagues:
Andrew McVeigh: colleagues
Jeff Kramer: colleagues
Jeff Magee: colleagues