BPMN and Beyond Business process modelling notation, workflow ...

More documents

Recommendations

Info

14 Bernhard Thalheim and Klaus-Dieter Schewe 2. A. Binemann-Zdanowicz and B. Thalheim. Modeling of information services on the basis of ASM semantics. In ASM’2003, LNCS 2589, pages 408 – 410. Springer, 2003. 3. E. Börger. Discrete systems modeling. Enclopedia of Physical Sciences and Technology, Academic Press, 2001. 4. E. Börger and R. Stärk. Abstract state machines - A method for high-level system design and analysis. Springer, Berlin, 2003. 5. G. Fliedl, C. Kop, W. Mayerthaler, and H. C. Mayr. NTS gestützte Vorentwurfsschemaeinträge aus natürlichsprachlichen Anforderungsdefinitionen. In Natürlichsprachlicher Entwurf von Informationssystemen, pages 260–279, Konstanz, 1996. Universitätsverlag Konstanz. 6. D. Goldin, S. Srinivasa, and B. Thalheim. IS = DBS + interaction - towards principles of information systems. In A. H. F. Laender, S. W. Liddle, and V. C. Storey, editors, ER, volume 1920 of LNCS, pages 140–153. Springer, 2000. 7. J. Lewerenz. Human-computer interaction in heterogeneous and dynamic environments: A framework for its conceptual modelling and automatic customization. PhD thesis, Brandenburg University of Technology at Cottbus, Faculty Mathematics, Natural Sciences and Computer Science, 2000. 8. G. Schellhorn. ASM refinement and generalizations of forward simulation in data refinement: A comparison. Theor. Comput. Sci., 336(2-3):403–435, 2005. 9. K.-D. Schewe and B. Thalheim. Conceptual modelling of web information systems. Data and Knowledge Engineering, 54:147–188, 2005. 10. K.-D. Schewe and B. Thalheim. Component-driven engineering of database applications. In APCCM’06, volume CRPIT 49, pages 105–114, 2006. 11. K.-D. Schewe and B. Thalheim. Design and Development of Web Information Systems. Springer, 2008. Forthcoming book. 12. K.D. Schewe and B. Thalheim. Web information systems: Usage, content, and functionality modelling. Technical Report 2004-3, Christian Albrechts University Kiel, Institute of Computer Science and Applied Mathematics, Kiel, 2004. 13. B. Thalheim. Entity-relationship modeling – Foundations of database technology. Springer, Berlin, 2000. 14. B. Thalheim. Readings in fundamentals of interaction in information systems. Reprint, BTU-Cottbus, accessible through http://www.is.informatik.unikiel.de/∼thalheim, Collection of papers by C. Binder, W. Clauß, A. Düsterhöft, T. Feyer, T. Gutacker, B. Heinze, J. Lewerenz, M. Roll, B. Schewe, K.-D. Schewe, K. Seelig, S. Srinivasa, B. Thalheim, 2000. 15. P. Wegner and D. Goldin. Interaction as a framework for modeling. In P. P. Chen, J. Akoka, H. Kangassalo, and B. Thalheim, editors, Conceptual Modeling, Current Issues and Future Directions, Selected Papers from the Symposium on Conceptual Modeling, Los Angeles, California, USA, held before ER’97, volume 1565 of LNCS, pages 243–257. Springer, Berlin, 1999. 16. W. Zimmermann and B. Thalheim. Preface. In ASM 2004, number 3052 in LNCS, pages V–VII, Berlin, 2004. Springer.
Extended Entity-Relationship Model Bernhard Thalheim Christian-Albrechts University Kiel, http://www.informatik.uni-kiel.de/∼thalheim SYNONYMS EERM, HERM; higher-order entity-relationship model; hierarchical entity-relationship model DEFINITION The extended entity-relationship (EER) model is a language for defining the structure (and functionality) of database or information systems. Its structure is developed inductively. Basic attributes are assigned to base data types. Complex attributes can be constructed by applying constructors such as tuple, list or set constructors to attributes that have already been constructed. Entity types conceptualise structuring of things of reality through attributes. Cluster types generalise types or combine types into singleton types. Relationship types associate types that have already been constructed into an association type. The types may be restricted by integrity constraints and by specification of identification of objects defined for a type. Typical integrity constraints of the extended entity-relationship model are participation, look-across, and general cardinality constraints. Entity, cluster, and relationship classes contain a finite set of objects defined on these types. The types of an EER schema are typically depicted by an EER diagram. HISTORICAL BACKGROUND The entity-relationship (ER) model was introduced by P.P. Chen in 1976 [1]. The model conceptualises and graphically represents the structure of the relational model. It is currently used as the main conceptual model for database and information system development. Due to its extensive usage a large number of extensions to this model were proposed in the 80’s and 90’s. Cardinality constraints [1, 3, 4, 8] are the most important generalisation of relational database constraints [7]. These proposals have been evaluated, integrated or explicitly discarded in an intensive research discussion. The semantic foundations proposed in [2, 5, 8] and the various generalisations and extensions of the entity-relationship model have led to the introduction of the higher-order or hierarchical entityrelationship model [8] which integrates most of the extensions and also supports conceptualisation of functionality, distribution [9], and interactivity [6] for information systems. Class diagrams of the UML standard are a special variant of extended entity-relationship models. The ER conferences (annually; since 1996: International Conference on Conceptual Modeling, http://www.conceptualmodeling.org/) are the main forum for conceptual models and modelling. SCIENTIFIC FUNDAMENTALS The extended entity-relationship model is mainly used as a language for conceptualisation of the structure of information systems applications. Conceptualisation of database or information systems aims to represent the logical and physical structure of an information system. It should contain all the information required by the user and required for the efficient behavior of the whole information system for all users. Conceptualisation may further target the specification of database application processes and the user interaction. Structure description are currently the main use of the extended ER model. An example of an EER diagram. The EER model uses a formal language for schema definition and diagrams for graphical representation of the
Page 1 and 2:
BPMN and Beyond Business process mo
Page 3 and 4:
[Tha00] B. Thalheim. Entity-relatio
Page 5 and 6:
can be defined elementwise, constru
Page 7 and 8:
Our target reader is either knowled
Page 9 and 10:
3 Framework for BPMN Execution Mode
Page 11 and 12:
is usually required to be an atomic
Page 13 and 14:
workflow designer to define in a si
Page 15 and 16:
AndJoinGateTransition(node) = Workf
Page 17 and 18:
that it does not depend only on the
Page 19 and 20:
elow, an instance of WorkflowTransi
Page 21 and 22:
as they arrive” [15, Sect.9.3.3 p
Page 23 and 24:
to whose boundary e is attached and
Page 25 and 26:
if active(targetAct(e)) then Consum
Page 27 and 28:
. . . with the assistance of a soft
Page 29 and 30:
The BPMN standard forsees also that
Page 31 and 32:
ComplMultInstExit has to keep track
Page 33 and 34:
and that “The performers determin
Page 35 and 36:
One project of practical interest w
Page 37 and 38:
OrSplitGateTransition(node) = let O
Page 39 and 40: 9.4 Activity Rules TaskTransition(t
Page 41 and 42: AdHocTransition(node) = [if Enabled
Page 43 and 44: ASM Modules Standard module concept
Page 45 and 46: 5. D. Batory and E. Börger. Modula
Page 47 and 48: On defining the behavior of OR-join
Page 49 and 50: Our definition is based upon a fram
Page 51 and 52: We advocate to separate the two dif
Page 53 and 54: In the token based approach to cont
Page 55 and 56: ConsumeAll({(t i , in i )) | 1 ≤
Page 57 and 58: one wants to impose as constraint o
Page 59 and 60: B1 D1 A1 Split 2 O B2 O Join 5 A2 S
Page 61 and 62: Token Sets To speak about the synch
Page 63 and 64: X Test 2 Assemble O Configure Test
Page 65 and 66: 19. J. Mendling, M. Moser, G. Neuma
Page 67 and 68: it is supposed to capture. In Sect.
Page 69 and 70: one may have in = out, so that the
Page 71 and 72: Separation Principle 5. The fifth e
Page 73 and 74: 5.2 Instantiating ComplexGateTransi
Page 75 and 76: the Z notation and offering the pos
Page 77 and 78: ASM Foundations of Database Managem
Page 89: ASM Foundations of Database Managem
Page 93 and 94: or cluster type. In this case they
Page 95 and 96: omitted until they have been define
Page 97 and 98: The EER schema can be used to defin
Page 99 and 100: Specialisation and Generalisation B
Page 101: abnormal, infrequent and untypical
show all

BPMN and Beyond Business process modelling notation, workflow ...

Create successful ePaper yourself

Delete template?

Save as template?