Remigijus Gustas Department of Information Systems, Karlstad University, Sweden

1. Integration of Interactive, Behavioral and Structural Aspects of Conceptual Models Remigijus Gustas Department of Information Systems, Karlstad University, Sweden PoEM 2010, Delft

2. Underlying principles of conventional Conceptual Modeling Approaches • EM methods distinguish disparate views/dimensions (Zachman, 1987). • UML individual diagram types are clear enough, but the semantic integration principles are quite vague. • Traditional way of modeling creates difficulties in reaching integrity and consistency among various diagram types. Remigijus Gustas

3. Description of a conference management system One of the authors plays the role of contact personwho submits a paper to a conference. The responsibility of a conference program committee (PC) chair is to appointreviewers for every submission. The reviewer is obliged to return reviewof the paper to the PC chairon time. Depending on the reviewing outcome, the PC Chairis authorized to accept or rejecta submitted paper.If the paper is accepted, then revision instructions are sent to the corresponding contact person. Otherwise, reviewer comments are included in the rejection letter. Remigijus Gustas

4. Interactions of a conference review management system

5. Activities in a conference review management system

6. Use case diagram

7. Activities in a conference review management system

8. Events and Transitions of a Paper Object

9. Classes, Attributes and Associations

10. Modeling Approach: Integration of Static and Dynamic Aspects • Enterprise system is defined as a set of interacting, loosely coupled subsystems, • Interaction and value flows can be explicitly captured, • When subsystems interact, they cause certain classes of objects to change. • Changes are manifested via properties, which are represented by class attributes, • Interactive, structural and behavioral aspects of conceptualizations are combined together in a single view.

11. Identification of interaction flows and static dependencies among actors

12. Flows can be Information, Material or Control

13. Examples of Service Interactions

14. Basic SO Modeling Constructs

15. Representation of Interactive and Behavioral Aspects of Conceptualizations

16. Subsystem Flow Flow Flow Action Action Action Subsystem Subsystem Action Action Flow Subsystem

17. Complementary Interactions

18. Diagram with the alternative Withdraw action

19. Four cases of Withdraw in State-Transition Diagram

20. Four cases of Withdraw in Activity Diagram

21. Conclusions • Most information system design methodologies fail to link interactions with state changes in terms of triggering effects. • The presented modeling approach introduces a single type of diagram. It is capable to capture, in concise form, the semantics of the behavioral effects and structural changes, which are justified by the interaction flows. • Using a semantically integrated way of modeling helps to detect inconsistencies and incompleteness of conceptualizations. • The similarity of conceptual models before and after adding evolutionary requirements, demonstrates the stability of the proposed modeling approach (in comparison with UML).

22. Stijn’s (4) Questions • 1. How does the paper relate to actual, industrial practice of enterprise modeling? Comparison with UML, based on a small case study, • 2. What would be the main message you would like practitioners to remember concerning your paper? Integration and evolution of diagrams is very difficult in UML • 3. How does the paper relate to applied theory development for enterprise modeling? Demonstrates totally different way of modeling • 4. What would be the main message you would like academics to remember concerning your paper? Modeling approach for semantic integration of static and dynamic aspects at conceptual level