Semantic Object Model (SOM)

Keywords: Enterprise Information Systems

Affiliation: University of Vienna

FAQ

In the following, frequently asked questions according to the handling of the SOM multi-view business process modeling tool, are listed. If your question is not covered yet, do not hesitate to ask me directly (dominik.bork@univie.ac.at).

List of questions:

How do I add additional environmental objects and enforcing transactions?

Additional environmental objects and enforcing transactions can be added to the initial SOM business process model by selecting the menu 'Organize Model' and then the respective menu item.

Hint: Additional enforcing transactions can only be added if the SOM model, i.e. the decomposition level currently visible in Interaction Scheme and Task-Event Scheme is on the initial level.

Hint: If you want to add an additional environmental object, the tool asks you, where to place the object geographically in the Interaction Scheme). Note, the addition of an environmental object requires the addition of an enforcing transaction as well.

How do i delete business objects and business transactions?

Deletion in the SOM modeling tool can only be performed using the context menu of the objects and transactions respectively. Please use the 'Revoke decomposition' menu item if you want to undo and already performed decomposition.

The additionally added enforcing transactions and business objects can be removed only by using the 'Organize Model' menu. Here, specific remove operations can be triggered.

How can i specify the behaviour of the business process model within the Task-Event Schema (TES)?

The behaviour of the business process model can be specified by activating / clicking in the Task-Event Schema. Afterwards, the modeler can select the VES_Connector element from the Modeling Palette shown on the left hand side of the modeling area.

After the 'VES_Connector' is selected, the modeler can click on two 'Tasks' within the Task-Event Schema in order to connect them with the relation. The relation is automatically routed, i.e., the first Task is used as outgoing object, the second Task as ingoing object.

The modeler may delete the relationships between the tasks, NOT the transactions, manually by selecting them and pressing 'DEL' on the keyboard.

Why is no drag & drop modeling supported by the tool?

The ADOxx modeling tool for SOM is strictly aligned to the SOM modeling method (cf. Ferstl and Sinz, Grundlagen der Wirtschaftsinformatik, Oldenbourg Verlag). The SOM method specifies very precisely concrete decomposition rules that need to be followed by the modeler. As a result, the modeling tool does not support drag & drop editing of the SOM models.

In order to further detail the initial business process model, the decomposition rules must be applied to business transactions and business objects, respectively. Respective modeling operations can be triggered within the context menu of business objects and business transactions. The modeler can choose between all decomposition rules, supported by the SOM method.

If the modeler realizes, that a formerly applied decomposition was not correct according to the semantics of the case, the 'Revoke decomposition' operator that is also included in the context menu of the business objects and business transactions in the decomposition trees can be executed. The tool then deletes the former decomposition and allows the modeler to once again decompose the object or transaction.

What is the difference between zooming and increase/decrease decomposition level?

There is major difference between zooming in and out of a SOM business process model and increasing/decreasing the business process level.

The zooming operator, which can be applied in the context menu of the decomposition tress, allows the modeler to immediately switch between different, formerly defined decomposition levels of the SOM model. It is important to note, that the application of the zooming operator does not imply any changes on the business process model or the connections between business transactions and business objects. By contrast, zooming can be applied as a visualization operator, i.e., to switch/visualize different decomposition levels.

The increase/decrease operator on the other hand change the SOM business process model every time they are executed. This means, that each time the increase operator is applied, the connections between business objects and business transactions on the next higher decomposition level is stored within the SOM business process model. Consequently, applying the decrease business process level operator not only visualizes a less detailed SOM business process level, it also removes the information about how the business objects have been connected to the business transactions on the former (i.e., higher) decomposition level.

How can I generate the Schema of Conceptual Classes (COS)?

The Schema of Conceptual Classes (COS) can be generated completely automatically by triggering the 'Generate Schema of Conceptual Classes' operator within the menu 'Model Transformation'.

The tool transforms the information gathered in the four business process models into a newly created model called 'BPMN' which will be stored within the same model group as the SOM business process model. The modeler is able to further process the generated model, however no backlink to the SOM business process model is implemented. The model is created as a snapshot of the business process model, taken at a certain point in time.

How can I generate the Schema of Task Classes (TAS)?

The Schema of Task Classes can be generated by selecting the 'Generate Schema of Task Classes' operator in the 'Model Transformation' menu. After triggering the transformation, the tool requires the modeler to select the considered business objects for the transformation. Multiple selections allow the modeler to select one, two, or up to all business objects that occur in the SOM business process model.

The tool then applies a meta model based model transformation and relates the different TAS sub-models with each other. The modeler may further process the generated model, however no backlink to the SOM business process model is implemented. The model is created as a snapshot of the business process model, taken at a certain point in time.

How can I generate the Business Process Modeling and Notation model (BPMN)?

The BPMN transformation ca be triggered by selecting the 'Generate BPMN' operator in the 'Model Transformation' menu. The modeling tool creates a new modeling window and performs the transformation automatically according to a meta model-based mapping specification (cf. Pütz and Sinz, 2010).

The modeler may further process the generated model (e.g., adding sub-processes or moving tasks to new pools), however no backlink to the SOM business process model is implemented. The model is created as a snapshot of the business process model, taken at a certain point in time.

How can I export SOM models into graphics?

ADOxx provides the functionality to export any models into standard graphics formats. In order to do so, select the 'Generate graphics' menu item. Afterwards, a dialog window shows up indicating the area of the current model that should be considered in the export. You can select the relevant part and the graphics format you want to export to. Afterwards the graphics file is created and stored on the defined file path on your local system. The following figure illustrates the graphics export functionality, the menu item is highlighted by a red rectangle.

What is the 'sa' password that is required during the installation fo SOM 3.0?

NOTICE: If you haven't had already an SQL Server installed, the installation routine will do it automatically. The initial 'sa' password is then '12+*ADOxx*+34' (without the ').

If you already had a SQL Sevrer installed, you need to know your sa password. If you cannot remember your 'sa' password, the ADOxx.org community provides help.