Open AccessJournal Article
Software Architecture and Component-Based Development
1
TL;DR: It is argued that the full benefit of component interoperability models can only be achieved if complemented by explicit architectural models.
read more
Abstract: In theory, software architecture (SA) and component-based development make an ideal match. On the other hand, SA seems a natural complement for reusable software components. We argue that the full benefit of component interoperability models can only be achieved if complemented by explicit architectural models. Firstly outline a set of driving factors in selecting an approach to engineering and evolving large, complex, distributed applications. Then discuss the requirements of SA and component supporting for each other. Lastly explore the possible ways of combining SA and component-based development.
read more
Chat with Paper
AI Agents for this Paper
Find similar papers on Google Scholar, PubMed and Arxiv
Write a critical review of this paper
Analyze citations of this paper to find unaddressed research gaps
Citations
Toward Exception Handling Infrastructures for Component-Based Software
Chrysanthos Dellarocas
- 01 Jan 2000
TL;DR: This paper argues that component-based software development introduces additional sources of risk because (i) independently developed components cannot be fully trusted to conform to their published specifications and (ii) very often, software failures are caused by systemic patterns of interaction that cannot be localized to any individual component.
References
Toward Exception Handling Infrastructures for Component-Based Software
Chrysanthos Dellarocas
- 01 Jan 2000
TL;DR: This paper argues that component-based software development introduces additional sources of risk because (i) independently developed components cannot be fully trusted to conform to their published specifications and (ii) very often, software failures are caused by systemic patterns of interaction that cannot be localized to any individual component.