GeekArticles
Testing
Software Development
Testing
Software DevelopmentDimensions of Component - Based Development
As the properties of components have gradually become clearer, attention has started to turn to the architectural issues which govern their interaction and composition. In this paper the authors identify some of the major architectural questions affecting component-based software development and describe the predominant architectural dimensions. Of these, the most interesting is the "architecture hierarchy" which they believe is needed to address the "interface vicissitude" problem that arises whenever interaction refinement is explicitly documented within a component-based system. The authors present a solution to this problem based on the concept of stratified architectures and object metamorphosis Finally, they describe how these concepts may assist in increasing the tailorability of component-based frameworks. Author(s) : Colin Atkinson, Thomas Kühne and Christian Bunse
Sponsored Links
Related Topics
Subscribe via RSS
Software Development
- Article :: Pat O'Toole's Dos and Don'ts of Process Improvement: DON’T Expect a Miracle
- Article :: Pat O'Toole's Dos and Don'ts of Process Improvement: DON’T: Attend Industry Conferences
- Article :: How to Monitor Software Process Improvement
- Article :: Pat O'Toole's Dos and Don'ts of Process Improvement: Do Exit Staged, Right?
- Article :: Pat O'Toole's Dos and Don'ts of Process Improvement: Do Set the Stage for Continuous Improvement
- Article :: Management Role: Ensuring That Software Process Improvement Sticks
- Article :: Pat O'Toole's Dos and Don'ts of Process Improvement: Don’t Maintain a Low Profile
- Article :: Pat O'Toole's Dos and Don'ts of Process Improvement: Don't Carry Old Baggage on a New Journey
- Article :: Real Process Improvement: Getting What You Need
- Article :: Pat O'Toole's Dos and Don'ts of Process Improvement: DO Your Level Best To Stay Under the Threshold
