Microsoft's Component Object Model Research Articles

Seamlessly Coupling Hydrological Modelling Systems and GIS through Object-Oriented Programming

Coupling hydrological modelling systems (HMS) with a geographic information system (GIS) can significantly enhance hydrological research and expand its applications. The calculation for HMS requires geographic information data; however, the current GIS data structure is not equipped to support the object-oriented hydrological modelling. Due to different objectives and design concepts, the differences between HMS and GIS have been profound, especially in their data structures from the perspective of object-oriented programming (OOP). This research introduces a novel approach to extend ArcGIS data structures for HMS, facilitating seamless coupling. This approach employs Microsoft Component Object Model (COM) technology to construct custom data structures that align with hydrological OOP principles. These can then be integrated into ArcGIS through a custom ArcGIS layer as an add-on. As a result, the HMS can leverage the full functionality of ArcGIS without the need for re-coding existing modelling systems. Moreover, HMS can be readily developed by using COM compatible computer languages, enabling the easy adaptation of this coupling approach to other HMS to ensure computational efficiency and to maximise the benefits of ArcGIS features. This new approach has been successfully implemented with the Xin’anjiang model, and the results validate its effectiveness in coastal areas.

Electrodynamic computations using <i>ANSYS Electronics Desktop</i> software controlled by a program developed in the <i>MATLAB </i>environment

The paper considers methods of controlling the process of electrodynamic structure simulation in the ANSYS Electronics Desktop software (previously known as ANSYS HFSS). The MATLAB software was leading the computation. In order to transmit data to the ANSYS Electronics Desktop software we employed the Microsoft Component Object Model technology, which makes it possible to combine software components into executables. We used simulation of a planar aperture phased antenna array to show the possibilities and limitations in controlling the ANSYS HFSS software subsequently outputting data to a text file and importing the latter into MATLAB for further computation. We present simulation results for a phased antenna array generated by the ANSYS Electronics Desktop software according to the array model compiled in MATLAB

Modules based on the geochemical model PHREEQC for use in scripting and programming languages

The geochemical model PHREEQC is capable of simulating a wide range of equilibrium reactions between water and minerals, ion exchangers, surface complexes, solid solutions, and gases. It also has a general kinetic formulation that allows modeling of nonequilibrium mineral dissolution and precipitation, microbial reactions, decomposition of organic compounds, and other kinetic reactions. To facilitate use of these reaction capabilities in scripting languages and other models, PHREEQC has been implemented in modules that easily interface with other software. A Microsoft COM (component object model) has been implemented, which allows PHREEQC to be used by any software that can interface with a COM server—for example, Excel ®, Visual Basic ®, Python, or MATLAB ®. PHREEQC has been converted to a C++ class, which can be included in programs written in C++. The class also has been compiled in libraries for Linux and Windows that allow PHREEQC to be called from C++, C, and Fortran. A limited set of methods implements the full reaction capabilities of PHREEQC for each module. Input methods use strings or files to define reaction calculations in exactly the same formats used by PHREEQC. Output methods provide a table of user-selected model results, such as concentrations, activities, saturation indices, and densities. The PHREEQC module can add geochemical reaction capabilities to surface-water, groundwater, and watershed transport models. It is possible to store and manipulate solution compositions and reaction information for many cells within the module. In addition, the object-oriented nature of the PHREEQC modules simplifies implementation of parallel processing for reactive-transport models. The PHREEQC COM module may be used in scripting languages to fit parameters; to plot PHREEQC results for field, laboratory, or theoretical investigations; or to develop new models that include simple or complex geochemical calculations.

Application of Function Deployment Model in Decision Making for New Product Development

In this study, a novel model called Function Deployment Model (FDM) for decision making in new product development is introduced. To demonstrate its usefulness pragmatically, the model is applied to the design problem of development of the micro/nano injection molding machine. Based on the Quality Function Deployment (QFD) technique, this model translates the customer needs to engineering characteristics. An Analytic Hierarchy Process (AHP) is used to prioritize customer requirements while a Linear Programing (LP) optimization method is used to determine the feasible solution of the design variables within limited resources. Also, a program with a tailor-made graphical user interface (GUI) using MATLAB library and Microsoft Component Object Model (COM) technology is implemented to guide the design engineers to employ the proposed methodology for decision making.

A case-based shape conceptualization system for supporting creative product design

This article attempts to explore the extent of the usefulness of computer-aided design tools applied in the conceptual design of a new product. Conceptual design is one of the most important steps in deriving the engineering characteristics and, more importantly, the expression in geometric shapes of a new product from customer requirements. However, current computer-aided systems are not capable of supporting this crucial design stage. This study proposed a computer-aided shape conceptualization design system that employs the use of morphological analysis together with functional analysis. Then, methods with a discursive bias are employed to assist a designer to generate concepts and search for solutions for a specified product. In addition, the proposed prototype system used the programming techniques of VB to create user interfaces for accessing the CATIA objects within a Microsoft Component Object Model environment. The solution principles, defined as feature-based computer-aided design models, can be stored in and retrieved from Excel spreadsheets. The case study of manually operated screwdrivers has demonstrated that the proposed shape conceptualization design system is capable of generating various design layouts to meet the product requirements.

STAO: a component architecture for raster and time series modeling

