Logical foundations of object-oriented and frame-based languages
Journal of the ACM (JACM)
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)
Software architecture classification for estimating the cost of COTS integration
Proceedings of the 21st international conference on Software engineering
Towards a taxonomy of software connectors
Proceedings of the 22nd international conference on Software engineering
The impact of component architectures on interoperability
Journal of Systems and Software
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
Classifying Interoperability Conflicts
ICCBSS '03 Proceedings of the Second International Conference on COTS-Based Software Systems
TRIPLE - A Query, Inference, and Transformation Language for the Semantic Web
ISWC '02 Proceedings of the First International Semantic Web Conference on The Semantic Web
Platform independent model transformation based on triple
Proceedings of the 5th ACM/IFIP/USENIX international conference on Middleware
Use cases for reasoning with metadata or what have web services to do with integrity constraints?
PPSWR'05 Proceedings of the Third international conference on Principles and Practice of Semantic Web Reasoning
Hi-index | 0.00 |
Component reuse is inhibited by two factors: Lack of an adequate modeling representation of components and lack of a method to predict properties of a composition of application components. In this paper, we propose a framework for conflict identification. The framework is primarily based on a taxonomy describing communication and technology related properties. Conflict identification is based on inference rules. Furthermore, we aim to integrate conflict reasoning in the software development process. We will show that the Unified Modeling Language and the Resource Description Framework can be combined to provide a solution to the representation problems, without resorting to extension mechanisms, and without limiting to a specific component platform. As a real life example, we model the connection of an .Net Serviced Component to an Enterprise Java Bean as part of a mortgage bank's enterprise architecture and prove its viability.