The starting point for every application which uses the UModel API is the IApplication interface.
To create an instance of the application object, call WScript.GetObject("", "UModel.Application") from JScript, or a similar function from your preferred development environment, to create a COM object.
|Note:||For 32-bit UModel, the registered name, or programmatic identifier (ProgId) of the COM object is UModel.Application. For 64-bit UModel, the name is UModel_x64.Application.|
There is no need (or other way) to create any objects other than to use the complete UModel API. All interfaces are accessed through other objects, with the application object (IApplication) as the starting point.
|Note:||When implementing a UModel IDE plugin, there is no need to create an instance of the application object, because UModel is already running and the current instance of the application object is provided by IApplication as parameter for all important methods of IUModelPlugIn.|
The application object consists of the following parts (each indentation level indicates a child–parent relationship with the level directly above):
IUMLData (and all other derived UML data interfaces)
Once you have created an application object, you can start using the functionality of UModel. You will generally either open an existing document, create a new one, or access the active document (IDocument).
IDocument corresponds to a UModel project and can be used to include sub-projects, generate documentation, synchronize model and code..., while also giving access to the main UMLData objects (root package, GUI root element, also see Object model UMLData).