| C. Gerety. HP SoftBench: A new generation of software development. Technical Report SESD-89-25, Hewlett-Packard Software Engineering Systems Division, Ft. Collins, Col., Nov 1989. |
....variable that speci es the event that was red and dispatch the announcement to the appropriate handlers. Some existing event mechanisms allow automatic event de nition. Examples, of such systems include system in Windows, and tool integration frameworks such as Field [Rei90] and, SoftBench [Ger89] do this. Allowing for automatic events is necessary when using events to integrate components that do not support the desired event mechanism. In such cases, the output from these components can be used as events within the integration environment. Allowing for automatic events is also useful ....
C. Gerety. HP SoftBench: A new generation of software development. Technical Report SESD-89-25, Hewlett-Packard Software Engineering Systems Division, Ft. Collins, Col., Nov 1989.
....the construction of large scale and complex distributed software systems in general, and loosely coupled ones in particular [7, 22] In the P S style, components interact by subscribing to and publishing messages. Mechanisms to support the P S style are found in commercial toolkits (e. g, Softbench [8], ToolTalk [23] TIB Rendezvous [25] communication standards (e.g. Corba [5] integration frameworks (e.g. JavaBeans [11] and programming environments. As the requirements to P S systems are growing both with respect to performance and subscription semantics, a subgroup of the current ....
C. Gerety. HP Softbench: A new generation of software development tools. Technical Report SESD-89-25, Hewlett-Packard Software Engineering Systems Division, Fort Collins, Colorado, November 1989.
....first tool to possess knowledge of the second tool s data structures. Another approach is to invoke the required action in the second tool The concept of tools invoking operations in other tools has been used in message broadcast environments such as Field[Rei90] and its derivative HP SoftBench[Ger89] In simple message broadcast schemes such as Field there are a set of messages defined within a group of tools. Each tool registers its interest in certain messages with a message broadcast component of the environment. When a message is received by this component it selectively distributes it ....
....extensive modification if they have not been implemented in a modular style that clearly separates system, data, procedural and userinterface functionality. Under certain circumstances it may be possible to use wrappers around existing batch type tools, as has been illustrated in HP SoftBench [Ger89] In order to explore this point further we can define some architectural requirements for both the tools and their environment. 8.1 TOOL AND ENVIRONMENT REQUIREMENTS Tools require: an external interface definition, i.e. a tool s events; a method tool must have a welldefined set of operations ....
Gerety, C.,"HP Softbench: A New Generation of Software Development Tools." Tech.report SESD-89-25, HP Software Engineering Systems Division, Fort Collins, Colorado. November 1989.
....the requirements for these tools and for an environment to support them. To take advantage of the eventcoordination strategy, tools will usually be written specifically for the environment. However, it may be possible to encapsulate simple batch style tools in a wrapper as is done in HP SoftBench [Ger89]. If we adopt a modular approach to implementing new tools we can use some of the concepts relating to the environment for the tools themselves. By decomposing method tools into small, cohesive tools, they can be assembled around a cluster coordinator in the same way as the environment is ....
....of the published work on tool integration deals with the mechanics of integration, and attainable levels of integration. Suggested integration approaches include rule based process modelling integration such as MARVEL[KBS90] and message broadcasting with and without policy mechanisms[GI91] Rei90][Ger89]. Another approach is to add adaptations to particular languages, for example to support implicit invocation [SN92] GS93] Exploring related work in the area of tool integration brought about the realisation that very little work on integration is done from an environment user s perspective, ie ....
Gerety, C., HP Softbench: A New Generation of Software Development Tools, Technical report SESD-89-25, HP Software Engineering Systems Division, Fort Collins, Colorado, November 1989.
....a single program allowing the use of local data structures to share data between components and to implement the event handling mechanisms. Their mediators are simple dispatching mechanisms rather than the fully programmable clusters we have described in this paper. Field [Rei90] and SoftBench [Ger89] do have concurrent execution of tools and use operating system provided mechanisms for inter process communication. However the event, or message, distribution mechanisms appear to be very simple and it would be difficult to provide the process level integration, or encapsulation possibilities, ....
Gerety, C.,"HP Softbench: A New Generation of Software Development Tools." Tech. Report SESD-8925, HP Software Engineering Systems Division, Fort Collins, Colorado. November 1989.
....The pub sub style has been used in programming environments [24] and operating systems, as well. The call back mechanism for signal handling in operating systems is a classic example of the pub sub style. Mechanisms to support the pub sub style are found in commercial toolkits (e. g, Softbench [16], ToolTalk [28] DecFuse) communications standards (e.g. Corba [12] integration frameworks (e.g. JavaBeans [19] and programming environments. Sun has recently announced a specification for a messaging service called the JAVA Message Service or JMS [22] JMS also supports primitives to ....
C. Gerety. HP Softbench: A new generation of software development tools. Technical Report SESD-89-25, Hewlett-Packard Software Engineering Systems Division, Fort Collins, Colorado, November 1989.
....with respect to a software system s if no modifications need to be made by the developer to the source code of the components of s in order for them to be made interoperable. It is important that nonintrusiveness is defined in context, with respect to a particular software system. SoftBench [24], for example, is nonintrusive only when applied 25 to software components that interact with the outside world through standard input and output (stdin and stdout) SoftBench could not bring interoperability to a graphical paint program that accepts only mouse events as input without ....
....languages to exchange messages is to provide a library of message passing functions for each programming language. For example, Polylith [60] provides functions for sending and receiving synchronous and asynchronous messages. Other well known message passing systems include FIELD [61] SoftBench [24], and Isis [11] 4.1.2 Common Type System A popular means for allowing software components to interoperate is to require all of them to create and access data objects via a common type system, rather than (or in addition to) the type systems of their respective programming languages. A primitive ....
[Article contains additional citation context not shown here]
Gerety, Colin. HP SoftBench: A new generation of software development tools. Hewlett-Packard Journal 41, 3 (June 1990), 48--59. 270
....applications [17, 18, 19] communicating using message exchange through a distributed message server. Many distributed applications use message server mechanisms to cooperate (following the ECMA NIST standard [5] Our underlying communication layer is based on a message server like HP s BMS [1,9], SUN s Tooltalk [7,8] or FIELD [12,13] and is used in the software open platform TOPIC SE [6,22] Our debugging technique is based on message monitoring. We propose an intrusion free monitoring method to collect messages. This method allows a on the fly monitoring and relies on an Observation ....
Gerety C. , "HP-SoftBench: a new generation of Software Development Tools", HP Journal, june 1990.
.... component is just a procedure or method. 1 There are a number of benefits of using the II architectural style, and it has been used in diverse settings such as programming environments and operating systems and others. Mechanisms to support II are found in commercial toolkits (e.g. Softbench [Ger89], ToolTalk, DecFuse) communication standards (e.g. Corba) integration frameworks (e.g. OLE) and programming environments (e.g. Smalltalk) However, there is currently no established basis for reasoning about II systems. In particular it is difficult to answer questions like: What will be ....
....Work There are two general areas of related work. The first is research on implicit invocation systems. Most of the work on such systems has centered around developing practical mechanisms for exploiting the paradigm in real systems, such as programming environments like Field and Softbench [Rei90,Ger89]. Our work is inspired by the practical success of this work, and hopes to make engineering efforts based on it more effectivebyproviding more principled basis for reasoning about II systems. Within the general area of II researchseveral researchers have attempted to provide precise ....
C. Gerety. HP Softbench: A new generation of software developmenttools. Technical Report SESD-89-25, Hewlett-Packard Software Engineering Systems Division, Fort Collins, Colorado, November 1989.
.... signals Connectors automatic invocation of processes that have registered interest in events Control structure decentralized; individual components are not aware of recipients of signal Implicit Invocation Object or Process Examples: Balzer 86] Garlan et al. 92] Gerety 89] Habermann and Notkin 86] Hewitt 69] Krasner and Pope 88] Reiss 90] Shaw et al. 83] Shaw 9 The repository architectural pattern Problem: This pattern is suitable for applications in which the central issue is establishing, augmenting, and maintaining a complex central body of information. ....
C. Gerety. HP Softbench: A New Generation of Software Development Tools. TR SESD-89-25, Hewlett-Packard Software Engineering System Division, Ft Collins CO, November 1989.
....scale. However, deployment of such systems at the scale of the Internet imposes new challenges that are not met by existing technology. In particular, the technology to support an event based architectural style is well developed for local area networks (e.g. Field s Msg [7] SoftBench s BMS [1], ToolTalk [3] and Yeast [4] but not for wide area networks. One of these systems, Yeast, was built and studied by the first author while he was on the research staff at AT T Bell Laboratories. Yeast is a general purpose platform for building distributed applications in an eventbased ....
C. Gerety, "HP SoftBench: A New Generation of Software Development Tools", Hewlett-Packard Journal, vol. 41, no. 3, pp. 48--59, 1990.
....data. Process integration components, such as ProcessWall [18] are likewise a natural focal point for such instrumentation. Many software engineering environments, even those that are not process based, can supply event data relatively easily. Message based systems, such as Field [25] Softbench [16], and ToolTalk [28] provide a natural framework from which to collect data about activities. E#orts to collect events across the Internet (e.g. user interface events [19] are also compatible with our approach. Of the existing tools that developers already use, many naturally provide some event ....
C. Gerety. HP SoftBench: A New Generation of Software Development Tools. Technical Report SESD-- 89--25, Hewlett-Packard Software Engineering Systems Division, Fort Collins, Colorado, November 1989.
.... this architectural style is well developed for local area networks (e.g. Field s Msg [31] SoftBench s 7R#DSSHDU#LQ#WKH#3URFHHGLQJV#RI#WKH#6L[WK#(XURSHDQ#6RIWZDUH#(QJLQHHULQJ RQIHUHQFH# 0#6, 62)7#)LIWK#6 PSRVLXP#RQ#WKH#)RXQGDWLRQV#RI#6RIWZDUH (QJLQHHULQJ##=XULFK##6ZLW]HUODQG##6HS###### BMS [13], ToolTalk [17] and Yeast [20] but it is ill suited to networks on the scale of the Internet. Hence, new technologies are needed to support the construction of large scale, event based software systems for the Internet. We envision event observation and notification as being an explicit ....
....specification, analysis and debugging of software, including Instant Replay [22] Event Based Behavioral Abstraction [2] TSL [23,32] and Rapide [24] 5. software buses, such as Polylith [30] OLE ActiveX [5] and CORBA [34] 6. tool integration frameworks, including Field [31] SoftBench TM [13] and ToolTalk TM [17] 5 4 Macintosh is a trademark of Apple Computer, Inc. 7. communication and collaboration systems, such as electronic mail, electronic bulletin boards, network news services [18] Lotus Notes , and Corona [15] 6 8. software agent technology (e.g. see Genesereth and ....
C. Gerety, "HP SoftBench: A New Generation of Software Development Tools", HewlettPackard Journal, vol. 41, no. 3, pp. 48--59, 1990.
.... handled by a separate dispatcher process that communicates with the tools through communication channels provided by the host operating system (such as sockets in Unix) Examples include Field, Forest, Softbench and several other commercial tool integration frameworks [Reiss 90, Garlan Ilias 91, Gerety 89] The second category is implicit invocation systems based on special purpose languages and application frameworks. In these systems implicit invocation becomes accessible through specialized notations and run time support. For example, many database systems now provide notations for defining ....
....changed event. 2 Active databases often have a fixed event vocabulary, where events are associated with primitive database operations, such as inserting, removing, or replacing an element in the database. At the other extreme, tool integration frameworks, such as Field and Softbench [Reiss 90, Gerety 89] have no explicit event declarations at all. A tool can announce an arbitrary string, although tool builders typically describe the event vocabulary of each tool as externally documented conventions. All four approaches can be implemented in Ada. In the first and second cases, events are ....
[Article contains additional citation context not shown here]
Colin Gerety. HP SoftBench: A New Generation of Software Development Tools. Technical Report SESD-89-25, Hewlett-Packard Software Engineering Systems Division, Fort Collins, Colorado (November 1989).
....invoke other programs on request. BMS has been used to integrate the SDL PIC [4] demo and the TESS [2] user interface. BMS runs under SunOS 4.x and is implemented on top of Q [3] from the University of Colorado. BMS is unrelated to the program of the same name which is a part of HP SoftBench [1]. 2 BMS Features BMS supports two services: 1. Simple broadcast of a message among a set of programs called BMS clients . 2. Invocation of other programs. Programs that wish to use BMS s features must register to use them, thereby becoming BMS clients . Any client may use BMS to broadcast a ....
Colin Gerety. HP SoftBench: A New Generation of Software Development Tools. SoftBench Technical Note Series SESD-89-25, Revision 1.4, Hewlett-Packard, November 1989.
....B or any other components are registered. 2 There are a number of benefits of using the II architectural style, and it has been used in diverse settings such as programming environments and operating systems and others. Mechanisms to support II are found in commercial toolkits (e.g. Softbench [Ger89], ToolTalk, DecFuse) communication standards (e.g. Corba) integration frameworks (e.g. OLE) and programming environments (e.g. Smalltalk) However, there is currently no established basis for reasoning about II systems. In particular it is difficult to answer questions like: What will be the ....
....Work There are two general areas of related work. The first is research on implicit invocation systems. Most of the work on such systems has centered around developing practical mechanisms for exploiting the paradigm in real systems, such as programming environments like Field and Softbench [Rei90,Ger89]. Our work is inspired by the practical success of this work, and hopes to make engineering efforts based on it more effective by providing more principled basis for reasoning about II systems. Within the general area of II research several researchers have attempted to provide precise ....
C. Gerety. HP Softbench: A new generation of software development tools. Technical Report SESD-89-25, Hewlett-Packard Software Engineering Systems Division, Fort Collins, Colorado, November 1989.
....of SDEs based on message passing It is possible to integrate Software Development Environments (SDE) based on message passing into SPADE 1 2.0. Possible candidates to integration in the SPADE 1 2. 0 environment are: ffl Steven Reiss FIELD environment [Rei90] ffl Hewlett Packard SoftBench [Ger90]. ffl Sun Microsystems ToolTalk [Sun91] ffl DEC FUSE [Dig91b] The above listed SDEs are based on the message passing approach, i.e. tools in the SDE communicate by passing messages informing other tools of their actions, and requesting services from other tools. Each SDE owns a message ....
C. Gerety. HP SoftBench: a new generation of Software Development Tools. HP journal, June 1990.
....another mode of communication based on the concept of subscription in addition to explicit sending. A subscription is a means by which activities and agents express their interest in receiving messages. In this mode of communication widely used in message servers (such as Field [Rei90] Tooltalk [Ger89]) sender and receivers do not know each other directly. A message can be disseminated with no obligation for the sender to know the receiver(s) Agents or activities who are interested in a message must subscribe first so that they can capture it. Figure 5: Communication principle A ....
C. Gerety. "HP SoftBench: A new generation of software development tools". Technical note series SESD-89-25, Revision 1.4, Hewlett Packard, November, 1989.
....data. Process integration components, such as ProcessWall [18] are likewise a natural focal point for such instrumentation. Many software engineering environments, even those that are not process based, can supply event data relatively easily. Message based systems, such as Field [25] Softbench [16], and ToolTalk [28] provide a natural framework from which to collect data about activities. Efforts to collect events across the Internet (e.g. user interface events [19] are also compatible with our approach. Of the existing tools that developers already use, many naturally provide some event ....
C. Gerety. HP SoftBench: A New Generation of Software Development Tools. Technical Report SESD-- 89--25, Hewlett-Packard Software Engineering Systems Division, Fort Collins, Colorado, November 1989.
....event data. Process integration components, such as ProcessWall [66] are likewise a natural focal point for such instrumentation. Many software engineering environments, even those not process based, can supply event data relatively easily; message based systems, such as Field [100] Softbench [58], and ToolTalk [112] provide a natural framework from which to collect data about system based activities. Of the existing tools that developers already use, many naturally provide some event data collection as well. For example, all configuration management systems provide a history of the ....
C. Gerety. HP SoftBench: A New Generation of Software Development Tools. Technical Report SESD-- 89--25, Hewlett-Packard Software Engineering Systems Division, Fort Collins, Colorado, November 1989.
....the components of a large software system. This experiment uncovered practical details about these integration mechanisms that are not obvious from their literature. 1 Introduction The problem of high level communication between concurrently executing programs has been addressed by many ([4], 5] 10] 11] et al. Recently, the term megaprogramming [2, 14] has been invented to describe the integration of large, diverse software systems or megamodules [14] Whether existing software integration mechanisms can handle the rigors of megaprogramming has yet to be seen. As an ....
....Links no no yes Access Control no no yes Modify Source indicates whether or not the source code of programs must be modified in order to participate in communication using the given mechanism. All three mechanisms surveyed require source code modification. Other mechanisms such as SoftBench [4] do not, but they have other limitations. Program Registration and Message Filtering indicate how (if at all) participating programs register for integration mechanism services in general, and for receipt of particular messages, respectively. ToolTalk was the most powerful of the mechanisms in ....
Colin Gerety. HP SoftBench: A New Generation of Software Development Tools. SoftBench Technical Note Series SESD-89-25, Revision 1.4, Hewlett-Packard, November 1989.
....of a system as a client server organization immediately conveys a strong image of the kinds of pieces and how they fit together. Fourth, use of standardized styles supports interoperability. Examples include CORBA object oriented architecture [Cor91] and event based tool integration [Ger89]. Fifth, by constraining the design space, an architectural style often permits specialized, style specific analyses. For example, it is possible to analyze pipefilter systems for schedulability, throughput, latency, and deadlock freedom. Such analyses might not be meaningful for an arbitrary, ad ....
Colin Gerety. HP Softbench: A new generation of software development tools. Technical Report SESD-89-25, Hewlett-Packard Software Engineering Systems Division, Fort Collins, Colorado, November 1989.
....a public domain OODB. ffl a toolkit for constructing graphical user interfaces: InterViews, a UI toolkit, together with Unidraw, a reusable framework for creating drawing editors [LVC89, VL90] ffl an event based tool integration mechanism: Softbench, a commercial event broadcast mechanism [Ger89] ffl a RPC mechanism: Mach RPC Interface Generator (MIG) an RPC stub generator that was well targeted to our host operating system [Dra87] All we had to do was put the subsystems together, a task considerably simplified by the fact they were all written in either C or C, had all been used ....
Colin Gerety. HP Softbench: A new generation of software development tools. Technical Report SESD89 -25, Hewlett-Packard Software Engineering Systems Division, Fort Collins, Colorado, November 1989.
....environment from a description of a specific architectural style. 2 Related Work 2. 1 Software Development Environments For the past decade there has been considerable research and development in the area of automated support for software development: tool integration frameworks [B 88, Ger89] environment generators and toolkits [RT89, vLDD 88, DGHKL84] process oriented support [KFP88, T 88] etc. These facilities typically provide generic support for some aspects of software development, and can be specialized or instantiated for a particular development environment. Inputs ....
.... organization immediately conveys a strong image of the kinds of pieces and how they fit together. Fourth, use of standardized styles supports interoperability. Examples include CORBA object oriented architecture [Cor91] the OSI protocol stack [McC91] and event based tool integration [Ger89] Fifth, as noted above, by constraining the design space, an architectural style often permits specialized, style specific analyses. For example, it is possible to analyze systems built in a pipe filter style for schedulability, throughput, latency, and deadlock freedom. Such analyses might not ....
[Article contains additional citation context not shown here]
Colin Gerety. HP Softbench: A new generation of software development tools. Technical Report SESD89 -25, Hewlett-Packard Software Engineering Systems Division, Fort Collins, Colorado, November 1989.
No context found.
C. Gerety. HP Softbench: A New Generation of Software Development Tools. TR SESD-89-25, HewlettPackard Software Engineering System Division, Ft. Collins CO, November 1989.
First 50 documents
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