Software interoperability

Expanding Process Modelling Capability through Software Interoperability Standards Application, Extension and Maintenance of CAPE OPEN standards... 

CAPE OPEN standards have been developed to the state of maturity where standards are finding application in industrial and academic applications. The need for further standards has been identified as well as sustaining existing standards. To be successful standards also need to be maintained and supported. Developments in applying, extending and maintaining software interoperability standards to expand Process Modelling Capability will be presented. 

Data standards and interoperable systems. When interoperability is in place, standard, automated software tools for systematically analyzing the data can be constructed. 

In component-based development, you must constmct software from components whose insides you can t see you must treat them as black boxes. When you constmct your own components, you m ust build them so that they will work with a wide variety of others even as their internal implementations change or are upgraded. Components that aren t interoperable have little value. For that reason, we are interested in separating external specification of behavior from the internal works. (This has been the situation in hardware for years that it s novel to our profession should perhaps be an issue of some embarrassment for us.)... 

Integration of instrumentation with the operational informatics infrastructure is a critical requirement to keep HTS workflow efficient and error-free. Different proprietary vendor software and platform incompatibilities can complicate system integration and in most cases, some software development effort and/or consulting services from the instrumentation and software vendors will be required. Interoperability and ease of integration should also be considered when designing an HTS operation. 

The model developer who wants to couple the models (1) has to include coupler-specific interfaces in the models, and (2) has to provide the model and coupling meta-data according to standards of the coupling software. Both tasks can be time consuming, and the gain of interoperability has to be balanced against the costs of the implementation. 

Promote and, if needed, develop software tools for ESM. A tool must be portable, usable independently and interoperable with the other PRISM tools, and freely available for research. There should be documented interest from the community to use the tool and the tool developers must be ready to provide user support... 

OSF Open Software Foundation a computing industry group that defines particular standards for operating and interoperating system software. 

Carney, D., Fisher, D., Morris, E., Place, P. Some current approaches to interoperability. Technical Report CMU/SEI-2005-TN-033, Carnegie Mellon University, Software Engineering Institute, SEI (2005)... 

Currently, all vendors provide software conforming to the DICOM standard, and agree to a commitment to that effect to all customers. Compliance with this standard establishes a common format for imaging systems connecting hardware and software components, and allows interoperability for transfer of images and associated information among multiple vendors devices. The DICOM standard is particularly useful in the implementation of the Picture Archival and Communication System (PACS), which is discussed here. 

Biological methodology in our everyday IT promises a kind of uniformity and interoperability that will encompass both medical and nonmedical computing, and mediation with implanted chips. This biology in IT is a methodology apart from neural nets, which are smart learning networks based on brain principles, represented in software. The changes of interest here are at the hardware level. It is probable that all traditional computer system architecture, medical and otherwise, will soon make the first steps to a transition to a deeper... 

Effort by the CMA will be needed to detect and overcome some natural, negative tendencies inherent in the site-focused management approach. It may even be necessary to limit site manager independence in selecting replacement equipment and software to ensure maximum interoperability. It is important that ECPs be shared between sites so that problems that could well affect more than one site need be solved only once and in a coordinated manner. Evidence shows that this objective has been recognized and appropriate action taken to maximize sharing under the mandatory lessons learned program. ... 

As consumers of ERP systems, manufacturers and their trading partners face the risk of being stranded when their systems do not interoperate. The lack of interoperability in manufacturing supply chains can create significant costs (Brunnermeier and Meutin 1999), tmd those costs tend to be hidden. More accurate cost structures must be developed for information goods, particulady for buy-configure-build software applications. Unlike off-the-shelf software applications, ERP systems are more like traditional assets, in the business sense, with capital costs and ongoing operational costs. 

The CIM Framework architecture is a layered system that enables distributed, object-oriented applications assembled from common software components to interoperate as a single, integrated system. 

---