Foundations for the study of software architecture
ACM SIGSOFT Software Engineering Notes
Architectural mismatch or why it's hard to build systems out of existing parts
Proceedings of the 17th international conference on Software engineering
Formalizing style to understand descriptions of software architecture
ACM Transactions on Software Engineering and Methodology (TOSEM)
Software architecture: perspectives on an emerging discipline
Software architecture: perspectives on an emerging discipline
A formal basis for architectural connection
ACM Transactions on Software Engineering and Methodology (TOSEM)
Towards a taxonomy of architecture integration strategies
ISAW '98 Proceedings of the third international workshop on Software architecture
A language and environment for architecture-based software development and evolution
Proceedings of the 21st international conference on Software engineering
Software architecture classification for estimating the cost of COTS integration
Proceedings of the 21st international conference on Software engineering
The unified software development process
The unified software development process
Uncovering architectural mismatch in component behavior
Science of Computer Programming
Towards a taxonomy of software connectors
Proceedings of the 22nd international conference on Software engineering
How system architectures impede interoperability
Proceedings of the 2nd international workshop on Software and performance
Static checking of system behaviors using derived component assumptions
ACM Transactions on Software Engineering and Methodology (TOSEM)
The impact of component architectures on interoperability
Journal of Systems and Software
An Event-Based Architecture Definition Language
IEEE Transactions on Software Engineering
Specifying Distributed Software Architectures
Proceedings of the 5th European Software Engineering Conference
A Field Guide to Boxology: Preliminary Classification of Architectural Styles for Software Systems
COMPSAC '97 Proceedings of the 21st International Computer Software and Applications Conference
The MBASE Life Cycle Architecture Milestone Package
WICSA1 Proceedings of the TC2 First Working IFIP Conference on Software Architecture (WICSA1)
Acme: an architecture description interchange language
CASCON '97 Proceedings of the 1997 conference of the Centre for Advanced Studies on Collaborative research
An Event-Based Software Integration Framework
An Event-Based Software Integration Framework
Composing heterogeneous software architectures
Composing heterogeneous software architectures
Merging Integration Solutions for Architecture and Security Mismatch
ICCBSS '02 Proceedings of the First International Conference on COTS-Based Software Systems
Identifying Evolvability for Integration
ICCBSS '02 Proceedings of the First International Conference on COTS-Based Software Systems
Designing Secure Integration Architectures
ICCBSS '03 Proceedings of the Second International Conference on COTS-Based Software Systems
Classifying Interoperability Conflicts
ICCBSS '03 Proceedings of the Second International Conference on COTS-Based Software Systems
Patterns of conflict among software components
Journal of Systems and Software
Software systems in-house integration: Architecture, process practices, and strategy selection
Information and Software Technology
Semantic mediation modelling in the service component design
International Journal of Metadata, Semantics and Ontologies
An industry case study of micro component design and semantic mediation
International Journal of Metadata, Semantics and Ontologies
Hi-index | 0.00 |
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 integrate 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.