M.R. Cagan. The HP SoftBench environment: an architecture for a new generation of software tools. Hewlett-Packard Journal: technical information from the laboratories of Hewlett-Packard Company, 3(41), June 1990.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....Requests Notifications . component interoperability models, and . software architectures. While C2 has many similarities to existing work in these areas, there are also important differences that distinguish it from them. In contrast to existing systems, such as Field [29] and SoftBench [6], X Windows [33] Chiron 1 [40] Arch [28] and Slinky [44] which support only a fixed number of layers in an architecture, the C2 architectural style allows layering to vary naturally with the application domain. In this, the C2 style is similar to GenVoca [2] whose components may be composed ....

M. R. Cagan. The HP SoftBench Environment: An Architecture for a New Generation of Software Tools. Hewlett-Packard Journal, volume 41, number 3, pages 36-- 47, June 1990.

....and the other technologies mentioned in Table 7 in greater detail. 7. 2 Message Based Integrated Environments The idea of integrating different components by means of messages was pioneered in a research system called Field [30] As in several commercial products that followed (e.g. HP SoftBench [4], DEC FUSE [19] and Sun ToolTalk [20] Field implements an environment in which several software development tools can cooperate by exchanging messages. Messages are the means by which one tool can request services to be carried out by other tools, or by which a tool announces a change of ....

M. R. Cagan. The HP SoftBench environment: an architecture for a new generation of software tools. Hewlett-Packard Journal: technical information from the laboratories of Hewlett-Packard Company, 41(3):36-- 47, June 1990.

....an event service that interacts with any reactive component and rules are always executed as separate transactions, independent of the triggering transactions. Concerning event management our event service compiles techniques proposed by active databases, commercial products such as HP SoftBench [5], DEC FUSE [17] and Sun ToolTalk [19] and distributed event based infrastructures [10, 24] But different to these approaches, it provides an event processing layer to offer facilities (i.e. ordering, composing, storing) within a configurable environment. Finally, as us they define adaptable ....

....of different areas from outside the classical active database context. The event service compiles event processing strategies that are spread out in existing products and proposals (subscription, filtering) from different domains such as active databases [26, 7] networks (communication protocols) [27, 5, 19], distributed systems [21, 24] and middle ware [24, 10, 22] As we already said, event processing with rich semantic can be tailored to different application needs. The rule service compiles i) classical rule execution characteristics or dimensions that have been revisited for distribution [25, ....

M.R. Cagan. The HP SoftBench environment: an architecture for a new generation of software tools. Hewlett-Packard Journal: technical information from the laboratories of Hewlett-Packard Company, 3(41), June 1990.

....noti es all the components that have declared their interest. Our event service compiles event processing strategies that are spread out in existing products and proposals (subscription, ltering) from di erent domains such as active databases [50, 20] networks (communication protocols) [52, 14, 38], distributed systems [49] and middle ware [49, 31, 45] Event processing with rich semantic can be tailored to di erent application needs. Figure 1 depicts our service framework to specify, generate and execute event managers. Using the Speci cation Interface of the service one can de ne an ....

M.R. Cagan. The HP SoftBench environment: an architecture for a new generation of software tools. Hewlett-Packard Journal: technical information from the laboratories of Hewlett-Packard Company, 3(41), June 1990.

....an event service that interacts with any reactive component and rules are always executed as separate transactions, independent of the triggering transactions. Concerning event management our event service compiles techniques proposed by active databases, commercial products such as HP SoftBench [5], DEC FUSE [17] and Sun ToolTalk [19] and distributed event based infrastructures [11, 24] But different to these approaches, it provides an event processing layer to offer facilities (i.e. ordering, composing, storing) within a configurable environment. Finally, as us they define adaptable ....

....of different areas from outside the classical active database context. The event service compiles event processing strategies that are spread out in existing products and proposals (subscription, filtering) from different domains such as active databases [26, 7] networks (communication protocols) [27, 5, 19], distributed systems [21, 24] and middle ware [24, 11, 22] As we already said, event processing with rich semantic can be tailored to different application needs. The rule service compiles i) classical rule execution characteristics or dimensions that have been revisited for distribution [25, ....

M.R. Cagan. The HP SoftBench environment: an architecture for a new generation of software tools. Hewlett-Packard Journal: technical information from the laboratories of Hewlett-Packard Company, 3(41), June 1990.

....these views of technology, and form a basis for making assertions about feature deltas. To this end it is also useful to annotate the links with feature lists. For example, consider a hypothetical genealogy of middleware technologies. In such a genealogy it would be plausible to describe SoftBench [15] and FIELD [16] as peers; this link could be annotated with the features that distinguish SoftBench from FIELD. 1. Technology analysts should freely extend this ontology, but should be guided by the principle that each element of the ontology should serve to relate technologies, and ultimately ....

Cagan, M.R., "The HP SoftBench Environment: An Architecture for a New Generation of Software Tools", HewlettPackard Journal, V41, #3, June 1990.

....is based on the monolithic Stoneman model. It has strong support for data integration, and provides a message service for tool communication as well. However, this service is a low level, Unix like mechanism which makes sophisticated messaging passing more difficult. Hewlett Packard s SoftBench (Cagan, 1990) is a commercial tool integration platform. The broadcast message server (BMS) routes requests and event notifications between tools (such as compilers, debuggers, and editors of a development environment) The messages follow an abstract tool protocol, each of which has its own set of operations. ....

Cagan, Martin R (1990). "The HP Softbench Environment: An Architecture for a New Generation of Software Tools," HP Journal, pp 36-47, June.

....expression of temporal patterns, for example, highlight the procedures that account for over 50 of execution time over the past 2 minutes. Tool integration. Query and visualization facilities such as we have described should be implemented as components within a framework such as SoftBench [Cag90] or OMG s CORBA [Gro91] providing an architecture that allows them to interoperate with other software tools. For example, a debugger could request visualization services to display and animate the call graph of a program, or a reverse engineering tool could issue queries to compute software ....

M.R. Cagan. The HP Softbench environment: An architecture for a new generation of software tools. Hewlett-Packard Journal, pages 36--47, June 1990.

....tools which present a non 2 Coordinating Software Development Tools with INDRA mandatory character because the broadcast information may be received by zero or more tools. As the software development community, we think that these two basic kinds of interactions are useful and sufficient [3][7][8] 10] 11] This paper focuses on the problem of the expression of the requests and the notifications in which a given tool may participate. The remainder of this paper is organized as follows. Section 2 establishes the main requirements that should be taken into account by a coordination ....

