Models and architecture

now browsing by category

The main category of my posts, my experience and research as well.

 

UML model and stereotypes as icons

Someone will ask: why all this? The thing is that managing presentation graphics (model consistency, tracing, etc.) is practically impossible: any change requires interference with block diagrams and laborious reinsertion into the analysis report (I wrote about this in an article about CASE tools). Such graphics are not transferable between tools other than as uneditable bitmaps. However, if someone feels that block diagrams expressed in more ‘friendly’ symbols add value to the project, they can do so. The UML provides for this and many tools allow it (I used Visual-Paradigm).

Source: UML model and stereotypes as icons – Jarosław Żeliński IT-Consulting.

Information architecture, information system vs. information technology in the organisation

There are also simple and obvious conclusions:

  • there is no point in designing an “information system” without fully understanding (i.e. also documenting) the “information system, “
  • there is no point in placing the elements of the “information system” on “information system” models (e.g. There is no point in putting the “information system” elements on “information system” models (e.g. symbols representing software on BPMN models)
  • the relationships between the “information system” elements and the “information system” elements are described with the help of the traceability matrix
  • Developing the requirements for the “information system” is about identifying the “business needs” and developing the logic of operation and architecture of the “information system” on their basis (MBSE, MDD), and not on collecting mythical “user requirements”, who in fact have no idea about “information systems”, but know very well if and when they need help in the business processes being implemented  this is why methods based on designing an “information system” on the basis of interviews (workshops) with future users are doomed to failure from the outset (because even if something sensible is finally created, it will take a lot of trial-and-error work)
  • One thing we have known for years: one of the most damaging theses in IT is the one saying that a document is a report from a database.

Source: Architektura informacji, system informacyjny a informatyczny w organizacji – Jarosław Żeliński IT-Consulting

Diagrams in UML notation

UML diagrams and the way they are used, since the very beginning of this notation, have aroused emotions and waves of conflicting comments. The reason for this is the high level of abstraction of the analysis stage and modelling as a discipline, and the fairly widespread misunderstanding of the essence of this notation. This is compounded by the huge difference between what we call analysis and object-oriented design (OOAD) and object-oriented programming languages (OOP).UML notation is mistakenly treated by many people as just another set of symbols for creating illustrations. Most developers I know feel that these diagrams do nothing to help them, and they are generally right, because the quality and content of much of the documentation produced with UML, is poor, and such documentation is actually useless to the software vendor.

Source: Diagramy w notacji UML – Jarosław Żeliński IT-Consulting

Value-stream mapping i.e. the value stream a company creates when creating its product

The acronym VSM has also started to appear in software engineering for some time now, but it has an old pedigree of more than 30 years. Value-stream Mapping (VSM), known for 30 years, more recently also as material- and information-flow mapping. It is a method with its origins in Lean Management, used to analyse the current state and design the future state for the series of events that lead a product or service from order to delivery to the customer.

Source: Value-stream mapping czyli strumień wartości jaki wytwarza firma tworząc swój produkt – Jarosław Żeliński IT-Consulting

What are tests and who tests what

Testing is checking, and here we have (should have) a clear division between the checker and the checked. It is typical of the IT market to tell customers that they have no competence in analysis, testing, design, that all this will be done by the software supplier. Thus, the following are ordered from the same, single, software supplier: business analysis, requirements analysis, design, implementation, writing acceptance tests and testing. An entity like the Purchaser in essence just watches, and pays as much as the suppliers want (T&M projects are out of control). In effect, the checker and checked are the same entity. Does this make sense?

Source: Czym są testy oraz kto i co testuje – Jarosław Żeliński IT-Consulting

SysML – a few words about

In this place, I have been collecting some speaks about the SysML language. It is origin from UML (it is a UML profile). SysML is the main MBSE method we use for documenting mechatronics models.

Who needs Model Based Systems Engineering (MBSE) in 6 minutes
Systems Engineering Your MBSE Deployment by David Long
SysML ?AND? Its Role and Place in Systems Engineering with Zane Scott
https://youtu.be/xGDErNmqNLw
Introduction to Systems Modeling Language (SysML)
The Four Pillars of SysML 

Ontology-Oriented Data Management and Document Databases

This study presents a method for the storage of data organized in digital documents, which is proven in practice. The discussed method does not bear any disadvantages of the relational model used for data organization, such as the loss of data context and complications evoked by the lack of data redundancy. The method presented here can be used for data organization into documents (digital and paper) as classified aggregates and for data classification. The study also describes a new metamodel for the data structure which assumes that documents, being data structures, form compact aggregates, classified as objects, or event descriptions, thus always assigning them a specific and unambiguous context. Furthermore, the study presents a design method for documents as context aggregates that allows leveling the disadvantages of the relational model and ensures efficient information management. The work also contains practical examples of the application of the described method.

Digital Documents as Data Carriers and a Method of Data Management Guaranteeing the Unambiguity of the Recorded Information: Ontology-Oriented Data Management and Document Databases

Buy and read more…

Synthesis of MOF, MDA, PIM, MVC, and BCE Notations and Patterns

Exactly one year ago my first paper in US ? (see liflet)

Abstract

Publications, including academic handbooks, contain numerous inconsistencies in the descriptions of applications of architectural methods and patterns hidden under the abbreviations such as MOF, MDA, PIM, MVC, BCE. An efficient analysis and the following software design, particularly when we are speaking of projects realized in large teams, requires standardization of the production process and the applied patterns and frameworks. This study attempted to sort out the system of notations describing this process and used to describe architectural patterns. Analysis of key notations?MOF and MDA, patterns MVC and BCE?was carried out, and a consistent system combining them into a whole was created.Chapter Preview Top

Background

In this study, Object Management Group notation systems have been used. MOF (Meta Object Facility) specification describes three abstraction levels: M1, M2, M3 and level M0 that is real items (OMG MOF, 2016). M0 is a real system, M1 level is abstraction of the items of this system (its model). Level M2 comprises of relationships between classes of these objects (names of their sets) that is system metamodel. M3 level is a meta-metamodel describing the modeling method with the use of named elements with specified semantics and syntactic.

The analysis and design process is based on the MDA (Model Driven Architecture) specifications. This process has three phases understood as creation of subsequent models: CIM (Computation Independent Model), PIM (Platform Independent Model), PSM (Platform Specific Model) and code creation phase. The CIM model is documented with the use of BPMN (Business Process Model and Notation) (OMG BPMN, 2013) and SBVR notation (Semantic of Business Vocabulary and Rules) (OMG SBVR, 2017). These are, respectively: business process models and notation models and business rules. PIM and PSM models are documented with the use of UML notation (Unified Modeling Language) (OMG UML, 2017).

Between CIM and PIM models, determination of the list of application services (system reactions) occurs, whose realization mechanism is described by PIM model. The standard pattern used for modeling application architecture is MVC pattern. Component Model of this pattern is modeled with the use of the BCE architectural pattern.

Semiotics vs. UML

Semiotics, as a science dealing with symbols and their meanings, provides us with the tool enabling determination of relationships between an object (thing), its name (expression) and definition of notation represented by the name (or sign, meaning). These relationships are referred to as the semiotic triangle. Figure 1 represents this triangle on the left (OMG SBVR, 2017).

The UML notation (OMG UML, 2017) operates instance classifier and class notations. To the right, Figure 1 demonstrates an equivalent to semiotic triangle expressed with those terms.

The UML notation further operates the general structure notation, which is the content of each correct UML diagram. Structures may express a conceptual model (Namespace) or model (also metamodel) of system architecture (e.g. software) in the form of a chart (Architecture).

Synthesis of MOF, MDA, PIM, MVC, and BCE Notations and Patterns

Jaroslaw Zelinski (Independent Researcher)
Source Title: Applications and Approaches to Object-Oriented Software Design: Emerging Research and OpportunitiesCopyright: ? 2020 |Pages: 12DOI: 10.4018/978-1-7998-2142-7.ch003

Business continuity management – how to model it

Business Continuity Management (BCM) projects are really difficult . The main reason is the system complexity: many documents, many tasks, many processes, many associations between all of them. Each task connected to one or more business application. Each documents stored in different database. The applications are integrated. Everything works like one chain ? but one broken link can crash everything .

How we can managing risks? We can create Business Architecture model and expand this up to Enterprise Architecture, as a model for trace process, data, IT system and infrastructure.

(source: https://en.wikipedia.org/wiki/Enterprise_architecture_framework)

How we prepare Enterprise Architecture model? Simple version: prepare business model :

Transform this to use case model (application services) :

Build matrix for trace mapping control :

Trace (map) use case to software components :

We have completed model, we can do impact analysis, e.g. what happens and where, when the Ruter go down:

Sometimes we ask: what does the possibility of carrying out the Package Goods task depend on?

How can we do this and what tools do we need? Welcome in my courses, hire me …

References

Laender, A. H. F., Liddle, S. W., & Storey, V. C. (Eds.). (2000). Conceptual modeling - ER 2000: 19th International Conference on Conceptual Modeling, Salt Lake City, Utah, USA, October 2000. Springer.
Hause, M. (2006). The SysML modelling language. Fifteenth European Systems Engineering Conference, 9, 1–12.
Pollack, S. L., Hicks, H. T., & Harrison, W. J. (1975). Tablice decyzyjne. PWN.
Zimmermann, D. A., & Pautasso, D. C. (2020). On the Evolvability Assurance of Microservices: Metrics, Scenarios, and Patterns. 347.
Marian Przełęcki. (1993). Pojęcie prawdy w językach nauk empirycznych. Filozofia Nauki, 1(2–3), 379–387.
Russell, B. (2007). An inquiry into meaning and truth. Spokesman.
Russell, B. (2011). Badania dotyczące znaczenia i prawdy. Wydawnictwo WAM.
Biłat, A. (2018). Metaontologia: o naturze pojęć i teorii ontologicznych (Copernicus Center Press, Ed.). Copernicus Center Press.
Marek Łabuzek. (2003). Wykorzystanie metamodelowania do specyfikacji ontologii znaczenia opisów rzeczywistości. e-Informatica Software Engineering Journal. https://www.e-informatyka.pl/index.php/pimio/inzynieria-wymagan/wykorzystanie-metamodelowania-do-specyfikacji-ontologii-znaczenia-opisow-rzeczywistosci/
Lamentowicz, W., & Wydawnictwo Uniwersytetu Łódzkiego. (2017). Status prawny i dynamika porządku prawnego. Wydawnictwo Uniwersytetu Łódzkiego.
Madkour, M., Butler, K., Mercer, E., Bahrami, A., & Tao, C. (2020). Semantic based model of Conceptual Work Products for formal verification of complex interactive systems. ArXiv Preprint ArXiv:2008.01623, 11.
Nill, C., & Sikka, V. (n.d.). Modeling Software Applications and User Interfaces Using Metaphorical Entities. 4.
Larson, H. (2020). Agent-Based Modeling of Locust Foraging and Social Behavior. 47.
Floyd, C., & Ukena, S. (2005). On Designing Ontologies for Knowledge Sharing in Communities of Practice. CAiSE Workshops (2), 559–569.
uml-diagrams.org. (n.d.). Examples of UML composite structure diagrams - Bank ATM, Apache Tomcat 7 web server, Observer design pattern. [UML Diagrams]. UML Composite Structure Diagram Examples. Retrieved August 8, 2020, from https://www.uml-diagrams.org/composite-structure-examples.html
Vanthienen, J. A. N., & Dries, E. (1992). Developments in decision tables: Evolution, applications and a proposed standard. DTEW Research Report 9227.
King, P. J. (1967). Decision tables. The Computer Journal, 10(2), 135–142.
Vanthienen, J., & Wets, G. (1992). Mapping Decision Tables to Expert System Shells: An Implementation in AionDS. Onderzoeksrapport 9228.
Vasilecas, O., & Smaizys, A. (2007). Business Rule Based Configuration Management and Software System Implementation Using Decision Tables. Local Proceedings of ADBIS, 2007, 27–37.
Anupama Yk. (2015). Decision Table Based Testing. International Journal on Recent and Innovation Trends in Computing and Communication, 3(3), 1298–1301. https://doi.org/10.17762/ijritcc2321-8169.150388
Ustawa z dnia 23 kwietnia 1964 r. - Kodeks cywilny. (1964). http://prawo.sejm.gov.pl/isap.nsf/DocDetails.xsp?id=WDU19640160093
Ustawa z dnia 16 kwietnia 1993 r. o zwalczaniu nieuczciwej konkurencji. (1993). http://prawo.sejm.gov.pl/isap.nsf/DocDetails.xsp?id=WDU19930470211
Ustawa z dnia 4 lutego 1994 r. o prawie autorskim i prawach pokrewnych. (1994). http://prawo.sejm.gov.pl/isap.nsf/DocDetails.xsp?id=WDU19940240083
Unmesh Joshi. (2020, August 4). Patterns of Distributed Systems [Martinfowler.com]. Martinfowler.Com. https://martinfowler.com/articles/patterns-of-distributed-systems/
Mamatsashvili, G.-G., Ponichtera, K., Małkiński, M., Ganzha, M., & Paprzycki, M. (2020). Semantic-Based System for Exercise Programming and Dietary Advice. In L. C. Jain, M. Virvou, V. Piuri, & V. E. Balas (Eds.), Advances in Bioinformatics, Multimedia, and Electronics Circuits and Signals (Vol. 1064, pp. 105–120). Springer Singapore. https://doi.org/10.1007/978-981-15-0339-9_10
Snook, C., & Butler, M. (n.d.). UML-B AND EVENT-B: AN INTEGRATION OF LANGUAGES AND TOOLS. 6.
Butler, M. (2009). Decomposition Structures for Event-B. In M. Leuschel & H. Wehrheim (Eds.), Integrated Formal Methods (Vol. 5423, pp. 20–38). Springer Berlin Heidelberg. https://doi.org/10.1007/978-3-642-00255-7_2
Abrial, J.-R., Butler, M., Hallerstede, S., Hoang, T. S., Mehta, F., & Voisin, L. (2010). Rodin: an open toolset for modelling and reasoning in Event-B. International Journal on Software Tools for Technology Transfer, 12(6), 447–466. https://doi.org/10.1007/s10009-010-0145-y
Calvaresi, D., Schumacher, M., & Calbimonte, J.-P. (2020). Agent-based Modeling for Ontology-driven Analysis of Patient Trajectories. Journal of Medical Systems, 44(9), 158. https://doi.org/10.1007/s10916-020-01620-8
Anne Francine Martins, Costa Affonso, R., Tamayo, S., Lamouri, S., & Baldy Ngayo, C. (2015). Relationships between national culture and Lean Management: A literature Review. 2015 International Conference on Industrial Engineering and Systems Management (IESM), 352–361. https://doi.org/10.1109/IESM.2015.7380183
Sokal, A., & Bricmont, J. (2004). Modne bzdury. O Nadużywaniu Pojęć z Zakresu Nauk Ścis\lych Przez Postmodernistycznych Intelektualistów.
Xu, S., Chen, X., Xie, J., Rahman, S., Wang, J., Hui, H., & Chen, T. (2020). Agent-based modeling and simulation of the electricity market with residential demand response. CSEE Journal of Power and Energy Systems, 1–12. https://doi.org/10.17775/CSEEJPES.2019.01750
Leech, G. (1983). Semantics: the study of meaning (Second edition). Harmondsworth : Penguin Books.
Enterprise Architecture Training in Aberdeen. (n.d.). Retrieved August 2, 2020, from https://www.nobleprog.co.uk/enterprise-architecture/training/aberdeen
Graics, B., Molnár, V., Vörös, A., Majzik, I., & Varró, D. (2020). Mixed-semantics composition of statecharts for the component-based design of reactive systems. Software and Systems Modeling. https://doi.org/10.1007/s10270-020-00806-5
Veizaga, A., Alferez, M., Torre, D., Sabetzadeh, M., Briand, L., & Pitskhelauri, E. (2020). Leveraging Natural-language Requirements for Deriving  Better Acceptance Criteria from Models. 11.
Sanchez Cuadrado, J., Burgueno, L., Wimmer, M., & Vallecillo, A. (2020). Efficient execution of ATL model transformations using static analysis and parallelism. IEEE Transactions on Software Engineering, 1–1. https://doi.org/10.1109/TSE.2020.3011388
Zhang, X., Dunn, S., Coates, G., & Hall, J. (2020). Emergency Evacuation from a Multi- floor Building using Agent-based Modeling. 12.
Bodine, E. N., Panoff, R. M., Voit, E. O., & Weisstein, A. E. (2020). Agent-Based Modeling and Simulation in Mathematics and Biology Education. Bulletin of Mathematical Biology, 82(8), 101. https://doi.org/10.1007/s11538-020-00778-z
Craver, C. F. (2007). Explaining the brain: mechanisms and the mosaic unity of neuroscience. Clarendon Press.
Marston, S., Li, Z., Bandyopadhyay, S., Zhang, J., & Ghalsasi, A. (2011). Cloud computing — The business perspective. Decision Support Systems, 51(1), 176–189. https://doi.org/10.1016/j.dss.2010.12.006
Simpson, T. W., Poplinski, J. D., Koch, P. N., & Allen, J. K. (2001). Metamodels for computer-based engineering design: survey and recommendations. Engineering with Computers, 17(2), 129–150.
Mesjasz, M. M., Ganzha, M., & Paprzycki, M. (2020). Modeling cyber-physical systems – a GliderAgent 3.0 perspective. Journal of Intelligent Information Systems. https://doi.org/10.1007/s10844-019-00588-3
Kogut, P., Cranefield, S., Hart, L., Dutra, M., Baclawski, K., Kokar, M., & Smith, J. (2002). UML for ontology development. The Knowledge Engineering Review, 17(1), 61–64.
James Human, & Azam M. Madni. (2014). Integrated Agent-based modeling and optimization in complex systems analysis | Elsevier Enhanced Reader. Procedia Computer Science, 28, 818–827. https://doi.org/10.1016/j.procs.2014.03.097
Gruber, T. R. (1993). A translation approach to portable ontology specifications. Knowledge Acquisition, 5(2), 199–220.
Götz, S., Fehn, A., Rohde, F., & Kühn, T. (2020). Model-driven Software Engineering for Construction Engineering: Quo Vadis? The Journal of Object Technology, 19(2), 2:1. https://doi.org/10.5381/jot.2020.19.2.a2
Gašević, D., Djurić, D., Devedzic, V., & Gašević, D. (2009). Model driven engineering and ontology development (2nd ed). Springer.
Cushing, R., Putra, G. H. H., Koulouzis, S., Belloum, A., Bubak, M., & de Laat, C. (2013). Distributed Computing on an Ensemble of Browsers. IEEE Internet Computing, 17(5), 54–61. https://doi.org/10.1109/MIC.2013.3
BPMDS (Workshop), Reinhartz-Berger, I., Zdravkovic, J., Gulden, J., Schmidt, R., EMMSAD (Workshop), & CAiSE (Conference). (2019). Enterprise, business-process and information systems modeling: 20th International Conference, BPMDS 2019, 24th International Conference, EMMSAD 2019, held at CAiSE 2019, Rome, Italy, June 3-4, 2019 : proceedings. https://public.ebookcentral.proquest.com/choice/publicfullrecord.aspx?p=5926895

Types instead of inheritance

Many time we can see requirement written as a “class diagram for project”. What “class diagram” mean? We can use UML class diagram for: architecture model, notions model, sometimes other. Which type of model do you need? Class diagram is a tool. When we say model, we have to provided context: model of what?

We use inheritance in models of notions (for building taxonomies), never in architecture.. In architecture models we use types. In 2015 OMG published UML v.2.5. Inheritance was removed from UML . Why? Welcome in my courses?

References

Laender, A. H. F., Liddle, S. W., & Storey, V. C. (Eds.). (2000). Conceptual modeling - ER 2000: 19th International Conference on Conceptual Modeling, Salt Lake City, Utah, USA, October 2000. Springer.
Hause, M. (2006). The SysML modelling language. Fifteenth European Systems Engineering Conference, 9, 1–12.
Pollack, S. L., Hicks, H. T., & Harrison, W. J. (1975). Tablice decyzyjne. PWN.
Zimmermann, D. A., & Pautasso, D. C. (2020). On the Evolvability Assurance of Microservices: Metrics, Scenarios, and Patterns. 347.
Marian Przełęcki. (1993). Pojęcie prawdy w językach nauk empirycznych. Filozofia Nauki, 1(2–3), 379–387.
Russell, B. (2007). An inquiry into meaning and truth. Spokesman.
Russell, B. (2011). Badania dotyczące znaczenia i prawdy. Wydawnictwo WAM.
Biłat, A. (2018). Metaontologia: o naturze pojęć i teorii ontologicznych (Copernicus Center Press, Ed.). Copernicus Center Press.
Marek Łabuzek. (2003). Wykorzystanie metamodelowania do specyfikacji ontologii znaczenia opisów rzeczywistości. e-Informatica Software Engineering Journal. https://www.e-informatyka.pl/index.php/pimio/inzynieria-wymagan/wykorzystanie-metamodelowania-do-specyfikacji-ontologii-znaczenia-opisow-rzeczywistosci/
Lamentowicz, W., & Wydawnictwo Uniwersytetu Łódzkiego. (2017). Status prawny i dynamika porządku prawnego. Wydawnictwo Uniwersytetu Łódzkiego.
Madkour, M., Butler, K., Mercer, E., Bahrami, A., & Tao, C. (2020). Semantic based model of Conceptual Work Products for formal verification of complex interactive systems. ArXiv Preprint ArXiv:2008.01623, 11.
Nill, C., & Sikka, V. (n.d.). Modeling Software Applications and User Interfaces Using Metaphorical Entities. 4.
Larson, H. (2020). Agent-Based Modeling of Locust Foraging and Social Behavior. 47.
Floyd, C., & Ukena, S. (2005). On Designing Ontologies for Knowledge Sharing in Communities of Practice. CAiSE Workshops (2), 559–569.
uml-diagrams.org. (n.d.). Examples of UML composite structure diagrams - Bank ATM, Apache Tomcat 7 web server, Observer design pattern. [UML Diagrams]. UML Composite Structure Diagram Examples. Retrieved August 8, 2020, from https://www.uml-diagrams.org/composite-structure-examples.html
Vanthienen, J. A. N., & Dries, E. (1992). Developments in decision tables: Evolution, applications and a proposed standard. DTEW Research Report 9227.
King, P. J. (1967). Decision tables. The Computer Journal, 10(2), 135–142.
Vanthienen, J., & Wets, G. (1992). Mapping Decision Tables to Expert System Shells: An Implementation in AionDS. Onderzoeksrapport 9228.
Vasilecas, O., & Smaizys, A. (2007). Business Rule Based Configuration Management and Software System Implementation Using Decision Tables. Local Proceedings of ADBIS, 2007, 27–37.
Anupama Yk. (2015). Decision Table Based Testing. International Journal on Recent and Innovation Trends in Computing and Communication, 3(3), 1298–1301. https://doi.org/10.17762/ijritcc2321-8169.150388
Ustawa z dnia 23 kwietnia 1964 r. - Kodeks cywilny. (1964). http://prawo.sejm.gov.pl/isap.nsf/DocDetails.xsp?id=WDU19640160093
Ustawa z dnia 16 kwietnia 1993 r. o zwalczaniu nieuczciwej konkurencji. (1993). http://prawo.sejm.gov.pl/isap.nsf/DocDetails.xsp?id=WDU19930470211
Ustawa z dnia 4 lutego 1994 r. o prawie autorskim i prawach pokrewnych. (1994). http://prawo.sejm.gov.pl/isap.nsf/DocDetails.xsp?id=WDU19940240083
Unmesh Joshi. (2020, August 4). Patterns of Distributed Systems [Martinfowler.com]. Martinfowler.Com. https://martinfowler.com/articles/patterns-of-distributed-systems/
Mamatsashvili, G.-G., Ponichtera, K., Małkiński, M., Ganzha, M., & Paprzycki, M. (2020). Semantic-Based System for Exercise Programming and Dietary Advice. In L. C. Jain, M. Virvou, V. Piuri, & V. E. Balas (Eds.), Advances in Bioinformatics, Multimedia, and Electronics Circuits and Signals (Vol. 1064, pp. 105–120). Springer Singapore. https://doi.org/10.1007/978-981-15-0339-9_10
Snook, C., & Butler, M. (n.d.). UML-B AND EVENT-B: AN INTEGRATION OF LANGUAGES AND TOOLS. 6.
Butler, M. (2009). Decomposition Structures for Event-B. In M. Leuschel & H. Wehrheim (Eds.), Integrated Formal Methods (Vol. 5423, pp. 20–38). Springer Berlin Heidelberg. https://doi.org/10.1007/978-3-642-00255-7_2
Abrial, J.-R., Butler, M., Hallerstede, S., Hoang, T. S., Mehta, F., & Voisin, L. (2010). Rodin: an open toolset for modelling and reasoning in Event-B. International Journal on Software Tools for Technology Transfer, 12(6), 447–466. https://doi.org/10.1007/s10009-010-0145-y
Calvaresi, D., Schumacher, M., & Calbimonte, J.-P. (2020). Agent-based Modeling for Ontology-driven Analysis of Patient Trajectories. Journal of Medical Systems, 44(9), 158. https://doi.org/10.1007/s10916-020-01620-8
Anne Francine Martins, Costa Affonso, R., Tamayo, S., Lamouri, S., & Baldy Ngayo, C. (2015). Relationships between national culture and Lean Management: A literature Review. 2015 International Conference on Industrial Engineering and Systems Management (IESM), 352–361. https://doi.org/10.1109/IESM.2015.7380183
Sokal, A., & Bricmont, J. (2004). Modne bzdury. O Nadużywaniu Pojęć z Zakresu Nauk Ścis\lych Przez Postmodernistycznych Intelektualistów.
Xu, S., Chen, X., Xie, J., Rahman, S., Wang, J., Hui, H., & Chen, T. (2020). Agent-based modeling and simulation of the electricity market with residential demand response. CSEE Journal of Power and Energy Systems, 1–12. https://doi.org/10.17775/CSEEJPES.2019.01750
Leech, G. (1983). Semantics: the study of meaning (Second edition). Harmondsworth : Penguin Books.
Enterprise Architecture Training in Aberdeen. (n.d.). Retrieved August 2, 2020, from https://www.nobleprog.co.uk/enterprise-architecture/training/aberdeen
Graics, B., Molnár, V., Vörös, A., Majzik, I., & Varró, D. (2020). Mixed-semantics composition of statecharts for the component-based design of reactive systems. Software and Systems Modeling. https://doi.org/10.1007/s10270-020-00806-5
Veizaga, A., Alferez, M., Torre, D., Sabetzadeh, M., Briand, L., & Pitskhelauri, E. (2020). Leveraging Natural-language Requirements for Deriving  Better Acceptance Criteria from Models. 11.
Sanchez Cuadrado, J., Burgueno, L., Wimmer, M., & Vallecillo, A. (2020). Efficient execution of ATL model transformations using static analysis and parallelism. IEEE Transactions on Software Engineering, 1–1. https://doi.org/10.1109/TSE.2020.3011388
Zhang, X., Dunn, S., Coates, G., & Hall, J. (2020). Emergency Evacuation from a Multi- floor Building using Agent-based Modeling. 12.
Bodine, E. N., Panoff, R. M., Voit, E. O., & Weisstein, A. E. (2020). Agent-Based Modeling and Simulation in Mathematics and Biology Education. Bulletin of Mathematical Biology, 82(8), 101. https://doi.org/10.1007/s11538-020-00778-z
Craver, C. F. (2007). Explaining the brain: mechanisms and the mosaic unity of neuroscience. Clarendon Press.
Marston, S., Li, Z., Bandyopadhyay, S., Zhang, J., & Ghalsasi, A. (2011). Cloud computing — The business perspective. Decision Support Systems, 51(1), 176–189. https://doi.org/10.1016/j.dss.2010.12.006
Simpson, T. W., Poplinski, J. D., Koch, P. N., & Allen, J. K. (2001). Metamodels for computer-based engineering design: survey and recommendations. Engineering with Computers, 17(2), 129–150.
Mesjasz, M. M., Ganzha, M., & Paprzycki, M. (2020). Modeling cyber-physical systems – a GliderAgent 3.0 perspective. Journal of Intelligent Information Systems. https://doi.org/10.1007/s10844-019-00588-3
Kogut, P., Cranefield, S., Hart, L., Dutra, M., Baclawski, K., Kokar, M., & Smith, J. (2002). UML for ontology development. The Knowledge Engineering Review, 17(1), 61–64.
James Human, & Azam M. Madni. (2014). Integrated Agent-based modeling and optimization in complex systems analysis | Elsevier Enhanced Reader. Procedia Computer Science, 28, 818–827. https://doi.org/10.1016/j.procs.2014.03.097
Gruber, T. R. (1993). A translation approach to portable ontology specifications. Knowledge Acquisition, 5(2), 199–220.
Götz, S., Fehn, A., Rohde, F., & Kühn, T. (2020). Model-driven Software Engineering for Construction Engineering: Quo Vadis? The Journal of Object Technology, 19(2), 2:1. https://doi.org/10.5381/jot.2020.19.2.a2
Gašević, D., Djurić, D., Devedzic, V., & Gašević, D. (2009). Model driven engineering and ontology development (2nd ed). Springer.
Cushing, R., Putra, G. H. H., Koulouzis, S., Belloum, A., Bubak, M., & de Laat, C. (2013). Distributed Computing on an Ensemble of Browsers. IEEE Internet Computing, 17(5), 54–61. https://doi.org/10.1109/MIC.2013.3
BPMDS (Workshop), Reinhartz-Berger, I., Zdravkovic, J., Gulden, J., Schmidt, R., EMMSAD (Workshop), & CAiSE (Conference). (2019). Enterprise, business-process and information systems modeling: 20th International Conference, BPMDS 2019, 24th International Conference, EMMSAD 2019, held at CAiSE 2019, Rome, Italy, June 3-4, 2019 : proceedings. https://public.ebookcentral.proquest.com/choice/publicfullrecord.aspx?p=5926895