Item 2: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
= Introduce a distinction between prototypes and products during the connectathon test. = | = Introduce a distinction between prototypes and products during the connectathon test. = | ||
== Section 1. Introduce a distinction between prototypes and products during the connectathon test. == | == Section 1. Introduce a distinction between prototypes and products during the connectathon test. == | ||
The | The connect-a-thon aim at testing the implementation of IHE actors and integration profiles withing company products. When new actors and integration profiles are defined by the IHE committees it is not realistic to test their implementation in products during the connect-a-thon that follows the release of the new supplements. | ||
==Section 2. Objective.== | ==Section 2. Objective.== | ||
Revision as of 04:32, 16 November 2006
Introduce a distinction between prototypes and products during the connectathon test.
Section 1. Introduce a distinction between prototypes and products during the connectathon test.
The connect-a-thon aim at testing the implementation of IHE actors and integration profiles withing company products. When new actors and integration profiles are defined by the IHE committees it is not realistic to test their implementation in products during the connect-a-thon that follows the release of the new supplements.
Section 2. Objective.
We need to distinguish products from prototypes in the connect-a-thon testing process.
Better characterization of the systems tested during the connect-a-thon. Are we testing a real product or a prototype. Improve inter vendor communication : Vendors need to know the status of their peers systems. Did they test with a product or with a prototype ? Reduce the risks for user when integrating systems in their institutions. User shall be informed of the quality of the system tested during the connectathon. Prevent usage of systems customized for the connectathon and that will not