....instances that are already active (i.e running) as well as new tool instances. Especially, it should be possible to enforce the activation of a tool for serving a request. 3 Related work Many coordination mechanisms have been designed and implemented: the Koala Bus [3] the HP SoftBench mechanism [7], the DEC Fuse EnCase mechanism [8] Field [10] and the SUN ToolTalk mechanism [11] However, none of them seems to comply to all the 4 Coordinating Software Development Tools with INDRA requirements described previously. Crucial requirements are R2 to R6, as R1 is often fulfilled through a ....

Cagan M., The HP SoftBench Environment: An Architecture for a New Generation of Software Tools, Hewlett-Packard Journal, Vol 41(3), pp. 36-47, June 90.

....Notifications are one to many communications between tools which present a non mandatory character because the broadcast information may be received by zero or more tools. As the software development community, we think that these two basic kinds of interactions are useful and sufficient [3][8][9] 13] 14] This paper focuses on the problem of the expression of the requests and the notifications in which a given tool may participate. The remainder of this paper is organized as follows. Section 2 establishes the main requirements that should be taken into account by a coordination ....

....running) as well as new tool instances. Especially, it should be possible to enforce the activation of a tool for serving a request. 3 Related work 3. 1 Control integration mechanisms Many coordination mechanisms have been designed and implemented: the Koala Bus [3] the HP SoftBench mechanism [8], the DEC Fuse EnCase mechanism [9] Field [13] the ESF software bus [11] and the SUN ToolTalk mechanism [14] However, none of them seems to comply to all the requirements described previously. Crucial requirements are R2 to R6, as R1 is often fulfilled through a dynamic binding mechanism ....

