| Chris Luer and David S. Rosenblum. Wren---an environment for component-based development. In Proceedings of the 8th European software engineering conference held jointly with 9th ACM SIGSOFT international symposium on Foundations of software engineering, pages 207--217. ACM Press, 2001. |
....distinction into roles is explicit in component based systems [28, 20, 17] and in many modular programming languages [1, 33] Lastly, we can differentiate features and qualities according to their usage during or applicability to different stages in module lifecycle. Current practice and research [2, 28, 15, 16] leads to several such classes: development time for correct compilation, static or dynamic linking, and packaging (when e.g. component assemblies are created from individual pieces) design time for the integration (or assembly) stage of creating module interconnections in a visual tool and ....
Chris L uer and David S. Rosenblum. WREN---An Environment for Component-Based Development, 2001.
....[35] is also implemented as an extension to Emacs. It has a knowledge base of clichs that programmers can reuse. KBEmacs helps programmers who already knew the clich because programmers have to refer to it by name, whereas CodeBroker tries to give programmers access to unknown components. Wren [23] is a component based development environment that supports software developers in locating, evaluating, and incorporating components from several component distribution sites. It also stresses the importance of making use of selfrevealing information contained in components. However, no automated ....
Ler, C., and Rosenblum, D.S. Wren--An Environment for Component-Based Development, in Proceedings of the Joint ESEC-8 and FSE-9 (Vienna, Austria, 2001), 207-217.
No context found.
Chris Ler and David S. Rosenblum. Wren---An Environment for Component-Based Development. Software Engineering Notes, 26 (5), 2001. 207-217.
No context found.
Ler, C. and Rosenblum, D.S. Wren---An Environment for ComponentBased Development. Software Engineering Notes, 26 (5), 2001. 207-217.
....linking as used in Java avoids redundant copies of the same module in the scope of the file system. In a networked or distributed system, one may still have to cope with multiple copies at the various locations. It is possible, however, to extend dynamic linking to work on an Internet scale [5]. While the performance overhead becomes large, it can be reduced significantly through caching and event notification: the local system keeps a copy of the module, and is notified by the server that owns the original copy of the module whenever it is updated. In this way, the module has to be ....
....and other forms of self description. In the same way, components will be able to install themselves through the network. Complex applications composed out of independent components will be hard to maintain; dynamic linking on an Internet scale will automate most of the maintenance tasks. WREN [5] is a prototypical component based development environment developed by us that supports component selfdescription and Internet wide dynamic linking. WREN allows an application developer to search for components in remote repositories, select components, compose them into an application, and ....
Ler, C., and Rosenblum, D. S. Wren---An Environment for Component-Based Development. In Joint 8th European Software Engineering Conference (ESEC) and 9th ACM Sigsoft International Symposium on the Foundations of Software Engineering (FSE-9). Vienna, 2001, to appear.
No context found.
Chris Luer and David S. Rosenblum. Wren---an environment for component-based development. In Proceedings of the 8th European software engineering conference held jointly with 9th ACM SIGSOFT international symposium on Foundations of software engineering, pages 207--217. ACM Press, 2001.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC