scientific-modelling/preface.md: added constructional phases for mode…

…lling

embedded-system-design/scientific-modelling/preface.md

@@ -1,4 +1,6 @@
 # Prologue
+> Created by [Pavl_G](https://github.com/Scrappers-glitch)
+
 _Scientific Modelling_ is a robust rocket-science way of miniaturizing real systems in order to examine, predict, and/or enhance a specific phenomena, and based on the underlying theory, one can derive the relations and the way the internal components interact together in a scientific space. 
 
 _Scientific Modelling_ is utilized in almost all human sciences including biomedical, engineering, and research fields.
@@ -16,13 +18,17 @@ Scientific Models: are miniaturized structures that idealize specific phenomenol
 
 ## Types of models:
 
+> House of scientific models:
 
+| The House of models | Description |
+|-----------|----------|
+| ![](https://electrostat-lab.github.io/Electrostatic-Sandbox/embedded-system-design/scientific-modelling/resources/models-house.jpg) | ![](https://electrostat-lab.github.io/Electrostatic-Sandbox/embedded-system-design/scientific-modelling/resources/models-house-description.jpg) | 
 
 This illustrative diagram depicts a full image to the different types of scientific modelling together with their specific level-of-details (LoD), and the variable indifference in the essence of two highly applicable sciences nowadays, Internal Medicine V.S. Computational Systems (disclaimer: it's not really a Versus relationship, it's just for applying some humor to the topic!). The diagram of concern is represented as a house of models to specify the essentiality of abstraction levels (aka. LoD or level of details), in which the most accurate models lie in the basement; as where the infrastructure resigns, the strong building parts are aligned. 
 
 The house of models is subdivided into 2 floors excluding the basement, but including the ceiling. The design typically starts with the "Conceptual Models" at the basement, those are very system-abstract in nature, and provide high level of details for the target system, a great example of these are the "Mathematical and Physical Models". On the second floor resides the "Iconic Models" and the "Analogous Models"; those concretize the conceptual models into further objectified structural and behavioral matters that map the components and relations of a given system in a more specialized way, very oriented to the system in-study or in-commission. On the last floor, aka. the ceiling, resides the most system-oriented layer of modelling, the "Symblic Models" with its both types, the "Phenomeno-logical Model" and the "Statistical or Stochastic Models", both of which having common interests prevailing the study of phenomena of a system, aka. the output of a group of theories. In conclusion, to model the phenomena of a system, it's better to start with a symbolic model and move all the way down to provide LoD as it essentiates, while to model the interaction between two or more components or a component and its internalized states, it's better to start with the iconic model and move up and down as it essentiates. On the other side of the spectrum, the conceptual models are deemed to the very specific needs of studying systems with a higher level of details to better predict outcomes of the target systems. However, of notice, the stochastic models and the mathematical models can be integrated in a one conceptual model!
 
-The spectrum of modelling is a very heavy topic, and cannot be covered easily in one post, but it's really handy to put these stuff in mind in parallelism to what we study in everyday life, it differs too much if your approach is too scientific as compared to that bad faulty ad-hoc maneuvers.
+The spectrum of modelling is a very heavy topic, and cannot be covered easily in one documentation manual, but it's really handy to put these stuff in mind in parallelism to what we study in everyday life, it differs too much if your approach is too scientific as compared to that bad faulty ad-hoc maneuvers.
 
 I've a lot of energized determination to show you how scientific modelling could be used in software engineering specializing in system engineering and design; as it uncovers the unrevealed components of systems, and maps the relations among them, and at the same time, utilizing the same models in describing medical states, diseases, approach, management, and monitoring.
 
@@ -32,6 +38,36 @@ The Medical Analyzer Model on the left side: provides a layered approach to inte
 
 > Notice, that sometimes some information is irrelevant to a specific system, and so this necessitates to omit specific layers of modelling while manifesting others, this is known widely in modelling as the "selectivity of system parts" including the phenomena and the underlying theories we are trying to model.
 
+## Construction of Models
+
+There are several maneuvers for bringing a scientific model into life for a specific system, for instance, the System Entity Structure Framework (SES) aka. the Entity-Component System in software design, and the Tricotyledon System Design (T3D) introduced by Wymore which utilizies the set theory and ports automata to the design of the system behavior. One way is introduced here is the System-Entity-Structure Framework (SES) according to _Pawletta T, Durak U, Schmidt A_ together with some insights from _Wymore's T3D_ (Fig-1.7).
+
+| Constructional Usage | Description |
+|-----------|----------|
+| ![](https://electrostat-lab.github.io/Electrostatic-Sandbox/embedded-system-design/scientific-modelling/resources/constructional-use.jpg) | ![](https://electrostat-lab.github.io/Electrostatic-Sandbox/embedded-system-design/scientific-modelling/resources/constructional-use-2.jpg) | 
+
+| System-Entity Structure Framework (SES) |
+|---------------------|
+| ![](https://electrostat-lab.github.io/Electrostatic-Sandbox/embedded-system-design/scientific-modelling/resources/system-entity-framework.jpg) |
+
+**Practical Steps in building a model (iconic, conceptual, and symbolic parts) and validating it:**
+1) Examining the phenomena of interest.
+2) Finding or deriving the theories underlying this specific phenomena.
+3) Recognition of the system infrastructure in which this phenomena occurs.
+4) Decomposing the system of interest into primitive components (Set Theory Applied).
+5) Finding and deriving relations between the decomposed components using the underlying theory.
+6) Finding and deriving conditional relations between components (Propositional Calculus Applied).
+7) Grouping the decomposed components into modules (modularization, Group Theory Applied). 
+8) Apply Step.05 and Step.06 on modules derived from Step.07.
+9) Surpass modules into Entities.
+10) Specialize entities objects into simulation environments.
+11) Data collection and processing from the simulation environments.
+12) Feed the data back into a comparing interface.
+13) Validate the model based on Steps.10-11-12 with Steps.04-05-06.
+14) Re-iterate and improve the model and the understanding of the underlying theory.
+
+> Notice, how (Fig-1.7) references the steps in this text, and those steps are coincident with (Fig-3) which conveys the structure and the relation between the various components in scientific modelling and not the process steps per se. 
+
 ### => References:
-- [Scientific Models Red Atoms, White Lies and Black Boxes in a Yellow Book Springer]()
-- [Body of Knowledge for Modeling and Simulation: A Handbook by the Society for Modeling and Simulation International]()
+- [Scientific Models Red Atoms, White Lies and Black Boxes in a Yellow Book Springer](https://link.springer.com/book/10.1007/978-3-319-27081-4)
+- [Body of Knowledge for Modeling and Simulation: A Handbook by the Society for Modeling and Simulation International](https://link.springer.com/book/10.1007/978-3-031-11085-6)