Abstract
This chapter concludes the introductory part with a general overview of the approach by means of a small library example. It should give the reader scome insight in all the techniques and principles that are present in MERODE, without going too much in detail. Part II of this book will then present each technique separately in a more elaborated and formal way. The chapter starts with a global overview of the modelling process and then reviews the models from inner layer to outer layer: first domain modelling, then information system service identification and finally business process modelling.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsNotes
- 1.
A very earlier version of the topics handled in Chapters 3–6 has been published as the journal paper ‘Existence Dependency: The Key to Semantic Integrity Between Structural and Behavioural Aspects of Object Types’ by Snoeck M. and Dedene G., which appeared in IEEE Transactions on Software Engineering, Vol. 24, No. 4, pp. 233-251, April 1998 © 1998 IEEE. The material from this paper has been integrated in this book with the kind permission of IEEE.
- 2.
The state of an object should not be confused with its ‘life cycle state’. The state refers to the more general concept of visible state, that is, the whole of values of the object’s attributes, while the ‘life cycle state’ explicitly refers to states as they appear in state transition diagrams such as finite-state machines and Harel Statecharts.
- 3.
To distinguish between event names and method names, in JMermaid, event names are by default prefixed with EV_ and method names with ME_.
- 4.
The R in CRUD stands for read. As will be explained in Chap. 5, we will not model the reading of objects at domain modelling level.
- 5.
The notation is further explained in Chap. 4.
- 6.
See Chap. 5 for a detailed definition of ‘owner participation’ and ‘owner class’.
- 7.
See Chap. 5 for a more detailed explanation.
- 8.
This naming convention applies to the development of new software. For existing software, the cell can be used to link an event type to an existing method of a software component (see Sect. 12.2).
References
Baeten JCM (1986) Procesalgebra. Kluwer programmatuurkunde, Deventer
Hoare CAR (1985) Communicating sequential processes, Prentice-Hall International, Series in Computer Science
Milner R (1982) A calculus of communicating systems. Springer, New York
OMG, The Unified Modelling Language (UML), version 2.5 FTF—beta 1, Retrieved from Object Management Group: http://www.omg.org/uml
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2014 Springer International Publishing Switzerland
About this chapter
Cite this chapter
Snoeck, M. (2014). Overview of MERODE. In: Enterprise Information Systems Engineering. The Enterprise Engineering Series. Springer, Cham. https://doi.org/10.1007/978-3-319-10145-3_3
Download citation
DOI: https://doi.org/10.1007/978-3-319-10145-3_3
Published:
Publisher Name: Springer, Cham
Print ISBN: 978-3-319-10144-6
Online ISBN: 978-3-319-10145-3
eBook Packages: Computer ScienceComputer Science (R0)