Implementation of spatially distributed models using Geographic Information System (GIS) involves accessing and processing of spatial and time series data. Most of the GIS software do not provide an explicit functionality to support handling of time series data in modeling and also requires exclusive client storage of one-dimensional array for raster data access. This paper describes an attempt to overcome such short comings by developing Spatial and Time series data Access Objects (STAO) using Microsoft's Component Object Model (COM ®). STAO has advanced enough modeling objects which are developed for the raster and time series data access and analysis while they are simple enough for the user to implement them in spatial models in a variety of native proprietary formats. The STAO architecture defined in this study has multiple advantages in terms of interoperability, reusability, and extendibility. The usefulness of these objects has been demonstrated by implementing: (1) the USDA's Soil Conservation Service (SCS) method of rainfall runoff estimation and (2) an algorithm for finding time area diagram at sub-watershed level. The results of implementing SCS using STAO in Kolli Hills watershed is discussed and the computed runoff values are in good agreement with field observed values.

Where is is middleware

Middleware is all about integration. Middleware has existed in various forms for many years in systems such as the IBM Customer Information Control System (CICS), numerous message queuing systems such as IBM's MQ Series, the Common Object Request Broker Architecture (CORBA), Microsoft's Component Object Model (COM), Java 2 Enterprise Edition (J2EE), and the latest rage, Web services. Virtually every form of application, programming language, operating system, and hardware has been a target of an integration effort involving these middleware systems or their cousins. Middleware is everywhere.

Connecting Lisp-Stat to COM

This article describes an interface between Lisp-Stat and Microsoft's Component Object Model (COM). This interface can be used, for example, to retrieve data stored in a spreadsheet or a database. After providing some brief background on Lisp-Stat and COM, the interface is presented through a series of examples. Issues in implementation and integration relevant to other statistical systems and other component systems are discussed.

Integration of legacy sub-system components into an object-oriented simulation model of a complete pastoral dairy farm

An object-oriented (OO) approach to developing a computer simulation of a complete pastoral dairy farm system is outlined. Since component models already existed which encapsulated the functionality of the high level objects in the overall system it was a primary design goal to be able to incorporate them into the OO framework. These components had been developed in procedural programming languages and techniques were investigated to incorporate them with little or no re-coding, and which allow them to be used in an ‘object-like’ way. The techniques involved recompilation of legacy source-code as dynamic link libraries (DLL's), and accessing stand-alone executable programs through inter-process communication (IPC) protocols. A cow metabolism model developed in the proprietary ACSL environment, and a pasture growth model for which FORTRAN source code was available were incorporated into the Smalltalk OO framework using the Microsoft Component Object Model (COM) techniques. Multiple instances of each component (each representing a distinct real farm entity) were required by the OO framework and the COM methodology was able to support this. The integration of these components into the host OO framework involved using proxy objects to provide translation to/from the COM messaging, thus providing the OO framework with consistent inter-object communication.

Calling hell from heaven and heaven from hell

The increasing popularity of component-based programming tools offer a big opportunity to designers of advanced programming languages, such as Haskell. If we can package our programs as software components, then it is easy to integrate them into applications written in other languages.In earlier work we described a preliminary integration of Haskell with Microsoft's Component Object Model (COM), focusing on how Haskell can create and invoke COM objects. This paper develops that work, concentrating on the mechanisms that support externally-callable Haskell functions, and the encapsulation of Haskell programs as COM objects.

Analysis of a conflict between aggregation and interface negotiation in Microsoft's Component Object Model

Many software projects today are based on the integration of independently designed software components that are acquired on the market, rather than developed within the projects themselves. A component standard, or integration architecture, is a set of design rules meant to ensure that such components can be integrated in defined ways without undue effort. The rules of a component standard define, among other things, component interoperability and composition mechanisms. Understanding the properties of such mechanisms and interactions between them is important for the successful development and integration of software components, as well as for the evolution of component standards. The paper presents a rigorous analysis of two such mechanisms: component aggregation and dynamic interface negotiation, which were first introduced in Microsoft's Component Object Model (COM). We show that interface negotiation does not function properly within COM aggregation boundaries. In particular, interface negotiation generally cannot be used to determine the identity and set of interfaces of aggregated components. This complicates integration within aggregates. We provide a mediator-based example, and show that the problem is in the sharing of interfaces inherent in COM aggregation.

Modern languages and Microsoft's component object model

article Free Access Share on Modern languages and Microsoft's component object model Authors: David N. Gray Harlequin Inc., Menlo Park, CA Harlequin Inc., Menlo Park, CAView Profile , John Hotchkiss Harlequin Inc., Cambridge, MA Harlequin Inc., Cambridge, MAView Profile , Seth LaForge Harlequin Inc., Seattle, WA Harlequin Inc., Seattle, WAView Profile , Andrew Shalit Harlequin Inc., Cambridge, MA Harlequin Inc., Cambridge, MAView Profile , Toby Weinberg Harlequin Inc., Cambridge, MA Harlequin Inc., Cambridge, MAView Profile Authors Info & Claims Communications of the ACMVolume 41Issue 5May 1998 pp 55–65https://doi.org/10.1145/274946.274957Published:01 May 1998Publication History 29citation1,057DownloadsMetricsTotal Citations29Total Downloads1,057Last 12 Months38Last 6 weeks4 Get Citation AlertsNew Citation Alert added!This alert has been successfully added and will be sent to:You will be notified whenever a record that you have chosen has been cited.To manage your alert preferences, click on the button below.Manage my Alerts New Citation Alert!Please log in to your account Save to BinderSave to BinderCreate a New BinderNameCancelCreateExport CitationPublisher SiteeReaderPDF

The promise of distributed business components

This paper discusses the advantages of replacing hand-crafted software with reusable components as a solution to the software crisis. Object-oriented programming provides insights on how to build components. Because components must have distributed implementations and well-defined interfaces, both the Microsoft Component Object Model (COM) and the Object Management Group (OMG) Common Object Request Broker Architecture (CORBA) models are described as distributed object architectures to support reusable components. A transaction processing monitor is also necessary for accessing business logic and the information contained in relational databases. Components are composed of object-oriented frameworks based on models of the problem domain or business.