{"title":"ivi -用户视角","authors":"P. Johnson","doi":"10.1109/AUTEST.2000.885624","DOIUrl":null,"url":null,"abstract":"The Interchangeable Virtual Instrument (IVI) Foundation was formed in 1997 by Instrument manufacturers and integrators desiring the development of instrument driver models which would support instrument changes without requiring test program changes. This was to be accomplished by developing instrument classes and the specifications to define them. During the development process, the scope of the Foundation widened to include both IVI-C and IVI-COM driver interfaces. As the first group of driver specifications have been released and revised to include COM architecture, implementation questions have been raised by driver developers and system integrators. The Common Code Component Model Group was formed to address concerns of ownership and control of IVI software modules. This paper addresses the user community concerns on ownership, configuration control, release, compliance testing, and others. The IVI Foundation position on each of these concerns is explained. In addition, the status of the development effort will be addressed.","PeriodicalId":334061,"journal":{"name":"2000 IEEE Autotestcon Proceedings. IEEE Systems Readiness Technology Conference. Future Sustainment for Military Aerospace (Cat. No.00CH37057)","volume":"49 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2000-09-18","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"1","resultStr":"{\"title\":\"IVI-a users perspective\",\"authors\":\"P. Johnson\",\"doi\":\"10.1109/AUTEST.2000.885624\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"The Interchangeable Virtual Instrument (IVI) Foundation was formed in 1997 by Instrument manufacturers and integrators desiring the development of instrument driver models which would support instrument changes without requiring test program changes. This was to be accomplished by developing instrument classes and the specifications to define them. During the development process, the scope of the Foundation widened to include both IVI-C and IVI-COM driver interfaces. As the first group of driver specifications have been released and revised to include COM architecture, implementation questions have been raised by driver developers and system integrators. The Common Code Component Model Group was formed to address concerns of ownership and control of IVI software modules. This paper addresses the user community concerns on ownership, configuration control, release, compliance testing, and others. The IVI Foundation position on each of these concerns is explained. In addition, the status of the development effort will be addressed.\",\"PeriodicalId\":334061,\"journal\":{\"name\":\"2000 IEEE Autotestcon Proceedings. IEEE Systems Readiness Technology Conference. Future Sustainment for Military Aerospace (Cat. No.00CH37057)\",\"volume\":\"49 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2000-09-18\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"1\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2000 IEEE Autotestcon Proceedings. IEEE Systems Readiness Technology Conference. Future Sustainment for Military Aerospace (Cat. No.00CH37057)\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/AUTEST.2000.885624\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2000 IEEE Autotestcon Proceedings. IEEE Systems Readiness Technology Conference. Future Sustainment for Military Aerospace (Cat. No.00CH37057)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/AUTEST.2000.885624","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
The Interchangeable Virtual Instrument (IVI) Foundation was formed in 1997 by Instrument manufacturers and integrators desiring the development of instrument driver models which would support instrument changes without requiring test program changes. This was to be accomplished by developing instrument classes and the specifications to define them. During the development process, the scope of the Foundation widened to include both IVI-C and IVI-COM driver interfaces. As the first group of driver specifications have been released and revised to include COM architecture, implementation questions have been raised by driver developers and system integrators. The Common Code Component Model Group was formed to address concerns of ownership and control of IVI software modules. This paper addresses the user community concerns on ownership, configuration control, release, compliance testing, and others. The IVI Foundation position on each of these concerns is explained. In addition, the status of the development effort will be addressed.