Abstract: Various forms of anti-clog suction tips apparatus are disclosed. For example, an anti-clog suction tip apparatus includes a suction tip assembly having a suction tip with a suction opening at a first end thereof for removing debris through suction, a hose attachment portion for attaching the suction tip assembly to a suction source, and an ejection wire channel. The apparatus further includes an ejection wire assembly having an ejection wire extending within the channel and an ejection button integral with or connected to the ejection wire. Applying a force to the ejection button advances the ejection wire through the channel such that an end portion of the ejection wire enters the suction tip and dislodges debris clogging the suction tip. The ejection wire may include an enlarged end portion such as, for example a ball tip. One or more of the components of the apparatus may be single-use and disposable.

Abstract: An architecture that allows target service interactions to be realistically simulated in a development environment. The architecture includes a proxy service, an interaction recorder, an interaction store and an emulator service. The proxy service delegates service requests received from a client component to a target service. If it is in “record” mode, the proxy service routes any interaction data corresponding to the interaction (between the target service and the client component) to the interaction recorder. Upon receipt, the interaction recorder records the interaction data in the interaction store. Later, the proxy service can be placed in “replay” mode so that a subsequent service request for the target service is delegated to the emulator service. Upon receipt, the emulator service retrieves the corresponding interaction data from the data store and replays the same to emulate/simulate the target service.

Abstract: A method for collecting and filtering biological material from blood and other fluids during a surgical procedure includes: attaching a first cover including a suction port and an intake port to a collection trap; attaching a suction source to the suction port; attaching an instrument to the intake port, through which blood and tissue are suctioned and received into the collection trap; filing the collection trap with blood and tissue; removing the collection trap from the first cover; attaching a second cover to the collection trap in place of the first cover, the second cover including a suction port and a plunger, the plunger including a press head having a screen portion permitting blood and other fluids to pass; attaching a suction source to the suction port of the second cover; separating the blood from the tissue by deploying the plunger; and drawing off the blood through the suction port.

Abstract: Apparatus and methods are disclosed for use during surgical procedures for collecting autologous bone. A preferred bone collection assembly collects bone by compressing blood products away from trapped bone using a press. Such bone collecting assembly is easy and uncomplicated to use, and can be easily integrated into an operation where the need for collection and utilization of autologous bone exists.

Abstract: Recording and replaying service interactions permits developers to evaluate, iteratively build and test middle-tier and other software components using realistic interaction data and quality of service (QoS) characteristics without requiring constant access to a resource operating in a production environment. Typical service execution sequences can be recorded once by the system administrator/deployer, then replayed as many times as necessary by developers iteratively building and testing middle-tier components.

Abstract: A method, system, and data structure for implementing a workflow. The workflow divides a general work task of an enterprise into activities and associated relationships with respect to participating roles in the workflow. A checklist file is generated for each participating role. Each checklist file is stored in a first database. Each checklist file specifies activities of each participating role and at least one relationship element for each activity of each participating role. The at least one relationship element of a first activity in the checklist file of a first participating role of the participating roles includes a dependency relationship. A plurality of checklist instances is generated. Each checklist instance being stored in a second database. Each checklist instance corresponds to an associated checklist file and records a status of each activity and of each relationship element in the associated checklist.

Abstract: An architecture that allows target service interactions to be realistically simulated in a development environment. The architecture includes a proxy service, an interaction recorder, an interaction store and an emulator service. The proxy service delegates service requests received from a client component to a target service. If it is in “record” mode, the proxy service routes any interaction data corresponding to the interaction (between the target service and the client component) to the interaction recorder. Upon receipt, the interaction recorder records the interaction data in the interaction store. Later, the proxy service can be placed in “replay” mode so that a subsequent service request for the target service is delegated to the emulator service. Upon receipt, the emulator service retrieves the corresponding interaction data from the data store and replays the same to emulate/simulate the target service.

Abstract: A tool (30) for graphically defining an expression is disclosed. The tool comprises a graphic user interface (GUI) component (31) and an expression generator component (32) adapted to read a graphic definition of an expression provided by a user through the GUI component. The GUI component is responsive to user input to define one or more tree structures comprising a hierarchical series of nodes, and one or more lists comprising a plurality of items, each list item being associated with respective node of an associated tree. The expression generator component analyzes the graphic definition and generates an expression based on the structure of the or each tree and any list items associated with respective nodes of a tree.

