Abstract
The progression of component-based software engineering (CBSE) is essential to the rapid, cost-effective development of complex software systems. Given the choice of well-tested components, CBSE affords reusability and increases reliability. However, applications developed according to this practice can often suffer from difficult maintenance and control, problems that stem from improper or inadequate integration solutions. Avoiding such unfortunate results requires knowledge of what causes the interoperability problems in the first place. The time for this assessment is during application design. In this paper, we define problematic architecture interactions using a simple notation with extendable properties. Furthermore, we delineate a multi-phase process for pre-integration analysis that relies on this notation. Through this effort, potential problematic architecture interactions can be illuminated and used to form the initial requirements of an integration architecture.
| Original language | English (US) |
|---|---|
| Pages | 132-141 |
| Number of pages | 10 |
| DOIs | |
| State | Published - 2001 |
| Externally published | Yes |
| Event | 8th Eiropean Engineering Conference (ESEC) and 9th ACM SIGSOFT Symposium on the Foundations of Software Engineering (FSE-9) - Vienna, Austria Duration: Sep 10 2001 → Sep 14 2001 |
Conference
| Conference | 8th Eiropean Engineering Conference (ESEC) and 9th ACM SIGSOFT Symposium on the Foundations of Software Engineering (FSE-9) |
|---|---|
| Country/Territory | Austria |
| City | Vienna |
| Period | 9/10/01 → 9/14/01 |
All Science Journal Classification (ASJC) codes
- General Computer Science
Keywords
- Architecture analysis
- Interoperability
- Software architecture
Fingerprint
Dive into the research topics of 'A notation for problematic architecture interactions'. Together they form a unique fingerprint.Cite this
- APA
- Author
- BIBTEX
- Harvard
- Standard
- RIS
- Vancouver