Die Johannes Kepler Universität Linz - Christoph

Reflects the often hierarchical organization of the company. □ Strategic, Administrative, Operative layers. □ Top management concerned with strategic decisions in which markets the company is active;. □ Administrative units work on the categories;. □ Operative units work on particular product models. □ The hierarchical ...
2MB Größe 2 Downloads 66 Ansichten
Multilevel Business Artifacts Christoph Schütz, Lois M. L. Delcambre, Michael Schrefl

Overview ■ Motivation ■ Multilevel Business Artifacts □ Multilevel Object □ Multilevel Object + Life Cycle Models

■ Multilevel Concretization □ Behavior-consistent Specialization □ Meta-process Modeling

■ Metamodel and UML Semantics ■ Discussion and Related Work ■ Summary and Future Work JKU Linz  Institut für Wirtschaftsinformatik – Data & Knowledge Engineering

2

Motivation ■ Many modeling situations are better represented using multilevel abstraction hierarchies □ For example: Product models are organized in categories.

■ Reflects the often hierarchical organization of the company □ Strategic, Administrative, Operative layers □ Top management concerned with strategic decisions in which markets the company is active; □ Administrative units work on the categories; □ Operative units work on particular product models.

■ The hierarchical levels do not work in isolation but are interdependent and need coordination. JKU Linz  Institut für Wirtschaftsinformatik – Data & Knowledge Engineering

3

Multilevel Objects + Life Cycle Models

MULTILEVEL BUSINESS ARTIFACTS

Multilevel Object (M-Object) ■ Neumayr et al. (2009) ■ Multiple levels of abstraction ■ For all levels: Class schema ■ Top level: Class instance

JKU Linz  Institut für Wirtschaftsinformatik – Data & Knowledge Engineering

5

Multilevel Business Artifact (MBA) M-Object + Life Cycle Models

JKU Linz  Institut für Wirtschaftsinformatik – Data & Knowledge Engineering

6

Coordination of Levels

JKU Linz  Institut für Wirtschaftsinformatik – Data & Knowledge Engineering

7

Behavior-consistent Specialization, Meta-process Modeling

MULTILEVEL CONCRETIZATION

Multilevel Concretization

JKU Linz  Institut für Wirtschaftsinformatik – Data & Knowledge Engineering

9

Aggregation

JKU Linz  Institut für Wirtschaftsinformatik – Data & Knowledge Engineering

10

Instantiation

JKU Linz  Institut für Wirtschaftsinformatik – Data & Knowledge Engineering

11

Specialization

JKU Linz  Institut für Wirtschaftsinformatik – Data & Knowledge Engineering

12

Specialization of Life Cycle Models

JKU Linz  Institut für Wirtschaftsinformatik – Data & Knowledge Engineering

13

Extension

JKU Linz  Institut für Wirtschaftsinformatik – Data & Knowledge Engineering

14

Refinement

JKU Linz  Institut für Wirtschaftsinformatik – Data & Knowledge Engineering

15

Meta-process Modeling ■ Concretization is not a one-shot activity ■ Immediately after creation of MBA, only inherited features

JKU Linz  Institut für Wirtschaftsinformatik – Data & Knowledge Engineering

16

Meta-process Modeling ■ Attributes, methods, transitions, states are added by the modeler

JKU Linz  Institut für Wirtschaftsinformatik – Data & Knowledge Engineering

17

Meta-process Modeling

JKU Linz  Institut für Wirtschaftsinformatik – Data & Knowledge Engineering

18

Formal Definition

METAMODEL AND UML SEMANTICS

Metamodel

JKU Linz  Institut für Wirtschaftsinformatik – Data & Knowledge Engineering

20

UML Semantics Each MBA corresponds to one aggregation hierarchy together with the instance of the top-level class.

JKU Linz  Institut für Wirtschaftsinformatik – Data & Knowledge Engineering

21

UML Semantics MBA Tour (Top level: range)

JKU Linz  Institut für Wirtschaftsinformatik – Data & Knowledge Engineering

22

UML Semantics MBA CityTour (Top level: category)

JKU Linz  Institut für Wirtschaftsinformatik – Data & Knowledge Engineering

23

UML Semantics MBA PacificCityTour (Top level: package)

JKU Linz  Institut für Wirtschaftsinformatik – Data & Knowledge Engineering

24

Discussion and Related Work ■ In current process modeling approaches, abstraction refers more to the blinding out of details ■ Flexibility in process modeling seems to be an important issue □ Recent paper on process design business entities (PD entities) by Liu et al. (2012)

■ Behavior-consistent specialization of life cycle models □ Yongchareon et al. (2012): Specialization of interactions between process models

JKU Linz  Institut für Wirtschaftsinformatik – Data & Knowledge Engineering

25

Summary and Future Work ■ MBAs extend m-objects with process models ■ Coordination of tasks at different levels within a company ■ Provide flexibility with multilevel concretization ■ Future work: □ Relationships between MBAs on multiple levels of abstraction □ Information about the actors who carry out tasks □ Implementation

JKU Linz  Institut für Wirtschaftsinformatik – Data & Knowledge Engineering

26

References ■ Neumayr, B., Grün, K., Schrefl, M.: Multi-level domain modeling with m-objects and m-relationships. In: 6th AsiaPacfic Conference on Conceptual Modeling, 2009. ■ R. Liu, F. Y. Wu, F. Pinel, and Z. Shan. A two-tier data-centric framework for exible business process management. In: AMCIS '12, 2012. ■ S. Yongchareon, C. Liu, and X. Zhao. A framework for behavior-consistent specialization of artifact-centric business processes. In: BPM '12, LNCS, vol. 7481, 2012.

JKU Linz  Institut für Wirtschaftsinformatik – Data & Knowledge Engineering

27