Abstract: An architecture that allows target service interactions to be realistically simulated in a development environment. The architecture includes a proxy service, an interaction recorder, an interaction store and an emulator service. The proxy service delegates service requests received from a client component to a target service. If it is in “record” mode, the proxy service routes any interaction data corresponding to the interaction (between the target service and the client component) to the interaction recorder. Upon receipt, the interaction recorder records the interaction data in the interaction store. Later, the proxy service can be placed in “replay” mode so that a subsequent service request for the target service is delegated to the emulator service. Upon receipt, the emulator service retrieves the corresponding interaction data from the data store and replays the same to emulate/simulate the target service.

Abstract: A meta-model for creating models of alternative physical representations of logically equivalent entities, such as alternative wire format representations of logically equivalent messages, includes a logical meta-model and a physical meta-model. The logical meta-model provides logical entity component classes for creating a logical model which describes, in a platform and programming language neutral manner (e.g. as an XML schema), the logical structure of the modeled entity as a hierarchy of logical entity components. The physical meta-model provides classes for creating a physical model which describes the alternative physical representations. The physical meta-model includes Base Classes representative of generic physical representations of the logical entity components, with “correspondence associations” being defined between the Base Classes and corresponding logical entity component classes.

Abstract: The invention provides a method, system, and program product for collaboratively editing a diagram.

Abstract: The invention provides a method and system for generating a visual representation of an interaction between a computer system and a user.

Abstract: A workflow UI generating method and generator.

Abstract: A method, system, and data structure for implementing a workflow. The workflow divides a general work task of an enterprise into activities and associated relationships with respect to participating roles in the workflow. A checklist file is generated for each participating role. Each checklist file is stored in a first database. Each checklist file specifies activities of each participating role and at least one relationship element for each activity of each participating role. The at least one relationship element of a first activity in the checklist file of a first participating role of the participating roles includes a dependency relationship. A plurality of checklist instances is generated. Each checklist instance being stored in a second database. Each checklist instance corresponds to an associated checklist file and records a status of each activity and of each relationship element in the associated checklist.

Abstract: In the process of hierarchical composition of software component types, the reusability of software component types is improved through the “promotion of features”. That is, a feature of an instance of a predetermined software component type may be promoted to a software component type containing instances of the predetermined software component type. The promoted feature may then be customized when the containing software component type is instantiated.

Abstract: A method, apparatus and computer program product is provided for creating and implementing a pattern solution by specifying one or more patterns and creating a pattern solution recipe which documents guidance related to use, organization and interconnection the patterns. The pattern solution recipe permits substitution of one or more specified pattern with a substitute pattern. The pattern solution is transformed (creating a pattern solution implementation) by implementing each pattern as a parameterizable computer accessible object. These parameters provide a point of customization. The pattern solution recipe is implemented as another computer accessible object providing further refined guidance on the use of the implemented pattern solutions. Pattern solutions knit many patterns together using the pattern solution recipe.

Abstract: An architecture that allows target service interactions to be realistically simulated in a development environment. The architecture includes a proxy service, an interaction recorder, an interaction store and an emulator service. The proxy service delegates service requests received from a client component to a target service. If it is in “record” mode, the proxy service routes any interaction data corresponding to the interaction (between the target service and the client component) to the interaction recorder. Upon receipt, the interaction recorder records the interaction data in the interaction store. Later, the proxy service can be placed in “replay” mode so that a subsequent service request for the target service is delegated to the emulator service. Upon receipt, the emulator service retrieves the corresponding interaction data from the data store and replays the same to emulate/simulate the target service.

Abstract: Recording and replaying service interactions permits developers to evaluate, iteratively build and test middle-tier and other software components using realistic interaction data and quality of service (QoS) characteristics without requiring constant access to a resource operating in a production environment. Typical service execution sequences can be recorded once by the system administrator/deployer, then replayed as many times as necessary by developers iteratively building and testing middle-tier components.

Abstract: An emulating system is provided for testing a computer application for use with a target computing system. The emulating system emulates the input/output behavior of the target system. The emulating system has access to a data source, which contains a plurality of requests acceptable to the target system and a plurality of responses. Each acceptable request is associated with a response that describes the expected behavior of the target system in response to the acceptable request. After communication between the emulating system and the application is established, the emulating system responds to a request from the application by obtaining a response associated with the request from the data source and responding as described by the response associated with the request.