//Artefact:SoftwareBundle/com/sphenon/products/EMOS (5.1) - Working/Architecture - Engine Architecture
Architecture of the EM/OS Engine
Roughly speaking, EM/OS consists of two augmenting subsystems, which can be used seperated as well as combined:
Purpose of the APS is the transformation of the models into a form of code, which allows to instantly operate the respective business solution. This includes, among other things, the automatic creation of an amount of optimised program code.
Purpose of the AOS is to run the solution, typically based on material provided by the APS. This includes, among other things, the provision of a variety of infrastructure services, as well as the aggregation of the solution code according to construction plans and adopted to the environment in which the solution runs.
The complete solution, i.e. the AOS in conjunction with the prepared solution code, is called EM/OS Runtime.
Abstraction Levels and Modelling Jobs
While Customers or Business Analysts usually operate with high level modelling constructs, which are sufficient to describe the desired business properties of the solution (Canvases, Definitions, Classes, Processes, possibly Stereotypes), the job of the EM/OS Solution Architect requires more detailed as well as more technical knowledge.
To fine tune the systems to precisely meet the expectations of the customer, the EM/OS Solution Architect specifies business details and technical aspects (State Machines, Properties, Technical Models, Construction Plans, Target Language Code).
Like many sophisticated modern software solutions, the inner workings of EM/OS are complex. A long list of measurements has been taken to manage that complexity, effectively. Yet, to find the optimal solution for a requirement, which might consist of just some proper setting or a few modifications in the model, one needs a good general idea of the interdependencies in the EM/OS system.
The purpose of this guide is to provide this necessary information, organised around recurring requirements topics.