Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
Some patterns for software architectures
Pattern languages of program design 2
Pattern-oriented software architecture: a system of patterns
Pattern-oriented software architecture: a system of patterns
Software architecture in practice
Software architecture in practice
IEEE Software
Mastering the Middleware Muddle
IEEE Software
GCSE '00 Proceedings of the Second International Symposium on Generative and Component-Based Software Engineering-Revised Papers
Towards a Broader View on Software Architecture Analysis of Flexibility
APSEC '99 Proceedings of the Sixth Asia Pacific Software Engineering Conference
XOTcl: an object-oriented scripting language
TCLTK'00 Proceedings of the 7th conference on USENIX Tcl/Tk - Volume 7
CORBA: integrating diverse applications within distributed heterogeneous environments
IEEE Communications Magazine
Hi-index | 0.00 |
Decisions for key technologies, like middleware, for large scale projects are hard, because the impact and relevance of key technologies go beyond their core technological field. E.g., object-oriented middleware has its core in realizing distributed object calls. But choosing a technology and product also implies to adopt its services, tools, software architectures, object and component paradigms, etc. Moreover, legacy applications and several other key technologies have to be integrated. And since no middleware product serves all requirements in the enterprise context, various middleware products have to be integrated, too. Another key problem of middleware evaluation is, that often the studies have to be performed very early in a project. In this paper we try to tackle these problems and describe how we can communicate the outcomes - which come from a technical viewpoint - to the management and other non-experts in the technological field.