Cagan M., "The HP SoftBench Environment: An Architecture for a New Generation of Software Tools", Hewlett-Packard Journal, vol. Vol 41, num. 3, pp. 36-47, June 90.

....by sending and receiving events, a particular form of messages. Our event service compiles event processing strategies that are spread out in existing products and proposals (subscription, filtering) from different domains such as active databases [11, 4] networks (communication protocols) [12, 2, 1], distributed systems [8, 10] and middle ware [10, 5, 9] We noticed that event services proposed in distributed system infrastructures (CORBA, RMI, MOM) range from event routers using simple event models (i.e. events can be any message such as a string with no associated inherent semantics) ....

M.R. Cagan. The HP SoftBench environment: an architecture for a new generation of software tools. HewlettPackard Journal: technical information from the laboratories of Hewlett-Packard Company, 3(41), June 1990.

....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 ....

Cagan M., "The HP-SoftBench Environment: An Architecture for a New Generation of Software Tools", Hewlett-Packard Journal, vol. 41, n3, june 1990.

....by sending and receiving events, a particular form of messages. Our event service compiles event processing strategies that are spread out in existing products and proposals (subscription, filtering) from different domains such as active databases [26, 7] networks (communication protocols) [27, 4, 19], distributed systems [22, 25] and middle ware [25, 13, 24] We noticed that event services proposed in distributed system infrastructures (CORBA, RMI, MOM) range from event routers using simple event models (i.e. events can be any message such as a string with no associated inherent ....

....meanings and it is often difficult to identify the applicability of every single technology and the added value with respect to well known technologies. 6.1 Event Services Commercial tools For quite a long time, the market has offered software that implements event services. HP SoftBench [4], DEC FUSE [16] and Sun ToolTalk [19] provide an environment in which several software development tools can cooperate by exchanging messages. The heart of these environments is a message bus between registered applications. Messages are sent to ask a service from a tool and to synchronize actions ....

M.R. Cagan. The HP SoftBench environment: an architecture for a new generation of software tools. Hewlett-Packard Journal: technical information from the laboratories of Hewlett-Packard Company, 3(41), June 1990.

....module is as straightforward as to browse it. A programmer can graphically build the skeleton of a module by creating a DAG of software units. Flesh of this skeleton can be filled in later by invoking operations associated with each software unit. 4. 5 Other Related Work Field [12] and SoftBench [13] allow a programmer to browse an existing software system in terms of logical units. Users can also visualize the interaction between abstractions at run time. But in these systems, software is organized in the traditional way instead of around these logical units. The mapping between logical ....

M.R. Cagan, "The HP SoftBench Environment: An Architecture for a New Generation of Software Tools.," Hewlett-Packerd Journal (June, 1990).

....programmed, instead it is driven by the occurrence of events. These systems realize their functionality by performing some actions in response to events, possibly using the information associated with the stimulating events. Examples of reactive systems are integrated development environments [64, 38, 11, 33], work flow and process analysis systems [16, 4] graphical user interfaces [59] network management systems [65] software deployment systems [32] and security monitors [36, 56, 75] There are two major motivations for designing applications as reactive systems. First, some applications are ....

....insights as far as the type of service that they offer. Message based integrated environments The idea of integrating different components by means of messages is first realized by Field [64] Field, together with other commercial products including 8 Background and New Challenges HP SoftBench [11], DEC FUSE [33] and Sun ToolTalk [38] implements an environment in which several software development tools can cooperate by exchanging messages. Messages are the means by which one tool can request services to be carried out by other tools, or they can be sent out by a tool to announce a change ....

M. R. Cagan. The HP SoftBench environment: an architecture for a new generation of software tools. Hewlett-Packard Journal: technical information from the laboratories of Hewlett-Packard Company, 41(3):36--47, June 1990.

....and friendly appearance of the whole system. Statemate tool 1 , SPeeDCHART 2 , and ExpessV HDL 3 , are examples of this kind. There are also environments for tool integration which facilitate the interface and communication among individual design tools in that environment. HP SoftBench [5] is a member of this group. The above tools in both domains (software and hardware) are attributed with some major characteristics such as: Use of graphical specification techniques, simulation of specification, code generation in common programming languages, use of project management, document ....

M. Cagan. The HP SoftBench Environment: An Architecture for a New Generation of Software Tools. Hewlett-Packard Journal, June 1990, pages 36-47.

....the components which need specific services, and propagates the request events to the components that have registered those services. This style supports reusability and system evolution, but suffers from poor predictability and testability. Examples include the Field system [77] and HP SoftBench [23]. ffl Layered systems provide hierarchical layers of service, in which a layer uses provides service from to its adjacent lower higher layer. To compensate for the performance inefficiency, bridging over layers is done in some systems. This style supports reuse, abstraction of the system ....

M. R. Cagan. The HP softbench environment: An architecture for a new generation of software tools. Hewlett-Packard journal, pages 36--47, June 1990.

....in Integrated Software Engineering Environments. Indeed, the integration dimensions we introduced in section 1 are not isolated one from the other, and especially, we consider that data and control dimensions are intimately connected. Most of the proposals for achieving the control dimension (like [9, 13, 8]) ooeers capabilities for message passing among the tools. This can be assimilated to service invocations. The coupling of the data and the control integration dimensions should enable the adaptation of the sent messages to any change of the invoked service interface. Figure 4 shows the scenario ....

M.R. Cagan. The HP Softbench Environment: An Architecture for a New Generation of Software Tools. Hewlett-Packard Journal, pages 3647, June 1990.

....and the other technologies mentioned in Table 7 in greater detail. 7. 2 Message Based Integrated Environments The idea of integrating different components by means of messages was pioneered in a research system called Field [30] As in several commercial products that followed (e.g. HP SoftBench [4], DEC FUSE [19] and Sun ToolTalk [20] Field implements an environment in which several software development tools can cooperate by exchanging messages. Messages are the means by which one tool can request services to be carried out by other tools, or by which a tool announces a change of ....

M. R. Cagan. The HP SoftBench environment: an architecture for a new generation of software tools. Hewlett-Packard Journal: technical information from the laboratories of Hewlett-Packard Company, 41(3):36-- 47, June 1990.

....existance of commonly used and well known traditional applications makes it interesting for the user to create graphical frontends for existing commandline oriented tools. An example for this kind of encapsulation of traditional applications into a graphical frontend is the HP Encapsulator TM [3] and [5] This is a language that can be used to embed existing non graphical applications into a graphical environment. Such an interface must be built easily, and the resulting code must be easy to handle. A programmer implementing such an interface usually does not want to learn how to use ....

Martin R. Cagan. The HP SoftBench Environment Architecture for a New Generation of Software Tools. Hewlett-Packard Journal, 41(3):36--47, June 1990.

....from the BusMaster In contrast, message transfer requests between clients are asynchronous, i.e, the sending client is not blocked after it sends a message. Communication systems whose architecture is similar to that of LSB are the Broadcast Message Server(BMS) in the HP Softbench environment [3], the Multicast Messaging System (MCMS) in the DEC FUSE environment [6] which have been greatly influenced by the Msg system used for messaging in the FIELD environment [10] They all have a central server which distributes messages and they all provide support for X and Motif applications and ....

M. R. Cagan. The HP SoftBench Environment: An Architecture for a New Generation of Software Tools. Hewlett-Packard Journal, pages pp. 36--47, June 1990.

No context found.

M.R. Cagan. The HP SoftBench environment: an architecture for a new generation of software tools. Hewlett-Packard Journal: technical information from the laboratories of Hewlett-Packard Company, 3(41), June 1990.

No context found.

M. Cagan, "The HP SoftBench Environment: An Architecture for a New Generation of Software Tools," Hewlett-Packard Journal (June 1990): 36 -- 47.

No context found.

M. R. Cagan. The HP SoftBenchEnvironment: An Architecture for a New Generation of Software Tools. Hewlett-Packard Journal, 41#3#:36#47, June 1990.

No context found.

M.R. Cagan. "The HP Softbench Environment: An Architecture for a New Generation of Software Tools." HewlettPackard Journal, pp. 36--68, June 1990.

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