Component object model, COM

A component-based prototype for intrusion detection and response has been realized. It is based on Microsoft s component architecture, the Component Object Model (COM) and its extension, the Distributed Component Object Model (DCOM). 

Component Object Model (COM) is an object-oriented system for creating binary software components that can interact. COM is the foundation technology for Microsoft s OLE (compound documents) and ActiveX (Internet-enabled components). 

To overcome these problems in the IT world, the industry has developed a component object model (COM) which basically defines what an object is and how it should relate to other objects. COM therefore allows software from different manufacturers to work together and is one of the things that makes such everyday functions such as "drag and drop" so easy to use. (The application you are dropping into needs to understand the format of what you are dropping, and the application you are dragging from needs to know how to how to place the data or object onto the "clipboard"). 

What is OPC This is another tool for system integration. OPC is open connectivity in industrial automation for interoperability supported by the creation and maintenance of open standards and specifications. OPC is a standardized interface for accessing process data. Object linking and embedding (OLE), component object model (COM)/distributed component object model (DCOM), was developed by Microsoft. When this is applied to the process control, OPC (OLE for process control) is developed. OPC is based on the Microsoft COM/DCOM standard and has been expanded according to the manufacturer s requirements. 

On a larger scale, self-contained application programs can be driven by each other object linking and embedding/Component Object Model (OLE/COM), UNIX pipes and signals, and Apple events allow this to happen. Communicating components can be written in different languages, and each can execute in its own space. 

Today, pharmaceutical companies are linking CDS to business systems such as SAP, chemical structure databases, electronic laboratory notebooks, and corporate data warehousing solutions. Many commonly used software products utilize COM Automation (Microsoft s Component Object Model) to provide a powerful array of programmable objects that allow seamless connections between applications. 

Specifying how the InterprocessCall relations will be implemented are the final steps of architecture refinement. As the COMOS PT API is implemented by the tool s vendor using COM (Component Object Model [846]), the InterprocessCall relation between the COMOS PT TechWrapper and the COMOS PT API is simply refined into a. COMCaII (cf. box 5 of Fig. 5.58). In case of the InterprocessCalI relation between the Integrator Tool and the COMOS PT HomWrapper, different alternatives are possible. 

In the context of IMPROVE, commercial and third-party tools had to be integrated into the engineering design environment. They were mostly equipped with a COM interface (e.g. Aspen Plus, Comos PT, or Documentum). Hence, our approach concentrated on COM (Component Object Model [846])" . COM follows the object-oriented paradigm, i.e. COM components represent subsystems, consisting of a set of classes including attribute and method definitions, relationships between classes, and a set of interfaces to access the subsystem. For every COM interface, fixed by standardization, a textual description is available in form of a so-called type library or a dynamic link library, respectively. 

Microsoft Component Object Model (2006), http //msdn.microsoft.com/ library/default.asp url=/library/en-us/dnanchor/html/component objectmodelanchor.asp... 

COM has been further enhanced to operate across multiple platforms in a network environment and in a distributed manner. This is known a D-COM (distributed component object model), but even D-COM fails to address... 

---