Abstract: A valve repair system for repairing a native valve of a patient during a non-open-heart procedure includes a delivery device and a valve repair device. The valve repair device include a pair of paddles, first gripping member, a second gripping member, and a spacer. First and second gripping member controls or first and second gripping member control portions are coupled to the first and second gripping members to move the gripping members. The spacer element is configured to close a gap in the native valve of the patient when the valve repair device is attached to the native valve.

Abstract: A valve repair device for repairing a native valve of a patient. The valve repair device includes a compressible spacer element, a pair of paddles, and a pair of gripping members. The pair of paddles are coupled to the spacer element. The pair of gripping members are disposed between the pair of paddles. The paddles and the gripping members are configured to attach to leaflets of a heart valve.

Abstract: An improved method for initializing an auxiliary code resource is provided. In a preferred embodiment of the present invention, a computer system has a multiple entry point code resource consisting of a main code resource, which contains global variables, and a plurality of auxiliary code resources. The method of the first aspect of the present invention provides for loading the auxiliary code resource into memory, searching the auxiliary resource for markers and, upon locating the markers, storing a reference to the global variables into the sequence of markers.

Abstract: An improved system and method for determining software reliability is provided. In a preferred embodiment of the present invention, a mapping mechanism and a preferred automated testing system are used. The mapping mechanism provides for the creation of a number of hits to failure metric. The preferred automatic testing system of the preferred embodiment of the present invention provides for the automatic testing of software and the creation of the number of hits to failure and the elapsed time to failure. The combination of the number of hits to failure metric and the results of the preferred automated testing system provide for a more accurate indication of the reliability of software.