Component Integration #16978/HEAD / v10 |
Tags:
not added yet
Model Development by Component Integrationmodel is a specific assembly of components that gets created using a visual model editor. This section introduces the supporting (visual) tools that allow the model creation model component assembly. Before you can build a model, a new and empty model file can be created using the Model creation wizard. Model Creation WizardThe model wizard allows the creation of a new model that can be used for visual model editing. To invoke the wizard, right click on the Models node in your project view and select New | Model. You are asked to provide a name for the new model and then finish the wizard. You can also right-click on the Project's Model folder and select New | Model to start the wizard. A new model file gets created and it opens for editing. OMS models do have the extension *.jma. You can always open a model by double clicking on a model jma file.
Model EditorThe model editor is the user interface element you see when you open a model. An overview of its user interface elements is shown in the picture below. The model editor relates to and consists of several user interface windows and parts.
The following sections describe the different parts that support the management of components within a model such as adding/removing components or managing the way how a component links to other parts of the model. Model Assembly ProcessAdding a component to a ModelYou can add components into a model by dragging them from the Component Library explorer into the Model Editor window. This requires the components to be compiled into a component archive. When you drop a component into a model, the dialog below shows up. The dialog shows a tree of nodes that can be chosen for attribute declaration. Since each component provides a list of attributes it wants to connect to this dialog ask for the location where these attributes should be declared. Declaring an attribute means allocating space for it in the model (or creating the attribute object). Attributes can be declared at different scopes within the model. The model scope is the root scope and always present. In the example above the TimeLoop scope is also shown. This scope was introduced from a TimeLoop component. You select the appropriate scoping level for attribute declaration. Declared Attributes need to be connected to the component. If you select the Checkbox Hookup all declared attributes? the component connects to all attributes that were declared before. If the Hookup only check box is selected no attributes will be declared. It connects to existing model attributes only. The Figure above shows the declared attributes for a selected node in a model. When selecting a declared attribute here, the Properties window shows its properties that are either real only or can be edited. All this information was introduces into the model when adding a component. Removing a component from a ModelA model can be removed from a model by selecting its node in the model editor and pressing Delete or selecting Delete from the right mouse context menu. If you delete a component from a model, all attributes declared by this model will stay there since other components might still use them. You check for and can clean up unused attributes Changing Component Attributes ConnectionsComponents are connected to declared Attributed in the model. The Hookups window lists all Attribute Connections for a selected component in the model editor. The Component Connectivity node contains all component attributes as sub nodes as seen in Figure below. Each entry in this list consists of two parts, the 'Component Attribute' that is connected to the 'Declared Attribute' in the model. The connection is indicated by the arrow symbol (->). In the given example above, the component attribute temp points to the model attribute /TimeLoop@temp. temp -> /TimeLoop@temp The Notation /TimeLoop@temp references the attribute named temp that resides in the TimeLoop scope. Such a Notation is called MPath (it is somehow related to XPath syntax) In MPath:
Viewing the Declared Attributes.The model editor can switch its view from a structural view showing the component execution sequence to a view that lists all declared attributes. Click on the Attributes Button in the model editor's tool bar. The view changes as its shown in the Figure below. The right part of this panel allows for the navigation within all attributes of a model. You can filter the attribute list by
Model ExecutionA model can be executed from the Model Editor window. Select the model node in the model editor or the model file in the model project. You can press Shift + F6 to run the model or select in the main menu Run | Run File | Run "model.jma to execute the active model. The model is then being executed using the selected Executor from the model executor settings. Model Executor SettingsOMS supports various ways to execute a model. This is configured by selecting the so called Excecutor in the properties window of a model. There following executors are available:
You can assign the proper executor to your model by clicking on the model file (jma) and choose in the Properties window the right executor using the provided combo box. This selection will be stored in your model. |
Navigation Bar for Object Modeling System
Resources:
Downloads You must login to see this link. Register now, if you have no user account yet. OMS API Javadoc Publications & Presentations Annotation Reference DSL Reference Handbook 3.0 (Draft) Frequently Asked Questions (FAQ) OMS License (LGPL 2.1) New Users: 1. Get an ALM account 2. Join the OMS project Contact Us: Jack Carlson Coordinator, OMS Laboratory OMS Laboratory Jack.Carlson@colostate.edu (970) 492-7323 Olaf David Director, OMS Laboratory odavid (at) colostate.edu (970) 491-8026 |