1-6. (canceled)
7. A method for testing plausibility of electrical impedance measurements obtained during a measurement of bioimpedance of a person, the method comprising the steps of:
determining real parts and imaginary parts of the impedance measurements for a plurality of different frequencies and comparing the real and imaginary parts with respect to their localization in a complex representation plane defined by a coordinate axis for the imaginary part and a coordinate axis for the real part with a nominal curve; and considering a measurement value as not plausible if the measurement value exceeds a predefinable deviation from the nominal curve.
8. The method according to claim 7, including using a semi-circle in the complex plane as the nominal curve.
9. The method according to claim 7, including changing the frequency from a minimum value to a maximum value during performance of the measurement.
10. The method according to claim 9, wherein the minimum value is 0 Hz and the maximum value is infinity.
11. The method according to claim 7, wherein at least three measurement values are determined.
12. The method according to claim 11, wherein at least eight measurement values are determined.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
1. A method for extending the software change management to handle unmanaged artifacts comprising:
storing an object within a software change management (SCM) system, wherein the object is managed as a traditional SCM artifact, wherein the object comprises a reference to one or more unmanaged artifacts, wherein the unmanaged artifacts lack restrictions imposed by the software change management system, wherein the unmanaged artifacts are associated with a binding of the traditional managed artifact; and
triggering a programmatic action on the stored object in response to an action associated with at least one of the traditional SCM artifact and the object.
2. The method of claim 1, wherein the traditional SCM artifact is a source code entity, wherein the restrictions that the unmanaged artifacts lack are at least one of a lifecycle, access rule, and a management policy, wherein the binding is a compile-time dependency binding, wherein the unmanaged artifacts is associated with a remote repository, wherein within the remote repository, the unmanaged artifacts are managed as another traditional SCM artifact, and wherein the action that triggers the programmatic action is a provisioning action.
3. The method of claim 1, wherein the object is associated with a traditional SCM artifact, wherein the object and the traditional SCM artifact are managed by the SCM in unison.
4. The method of claim 1, wherein the programmatic action automatically updates at least one of the unmanaged artifacts associated with the object.
5. The method of claim 1, wherein the unmanaged artifacts include a set of different unmanaged artifacts and a set of revisions for a single unmanaged artifact.
6. The method of claim 2, wherein the provisioning action results in importing at least one unmanaged artifact into a development environment associated with a client computing device.
7. The method of claim 1, wherein the programmatic action is performed prior to or subsequent to compile time.
8. The method of claim 1, wherein the method is performed by a plug-in component of an integrated development environment (IDE), wherein the plug-in component is associated with an IBM WEBSPHERE INTEGRATION DEVELOPER software, wherein the IDE is an IBM ECLIPSE IDE.
9. A system for extending the software change management to handle unmanaged artifacts comprising:
an object comprising of a reference stored within a software change management (SCM) system, wherein the reference is a linkage to a remote managed artifact stored within a repository, wherein the at least one reference lacks artifact restrictions, wherein the artifact restrictions are traditional software change management artifact restrictions associated with a managed artifact within the SCM, wherein the object is associated with a binding to the managed artifact stored within the SCM; and
an SCM engine able to perform operations on the object in a manner consistent with a managed artifact; and
a portion of metadata associated with the object, wherein the metadata comprises of at least a name information and a location information associated with the remote managed artifact.
10. The system of claim 9, wherein the operations are at least one of a fetch operation and a compare operation.
11. The system of claim 9, wherein the managed artifact is a source code entity, and wherein the portion of metadata is stored within an extensible markup (XML) language file within the SCM, wherein the portion of metadata indicates a means to access the remote managed artifacts.
12. The system of claim 9, wherein the system is a portion of a Web-enabled service.
13. The system of claim 9, wherein the location information is a Uniform Resource Identifier (URI), wherein the URI is associated with a source code repository.
14. The system of claim 9, wherein the SCM performs a dependency check on each unmanaged artifact associated with object.
15. The system of claim 9, wherein the object comprises of at least one remote managed artifact.
16. The system of claim 9, wherein the SCM is an IBM RATIONAL ASSET MANAGER software.
17. A computer program product comprising a computer readable storage medium having computer usable program code embodied therewith, the computer usable program code comprising:
computer usable program code stored in a tangible storage medium, when said computer usable program code is executed by a processor it is operable to store an object within a software change management (SCM) system, wherein the object is managed as a traditional SCM artifact, wherein the object comprises a reference to one or more unmanaged artifacts, wherein the unmanaged artifacts lack restrictions imposed by the software change management system, wherein the unmanaged artifacts are associated with a binding of the traditional managed artifact; and
computer usable program code stored in a tangible storage medium, when said computer usable program code is executed by a processor it is operable to trigger a programmatic action on the stored object in response to an action associated with at least one of the traditional SCM artifact and the object.
18. The computer program product of claim 17, wherein the traditional SCM artifact is a source code entity, wherein the restrictions that the unmanaged artifacts lack are at least one of a lifecycle, access rule, and a management policy, wherein the binding is a compile-time dependency binding, wherein the unmanaged artifacts is associated with a remote repository, wherein within the remote repository, the unmanaged artifacts are managed as another traditional SCM artifact, and wherein the action that triggers the programmatic action is a provisioning action.
19. The computer program product of claim 18, wherein the provisioning action results in importing at least one unmanaged artifact into a development environment associated with a client computing device.
20. The computer program product of claim 17, wherein the programmatic action is performed prior to or subsequent to compile time.