Titlebook: Engineering Distributed Objects; Second International Wolfgang Emmerich,Stefan Tai Conference proceedings 2001 Springer-Verlag Berlin Heide

STH

书目名称Engineering Distributed Objects影响因子(影响力)




书目名称Engineering Distributed Objects影响因子(影响力)学科排名




书目名称Engineering Distributed Objects网络公开度




书目名称Engineering Distributed Objects网络公开度学科排名




书目名称Engineering Distributed Objects被引频次




书目名称Engineering Distributed Objects被引频次学科排名




书目名称Engineering Distributed Objects年度引用




书目名称Engineering Distributed Objects年度引用学科排名




书目名称Engineering Distributed Objects读者反馈




书目名称Engineering Distributed Objects读者反馈学科排名

光明正大

Intersect

A Key Technology Evaluation Case Study: Applying a New Middleware Architecture on the Enterprise Scair 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 ot

苦笑

glucagon

催眠

The Importance of Resource Management in Engineering Distributed Objectsd systems. However, more work still need to be done to develop methodologies for the construction of distributed objects. In addition, little attention has been paid to the development of methodologies for the configuration of computational resources among distributed objects. This paper introduces

催眠

Towards Designing Distributed Systems with ConDILsing distribution decisions in the system model based on the system’s context. Hence, UML is enriched by two new speci- fication techniques for planning distribution: On the one hand, ‘..’ describe dependencies on the design level between otherwise possibly unrelated model elements, which share the

龙卷风

门闩

Architectural Reflection Realising Software Architectures via Reflective Activities practical experience in industrial projects, in this pa- per we expand the approach and show a practical (albeit very simple) example ofa pplication of architectural reflection. The example shows how one can express, thanks to reflection, both functional and non-functional requirements in terms of

可憎